pascal <[EMAIL PROTECTED]> writes: > Le Jeudi 28 F�vrier 2002 00:06, Guillaume Cottenceau a �crit : > <snip> > > Yes, you're in trouble. The same as if you "dd if=/dev/zero > > of=/dev/hda", etc. You can do a lot of bad things touching to > > your system... > > > > you cannot compare a complete disaster (not recoverable), to a situation where > a little mistake renders the system unbootable because of what we can > consider a LOGICAL BUG in /etc/rc.sysinit.
i don't include myself in your "we". > > I'm not gonna add a check for that situation, we'd need to add > > another hundred of checks for errors that could happen with the > > same frequency.. > > Then just tell us what kind of situation can lead to fsck refusing to work, > appart a disaster, which i dont discuss here ? 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. including for example removing /etc/inittab. do you really think /sbin/init should consider this situation and have a "default" inittab only for people dumb enough to remove /etc/inittab and then to yell? that's what the rescue is for, though. for all the situations where you can't boot anymore because you're made a mistake (and we all do). > the problem here is quite simple : rs.sysinit is trapping us into a boot loop > on a system that is perfectly bootable ! this is not acceptable. at least we > must fix rc.sysinit in order to permit the system to boot in this situation, > don't you agree ? 1- i'm not authoritative to talk about the initscripts 2- my personal opinion is "no", i don't think we should begin to consider all possible ways of destroying your machine and try to always boot fine with them -- Guillaume Cottenceau - http://www.frozen-bubble.org/
