Date: Sun, 6 Aug 2000 03:21:50 +0200
From: Marcus Brinkmann <[EMAIL PROTECTED]>
However, I think my result is partly the result of mke2fs -o hurd setting
the filetype feature on linux. Ted, can you make the default of -O be
dependant on the -o option instead on the system you run the command?
(The default of the -o option is of course system specific, which is fine).
I'm not sure what you're talking about. This is what happens.
mke2fs -o hurd should always disable the filetype feature by default,
regardless if called from linux or not.
If you Read The Fine Source code, you'll find:
/*
* For the Hurd, we will turn off filetype since it doesn't
* support it.
*/
if (fs->super->s_creator_os == EXT2_OS_HURD)
fs->super->s_feature_incompat &=
~EXT2_FEATURE_INCOMPAT_FILETYPE;
The other thing that could be changed is: If filetype is disabled, let "yes"
be the default answer on the question: File with filetype found, clear it?
Just as setting the filetype is also done without asking.
If you convert an existing hurd fs, this helps a lot (you could provide -y,
but then you might miss more serious messages).
Uh, it is the default. Or I'm badly misinterpreting your question:
e2fsck 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09
The Hurd does not support the filetype feature.
Clear<y>? yes
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Entry '.' in / (2) has filetype set
Clear<y>?
Or are you saying it should just clear the filetype without asking?
This situation shouldn't happen all that often in practice anyway; it
should only happen for those folks who used development snapshots of
1.19 to create Hurd filesystems.
- Ted
