Casper.Dik at sun.com wrote:

> The reason a split "/" and "/usr" is *stupid* is fairly simple; there
> are precious few scenarios which you can recover without /usr.
>
> (E.g., you can *always* mount "/" because the kernel boots from it and
> knows the boot device; but there are many scenarios where the /usr cannot
> be mounted and where recovery is not possible, e.g., when the devices
> pointing to the disk are not in the filesystem)

This has been true in former times. Since we have the devfs on /devices, this 
is most unlikely and would lead to a broken kernel.

> >Why doesn't apply the same argumentation to "libshell in the root
> >filesystem", too ?
>
> Because we need one shell and /sbin/sh suffices for now.

This is my impression too:

Let us have the smalles possible shell as /usr/bin/sh & /sbin/sh

> >- |libc::wordexp()| currently uses the old Solaris /usr/bin/ksh but
> >should use "ksh93" in the future. Since libc sits in "/lib" it may be
> >nice to have a copy of ksh93 in the root filesystem, too - otherwise
> >|libc::wordexp()| will only work when "/usr" is mounted
>
> So this currently doesn't work when /usr isn't mounted.

Correct.


> >- Replace some of the standalone commands with the libshell builtins
> >(low-hanging fruits include "sleep", "pwd", "test" etc.)
>
> All programs living in /usr

If we talk about thiese functions, I still do not understand why ksh still
not includes "sync" as builtin while my "bsh" (where I did start with
a cursor editable history between 1982 and 1984) includes the sync command
as builtin since 1982.

This did save me a lot of trouble in the 1980s with SunOS when the machine
was unresponsive but my login shell did still work. I did type sync; sync
and then powercled.


J?rg

-- 
 EMail:joerg at schily.isdn.cs.tu-berlin.de (home) J?rg Schilling D-13353 Berlin
       js at cs.tu-berlin.de                (uni)  
       schilling at fokus.fraunhofer.de     (work) Blog: 
http://schily.blogspot.com/
 URL:  http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily

Reply via email to