Subject: Re: RFC: migration to a fully dynamically linked system
To: der Mouse <mouse@Rodents.Montreal.QC.CA>
From: Ignatios Souvatzis <>
List: tech-userlevel
Date: 12/26/2001 18:37:46
On Wed, Dec 26, 2001 at 08:21:55AM -0500, der Mouse wrote:
> > As to /sbin/init; there's a couple of solutions:
> [...]
> > 	  Provide /sbin/init.static and/or /recovery/sbin/static
> > 	  (see below for more info about recovery options), and add
> > 	  those paths to the list of paths (listpaths[]) that
> > 	  sys/kern/init_main.c::start_init() tries to exec.
> You mean the kernel still has a hardwired list of paths?  Ages ago I
> added code so that if the exec of init fails, or if an option
> (RB_INITPATH) is provided by the MD boot code, it prompts for a
> pathname for init.

Hm... doesn't Linux provide some similar functionality, resulting in instant
root access (for the knowledgable) in Linux-equipped student workstation 
pools? Of course, it's hard (nearly impossible) to secure a machine with
semi-public physical access...