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. 2. For all other points, I perfectly agree with you that it is not the responsability of init scripts to deal with user problems 3. can someone responsible of the initscripts tell us his point of view ? 4. Prends un dany, ca ira mieux ;) Pascal > > 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
