Skip to contentSkip to conversation

question \ information request on init \ boot sequence when using initrd

DISCUSSION Stuart Lynne 2 participants 2 messages Mar 27, 2001 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

#1 lore raw

In article <[email protected]>,

Quoted 39 lines · Amit D Chaudhary

Hi,

We(my team) had some questions regarding booting from initrd and using /linuxrc. It will help someone(David, Werner,...) can give their thoughts on this.

To put it in brief, since running sbin/init from /linuxrc as resulting in init not having PID 1 and thereby not doing some initialization as expected.

Thereby instead of loading running /sbin/init, we just set /proc/sys/kernel/real-root-dev to /dev/ram0's value which then does the following
runs 2 statements in init/main.c to unlock_kernel and free init memory and then run sbin/init.
This results in /sbin/init running fine.

Is this ok or should be modify /sbin/init to run properly inspite of PID <> 1 or is there a 3rd way of doing this?

mkdir initrd
../bin/pivot_root . initrd

exec sbin/chroot . sbin/init.new 3 <dev/console >dev/console 2>&1

The above results in init running with PID != 1 and thereby skipping some relevant processing my default. see ps output below:

Instead of the "chroot" above is changed to following
exec sbin/chroot . sh -c 'bin/mount proc proc -t proc; echo 0x01000000 > proc/sys/kernel/real-root-dev'
And linuxrc exits

(none):root> ps -e
PID TTY TIME CMD

Quoted 16 lines
    1 ?        00:00:04 swapper
    2 ?        00:00:00 keventd
    3 ?        00:00:00 kswapd
    4 ?        00:00:00 kreclaimd
    5 ?        00:00:00 bdflush
    6 ?        00:00:00 kupdate
    7 ?        00:00:00 mtdblockd
    8 ?        00:00:00 init
   26 ?        00:00:00 sh
   39 ?        00:00:00 portmap
   50 ?        00:00:00 ypbind
   51 ?        00:00:00 ypbind
   84 ?        00:00:00 inetd
   93 ?        00:00:00 syslogd
  100 ?        00:00:00 klogd
  119 ?        00:00:00 ps

You can run your linuxrc with:

init=/linuxrc

and then end your /linuxrc with:

exec /sbin/init

Signature · 4 lines
                                            __O 
Lineo - For Embedded Linux Solutions      _-\<,_ 
PGP Fingerprint: 28 E2 A0 15 99 62 9A 00 (_)/ (_) 88 EC A3 EE 2D 1C 15 68
Stuart Lynne <[email protected]>       www.fireplug.net        604-461-7532
#2 lore raw
Quoted 2 lines · Stuart Lynne

In article <[email protected]>,
Amit D Chaudhary <[email protected]> wrote:

[snip]

Quoted 3 lines

You can run your linuxrc with:

init=/linuxrc

Yes.

Quoted 3 lines

and then end your /linuxrc with:

exec /sbin/init

No. He's doing a pivot_root to a new root filesystem. You have to do the 'exec chroot . /sbin/init ...' command given in the file Documentation/initrd.txt in order for init to start up correctly.

Having played with pivoting to a ramfs out of an initrd for the last several days, I can think of a couple of possible problems. The first is that Amit's final linuxrc command:

Quoted 1 line

exec sbin/chroot . sbin/init.new 3 <dev/console >dev/console 2>&1

is different from what's described in initrd.txt. I'm using the exact line that's in there in my linuxrc, and it works fine. Amit, try changing that line to:

exec chroot . /sbin/init.new 3 <dev/console >dev/console 2>&1

and see if that works. This does require having chroot in your initrd, but that is mentioned in initrd.txt as a requirement anyways. If init.new is the wrapper that I think was mentioned here previously, I'd suggest just trying a regular init and doing the umount and free of the ramdisk later somewhere in your rc.sysinit or equivalent.

The second potential problem I can think of would be a missing dev/console node in the new root filesystem. I think I experienced a similar failure mode once last Friday; it may have been the time I forgot to mount devfs on /dev in my new root filesystem.

Scott

--
=============================================================================
Scott Murray email: [email protected]
http://www.spiteful.org (coming soon) ICQ: 10602428
-----------------------------------------------------------------------------
"Good, bad ... I'm the guy with the gun." - Ash, "Army of Darkness"