--FxavXfDenm+F7xE/
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Apr 15, 2005 at 10:35:42PM -0400, der Mouse wrote:
  | >> exec /sbin/init: error 20
  | >> exec /sbin/oinit: error 20
  | >> exec /sbin/init.bak: error 20
  | >> init: not found
  | >> panic: no init
  |=20
  | 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.

It's possible that the system has been configured to prevent use
of boot flags without a password, and your suggestion could allow
circumvention of that in this particular failure condition.
(Yes, this is probably unlikely; but I suspect there'd be at least
one user out there who is relying upon the existing behaviour...)

--FxavXfDenm+F7xE/
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (NetBSD)

iD8DBQFCYoW/pBhtmn8zJHIRArbDAJ0eVLkxZiDK/GV0RBx9MdTULB3FTgCfUOey
RKZR30j9ljFP3XebiYS1hEc=
=iMOb
-----END PGP SIGNATURE-----

--FxavXfDenm+F7xE/--