This is all fine and good, but why not just treat the wires in a parallel cable as individual serial wires? Sure, if you increase the signal frequency, it becomes next to impossible to guarantee that all the signals arrive at exactly the same time, but I don't see the need for bit-level synchronization. If each wire has its own protocol, its own synchronization, and its own buffers, then as long as there is synchronization at the packet level, there should be no need to worry about synchronizing at the bit level. This would allow both high frequencies, and lots of wires.
Congratulations, you have just invented the RDRAM bus. The disadvantage is price. 150MB/s from one set of wires is more than enough for current drives, and serial speeds increase all the time, so it should not be necessary for many years for hard drives.
1. You can't HOTSWAP an IDE drive without risking blowing your drive, crontroller, or upsetting the powersupply.
With SATA you can.
2. You can't WARMSWAP an IDE drive, without risking blowing your drive, controller, or upsetting your powersupply.
With SATA you can.
3. IDE still only supports 2, yes 2 drivers per controller, which makes it impossible to do hardware RAID-5. That leaves us with software RAID-5 as our only option.
Who cares when you can get hardware RAID-controllers with 12 ports on one card? What is the great advantage of having the cable be the single point of failure for your whole RAID, like SCSI does?
4. IDE cables can only stretch so far, so even if you could somehow manage to get 8 IDE controllers into a box, for a total of 16 drives, there would still be cable length issues. I think 1 m is max. We need differential IDE:)
Ok, 1m can be a problem for some people. However most people do not have cases larger than 1m.
5. IDE drives are just now able to verify data integrity, but thats good since we can start using IDE drives in servers that don't need 100% uptime.
Err, why is it a problem when it is already fixed as you say?
6. ATA/100 Round IDE cables are already available. In fact I just ordered some that have a UV reflective coating for my next case mod which features a black light. Airflow isn't a big issue, in fact Compaq has been slicing up IDE cables for a long time now to increase airflow.
Round IDE-cables are expensive to produce and still large and inflexible. SATA solves it.
7. The SUSTAINED TRANSFER WRITE RATE of IDE drives is still not fast enough to store uncompressed NTSC video at 60 frames per second, or store high bandwidth Satellite streams.
So get the hardware RAID-controller and start streaming away. Oh wait, hardware RAID for SATA doesn't exist. 3ware is a figment of my imagination.
8a. Size increase (GB's) are not keeping pace with read/write access speeds and simply adding cache RAM and tweaking seek algorithms isn't going to remedy this problem.
You can't blame the interface for that. 150MB/s per drive for 12 drives on one card is way more than any SCSI solution supports -- and way more than current drives need.
8b. As, internal volatile write caches grow larger, the risk of uncommitted writes being lost in a power outage or crash increases.
So turn off the write cache. ATA supports Transaction Command Queueing although not all drives support it yet. By the time SATA drives become available, TCQ should be common.
I may be completely off, but doesn't ice take up more volume than an equivalent mass of water.
So if the polar caps melted, wouldn't the sea levels drop?
This would be the case if the ice was at the bottom of the sea. That is however not the usual place you find ice. Instead, ice is either on 1) top of the water or 2) on land.
When ice on top of water melts, the sea level does not change. Try the experiment yourself with an ice cube in a glass.
When ice on land melts, you are adding water to the sea. That will raise the sea level.
I am somewhat impressed that someone with moderation points found the parent informative. Not that flamebait is much better.
"This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version."
Tell me how this is not the exact same situation, but where RMS has the power to screw developers.
If you are the developer of the software it was you who decided to put the "any later version" clause in. Linus Torvalds deliberately left it out. You can hardly say Richard Stallman is screwing you for something you did yourself.
If you are not the developer, you get to choose whether to use the version 2 or a later version. If you feel you are being screwed by that, you just stick to the version 2.
Neither developers nor users are getting screwed unless they want to be. On the other hand, if you accept the license for the "free" version of BitKeeper, you accept being screwed and being unable to do anything about it.
This proposal requires everyone to switch to new chips and new software. The new chips happen to run old software. That sounds like AMD's 64-bit chips to me. When you are doing an incompatible change you might as well get decent benefits out of it, instead of more complexity.
Besides, segmented registers. I am having severe troubles finding an example of a worse idea actually proposed.
1) They're applying for patents. Buying a handgun (copyright) for personal self-defense is reasonable. Buying a thermonuclear device (patent) for personal self-defense is not.
Hand-guns are not very useful if all your opponents have thermonuclear weapons. Anyway, I will always prefer being hit by a patent lawsuit to being hit by a thermonuclear weapon.
First of all, *read* the article. I quote " The international project uses radio dishes in Arizona, Spain, Finland and Chile" Same hemisphere? Don't think so.
Why don't you think so? Try looking at a globe, and you'll see that those locations have a decent overlap in their fields of view. Alternatively, think of their time zones -6, +1, +2, -8. The maximum difference is 10, and half the earth is 12. Hence they are on the same hemisphere.
this page shows that this has been predicted as far back as 1993. It is nice to see climate theory match up with experimental evidence. Actually "nice" is the wrong word, I would certainly prefer if the whole global warming thing turned out to be a hoax. So far I am having very little luck on that wish.
If the parent or employer can change the key, then so can the children or employees. If physical tampering is not a problem, then existing access control mechanisms are fine. If physical tampering is a problem, Palladium will not help. The "content producers" are the only ones seeing a benefit from Palladium, and the only ones that physical tampering will not easily defeat.
All this historic stuff is mostly told in legends. Very little is documented, especially on the Web. You can find some things in the Google Web Directory or directly in The Unix Heritage Society. I have not had any luck finding references for file hierarchy stuff. If you like to read there is a nice list of books.
It does seem a bit funny that a high speed ISP would partner up with a file-sharing company that eats up all their bandwidth. While some ISPs are figuring out how to ban them, others are joining with them. I hope they have a lot of bandwidth to spare.
File sharing is just about the only way they can sell high-speed connections. There are practically no content providers for high-bandwidth content. It is nice to have web pages download slightly faster, but for most users the difference is not worth the extra cost. Personally I went for ADSL because the alternative around here is to pay by the minute. I want to be on always, the bandwidth is secondary.
Tiscali is one of the nicer ISP's, at least here in Denmark. They do not mind sharing of connections or running servers.
Incidentally, I find it sad that we are calling ADSL high-speed.
Now, with everything dynamically linked and the rescue system properly moved to/rescue instead of polluting/, it is time to finally get rid of/usr -- or even better turn it back into the user directory it was always supposed to be./usr/bin was invented way back when someone was running out of disk space in / and figured he could create a user account called bin (with home directory/usr/bin) and dump the extra binaries there. These days with logical volume management and overly large disks such hacks are no longer necessary.
NetBSD has just removed the last excuse for having / separate. Only one more step, and the Unix file hierarchy is back to its root.
Encouraged by the support for previous CleanSlashdot comments, an improved version of Cyberllama's comment above is offered. Please mod parent down. Thank you.
Why did you add the "mod parent down" part? It ruins your point. As far as I know ClearFlicks does not try to limit access to unedited versions.
Fortunately, here in the USA, the First Amendment protects our right to write and publish generalized streams of characters, not just text streams that are comprised solely of whitespace-separated lists valid English words.
As long as those streams of characters are not compilable into computer programs which can be used to circumvent access control.
Sorry, I fell into following your sloppiness in not distinguishing between what is legal and what is moral:
but the same laws that uphold their proprietary licenses uphold my GPL and BSD licenses.
This is the legal part. As I showed, the same laws do not apply. One is dependent on copyright law, the other on contract law. Copyright does not restrict use, only copying. EULA's could be found to be valid even if copyright was abolished.
If it is wrong for people to violate those licenses (and I think it is), then it is wrong to break a EULA from Microsquish or whomever.
This is the moral part and it has nothing to do with the legal part. It is just an independent statement that is not supported. I think it is wrong, and since it is your statement, the burden of proof is on you.
But the GPL then establishes a contract that says "in return for giving you permission to use this software, you agree to these terms".
Read the GPL. Let me quote:
You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Program (or any work based on the Program), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Program or works based on it.
It is not required to agree to the GPL to use the software. That is required only if you modify or distribute the program or its derivative works.
Slashdot Mirror
Congratulations, you have just invented the RDRAM bus. The disadvantage is price. 150MB/s from one set of wires is more than enough for current drives, and serial speeds increase all the time, so it should not be necessary for many years for hard drives.
1. You can't HOTSWAP an IDE drive without risking blowing your drive, crontroller, or upsetting the powersupply.
With SATA you can.
2. You can't WARMSWAP an IDE drive, without risking blowing your drive, controller, or upsetting your powersupply.
With SATA you can.
3. IDE still only supports 2, yes 2 drivers per controller, which makes it impossible to do hardware RAID-5. That leaves us with software RAID-5 as our only option.
Who cares when you can get hardware RAID-controllers with 12 ports on one card? What is the great advantage of having the cable be the single point of failure for your whole RAID, like SCSI does?
4. IDE cables can only stretch so far, so even if you could somehow manage to get 8 IDE controllers into a box, for a total of 16 drives, there would still be cable length issues. I think 1 m is max. We need differential IDE :)
Ok, 1m can be a problem for some people. However most people do not have cases larger than 1m.
5. IDE drives are just now able to verify data integrity, but thats good since we can start using IDE drives in servers that don't need 100% uptime.
Err, why is it a problem when it is already fixed as you say?
6. ATA/100 Round IDE cables are already available. In fact I just ordered some that have a UV reflective coating for my next case mod which features a black light. Airflow isn't a big issue, in fact Compaq has been slicing up IDE cables for a long time now to increase airflow.
Round IDE-cables are expensive to produce and still large and inflexible. SATA solves it.
7. The SUSTAINED TRANSFER WRITE RATE of IDE drives is still not fast enough to store uncompressed NTSC video at 60 frames per second, or store high bandwidth Satellite streams.
So get the hardware RAID-controller and start streaming away. Oh wait, hardware RAID for SATA doesn't exist. 3ware is a figment of my imagination.
8a. Size increase (GB's) are not keeping pace with read/write access speeds and simply adding cache RAM and tweaking seek algorithms isn't going to remedy this problem.
You can't blame the interface for that. 150MB/s per drive for 12 drives on one card is way more than any SCSI solution supports -- and way more than current drives need.
8b. As, internal volatile write caches grow larger, the risk of uncommitted writes being lost in a power outage or crash increases.
So turn off the write cache. ATA supports Transaction Command Queueing although not all drives support it yet. By the time SATA drives become available, TCQ should be common.
So if the polar caps melted, wouldn't the sea levels drop?
This would be the case if the ice was at the bottom of the sea. That is however not the usual place you find ice. Instead, ice is either on 1) top of the water or 2) on land.
- When ice on top of water melts, the sea level does not change. Try the experiment yourself with an ice cube in a glass.
- When ice on land melts, you are adding water to the sea. That will raise the sea level.
I am somewhat impressed that someone with moderation points found the parent informative. Not that flamebait is much better....apart from the name.
Tell me how this is not the exact same situation, but where RMS has the power to screw developers.
If you are the developer of the software it was you who decided to put the "any later version" clause in. Linus Torvalds deliberately left it out. You can hardly say Richard Stallman is screwing you for something you did yourself.
If you are not the developer, you get to choose whether to use the version 2 or a later version. If you feel you are being screwed by that, you just stick to the version 2.
Neither developers nor users are getting screwed unless they want to be. On the other hand, if you accept the license for the "free" version of BitKeeper, you accept being screwed and being unable to do anything about it.
Besides, segmented registers. I am having severe troubles finding an example of a worse idea actually proposed.
Try gtk-gnutella or another Gnutella program. Search for psyche-i386-disc1.iso (and so on). I'm sharing it and I know I'm not the only one.
Hand-guns are not very useful if all your opponents have thermonuclear weapons. Anyway, I will always prefer being hit by a patent lawsuit to being hit by a thermonuclear weapon.
Why don't you think so? Try looking at a globe, and you'll see that those locations have a decent overlap in their fields of view. Alternatively, think of their time zones -6, +1, +2, -8. The maximum difference is 10, and half the earth is 12. Hence they are on the same hemisphere.
This sentence should be parsed: Some other options are to (downgrade to Windows 98), (get a free operating system such as Linux).
this page shows that this has been predicted as far back as 1993. It is nice to see climate theory match up with experimental evidence. Actually "nice" is the wrong word, I would certainly prefer if the whole global warming thing turned out to be a hoax. So far I am having very little luck on that wish.
There was no need for imagination at the time. The flames were hot enough to push even RMS back. He is not known for his fear of fire.
The FAQ says that Linux is the most important secondary component.
Read the link to Heise. You probably do not know c't, since it is only available in German, but it is famous for the quality of its reporting.
If the parent or employer can change the key, then so can the children or employees. If physical tampering is not a problem, then existing access control mechanisms are fine. If physical tampering is a problem, Palladium will not help. The "content producers" are the only ones seeing a benefit from Palladium, and the only ones that physical tampering will not easily defeat.
Speaking of DEC... After it was announced that HP would buy Compaq, a rumour quickly spread that Apple would be acquired next. This is why.
Caldera bought SCO and turned into SCO. HP bought Compaq and turned into Compaq. It is not that unusual.
All this historic stuff is mostly told in legends. Very little is documented, especially on the Web. You can find some things in the Google Web Directory or directly in The Unix Heritage Society. I have not had any luck finding references for file hierarchy stuff. If you like to read there is a nice list of books.
File sharing is just about the only way they can sell high-speed connections. There are practically no content providers for high-bandwidth content. It is nice to have web pages download slightly faster, but for most users the difference is not worth the extra cost. Personally I went for ADSL because the alternative around here is to pay by the minute. I want to be on always, the bandwidth is secondary.
Tiscali is one of the nicer ISP's, at least here in Denmark. They do not mind sharing of connections or running servers.
Incidentally, I find it sad that we are calling ADSL high-speed.
NetBSD has just removed the last excuse for having / separate. Only one more step, and the Unix file hierarchy is back to its root.
Why did you add the "mod parent down" part? It ruins your point. As far as I know ClearFlicks does not try to limit access to unedited versions.
Amazon bothered Barnes&Noble over the one-click patent. Expecting them to be benevolent is slightly optimistic.
As long as those streams of characters are not compilable into computer programs which can be used to circumvent access control.
but the same laws that uphold their proprietary licenses uphold my GPL and BSD licenses.
This is the legal part. As I showed, the same laws do not apply. One is dependent on copyright law, the other on contract law. Copyright does not restrict use, only copying. EULA's could be found to be valid even if copyright was abolished.
If it is wrong for people to violate those licenses (and I think it is), then it is wrong to break a EULA from Microsquish or whomever.
This is the moral part and it has nothing to do with the legal part. It is just an independent statement that is not supported. I think it is wrong, and since it is your statement, the burden of proof is on you.
Read the GPL. Let me quote:
It is not required to agree to the GPL to use the software. That is required only if you modify or distribute the program or its derivative works.