Slashdot Mirror

For example, is it possible or beneficial for both the baby and placenta to be outside the mother for a while?

I don't know whether it's beneficial for the baby, but it's certainly detrimental at least to some fathers. I sentence you to look at three placentas for making such silly suggestions!

Explicit memory allocation/deallocation relies on the programmer to know the last places in the program where the allocated memory is ever used, so that they can be sure to free the memory at or after those points. In large object oriented systems where you're not supposed to need to know how this object that you've got does its business, having to know that it has allocated itself some memory breaks the wall.

more detail if you care

http://www.cs.bilkent.edu.tr/~david/david/educphilosophy.htm

http://hermitslantern.ning.com/forum/topic/show?id=1062477%3ATopic%3A2741

There was a book on this topic, but I forgot what it is called.

If you think I need a teacher, go to hell.

The information is all I need.

I am the teacher.

I teach myself.

I've been doing this my whole life.

I'm satisfied. I take FULL responsibility for
my learning.

I give NO power to anyone else for my education.

Oh, your going to teach me? Do you see this? ..|.

I don't need you. I will buy my own books, and study on my own.

Screw you.

The ONLY real reason people want a diploma,
or certificate is for "recognition", and official
"government" supported education.

That and they are too dumb to teach themselves.

Or they have no motivation. Or they see no

point in learning anything.

Sure you can- get rid of the corporate veil. For every $100,000 a company is fined, the CEO and board of directors must stay 1 month in jail, with no possibility of parole. Watch corporations follow the law instantly.

Even better, void the Corporate Charter. Corporate charters were originally granted only if the corporation served the public good. However as corporations gained power they were able to have the public good requirements removed.

Yes, but PNG files are only of use for flat color images with a VERY limited range of colors (as with GIF). They are totally useless for pretty much everything else - eg photographs, game screen shots, etc.

You can get PNG-24 which allows 24 bit color, but it's basically an uncompressed bitmap and therefore useless for the web or any large images as the files are all way too big.

PNG supports up to 16 bits per channel RGBA color, losslessly compressed, complete with chromacity and gamma values in seperate chunks.

PNGs made from high-resolution image data might still be too large for web use, but they're still much smaller than an equivilent TIFF, contain checksumming and are streamable (unlike TIFF).

In theory, Ethernet on coax should be stable under heavy load. But in the late 1980s and early 1990s, it wasn't, due to defective design of some widely used interface chips. Here's the actual story. See this note by Wes Irish at Xerox PARC

The worst device was the SEEQ 8003 chip, found in some Cisco and SGI devices. Due to an error in the design of its hardware state machine, it would turn on its transmitter for a few nanoseconds in the middle of an interframe gap. This noise caused other machines on the LAN to restart their interframe gap timers and ignore the next packet, if it followed closely enough. This happened even if the SEEQ chip was neither the sender or the receiver of the packets involved. So as soon as you plugged one of these things into a LAN, throughput went down, even if it wasn't doing anything. A network analyzer wouldn't even see the false collision; this was at too low a level.

This was tough to find. Wes Irish worked on the problem by arranging for both ends of Xerox PARC's main coax LAN to terminate in one office. Then he hooked up a LeCroy digital oscilloscope to both ends. Then he tapped into a machine with an Ethernet controller to bring out a signal when the problem was detected and trigger the oscilloscope. Then, when the problem occured, he had a copy of the entire packet as an analog waveform stored in the scope. This could then be printed with a thermal printer and gone over by hand.

Because he had the same signal from both ends of the wire, the wierd SEEQ interference mentioned above appeared time-shifted due to speed of light lag, making it clear that the interference was from a different node than the one that was supposed to be sending. You could measure the time shift and figure out from where on the cable the noise was being inserted. Which he did.

It took some convincing to get manufacturers to admit there was a problem. It helped that Wes was at Xerox PARC, where Ethernet was born. I went up there to see his work, and once I saw the waveforms, I was convinced. There was much faxing of waveform printouts for a few months, and some vendors were rather unhappy, but the problem got fixed.

So that's why.

Somebody has to point out that the original Yahoo is a total failure, since a manually-maintained hierarchical web index just wasn't a good idea. Except that Yahoo managed to establish itself as a popular web "portal" before that fact became painfully obvious. So Filo and Yang are failures in the sense that their original project was a bad idea, but probably don't care, since they're both now multi-millionaires. Depressing how many people get rich through blind luck!

• 1990: CCITT standard H.261 (p x 64) video coding
• 1990 Dec: CCITT standard H.320 for ISDN conferencing
• 1991 Sep: First audio/video conference (H.261 hardware codec) at DARTnet

And from http://www.dip.ee.bilkent.edu.tr/cost211.html

• COST211: Redundancy Reduction Techniques for Video Signals (1977-1982)
  
  Outcome: CCITT Recommendation H.121 2 Mbit/s codec for videoconferencing
• COST211bis: Redundancy Reduction Techniques for Coding of Broadband Video Signals (1983-1990)
  
  Outcome: CCITT Recommendation H.261 p x 64 kbit/s codec (1991)

Surely these people are just trying to benefit from obvious uses of other peoples' inventions. I can't even see a description of a codec in the application.

Bang paths in 1992? I'm pretty sure that's as nonsensical as the fact that I had to learn a subset of EBCDIC in High School "computer technologies" class. (And I'm still in High School.) TCP/IP and DNS were pretty well implemented by 1992.

But I thought Indians invented the 0

A "gb" is a groucho bit.
There are 10^30 * 8 * 2^30 grouchobits in a gibibyte.

Compressed audio and video transmission patented? In 1991 at that? Come on, that's like me patenting that you can wear shoes and socks at the same time. Digitally compressed video and audio existed LONG before these jokers. I mean CDs used PCM back in the mid-80s, and as for video, look here and here and about 20,000 more references on Google. This patenting of ideas that are just naive bundles of existing concepts just blows me away ... STOP THE INSANITY!

I'd made a research on Ontology Tools for Repositories on Internet including a quite satisfactory survey of ontology subject and a preliminary ontology language design for a grad. course given by Varol Akman at Bilkent CS. Dept.

It answers the quintessential question of "What is an Ontology?"

Thanks,

• Any FPGA design can be converted into an ASIC design with minimal or zero modifications, and usually with a substaintial performance improvement. There are several companies out there that will take your synthesized netlist and give you an ASIC, and will do it cheaply. The FPGA vs ASIC break even point is in the ball part of 100,000 units and it's getting better every day.

• While it may take a Virtex-II to compete with a decent accelerator for all applications, it may be possible to have multiple optimized implementation that are specific to specific applications. For instance, you could program the FPGA with an image optimized for 2D applications for general purpose use and then reprogram it with an image optimized for 3D applications as soon as you run your favorite FPS. Also, A decent sized Virtex-II can be purchased for US $323 in single quantities, and roughly half that in quantities of 1,000 or more.

• Design tools from Xilinx are less than US $1,000. And if you use their web-based tools, they are free.

• The circuit board would not be a major problem. I recently designed a PCI board with an FPGA and SDRAM on it (and wrote the FPGA code) and we got our 10 board for less than US $2,000. Most of this is set up cost, of course, so it gets really cheap really quickly as the numbers go up.

• 266 Mhz DDR RAM really only runs at 133 Mhz, and high end FPGAs can run at 300 Mhz. FPGA vendors often have hardware build into the FPGA to suppport high speed interfaces like that, or provide HDL source so that you can implement your own.

• Even if it takes 5A to run these chips (slightly excessive IMHO), the requirement is at the core voltage (1.5V for the Virtex-II mentioned earlier). With a 85% efficient switching regulator (typical), that would equal 2.7A @ 3.3V or 1.8A @ 5V or 750mA @ 12V (all of which are available on the AGP connector). Besides 5A @ 1.5V is just 8W after you include the switching inefficies, and you probably have at least a 300W power supply, so it's less than 3% of your total power budget.

• We do need to factor in assembly costs, which for a prototype run of 10 boards is going to to be about $3000 total, but the costs get really cheap if the quantity goes up, especially if the through-hole components are soldered by the enthusiasts who buy these cards.

  So, you don't really need all that much capital, and the open-source development model will provide the large teams of engineers.

  Unfortunately I can't contribute to this project because I code not in VHDL but in Verilog (which gets a lot more done for the same amount of effort in my opinion and others here and here).

In a review of your "Code and Other Laws of Cyberspace" which I had written, I had argued that there would be technical limits to regulation by architecture, i.e. in that a "perfect control" is not possible (while supporting the rest of the main views). To summarize "Limits to Regulation: Code and Coders" section , I first argue that there is a mathematical limit that prevents us from increasing the accuracy of control arbitrarily and there is a limit due to the distributed nature of control itself.

Computers, being finite things, present us many limits. For instance, there can be only a certain amount of network traffic, memory and computation power. What do you think will be the limits of regulation by architecture in the age of Cyberspace?

Thanks,

Eray Ozkural, CS Dept., Bilkent University

In a review of your "Code and Other Laws of Cyberspace" which I had written, I had argued that there would be technical limits to regulation by architecture, i.e. in that a "perfect control" is not possible (while supporting the rest of the main views). To summarize "Limits to Regulation: Code and Coders" section , I first argue that there is a mathematical limit that prevents us from increasing the accuracy of control arbitrarily and there is a limit due to the distributed nature of control itself.

Computers, being finite things, present us many limits. For instance, there can be only a certain amount of network traffic, memory and computation power. What do you think will be the limits of regulation by architecture in the age of Cyberspace?

Thanks,

Eray Ozkural, CS Dept., Bilkent University

Here are some of the more promising results of a search from google.com (String used was :unix ref card pdf)

Unix Cheat Sheet
Unix Cheat Sheet
From Rice University : Very basic
Another Too large and outdated
Selection of Unix, Vi, and Emacs refferences Courtesy Univ. of Alberta.ca

You should be able to find what you need easy enough. I should also highly reccommend to everyone the linuxsecurity.com Linux Security guidesheet. Damn good reading to hardening your system. Here

Toodles

Maybe $100K/year is barely enough for some families. But, Christ, nobody needs more than that (hello, affluenza). What if we established a dimishing point of returns? Rather than a maximum wage, we implement a tax program that taxes maybe 10% of your income if you make $100K/year or less. After $100K, parabolically increase the rate toward 90% or 100% (where 100% is like trying to reach warp factor 10: you never get there).

So, if you make $200K/year, you get taxed 15%, and you end up with $170K. If you make $500K, pay something like 25%, $1 million, maybe 40%, $100 million, 80% (and end up with $20 million, boo fucking hoo), and so on.

This way, you can still get a return for your "hard work", and Bill Gates and Ted Turner can still help us pay off the national debt.

I hate to date myself (but I will) but way back when, we got to add lines to feed the line-eater on our posts, and filled them with all sorts of vague (and not so vague) references to selling drugs, bombing buildings, etc. in the belief that there was some computer somewhere snarfing down all our messages.

Now I find out it's true. I am not sure if I should be happy or sad. From The Jargon Dictionary

NSA line eater n. The National Security Agency trawling program sometimes assumed to be reading the net for the U.S. Government's spooks. Most hackers describe it as a mythical beast, but some believe it actually exists, more aren't sure, and many believe in acting as though it exists just in case. Some netters put loaded phrases like `KGB', `Uzi', `nuclear materials', `Palestine', `cocaine', and `assassination' in their sig blocks in a (probably futile) attempt to confuse and overload the creature. The GNU version of EMACS actually has a command that randomly inserts a bunch of insidious anarcho-verbiage into your edited text.

There is a mainstream variant of this myth involving a `Trunk Line Monitor', which supposedly used speech recognition to extract words from telephone trunks. This one was making the rounds in the late 1970s, spread by people who had no idea of then-current technology or the storage, signal-processing, or speech recognition needs of such a project. On the basis of mass-storage costs alone it would have been cheaper to hire 50 high-school students and just let them listen in. Speech-recognition technology can't do this job even now (1993), and almost certainly won't in this millennium, either. The peak of silliness came with a letter to an alternative paper in New Haven, Connecticut, laying out the factoids of this Big Brotherly affair. The letter writer then revealed his actual agenda by offering --- at an amazing low price, just this once, we take VISA and MasterCard --- a scrambler guaranteed to daunt the Trunk Trawler and presumably allowing the would-be Baader-Meinhof gangs of the world to get on with their business.

NSA_LINE.HTML

Reading through 150+ posts, what I find most striking is how few suggestions there are, beyond the RFC's. Anyway, I'd propose Chuq von Rosbach's Usenet etiquette guide (even if he did once chew me out for an off-topic posting on an Apple mailing list).