Subject: Re: /sbin/init failure
To: None <port-i386@NetBSD.org>
From: der Mouse <mouse@Rodents.Montreal.QC.CA>
List: port-i386
Date: 04/15/2005 22:35:42
>> exec /sbin/init: error 20
>> exec /sbin/oinit: error 20
>> exec /sbin/init.bak: error 20
>> init: not found
>> panic: no init
Is there any reason why the kernel doesn't prompt for an init path when
the attempt to exec init fails, rather than panicking and making the
user reboot with the appropriate flag? That's always seemed to me to
be much the more suitable response, and it isn't even very hard to do.
/~\ The ASCII der Mouse
\ / Ribbon Campaign
X Against HTML mouse@rodents.montreal.qc.ca
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B