Hi, I'm working on afew alix based devices working under voyage 0.6 with a custom kernel. I found that one of this devices had the file system corrupt (I'm using ext2 in some devices and ext3 in some other devices I don't remember if it was one or the other, but I don't think this is relevant to the problem). When I looked at the mount count it almost doubled the amount that should trigger the automatic fsck on boot. I been trying to find why fsck hasn't run at boot time even with that mount count and with a filesystem state of not clean (the only reason I can think of is that due some packages installed the filesystem is always in rw mode once set that way). I'd like to have fsck up and running again on boot time. Any ideas? Thank you!
-- Jordi Soucheiron Software Engineer DEXMA Parc Tecnològic la Salle Sant Joan de la Salle, 42 08022 Barcelona t/f: [+34] 93 181 01 95 www.dexmatech.com [email protected] _______________________________________________ Voyage-linux mailing list [email protected] http://list.voyage.hk/mailman/listinfo/voyage-linux
