Le Jeudi 28 F�vrier 2002 15:01, pascal a �crit : > Le Jeudi 28 F�vrier 2002 13:37, Borsenkow Andrej a �crit : > > > Le Jeudi 28 F�vrier 2002 12:59, Guillaume Cottenceau a �crit : > > > > if you're root, you can do many things leading to a situation > > > > where you can't boot, because you may set things up a very > > > > illogical way. > > > > > > Guillaume, > > > > > > 1. The machine is not destroyed in the situation I describe. It is > > > > perfectly > > > > > functionnal but rc.sysinit will NOT ALLOW the user to boot it. This is > > > > the > > > > > point I am trying to be understood here. > > > > I must agree here. If you are using journaling fs for root it is > > perfectly legal (even if not advisable) to mount it rw on boot. This is > > not an error and must be supported (actually I am surprised to know it > > does not work now. It worked all the time before). > > > > -andrej > > I'm running ext3 on my ROOTFS. Actually fsck does not like to check a > mounted FS, which is normal. But rc.sysinit takes this for an error and > drops us to a maintenance shell. Just try to rebuild an initrd with rootfs > rw in /etc/fstab, rebuild the boot loader then reboot, instant nitemare :) > Pascal
Addon : the problem does not appear with ROOTFS as Reiserfs fsck does not complain in this case, so rc.sysinit continue to boot. Pascal
