Earlier quoted context omitted.
We should create a URI standard for that; xkcd://927
Let me propose the xkcd2 scheme, to be used like xkcd2:927, because who really needs those two slashes?!
And that's why Linux desktop is going nowhere.
21–30 of 45 posts
Earlier quoted context omitted.
We should create a URI standard for that; xkcd://927
Let me propose the xkcd2 scheme, to be used like xkcd2:927, because who really needs those two slashes?!
And that's why Linux desktop is going nowhere.
Earlier quoted context omitted.
All attempts at such will fail. vfat won because it works in Windows without additional drivers. Anything you come up with to replace it will also have to work in Windows without additional drivers. It will also have have a workable implementation in what is essentially equivalent to the public domain, and be simple enough to process that hardware manufacturers can read it with a microcontroller. I would love to see…
vfat only won in the sense that if you're forced to use windows you still have to use vfat. In every other context there is a better option. I haven't needed to move files to a windows box in 15 years so—to me—it's a massive surprise anyone still uses it at all. Just don't use USB keys; they're terrible security-wise and you're forced to use technology built for your grandmother.
I live in an environment where I need to move files between several builds of Windows, Linux and macOS - and often where there is no network access because of security policy (misguided policy perhaps). Thumb Drives are the only way to function.
Just yesterday I was thinking how all of the platforms are still using vfat as a go between. There really should be a new FS "for them all"
I tend to just use ntfs for most of my external storage and cifs for network storage only because it's easier to get on my non-windows systems than nfs and ext3 are to get working on windows... ymmv though.
Just yesterday I was thinking how all of the platforms are still using vfat as a go between. There really should be a new FS "for them all"
All attempts at such will fail. vfat won because it works in Windows without additional drivers. Anything you come up with to replace it will also have to work in Windows without additional drivers. It will also have have a workable implementation in what is essentially equivalent to the public domain, and be simple enough to process that hardware manufacturers can read it with a microcontroller. I would love to see…
Earlier quoted context omitted.
vfat only won in the sense that if you're forced to use windows you still have to use vfat. In every other context there is a better option. I haven't needed to move files to a windows box in 15 years so—to me—it's a massive surprise anyone still uses it at all. Just don't use USB keys; they're terrible security-wise and you're forced to use technology built for your grandmother.
That is the only sense in which a 'universal file system' can win. There is no other context. Your personal usage habits are completely irrelevant ("I haven't had to shoot a gun since the first gulf war, so to me it's a massive surprise that anyone still fights wars at all.") I don't use USB keys. I don't have any windows systems. But I do have UEFI, and that is based on FAT as well. Disregarding my grandmother's tec…
Earlier quoted context omitted.
Let me propose the xkcd2 scheme, to be used like xkcd2:927, because who really needs those two slashes?!
My proposal: xkcd3, works as xkcd3:927 AND xkcd3://927 And that's why Linux desktop is going nowhere.
Just yesterday I was thinking how all of the platforms are still using vfat as a go between. There really should be a new FS "for them all"
All attempts at such will fail. vfat won because it works in Windows without additional drivers. Anything you come up with to replace it will also have to work in Windows without additional drivers. It will also have have a workable implementation in what is essentially equivalent to the public domain, and be simple enough to process that hardware manufacturers can read it with a microcontroller. I would love to see…
I would not understate that it is also very simple to write a driver for. The reasons for this have high overlap with the fact that the ondisk structure is crap. But it does mean that many people were able to write drivers.