As per: http://www.phoronix.com/scan.php?page=news_item&px=MTgxMTg
So thoughts? I never really cared about ChromeOS but I find it very
strange why google would take time to drop support for ext*…
–
openSUSE Factory 64 bit
KDE 4.14.0
Maybe they found a CVE in ext* and wanted to avoid it lol!.
Decision reportedly reversed.
Rebellion sees Chromium reverse plans to dump EXT filesystem • The Register
On 10/13/2014 11:06 AM, rafter22 wrote:
>
> Decision reportedly reversed.
>
> ‘Rebellion sees Chromium reverse plans to dump EXT filesystem • The
> Register’ (http://tinyurl.com/nmaycou)
>
>
Maybe I am not reading it right but where does it say they are bringing
back the support? All I saw was a developer saying they are “confident
we can improve the situation” which just sounds like PR speak/damage
control.
If they went to the trouble of removing support, I find it unlikely they
would revert back after the negative reaction (which they likely
anticipated), especially so quickly.
–
openSUSE Factory 64 bit
KDE 4.14.0
On 10/13/2014 11:44 AM, alanbortu wrote:
> On 10/13/2014 11:06 AM, rafter22 wrote:
>>
>> Decision reportedly reversed.
>>
>> ‘Rebellion sees Chromium reverse plans to dump EXT filesystem • The
>> Register’ (http://tinyurl.com/nmaycou)
>>
>>
>
> Maybe I am not reading it right but where does it say they are bringing
> back the support? All I saw was a developer saying they are “confident
> we can improve the situation” which just sounds like PR speak/damage
> control.
>
> If they went to the trouble of removing support, I find it unlikely they
> would revert back after the negative reaction (which they likely
> anticipated), especially so quickly.
>
To add to this, I noticed
https://code.google.com/p/chromium/issues/detail?id=315401#c101
“We should reconsider this decision until we have a long term solution
for supporting ext* in place (e.g., that proposed by agoode@ in issue
422764). The intermediate compromise of disabling rename or returning an
error on rename seems perfectly reasonable, at the very least. If
there’s a security concern here, please link to it.”
So they might be adding a way for chromos to support ext*
–
openSUSE Factory 64 bit
KDE 4.14.0
Why does Google need EXT?
Not google but chrome os is based on linux os and not having support for etx* even on an external device is a bit surpising, but thats just coming from a lowlife linux user point of view 
It seems like enough people was complaining so they revert the decision, or do I misunderstand this:
…re-enables the support of ext2/3/4 filesystem in cros-disks.
This CL updates platform_CrosDisksFilesystem ext2/3/4 tests to verify
that mounting of ext2/3/4 filesystems via cros-disks succeeds again…
https://chromium-review.googlesource.com/#/c/223383/
regards