On 2011-11-30 05:37, Stefan Schmidt wrote:
Hello.
On Wed, 2011-11-30 at 05:19, Gary Thomas wrote:
The file /etc/filesystems is used by busybox 'mount' when
attempting to mount a file system when the type is not
specified. This change alters the order so that more
capable systems are tried first. Without this change, an
EXT3 system will mount as EXT2 which disables many of the
EXT3 features. With the change, EXT3 systems are mounted
properly.
Signed-off-by: Gary Thomas<[email protected]>
---
.../recipes-core/base-files/base-files/filesystems | 8 ++++----
meta/recipes-core/base-files/base-files_3.0.14.bb | 2 +-
2 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/meta/recipes-core/base-files/base-files/filesystems
b/meta/recipes-core/base-files/base-files/filesystems
index 2af6a7e..14f5abb 100644
--- a/meta/recipes-core/base-files/base-files/filesystems
+++ b/meta/recipes-core/base-files/base-files/filesystems
@@ -1,7 +1,7 @@
-minix
-fat
-vfat
-ext2
ext3
+ext2
+vfat
+fat
btrfs
+minix
In the commit message you explain the problem with ext2/3. And I agree
that it makes sense to start with ext3. Actually, adding ext4 would
make sense, too.
Agreed.
What is the deal with the re-ordering of fat/vfat/minix though? Looks
unrelated to me.
Same argument as above - try more capable file systems first.
I also moved minix to the end as it is rarely, if ever, used.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
