Subject: kern/18027: RB_ASKNAME should prompt for path to init(8)
To: None <gnats-bugs@gnats.netbsd.org>
From: None <lukem@netbsd.org>
List: netbsd-bugs
Date: 08/22/2002 10:59:09
>Number: 18027
>Category: kern
>Synopsis: RB_ASKNAME should prompt for path to init(8)
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: kern-bug-people
>State: open
>Class: change-request
>Submitter-Id: net
>Arrival-Date: Wed Aug 21 18:00:01 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator: Luke Mewburn
>Release: NetBSD 1.6_BETA3
>Organization:
>Environment:
System: NetBSD argo.mewburn.net 1.6_BETA3 NetBSD 1.6_BETA3 (ARGO from GENERIC-$Revision: 1.491 $) #1: Fri Jun 28 08:52:16 EST 2002 lukem@argo.mewburn.net:/var/scratch/obj.i386/usr/src/sys/arch/i386/compile/ARGO i386
Architecture: i386
Machine: i386
>Description:
whilst testing a dynamically linked /sbin/init, it occurred to
me that "boot -a" (which sets RB_ASKNAME) could also prompt
for the path to init, so you could answer "/rescue/init" (for
example) in a recovery situation
>How-To-Repeat:
boot with a borken /sbin/init, and missing or non-functioning
/sbin/init.bak and /sbin/oinit. consider your options...
>Fix:
whip up some code in sys/kern/init_main.c::start_init().
could probably clean up how the loop works as well, but that's
a separate issue, as is adding "/rescue/init" to the list of
names to try.
>Release-Note:
>Audit-Trail:
>Unformatted: