Actually, it's because they didn't run it over enough stuff - Debian potato alone has around 218 million lines of code (compare to slink's 70 million).
As for number of projects, potato has 4376 packages, not all of those are separate projects (some are from multi-binary source, some are task packages), but I'm rather sure more than 3149 of them are:)
I don't get why everyone is advocating tricks to get around clicking 'ok' on the license agreement. Does anyone really think that a judge would uphold that dodge in court? 'Oh, you didn't know the license was there, so you accidentally used winzip rather than just double clicking on the executable'. I don't see this going over well.
Actually, I did exactly that (right-clicked on the.exe and chose extract-to-folder) and never knew there was a click-through agreement until I read these slashdot comments.
The only way you could use one way networking to log a server is if you were to send the logging information out, and have it configured to not recieve a reply signal.
Syslog does indeed work this way - it uses port 514 UDP.
Yes, you can run two ethernet connections down the same line, but at 10mbps I've had about 50% luck with this in runs > 50 feet. Especially when you're trying to push traffic through both sides of the cable at once.
As for putting voice traffic through the spare lines on an ethernet cable, I wouldn't see a problem with that (they're two entirely different frequency ranges), except you might get crosstalk between two voice lines on the same cable.
BTW, you *can* run one-way ethernet with two wires - if you hardwire ARP addresses on one side and the remote machine is only receiving UDP packets (you can't do TCP over such a link). Also you'll only get a link light on the receiving end (this may confuse your transmitting NIC).
In fact, this could be useful for logging servers:)
When I hand over $20 for a CD, what am I paying for?
A disc that happens to have copyrighted works on it.
You are not limited by what you do with that disc (it's yours) except if you want to make a copy of the copyrighted works on it.
The copyrighted works on CD's come with no license, so the only rights you get are those set by Fair Use precedence (and precedence is the only thing that defines Fair Use - check the United States Code for copyright law, it explicitly avoids defining Fair Use).
So, if you want to copy the copyrighted works on your CD onto tape, or mp3's, or whatever, then that action has to be covered by a Fair Use precedent to be considered legal. Previously, I was of the opinion that this was fair use, but this court decision contradicts me, and frankly I'm rather worried about this.
why do CDs cost so much more than cassettes of the same album?
Capitalists price things at whatever people are willing to pay for them. Otherwise they get sued by their shareholders. If it costs you $0.60 to make something, and you're selling it at $5.00, but people will pay $18.00, you're either generous or stupid.
At least the P3 serial number isn't backed up via a lithium battery that dies after five years causing your Sun to lose its ethernet address:)
Then again, you could actually use a dremel tool to drill into the RTC chip to solder in wires for a new external battery - I'd hate to attempt this to anything in a slot1 cartridge.
Nonsense - the P150 was an underclocked P166. Just like the P166MMX and P200MMX was an underclocked P233MMX (which in turn was an underclocked P266MMX, which they never released because it would interfere with PII sales), just like the PII 300-400 was an underclocked 450, the Celeron 366 through 466s were underclocked 500's, etc etc etc.
Saying the P166 was an overclocked P150 would be saying that all P166's wouldn't necessarily run at 166.666mhz - excluding defective chips, this was most certainly not the case.
With open-source software, "you could well have somebody developing a little application that they become dependent on. The person who develops it leaves, somebody else moves in who's never seen it before. If that's your expert, and they're now over in Saudi, you're kind of out of luck."
This is a serious problem with some Linux apps.
I could easily say the same thing about commercial software, or for that matter, any software developed on the job anywhere for anyone:
With commercial software, you could well install an application that you become dependant on. The company who developed it is now out of business, and you're SOL.
With commercial software, you could well install an application that you become dependant on. The company who developed it has released a new version, and isn't supporting the old one anymore.
With commercial software, you could well install an application that you become dependant on. The person at that company who developed it quit, and while the company would like to help you, they can't understand the code themselves and don't have the time to fix it for you.
With commercial software, you could well install an application that you become dependant on. The company who developed it doesn't have the source code any more because they were careless with backups.
With commercial software, you could well install an application that you become dependant on. The company who developed it was bought out by a competitor who wants to audit you for copyright infringement before they're willing to support you.
...and those are just the scenarios that I've seen myself:) At least if you have the source you have a fighting chance at recovering from most of these scenarios.
As for your comment about v0.02 software, yes, of course there's a lot of it, but usually that stuff either withers and dies before it gets put to use anywhere important, or actually gets developed into something useful.
The moral of the story is, don't take that next "this'll fix everything" release/patch/service pack for granted. For any software, free or not. Switch to stuff that you can verify as working as-is.
Do the math - light (and therefore RF and therefore wireless signals) travel at 300000000 meters per second. Your wireless round trip is 5km, 5000 meters, so that takes.016 milliseconds. Now, if that signal has to reach a satellite 36000000 meters away, that's going to take it 240 milliseconds. So yes, it is exactly equivalent to gamers playing over DirectPC:)
Some (VBRUN300.DLL) are, most (SHELL32.DLL, etc) aren't. The checksumming isn't internal to Windows' DLL-loading process, but some DLL's do a checksum of themselves and refuse to run if modified.
In this case, you could probably make as many changes as you wanted. Just don't change the length of the string unless you're really really good at changing offsets and entry points.:)
Out side the door I seen people I knew from when I was younger. They starting talking to me, and poking me and making this awful sounds (Bob said it was probably laughter), confused and dazed I retreated back into my room to review the sisuation with Bob.
The laughter thing has an easy fix - you have to put these things called "clothes" over yourself. Bob probably just assumed you already had them on.
If I want a quiet machine hooked to my stereo to play MP3s netbooting would let me avoid a hard drive
I'm running a P133 as just such a machine now. Originally it had a hard disk in it but I copied everything from it (cp -avx:) to an nfs server and made an nfsroot boot disk (linux/Documentation/nfsroot.txt has all the info you'll need on this).
It loads LILO and the kernel from floppy, but after that there's no moving parts (the P133 doesn't need a cpu fan, only a large sink, and I've ripped out the power supply fan). I suppose I could write a PROM chips that loads the kernel via TFTP or something (etherboot would do this), but I don't have any of the equipment to do that yet.
BTW, packard bell desktop machines can actually look pretty cool if you take all the plastic off, paint the metal casing jet black, and screw a carefully sized (black painted) metal sheet to the front. Maybe not as cool as jet-black painted Mac SE/30's running Debian, but close:)
They are absolutely made off the same die - this is how people were getting their P166MMX's to run at 250mhz and often 291mhz at the time. The 166's, 200's, and 233's all came off the same line, they would all run at 233 fine, 95% would run at 250 (you also had to have a motherboard and cards that would handle 83.3mhz bus, rarer in the pentium days), and a few would go up to 83.3*3.5.
Shortly after this, Intel started multiplier-locking their cpu's, which while not eliminating overclocking, definately made it harder (you had to start being picky about what chip you started with, a celeron 400 didn't have much overclock potential but a 366 did, etc).
I really don't understand where you get the idea that 10 lines of code or less are uncopyrightable/freely borrowable.
You can do anything you want with 10 lines of code for the same reasons you can do anything with an excerpt out of the paper or a book. It's called fair use.
If you write a 4-line memory compression algorithm - it's just that, an algorithm. There probably wouldn't be that many ways if any to rewrite it. You'd have better luck protecting it with a patent.
10 lines is just a guideline I've heard over and over. There is, of course, no clear definition of fair use in the US, and recent Congresses wish to keep it that way. Check http://fairuse.stanford.edu/.
Slashdot Mirror
Whether the claims of protection are actually true or not is another discussion, one in which the courts have the final word.
A Martian packet is one that appears to have made a round trip to Mars (i.e. is older than the TCP 120 second timeout) en route to your computer.
As for number of projects, potato has 4376 packages, not all of those are separate projects (some are from multi-binary source, some are task packages), but I'm rather sure more than 3149 of them are :)
~/linux/net/ipv4$ grep martian * /* Check for the most weird martians, which can be not detected
devinet.c: {NET_IPV4_CONF_LOG_MARTIANS, "log_martians",
devinet.c: &ipv4_devconf.log_martians, sizeof(int), 0644, NULL,
route.c:
route.c: goto martian_source;
route.c: goto martian_source;
route.c: goto martian_destination;
route.c: goto martian_source;
route.c: goto martian_destination;
route.c: goto martian_source;
route.c: goto martian_source;
route.c: * Do not cache martian addresses: they should be logged (RFC1812)
route.c:martian_destination:
route.c: printk(KERN_WARNING "martian destination %08x from %08x, dev %s\n", daddr, saddr, dev->name);
route.c:martian_source:
route.c: * RFC1812 recommenadtion, if source is martian,
route.c: printk(KERN_WARNING "martian source %08x for %08x, dev %s\n", saddr, daddr, dev->name);
(yes, I am kidding, and yes, that grep will actually print out what I posted)
Actually, I did exactly that (right-clicked on the .exe and chose extract-to-folder) and never knew there was a click-through agreement until I read these slashdot comments.
Syslog does indeed work this way - it uses port 514 UDP.
As for putting voice traffic through the spare lines on an ethernet cable, I wouldn't see a problem with that (they're two entirely different frequency ranges), except you might get crosstalk between two voice lines on the same cable.
BTW, you *can* run one-way ethernet with two wires - if you hardwire ARP addresses on one side and the remote machine is only receiving UDP packets (you can't do TCP over such a link). Also you'll only get a link light on the receiving end (this may confuse your transmitting NIC).
In fact, this could be useful for logging servers :)
When I hand over $20 for a CD, what am I paying for?
A disc that happens to have copyrighted works on it.
You are not limited by what you do with that disc (it's yours) except if you want to make a copy of the copyrighted works on it.
The copyrighted works on CD's come with no license, so the only rights you get are those set by Fair Use precedence (and precedence is the only thing that defines Fair Use - check the United States Code for copyright law, it explicitly avoids defining Fair Use).
So, if you want to copy the copyrighted works on your CD onto tape, or mp3's, or whatever, then that action has to be covered by a Fair Use precedent to be considered legal. Previously, I was of the opinion that this was fair use, but this court decision contradicts me, and frankly I'm rather worried about this.
why do CDs cost so much more than cassettes of the same album?
Capitalists price things at whatever people are willing to pay for them. Otherwise they get sued by their shareholders. If it costs you $0.60 to make something, and you're selling it at $5.00, but people will pay $18.00, you're either generous or stupid.
If only society would value the former :)
I hope you're not thinking of this:
C:\>dir
Volume in drive C has no label.
Volume Serial Number is E0F1-8483
Because that E0F1-8483 is just a fancy timestamp written by DOS's format command.
I believe the stuff in /proc/ide/ide*/hd*/identify is actually hardware information and is AFAIK unique.
Then again, you could actually use a dremel tool to drill into the RTC chip to solder in wires for a new external battery - I'd hate to attempt this to anything in a slot1 cartridge.
Nonsense - the P150 was an underclocked P166. Just like the P166MMX and P200MMX was an underclocked P233MMX (which in turn was an underclocked P266MMX, which they never released because it would interfere with PII sales), just like the PII 300-400 was an underclocked 450, the Celeron 366 through 466s were underclocked 500's, etc etc etc.
Saying the P166 was an overclocked P150 would be saying that all P166's wouldn't necessarily run at 166.666mhz - excluding defective chips, this was most certainly not the case.
This is a serious problem with some Linux apps.
I could easily say the same thing about commercial software, or for that matter, any software developed on the job anywhere for anyone:
With commercial software, you could well install an application that you become dependant on. The company who developed it is now out of business, and you're SOL.
With commercial software, you could well install an application that you become dependant on. The company who developed it has released a new version, and isn't supporting the old one anymore.
With commercial software, you could well install an application that you become dependant on. The person at that company who developed it quit, and while the company would like to help you, they can't understand the code themselves and don't have the time to fix it for you.
With commercial software, you could well install an application that you become dependant on. The company who developed it doesn't have the source code any more because they were careless with backups.
With commercial software, you could well install an application that you become dependant on. The company who developed it was bought out by a competitor who wants to audit you for copyright infringement before they're willing to support you.
As for your comment about v0.02 software, yes, of course there's a lot of it, but usually that stuff either withers and dies before it gets put to use anywhere important, or actually gets developed into something useful.
The moral of the story is, don't take that next "this'll fix everything" release/patch/service pack for granted. For any software, free or not. Switch to stuff that you can verify as working as-is.
Do the math - light (and therefore RF and therefore wireless signals) travel at 300000000 meters per second. Your wireless round trip is 5km, 5000 meters, so that takes .016 milliseconds. Now, if that signal has to reach a satellite 36000000 meters away, that's going to take it 240 milliseconds. So yes, it is exactly equivalent to gamers playing over DirectPC :)
Your latency data point from your wireless network is useless. 2.5km is a much smaller number than 36000km :)
In this case, you could probably make as many changes as you wanted. Just don't change the length of the string unless you're really really good at changing offsets and entry points. :)
The laughter thing has an easy fix - you have to put these things called "clothes" over yourself. Bob probably just assumed you already had them on.
I'm running a P133 as just such a machine now. Originally it had a hard disk in it but I copied everything from it (cp -avx :) to an nfs server and made an nfsroot boot disk (linux/Documentation/nfsroot.txt has all the info you'll need on this).
It loads LILO and the kernel from floppy, but after that there's no moving parts (the P133 doesn't need a cpu fan, only a large sink, and I've ripped out the power supply fan). I suppose I could write a PROM chips that loads the kernel via TFTP or something (etherboot would do this), but I don't have any of the equipment to do that yet.
BTW, packard bell desktop machines can actually look pretty cool if you take all the plastic off, paint the metal casing jet black, and screw a carefully sized (black painted) metal sheet to the front. Maybe not as cool as jet-black painted Mac SE/30's running Debian, but close :)
Eh? I don't see copyright infringers taking guns to artist's heads.
I hope not - if this is a 3" diameter fan, this means that the tips would be doing a bit over mach 5 :)
BTW if you put a tuned pipe on your cpu cooling exhaust headers you can get another 20mhz out of it.
Shortly after this, Intel started multiplier-locking their cpu's, which while not eliminating overclocking, definately made it harder (you had to start being picky about what chip you started with, a celeron 400 didn't have much overclock potential but a 366 did, etc).
Well, to me, it means any team activity (usually as part of employment) that results in completely botched results.
Example: "My ISP really clustered on that DNS switchover."
unsigned char *a="\x98mWPS\x1\x87hSJH\0159F",b;main(){for(;b+=*a ++-80;putchar(b));}
:)
If anyone knows how to make a shorter "Hello World" in C that doesn't actually have the text "Hello World" in it, I'd love to see it
Eh?
You can do anything you want with 10 lines of code for the same reasons you can do anything with an excerpt out of the paper or a book. It's called fair use.
If you write a 4-line memory compression algorithm - it's just that, an algorithm. There probably wouldn't be that many ways if any to rewrite it. You'd have better luck protecting it with a patent.
10 lines is just a guideline I've heard over and over. There is, of course, no clear definition of fair use in the US, and recent Congresses wish to keep it that way. Check http://fairuse.stanford.edu/.