Messages in this thread |  | | | Date | Fri, 17 Apr 1998 21:00:57 +0200 | | From | Martin Schulze <> | | Subject | Re: init is pid 1 vs. initrd |
| |
On Fri, Apr 17, 1998 at 02:05:12PM -0400, Raul Miller wrote: > [I'm replying to a message I deleted.] > > I am confused by this concept of "can't call mount for initrd" > because "then init wouldn't be process 1". I mean, can't you > just create the init process first (as in: you don't have to > exec init right away)? > > Even simpler would be: on the initrd make /bin/init be a shell > script. Conceptually, it a installs some modules, remounts > root, then exec's /bin/init.
Too difficult. Why not just . use initrd . add modules . tell the kernel its root device . exit . let the kernel load its root device.
With rootfs on RAID0 I use the following as /linuxrc in initrd
#! /bin/ash
if [ -s /etc/mdtab -a -f /sbin/mdadd ] then echo "Preparing system for rootfs raid." /sbin/mdadd -ar /bin/mount -t proc /proc /proc echo 0x900 > /proc/sys/kernel/real-root-dev /bin/umount /proc else echo "No mdtab or mdadd found." fi I'm sending you a longer description in a different mail, describing this. If others are interested, drop me a line.
Regards,
Joey
-- / Martin Schulze http://home.pages.de/~joey/ / *** Fatal Error: Found [MS-Windows], joey@linux.de / / repartitioning Disk for Linux ... / [unhandled content-type:application/pgp-signature] |  |