ChromeOS Will No Longer Support Ext2/3/4 On External Drives/SD Cards
An anonymous reader writes Chrome OS is based on the Linux kernel and designed by Google to work with web applications and installed applications. Chromebook is one of the best selling laptops on Amazon. However, devs decided to drop support for ext2/3/4 on external drivers and SD card. It seems that ChromiumOS developers can't implement a script or feature to relabel EXT volumes in the left nav that is insertable and has RW privileges using Files.app. Given that this is the main filesystem in Linux, and is thereby automatically well supported by anything that leverages Linux, this choice makes absolutely no sense. Google may want to drop support for external storage and push the cloud storage on everyone. Overall Linux users and community members are not happy at all.
Whenever Chromebooks and ChromeOS comes up, somebody always points out those Amazon stats.
But are they actually legitimate sales?
By that, I'm asking if people actually bought these devices because they wanted to use them as Chromebooks running ChromeOS.
How many were technically-naive purchasers merely buying the cheapest laptops available, thinking they were typical Windows laptops, and not realizing that ChromeOS is actually so crippled?
How many were technically-savvy purchasers merely buying them so they could replace ChromeOS with a real Linux distro or some other OS?
Did anyone actually buy them intending to use ChromeOS?
By the way, what a horrendous summary.
Sergey Brin needs to remind himself what country he escaped as a child and stop helping American versions of the FSB from growing their powers. Of-course he hasn't been through a TSA experience himself and I am sure his and his family privacy are safe from Google's data mining operation, but he should not kid himself, he is on a special list of persons of interest, USA powers that be are certainly paying close attention to high profile targets like Brin and other influential and wealthy individuals. Does he really want to increase their powers? It would be a grave error on his part because private property rights are quite transient in the United Socialist States of Republicans (and Democrats).
Keeping all private information on line, where it can be data mined by Google and the NSA is profitable for Google but it also grows the power of the state and people should think really hard about letting the state have all that power.
You can't handle the truth.
tely agree
CLI paste? paste.pr0.tips!
I think the article hits it head-on about pushing users toward cloud storage, specifically Google Drive. I just got a Droid Maxx with KitKat and was shocked to find they had removed the ability to mount USB drives via USB OTG. Had to root my phone and install USB OTG Helper to have that basic functionality again. Obviously, the support is still there in the kernel; just the userspace access was removed, and USB OTG Helper was able to mount my flash drives successfully, even NTFS. Did I mention the Droid Maxx (made by Motorola after Google's acquisition) lacks an SD card? The 32 GB model was discontinued, so this is the 16 GB version and a Verizon exclusive, so you KNOW it's full of unremovable bloatware further depleting its limited, unexpandable storage. They tried to justify this by including 50 GB of Google Drive space for 2 years, but cloud storage should not be a replacement for local storage, only a supplement. Also, what if I did jump in feet-first and use all that extra space? What happens to my data 2 years from now? It's essentially being held hostage by the free "trial". Thankfully I only use cloud storage as off-site backup for important documents; I also store them in encrypted containers to prevent them from being data mined. Also, cloud storage is a pain when you have metered internet. I love me some Google products, but their "don't be evil" philosophy has gone out the window long ago.
The target market for the units isn't uber-geeks, it's home users. Those home users will virtually always be inserting memory cards from their camera and attaching external drives they picked up at the local electronics store. As long as the boxes can talk to those, Google is fine.
Why bother developing, testing, and supporting a feature that few in their target market will ever use?
Google Apps, combined with Chromebooks is a very compelling platform for schools.
We are deploying tons of these. They are cheap to buy, easy to manage, and great for 90% of the work that students are asked to do. (We use Macs for the other 10%).
When a kid drops a $1000 Macbook, I cringe. I cringe at the cost, and at the loss of whatever data that kid saved to his/her desktop. When that same kid drops a $250 chromebook, the hardware loss isn't too terrible, and I know that kid's data is saved to their Google Drive - automatically.
These things are fantastic in schools.
Probably most of them. The drivers don't exist for Windows, and installing a Linux distro is a little more complicated than you might hope for. Plus, there are some actual benefits to ChomeOS, mostly that it will back up your files for you, and that it boots in seconds (maybe a total of ten seconds from clicking reboot to having all the browser windows open again), but it's also more secure than Linux. Security is achieved at the cost of making it hard to change the system.
Also keep in mind, these things ship with a 16GB SSD. You can install a couple Linux distributions in that space, but it's pretty cramped for any sort of content: you're not going to be gaming or torrenting very much. Increasing the storage is possible, but if you're going to buy a $200 laptop and a $100 SSD, you may as well buy a real laptop.
Generally speaking, it's a nice, cheap, internet appliance, for those who want a keyboard instead of a touchscreen. It's really not that bad of a user experience. I have been leaving mine around the house for the roommates; they browse the web, listen to music, watch movies, and type their resumes. I don't know what other features you think it needs.
Those who advocate genocide deserve every protection afforded by law, and none afforded by common human decency.
Same here. I had used Linix exclusively for fifteen years, so I installed a full-featured Linux distribution for dual boot. It's never been booted to the big Linux except that one day. ChromeOS does everything we've ever wanted to do on a small machine. Almost everything I do with my $2,500 big machine could be done within ChromeOS too, but for some things you want a 22 inch screen.
Last time I tried, linux couldn't fsck or chkdsk the NTFS file system. Need to boot into Windows.
So, with this Chrome thing you can use an external hard drive, but if it's become corrupt you need a Windows laptop or desktop to fix the drive's content.
But maybe file system checks are deemed too confusing and are inaccessible from the GUI regardless of the file system, I don't know.
Ext 2/3/4 and any filesystem that records file ownership (especially numeric uids/gids) is not suitable for storage that's not associated with a particular system's user account database (/etc/passwd or otherwise). Linux could attempt to support such usage by virtualizing/remapping uids for "external" ext2/3/4-formatted drives, but it doesn't. Instead, you have a situation where file ownership is just silently wrong when you plug the drive into a different computer. So removing support is a big hammer, but I see how they could see it as a justifiable one when the status quo is broken like this.
If you read one of the last comments, they appear to have listened and are considering reconsidering this decision.
Which marks the difference between a professional development shop such as Google, and Lennart Poettering.
For linux tips: http://www.linuxtipsblog.com
From reading the linked proposal to drop ext2/3/4 support, there has been a lot of pushback from users, particularly developers and other power users. As far as I can gather, especially from comment #101, they are taking this feedback very seriously, and are looking into either making ext2/3/4 work with the feature that was supposedly the reason for dropping support, and/or finding an alternative way of supporting external drives with those file systems.
To me, this smells a lot like a couple of developers thinking they could pull a fast one and drop file systems they considered "unneeded", but now that feedback has been received, the overall feeling I get is "let's find a way to make this work". There may also have been a possible security risk with rogue disk images that needs to be handled.
Eat the rich.
Once a student has completed all of a teacher's assignments, what should the student be doing while sitting quietly between having completed the assignments and the bell other than games?
Perish the thought that they might--in a classroom, of all places--find a book to read.
Il n'y a pas de Planet B.