mikemuch writes "ExtremeTech has a review and benchmarks of the Hitachi Deskstar 7K1000 1TB Hard Drive, which ushers in the terabyte age. It performs well on HDTach and PCMark benchmarks, though not as speedily as professional-grade drives. It could be just the ticket for digital media junkies. 'One of the first issues to note is that you may not see an actual one terabyte capacity on your system. First, the formatted capacity is always less than the raw space available on the drive. Directory information and formatting data always take up some space. Second, the hard drive industry's definition of a megabyte differs from the rest of the PC business. One megabyte of hard drive space is 1,000,000 bytes: 10^6 bytes. Operating systems calculate one megabyte as 2^20 bytes, or 1,048,576 bytes. Once installed and set up, Hitachi's 1TB hard drive offers up an actual formatted capacity of about 935GB, as measured by the OS. That's still a lot of space, by anyone's definition.'"Update: 05/17 21:52 GMT by Z: Adding '^s' missing from article.
Is there anyone out there who would be buying a 1TB hard drive who doesn't already know the difference between binary and decimal prefixes? I think their target market is well aware of the differences between GiB and GB.
Actually, it seems some Microsoft programmers still don't know the difference. At least most open source apps properly distinguish between binary and decimal prefixes. Not so for Windows...
No, it isnt. From a user perspective, it doesnt matter shit if a byte is 8 bit. That solves the whole "base 10" crisis you seem to have. Next, gather your brain for some thought: you have a CPU that runs at some Ghz, and memory busses/network cards that run at megabyte/s.
Now guess what kind of "mega" those aspects used from the beginning of time? Yes, SI. Just for some strage reason, for memory and disks people thought that 1024 is close enought to 1000 as not to matter. Too bad now we are at 10^9 vs 2^30, wher
For an example of the difference, people don't say that they have a megadollar or a gigaduck (not normal people)
Maybe not, but they do say "centidollar" -- at least in its abbreviated form, "cent".
I'd like to see the pedantic community start discussing things in mebimeters and gibiwatts before they start trying to change the computer community's standard meanings.
Huh? There would be no reason for people to use mebimeters and gibiWatts, because metres and Watts are Metric units and thus are base 10. It would not make sense to use base 2 prefixes (mebi, gibi) in a base 10 system. It does, on the other hand, make sense to use base 10 units in a base 10 system such as the metric system, and likewise base 2 units in a binary system.
Don't complain about the fact a megabyte isn't what you thought it was. Complain about the fact the industry still uses it for labels. But don't try and make the megabyte a mebibyte.
The reason why nobody uses "mebibyte", "kibibyte", "gibibyte", and all of these other terms are because of two reasons: they are new and relatively unknown, and they just sound stupid and unnatural (try pronouncing them). It is commonly accepted knowledge in electrical engineering and computer science circles that we use 2^10, 2^20, 2^30, etc. when describing kilobytes, megabytes, and gigabytes, respectively, except when dealing with data storage capacities (which I feel is a marketroid invention and a sales gimmick. "10^9 vs. 2^30? Who'll know the difference?"). It's been that way since the 1960s. The new terms like "mebibyte," "gibibyte," and the rest of them just sound silly, hard to pronounce, and unnatural.
seriously, The computer uses power of two, it's how it measures things. We should use BI prefix, anything else is just cheap used car saleman gimmicks.
They are still wrong. The fundamental organization of computers is base 2. Ever try to design a processor that uses 1000 byte pages? Good freaking luck.
The purpose of SI units being in base 10 is because the number system that we use to measure things is ALSO in base 10. Therefore, the unit fits comfortably within mathematics associated with the relative fields. However, A base-10 numbering scheme basically does not exist in the computing world; obscure BCD hardware notwithstanding, all occurrences of base ten in computing are entirely a fiction created by the machine to try to make things more understandable to people used to base 10.
More to the point memory and storage are inherently organized in units of powers of two. Memory will ALWAYS be organized in power-of-two increments as long as computer operate based on the binary system. Why? Because this makes it possible to express divisions of memory in terms of bit boundaries. A power-of-10 memory organization would require computationally heavy division or multiplication operations throughout the memory management code, while a power-of-2 memory organization requires an extremely lightweight bit shift. For this reason, as long as we have binary-based computers, we are stuck with power-of-two units of RAM.
Similarly, a hard drive block will ALWAYS be evenly divisible by the size of a memory page or vice versa. If this were not the case, the complexity of writing an operating system would be beyond insane. Paging and memory mapping of files alone would be enough to make the engineers commit seppuku. Therefore, as long as RAM is organized into groupings based on powers of two, hard drives will always be physically laid out in blocks whose length is a power of two.
Because the fundamental organization of data in a computer is, by nature, organized into power-of-two units, describing storage in power-of-ten units makes no sense, as it will almost always be a crude approximation. There are probably exactly zero hard drives with an exact decimal gigabyte capacity. The fundamental storage in hard drives is a 512 byte block, and 512 does not divide evenly into most multiple-of-ten values. Sure, you could create a 512 decimal gigabyte drive, I suppose, but for the most part, the values just don't divide evenly by 512. Therefore, using a multiple of a power-of-ten number to describe the amount of storage will almost always be a very crude approximation, while using a multiple of a power-of-two number can be (and usually is) an exact value.
In other words, the idiots in charge of making up the SI units should have been taken out and beaten for "Gibibyte". There is one natural unit in computers, and that is the base-2-derived gigabyte. All base-10 units are inherently inaccurate, and thus a poor fit for computing. They should be summarily rejected by the industry, as they simply do not make any sense in the context of storage. Honestly, they don't make a lot of sense for networking, either for the same reason, but I'm willing to overlook that... for now....
Alright, after reading that, I want a yottabyte hard drive in my house server- ought to be good for recording all sensor data, including DVR, for the next century or so....
Don't complain about the fact a megabyte isn't what you thought it was. Complain about the fact the industry still uses it for labels. But don't try and make the megabyte a mebibyte.
What!?! Next thing you'll be telling me is that a kilometer isn't 1024 meters long. Please, stop this madness before it spreads!
What!?! Next thing you'll be telling me is that a kilometer isn't 1024 meters long. Please, stop this madness before it spreads!
Don't be silly. As we all know, God Almighty came down from the heavens to decree that Computers must use powers of 2 to describe international standard unit prefixes that were previously defined as powers of 10.
Of course, we all know this is an evil conspiracy by the hard drive industry.... and the network card industry (I was shocked to find my gigabit card is not actually 1,073,741,824 bits per second).... and the processor industry (2.4GHz? Hah, more like 2.23517GHz!).... and the digital camera industry (blah blah megapixels. they're screwing me out of precious resolution).
The difference between the two numbers is due to this:
Manufacturers have an interest in you paying more and getting less, while computers do not. Manufacturers who are successful and have the cash to spend can then lobby international standards bodies to skew "standards" in their favor, regardless of historical context and practical day-to-day usage patterns (both technical and linguistic).
Don't side with "the man" on/. unless you enjoy tar + feathers, not even if it means bucking the "standard".
Don't try to invent a new notation to make-up for corporate marketing corrupting established and well-understood notation.
I would point out the "mega" was an established and well-understood prefix for 10^6 well before the computer industry (sans hard drive makers) started to use it mean 2^20.
eh, you're not missing anything anyway. TFA is just one of those meager gear review sites with 20 words per page spread out onto 8 pages all mostly covered with a bunch of empty rectangles.
what is the DEAL with all those empty rectangles anyway?
I remember when I paid $150 for a 10meg MFM drive! (poke c800:50;) I remember paying $1000 for my first 1gig drive! I remember paying $500 for my first 1TB of drive space (6x300gb drives ok 1.8TB unformatted) I remember paying $350 for my second 1.1TB of drive space (4x320gb Just last week)
I can not wait to get to my first 6TB system! I may have said, many years ago, that I would never fill 1gig, but I know I can fill 6TB It should not take me more than a couple of months.
Man how things have changed!
Then 8mhz, 640k ram and 10megs. Now 2.4Ghz dual core, 2gig ram, 1.1TB HD
We can only guess what Zonk meant to say. But I'll try to make some sense.
First, hard drive manufacturers have always calculated drive space differently than the rest of the entire computing world. It allows them to say that a drive is bigger than it really truly is. They've been able to do it for years, and lawsuits have been lost and won on this very issue. But essentially, their use of the metric words "kilo," "mega," and "giga" are the literal meanings of "1000," "1,000,000" and "1,000,000,000" instead of the computing world's 1024 multiplier.
Therefore, a "kilobyte" to them is 1,000 bytes (as opposed to 1,024 bytes in real life), and a "megabyte" is "1,000,000" bytes (as opposed to 1,048,576 bytes [1024 x 1024]), and a "gigabyte" is 1,000,000,000 bytes (instead of 1,073,741,824 [1024 x 1024 x 1024] bytes in real life).
The real difference in a terabyte? Divide 1,000,000,000,000 by 1024/1024/1024 and you get 931.32 gigabytes. That's a theoretical limit, mind you, and there is overhead for cluster size, partition info, FAT tables, etc., so you really don't even get that.
Therefore, a "kilobyte" to them is 1,000 bytes (as opposed to 1,024 bytes in real life)
Actually, it is more like the "kilo = 1000" is the real life meaning, and the "kilo = 1024" is something dreamed up by some hacker in his own little world. I mean, one kilogram is 1000 grams, one kilohertz is 1000 hertz, one kilometer is 1000 meters, etc.
Cue the ensuing Mebi/Gibi/Tebi vs. SI notation fights.
While it's takes a while to get used to it, I actually prefer the Bi-units now. 4,3GiB or 4,7GB is already a huge difference when talking about DVD capacity. At terabyte, it gets enormous.
Linux already uses those units.
Only place where I still see a purpose for using binary units in computing is memory - address bus is still addressed exactly with n lines so memory capacity will be 2^n. For all other cases, it's not needed. Yes, the hard drives have 512 to 4096 byte sectors, but who cares when were talking about trillions of them?
While I know that most folks like the faster larger disks, the truth is that these are NOT used in most businesses. Many business will use >= 10K, SCSIed and raided (save the small ones). These will be used in home drives or as LARGE storage. It would make sense to have these spin at lower speeds to increase the MTBF. In particular, if these are raided, then you can get plenty of speed.
Hitachi probably say all the recent AACS compromises and thought "Well, people are obviously going to need more hard drive space now". Hitachi have their finger on the pulse:)
In other news, Seagate announced that its upcoming line of hard drives will be measured using the new LoC (Library of Congress) storage units to avoid confusion. The advanced ST-54883432, weighing in at a monstrous.00000000000017 LoC, goes on sale June 14th.
The Hitach is a 1000mb drive with 5x200gb platters. The Seagate (due soon) is a 1000mb drive with 4x250gb platters and (iirc) 32mb of cache.
The increased platter density will slightly increase performance and theoretically decrease cost, it'll slightly reduce heat and also power use too.
On top of this Seagate offer a 5 year warranty on all drives (Hitachi may also, sorry not sure) and Seagate used to be one of the quietest available to boot. (although I hear the 7200.10's suck for noise, apparently some kind of patent issue with using low acoustic mode - hope that's sorted?)
Anyhow, what this does mean for us end users is you'll see 2 platter, 500gb drives which weigh less, cost less, run faster and cost substantially less than the 1000mb models, also the glorious 750gb will become a 3 platter model instead of a 4 platter (my personal 'limit' is 3playtters - after that I find it too prone to noise / heat / failure rate)
I'd say we'll see 80$ (rebate) 500gb drives within 3 months and we'll see the 750's at 169$ or something soon(ish)
Regardless of whether the original article had it wrong, someone at Slashdot should've read the posted summary text and noticed the error. You shouldn't be a "News for Nerds" editor and not immediately notice that the sentence makes absolutely no sense as written.
by Anonymous Coward
on Thursday May 17 2007, @08:49PM (#19173497)
This is still not really correct: One megabyte of hard drive space is 1,000,000 bytes: 10^6 bytes. Operating systems calculate one megabyte as 2^20 bytes, or 1,048,576 bytes.
It should read: Hard disk manufacturing company marketing departments define one megabyte of hard drive space as 1,000,000 bytes: 10^6 bytes. Fucking reality calculates one megabyte as 2^20 bytes, or 1,048,576 bytes.
It's common practise to use the highest number when representing something in an ad. Like for instance Cirrus aircraft advertise their aircraft's speed in MPH, when pilots actually use knots. This is because you get a number on the ad that's 15% bigger. And I bet Cirrus advertise the speed of their planes in Europe in km/h because this yields an even bigger number.
Personally, I wish we'd just get on with it and switch to base 16. It would be so much more convenient, and I'd be back in my early 20s again!
AC> Pilots are just nuts, with their knots and feet.
While the use of feet might be dubious, there's a good rationale for using knots. One minute of latitude is one nautical mile long. This makes it very easy to do quick measurements on a chart while in-flight - since however you have a chart folded, you'll be able to see a longitude line (which has latitude tick marks as it goes up the page).
One megabyte of hard drive space is 1,000,000 bytes: 10<sup>6</sup> bytes. Operating systems calculate one megabyte as 2<sup>20</sup> bytes, or 1,048,576 bytes.
Now I need faster broadband (Score:5, Funny)
Re:Now I need faster broadband (Score:4, Funny)
Parent
New New Math? (Score:5, Funny)
Re:SUP tag missing - 10^6 and 2^20 (Score:5, Funny)
Parent
why explain prefixes? (Score:4, Interesting)
Actually, it seems some Microsoft programmers still don't know the difference. At least most open source apps properly distinguish between binary and decimal prefixes. Not so for Windows...
Re: (Score:3, Informative)
From a user perspective, it doesnt matter shit if a byte is 8 bit. That solves the whole "base 10" crisis you seem to have.
Next, gather your brain for some thought: you have a CPU that runs at some Ghz, and memory busses/network cards that run at megabyte/s.
Now guess what kind of "mega" those aspects used from the beginning of time? Yes, SI.
Just for some strage reason, for memory and disks people thought that 1024 is close enought to 1000 as not to matter.
Too bad now we are at 10^9 vs 2^30, wher
Re:why explain prefixes? (Score:4, Informative)
Parent
Why is this still a discussion? (Score:5, Insightful)
http://en.wikipedia.org/wiki/Binary_prefix [wikipedia.org] vs http://en.wikipedia.org/wiki/Si_prefix [wikipedia.org]
Re:Why is this still a discussion? (Score:4, Insightful)
The reason why nobody uses "mebibyte", "kibibyte", "gibibyte", and all of these other terms are because of two reasons: they are new and relatively unknown, and they just sound stupid and unnatural (try pronouncing them). It is commonly accepted knowledge in electrical engineering and computer science circles that we use 2^10, 2^20, 2^30, etc. when describing kilobytes, megabytes, and gigabytes, respectively, except when dealing with data storage capacities (which I feel is a marketroid invention and a sales gimmick. "10^9 vs. 2^30? Who'll know the difference?"). It's been that way since the 1960s. The new terms like "mebibyte," "gibibyte," and the rest of them just sound silly, hard to pronounce, and unnatural.
Parent
Re: (Score:3, Insightful)
seriously, The computer uses power of two, it's how it measures things. We should use BI prefix, anything else is just cheap used car saleman gimmicks.
Re:Why is this still a discussion? (Score:5, Insightful)
They are still wrong. The fundamental organization of computers is base 2. Ever try to design a processor that uses 1000 byte pages? Good freaking luck.
The purpose of SI units being in base 10 is because the number system that we use to measure things is ALSO in base 10. Therefore, the unit fits comfortably within mathematics associated with the relative fields. However, A base-10 numbering scheme basically does not exist in the computing world; obscure BCD hardware notwithstanding, all occurrences of base ten in computing are entirely a fiction created by the machine to try to make things more understandable to people used to base 10.
More to the point memory and storage are inherently organized in units of powers of two. Memory will ALWAYS be organized in power-of-two increments as long as computer operate based on the binary system. Why? Because this makes it possible to express divisions of memory in terms of bit boundaries. A power-of-10 memory organization would require computationally heavy division or multiplication operations throughout the memory management code, while a power-of-2 memory organization requires an extremely lightweight bit shift. For this reason, as long as we have binary-based computers, we are stuck with power-of-two units of RAM.
Similarly, a hard drive block will ALWAYS be evenly divisible by the size of a memory page or vice versa. If this were not the case, the complexity of writing an operating system would be beyond insane. Paging and memory mapping of files alone would be enough to make the engineers commit seppuku. Therefore, as long as RAM is organized into groupings based on powers of two, hard drives will always be physically laid out in blocks whose length is a power of two.
Because the fundamental organization of data in a computer is, by nature, organized into power-of-two units, describing storage in power-of-ten units makes no sense, as it will almost always be a crude approximation. There are probably exactly zero hard drives with an exact decimal gigabyte capacity. The fundamental storage in hard drives is a 512 byte block, and 512 does not divide evenly into most multiple-of-ten values. Sure, you could create a 512 decimal gigabyte drive, I suppose, but for the most part, the values just don't divide evenly by 512. Therefore, using a multiple of a power-of-ten number to describe the amount of storage will almost always be a very crude approximation, while using a multiple of a power-of-two number can be (and usually is) an exact value.
In other words, the idiots in charge of making up the SI units should have been taken out and beaten for "Gibibyte". There is one natural unit in computers, and that is the base-2-derived gigabyte. All base-10 units are inherently inaccurate, and thus a poor fit for computing. They should be summarily rejected by the industry, as they simply do not make any sense in the context of storage. Honestly, they don't make a lot of sense for networking, either for the same reason, but I'm willing to overlook that... for now....
Parent
Re:Why is this still a discussion? (Score:4, Informative)
Ever try to design a processor that uses 1000 byte pages? Good freaking luck.
No, but these guys [wikipedia.org] did.
Parent
Re: (Score:3, Interesting)
Re:Why is this still a discussion? (Score:5, Funny)
What!?! Next thing you'll be telling me is that a kilometer isn't 1024 meters long. Please, stop this madness before it spreads!
Parent
Re:Why is this still a discussion? (Score:4, Funny)
Of course, we all know this is an evil conspiracy by the hard drive industry.
Parent
Re:Why is this still a discussion? (Score:5, Insightful)
Manufacturers have an interest in you paying more and getting less, while computers do not. Manufacturers who are successful and have the cash to spend can then lobby international standards bodies to skew "standards" in their favor, regardless of historical context and practical day-to-day usage patterns (both technical and linguistic).
Don't side with "the man" on
Parent
Re:Why is this still a discussion? (Score:4, Funny)
* 7 bit bytes
Parent
Re:Why is this still a discussion? (Score:5, Funny)
Parent
Re:Why is this still a discussion? (Score:5, Insightful)
Parent
Reality (Score:3, Funny)
I sure as hell don't want it to say 106 bytes.
Ahh Slashdot (Score:3, Insightful)
Re:Ahh Slashdot (Score:5, Funny)
eh, you're not missing anything anyway. TFA is just one of those meager gear review sites with 20 words per page spread out onto 8 pages all mostly covered with a bunch of empty rectangles.
what is the DEAL with all those empty rectangles anyway?
Parent
First review? ummm... Anandtech, March 19th.... (Score:5, Informative)
http://www.anandtech.com/storage/showdoc.aspx?i=2
Follow-up RAID performance April 19th:
http://www.anandtech.com/storage/showdoc.aspx?i=2
Follow-up to the follow-up April 23rd:
http://www.anandtech.com/storage/showdoc.aspx?i=2
Sloppy editing. (Score:3, Funny)
Wow, I love ponies.
WOW, 1TB (Score:5, Interesting)
I remember paying $1000 for my first 1gig drive!
I remember paying $500 for my first 1TB of drive space (6x300gb drives ok 1.8TB unformatted)
I remember paying $350 for my second 1.1TB of drive space (4x320gb Just last week)
I can not wait to get to my first 6TB system! I may have said, many years ago, that I would never fill 1gig, but I know I can fill 6TB It should not take me more than a couple of months.
Man how things have changed!
Then 8mhz, 640k ram and 10megs.
Now 2.4Ghz dual core, 2gig ram, 1.1TB HD
I wonder what we will say in another 16 years.
Re:WOW, 1TB (Score:5, Insightful)
High quality 1080p video. Animated textures for video games. A massive sample database for a voice synthesizer.
I'm not actually sure what you would do with a 10,000 TB hard disk - but 10 TB is well within the "use it up with some video" range.
Parent
Megabyte/Terabyte (Score:4, Informative)
First, hard drive manufacturers have always calculated drive space differently than the rest of the entire computing world. It allows them to say that a drive is bigger than it really truly is. They've been able to do it for years, and lawsuits have been lost and won on this very issue. But essentially, their use of the metric words "kilo," "mega," and "giga" are the literal meanings of "1000," "1,000,000" and "1,000,000,000" instead of the computing world's 1024 multiplier.
Therefore, a "kilobyte" to them is 1,000 bytes (as opposed to 1,024 bytes in real life), and a "megabyte" is "1,000,000" bytes (as opposed to 1,048,576 bytes [1024 x 1024]), and a "gigabyte" is 1,000,000,000 bytes (instead of 1,073,741,824 [1024 x 1024 x 1024] bytes in real life).
The real difference in a terabyte? Divide 1,000,000,000,000 by 1024/1024/1024 and you get 931.32 gigabytes. That's a theoretical limit, mind you, and there is overhead for cluster size, partition info, FAT tables, etc., so you really don't even get that.
Doesn't that byte?
Re:Megabyte/Terabyte (Score:4, Informative)
Actually, it is more like the "kilo = 1000" is the real life meaning, and the "kilo = 1024" is something dreamed up by some hacker in his own little world. I mean, one kilogram is 1000 grams, one kilohertz is 1000 hertz, one kilometer is 1000 meters, etc.
Parent
"...by anyones definition" (Score:4, Funny)
Note to future self: remember when 1 terabyte was considered a lot of storage? those were the days....
I look forward to more write-ups like this (Score:4, Funny)
SI prefixes are powers of thousand. (Score:5, Insightful)
While it's takes a while to get used to it, I actually prefer the Bi-units now. 4,3GiB or 4,7GB is already a huge difference when talking about DVD capacity. At terabyte, it gets enormous.
Linux already uses those units.
Only place where I still see a purpose for using binary units in computing is memory - address bus is still addressed exactly with n lines so memory capacity will be 2^n. For all other cases, it's not needed. Yes, the hard drives have 512 to 4096 byte sectors, but who cares when were talking about trillions of them?
See http://en.wikipedia.org/wiki/Binary_prefix [wikipedia.org] for more.
I want a 5400 (Score:3, Interesting)
Windoze (Score:3, Funny)
AACS Compromises (Score:4, Funny)
New drive storage metrics needed (Score:5, Funny)
Screw the hitachi! (Score:5, Interesting)
The Seagate (due soon) is a 1000mb drive with 4x250gb platters and (iirc) 32mb of cache.
The increased platter density will slightly increase performance and theoretically decrease cost, it'll slightly reduce heat and also power use too.
On top of this Seagate offer a 5 year warranty on all drives (Hitachi may also, sorry not sure) and Seagate used to be one of the quietest available to boot. (although I hear the 7200.10's suck for noise, apparently some kind of patent issue with using low acoustic mode - hope that's sorted?)
Anyhow, what this does mean for us end users is you'll see 2 platter, 500gb drives which weigh less, cost less, run faster and cost substantially less than the 1000mb models, also the glorious 750gb will become a 3 platter model instead of a 4 platter (my personal 'limit' is 3playtters - after that I find it too prone to noise / heat / failure rate)
I'd say we'll see 80$ (rebate) 500gb drives within 3 months and we'll see the 750's at 169$ or something soon(ish)
Re:106 bytes and 220 bytes, ??? (Score:5, Informative)
Parent
Re:106 bytes and 220 bytes, ??? (Score:4, Insightful)
Parent
Re:Zonk (Score:4, Informative)
Parent
Re:Zonk (Score:4, Insightful)
This is still not really correct: One megabyte of hard drive space is 1,000,000 bytes: 10^6 bytes. Operating systems calculate one megabyte as 2^20 bytes, or 1,048,576 bytes.
It should read: Hard disk manufacturing company marketing departments define one megabyte of hard drive space as 1,000,000 bytes: 10^6 bytes. Fucking reality calculates one megabyte as 2^20 bytes, or 1,048,576 bytes.
Parent
Re:kibibytes & mibimeters (Score:4, Insightful)
Personally, I wish we'd just get on with it and switch to base 16. It would be so much more convenient, and I'd be back in my early 20s again!
Parent
Re:kibibytes & mibimeters (Score:4, Informative)
While the use of feet might be dubious, there's a good rationale for using knots. One minute of latitude is one nautical mile long. This makes it very easy to do quick measurements on a chart while in-flight - since however you have a chart folded, you'll be able to see a longitude line (which has latitude tick marks as it goes up the page).
Parent
Re:Zonk (Score:5, Funny)
From this day forward all badly formed posts shall be known as Zonks.
Parent
Re:Zonk (Score:4, Funny)
Parent
Re:Zonk (Score:5, Informative)
And then the tags got stripped somehow.
Parent
Re: (Score:3, Interesting)
Re: (Score:3, Funny)
I may have thrown rocks at my neighbor from time to time.
Re: (Score:3, Insightful)
Re:Damn... (Score:5, Funny)
Parent
Re: (Score:3, Insightful)
Now when will the first 1TB drive come out with a name I can trust? (Seriously, how they never retired the DeskStar name is beyond me.)
If you don't know what I mean... [wikipedia.org]