Hi, e2fsck 1.19 will produce the following problem message on the Hurd with a filesystem that has filetypes: The Hurd does not support the filetype feature. Clear <y>? This will lead to problems with fsck --preen --writable, which is used at boot time: fsck will barf out with an UNEXPECTED INCONSISTENCY and asks to RUN fsck MANUALLY. And this although the Hurd can perfectly cope with filetypes, it just won't make use of them and won't set them. e2fsck should not bail out in this strong way. It is okay to provide some option to clear filetypes, but the default on the Hurd should be to always accept filetypes without asking. It's just annoying to report this as a problem, especially if you use both the Hurd and Linux and interchange filesystems. And if you are tricked into answering yes to the question above, e2fsck will ask for every single file if you want to clear the filetype! If you say no, it will just correct the wrong filetypes, which is fine for the Hurd. Thanks, Marcus -- `Rhubarb is no Egyptian god.' Debian http://www.debian.org Check Key server Marcus Brinkmann GNU http://www.gnu.org for public PGP Key [EMAIL PROTECTED], [EMAIL PROTECTED] PGP Key ID 36E7CD09 http://homepage.ruhr-uni-bochum.de/Marcus.Brinkmann/ [EMAIL PROTECTED]
