|
| Authored by: SpaceLifeForm on Saturday, June 30 2012 @ 10:48 PM EDT |
Well, on my rooted motodroid,
which is 2.6.32.9 kernel, I have
3 modules for ext2, 3, and 4.
All in increasing size, BTW.
Ext2 and ext3 are not abandoned by any means.
And I don't want ext3 or ext4
for two reasons.
One, I don't want the extra writes
for journaling to the sdcard, and two,
ext3 and ext4 are buggy and not trustable.
I'll take my chances with ext2 and having
to run e2fsck. I partition the sdcards,
and keep part1 as VFAT to keep Android happy,
and the rest are ext2.
On desktops or servers, I use ext2 or xfs, maybe
even minux when I am hacking for small size.
Never ext3 (corruption during recovery post boot),
never ext4 (filesystem lockup under heavy load).
And even if you have ext2 support from windows,
you know Microsoft will break it at some point.
So, use VFAT where needed to move files between
windows and Linux or OSX.
And don't depend on any filesystem features
that you would expect under Linux such as keeping
permissions, ownership, etc.
And let Microsoft try to sue the world over it.
---
You are being MICROattacked, from various angles, in a SOFT manner.[ Reply to This | Parent | # ]
|
| |
| Authored by: Anonymous on Sunday, July 01 2012 @ 09:05 AM EDT |
> And in case some people here don't know, the ext set of
> filesystems are "compatible supersets"
That's true between ext2 and ext3, but not so for ext4, which is very
different.
I'd be wary of putting ext4 drivers into the hands of inexperienced Windows
users; it has a tendency to lose data, particularly if a volume is removed
without being properly unmounted. I'd stick with ext2/3 (depending on whether or
not journalling support is appropriate).
[ Reply to This | Parent | # ]
|
|
|
|
