lkml.org 
[lkml]   [1998]   [Apr]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Date
SubjectRe: 2.1.95 freezes were my fault; kmod patch
>> = Adam Richter
> = Peter Anvin
>> switch to the new root by doing "exec chroot /mnt /sbin/init" rather
>> than exiting to enable initial ramdisks that can select from more than
>> one possibility for finding the actual root partition (e.g., bringing
>> up a screen that says "boot from CDROM or boot from network?").
>> Please do not remove that functionality.

>Why? Shouldn't this be set by putting the proper values in the
>relevant /proc/sys entries before exiting from linuxrc?

In addition to the examples I gave in my previous message, I would
like to add that I want better error handling than the kernel
can provide. If the mount fails (even if the initial ramdisk was
able to do a successful test mount and unmount), I want to be able
to recover and handle the error, get further instructions from the user,
whatever. It is also conceivable that I may want to chroot to something
that is not at the top of a mount point. For example, I may want to create
and then chroot to /mountpoint/disklessworkstation-<ethernet_address>.
Admittedly, this last example is something that I just contrived
right now. Anyhow, it just goes to show how much more flexible
this facility is when it is left to userland.

Adam J. Richter __ ______________ 4880 Stevens Creek Blvd, Suite 205
adam@yggdrasil.com \ / San Jose, California 95129-1034
+1 408 261-6630 | g g d r a s i l United States of America
fax +1 408 261-6631 "Free Software For The Rest Of Us."

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu

\
 
 \ /
  Last update: 2005-03-22 13:42    [W:0.579 / U:0.020 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site