W
Wolf K
Why would I "decide to change file systems"? The only reason this isSo, you're saying that if you decide to change file systems, you'd ratherWolf said:On 6/4/2013 3:26 AM, NY wrote:
[...]As an aside, why do we still have dumb drives that need guidance andAs an aside, why does *anything* that stores to a filesystem or reads
from a filesystem still use FAT, given that NTFS has been the standard
for Windows PCs for many years? [...]
control from an OS? Why should the OS know or care what file system a
storage device uses?
It's way past time to for storage (and other) devices that from an OS
POV are merely data destinations and and sources. Let the device handle
everything else.
have to go out and buy a new hard drive? Or even something as "simple" as a
firmware upgrade?
even a meaningful question is precisely because the FS is linked to the
OS. As for firmware upgrades, for the vast majority of users I don't see
any need for them at all. They just don't stress their HDDs enough to
make a few percent improvement in throughput meaningful in any way. They
are far more likely to need additional storage, and that should be
completely plug'n'play.
Frankly, I don't get it. If the storage device is data source andFile systems are constantly evolving. Maybe not so much in the Windows world,
where's there's relatively few (a handful of FAT systems + a few revisions of
NTFS), but the *nix file systems see constant development. The last thing in
the world I'd want is to have to upgrade the *disk* to support the *file
system*.
target, why do you need to mess with its file system? As I understand
it, a file system defines how data is stored on the disk, and how data
is tracked. That's all. I see no reason why that shouldn't be built into
the device. Or that any upgrades to it shouldn't be done the same way as
BIOS or other firmware upgrade is done now. If you actually need an
upgrade, that is. See above.
I repeat: the OS and any attached device only need to know how to
connect, and how to exchange data. That's all. How either one
accomplishes its data processing task(s) is irrelevant to the other.
Why would you need a driver for what is essentially an address? "ThisBesides, you'd still need drivers for the disks anyway. (Modern drives *are*
a lot smarter than they used to be, but that's the hardware, not the FS.)
HDD needs a driver" means "My machine has to do stuff that the HDD can't
do for itself". Give the HDD a URL, and send/request data, just like you
do with any other URL.
I notice that my system exchanges data with systems with different OSs
all the time. Why should a HDD be any different? I can even exchange
data with computers on my home network with different OS's. So why
should any of those machines have to know stuff about their own HDDs
that they don't need to know about the HDDs in the other machines?
Bottom line: storage devices as presently designed are kluges based on
past practices, when CPUs were a lot more expensive than they are now.