Of course having looked at this for a couple of days I found the answer to
my own question ten minutes after the post

You have to be clever enough to append the correct arguments to the kernel
boot command :-(

append root=/dev/ram0 initrd=initrd.ltsp init=/linuxrc rw

and NOT

append ram=/dev/ram0 initrd=initrd.ltsp init=/linuxrc rw

Thanks to anybody who thought about this anyway.


| Ian Neilson


> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Ian
> Neilson
> Sent: 01 August 2002 14:33
> To: LTSP-Discuss
> Subject: [Ltsp-discuss] Problem exec'ing /sbin/init with PID 7
>
>
> Does anybody have any ideas why my /linuxrc script should be running with
> a PID of 7 ? This causes /sbin/init to fall over as in log below.
> I've seen
> some similar questions in other newsgroup archives but no answers
> as to what
> I've done or missed in my configuration.
>
> The kernel is built using the config-2.4.18-ltsp-1 from the LTSP
> initrd-kit
> download with sources from ftp.kernel.org.
>
> The initrd is built using the buildk script from the initrd-kit
>
> The kernel and initrd are then loaded by pxelinux and then
> everything seems
> to be going fine until /linuxrc finishes.
>
> Thanks for any advice.
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> ~~~~~~~~~~
> ~~~
>
> Loading vmlinuz..............
> NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
> RAMDISK: Compressed image found at block 0
> Freeing initrd memory: 718k freed
> VFS: Mounted root (ext2 filesystem).
> ==================================================================
> ==========
> ===
> Running /linuxrc
> Mounting /proc
> linuxrc: Installing eepro100 driver
> modprobe eepro100
> /sbin/insmod /lib/modules/2.4.18-ltsp-1/kernel/drivers/net/eepro100.o
> Using /lib/modules/2.4.18-ltsp-1/kernel/drivers/net/eepro100.o
> Symbol version prefix ''
> eepro100.c:v1.09j-t 9/29/99 Donald Becker
> http://www.scyld.com/network/eepro100.
> html
> eepro100.c: $Revision: 1.36 $ 2000/11/17 Modified by Andrey V. Savochkin
> <saw@sa
> w.sw.com.sg> and others
> eth0: OEM i82557/i82558 10/100 Ethernet, 00:D0:B7:B8:6F:C8, IRQ 10.
>   Board assembly 000000-000, Physical connectors present: RJ45
>   Primary interface chip i82555 PHY #1.
>   General self-test: passed.
>   Serial sub-system self-test: passed.
>   Internal registers self-test: passed.
>   ROM checksum self-test: passed (0x04f4518b).
> Running dhclient
> Mounting root filesystem: /opt/ltsp/i386 from: xxx.xxx.xxx.xxx
> Doing the pivot_root
> Mounting the devfs filesystem
> Running /sbin/init as PID 7        <<<<< I changed it only here
> to print PID
> Usage: init 0123456SsQqAaBbCcUu    <<<<<< Falls over here
> VFS: Cannot open root device "" or 03:01
> Please append a correct "root=" boot option
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> ~~~~~~~~~~
> ~~~
>
> | Ian Neilson
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _____________________________________________________________________
> Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
>       https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
> For additional LTSP help,   try #ltsp channel on irc.openprojects.net
>



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_____________________________________________________________________
Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
      https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help,   try #ltsp channel on irc.openprojects.net

Reply via email to