Someone over at Google has decided to drop support for EXT* file-systems in favour of M$’s stuff…“Chromium OS is for consumer devices which should not need support for mounting external ext4 storage. In principle, we should drop unnecessary features. There was a case that an unnecessary feature was used for a security exploit.” This has ticked off GNU/Linux users who want to move files between other GNU/Linux operating systems and ChromeOS, including developers…
The only justifications seem to be
- EXT* support is unnecessary and increases security surface without justification – That’s kind of hard to swallow since EXT* has had very few problems that I know of and definitely is widely used by many people including developers. If consumers aren’t aware of EXT* then this move won’t impress them much. Forcing developers to change file-systems seems like the unnecessary thing here. I’ve had to add FAT-support to my custom kernels because folks wanted to use USB devices from that other OS and “partners”. I found that annoying and unnecessary. If I had a Chromebook, one of the first things I would change would be a limitation to FAT, either by tweaking ChromeOS or replacing it. Would replacing ChromeOS make Google happier?
- EXT* support is extra work – Come on. The kernel boys and girls do some, and the file-system is backwards-compatible with previous versions… What extra work? Oh, you want to rename the mount-point? Give me a break. Who does that? Give them a “file-system busy” message.
Does Google want to give a fair segment of users a reason not to use ChromeOS? What were they thinking? I’ve read endless criticism of ChromeOS on TV, in this blog, and elsewhere on the web and no one has complained that it supported EXT* file-systems, not even M$… If you want to increase the “attack-surface”, drop the file-system… 8-(