RE: [Ltsp-discuss] I want to use a ram disk as / after network boot.

[Jim M. <jam@McQuil.com>]

The error about /sbin/init not found is more likely a failure to find
the dynamic linker '/lib/ld-linux.so.2', which is part of glibc.

The /sbin/init, and any other binaries from the /opt/ltsp/i386 tree are
all needing glibc.  The initrd image is built with uClibc.

You'll probably need to build a complete initrd with the right
libraries.

Jim McQuillan
jam@Ltsp.org



On Tue, 30 Aug 2005, hckimm2 wrote:

>
> I used ltsp_initrd_kit.
> And I added some initial files in root file system including 'sbin/init'
> and copied a number of files from /opt/ltsp/i386 of ltsp tools.
> I edited linuxrc file and erased some lines related to  NFS mouning and
> pivot_root like below.
> But I could only an error written that could not find "/sbin/init" file
> I think root file system was disappeared after executing linuxrc.
>
> What did I missing. What should I change in linuxrc file.
>
> Thanks.
>
>
> . /etc/dhcpc/dhcpcd-eth0.info
> #
> # If a root-path has been specified on the kernel cmdline, then use it
> #
> if [ -n "${RP}" ]; then
>   ROOTPATH=${RP}
> fi
>
> #
> # Check for a root-path from the dhcp server
> #
> [ "${INITRD_DBG}" = "7" ] && exec /bin/sh
> if [ -z "${ROOTPATH}" ]; then
>     [ -w /proc/progress ] && echo f >/proc/progress
>     echo
>     echo "ERROR!  No root-path.  Check your DHCP configuration, to make"
>     echo "        sure that the 'option root-path' is specified"
>     echo
>     cat /etc/dhcpc/dhcpcd-eth0.info
>     exit 1
> fi
> ###################################
> ##### erased line #################
> ###################################
> echo "Running /sbin/init"
> exec /sbin/init
>
>
>
>
> -----Original Message-----
> From: lts...@li...
> [mailto:lts...@li...] On Behalf Of Ken
> Cobler
> Sent: Tuesday, August 30, 2005 9:00 PM
> To: ja...@ti...
> Cc: lts...@li...
> Subject: Re: [Ltsp-discuss] I want to use a ram disk as / after network
>
> ja...@ti... wrote:
>
> >On Tuesday 30 August 2005 11:23,
> lts...@li...
> >wrote:
> >
> >
> >>HCK,
> >>
> >>just use the initrd for your ramdisk.  Rather than doing a NFS mount,
> >>and a pivot-root, just put all the stuff you need into your initrd,
> and
> >>at the end of /linuxrc, run /sbin/init.
> >>
> >>If you are using a 2.6 kernel, take a look at initramfs, rather than
> >>initrd.  It's a bit more flexible.
> >>
> >>Jim McQuillan
> >>jam@Ltsp.org
> >>
> >>On Sat, 27 Aug 2005, hckimm2 wrote:
> >>
> >>
> >>>Hi
> >>>
> >>>I am an engineer who is making communication systems.
> >>>I have a board(made by Kontron ltd, Intel CPU, currently with
> diskless )
> >>>that is used in compactPCI.
> >>>I boot that board with network PXELINUX method and currently using
> NFS.
> >>>But I don't want to use NFS and I want to make and use ram disk
> image.
> >>>That means I want to use a ram disk as / after network booting.
> >>>Currently I made a initrd by ltsp_initrd_kit.
> >>>What should I have to change in 'linuxrc' file and
> pxelinux.cfg/default
> >>>file. And how can I make ram disk image.
> >>>
> >>>
> >
> >I'd love to hear pros/cons of using the initrd for ever, vs using the
> initrd
> >to unwind a root fs into ram, then pivot root to ram. I've done both.
> >
> >The only caveat I've got: if you unwind a usb-mem stick (even a fast
> stick)
> >it's s--o-- s--l--o--w-- (100s K/sec no Ms/sec!!)
> >
> >
> initrd purpose is to load an initial filesystem in ramdisk memory.  What
>
> programs are called in that initrd is up to you (edit your linuxrc file
> accordingly).
>
> The only potential drawback I could see to using a initrd only root FS
> is the initrd file could get so large that it would not all fit into
> memory.  To correct, it would require a special kernel built to make
> initrd image as large as you need.  Not an impossible problem to work
> around.
>
>
> The memory stick is slow because of the technology (slow writes,
> slightly improved reads). Memory sticks are meant for a convenient
> replacement for floppies.  I have a boot version of Linux working with a
>
> USB memory stick.  It does work, but, I agree is slow.  However, it
> makes it very convenient to load a complete Linux OS (with GUI) on a
> memory stick, go to a Windows computer that supports booting from USB
> device, and boot into Linux without touching the Windows drive.
>
> Ken Cobler
>
>
> -------------------------------------------------------
> SF.Net email is Sponsored by the Better Software Conference & EXPO
> September 19-22, 2005 * San Francisco, CA * Development Lifecycle
> Practices
> Agile & Plan-Driven Development * Managing Projects & Teams * Testing &
> QA
> Security * Process Improvement & Measurement *
> http://www.sqe.com/bsce5sf
> _____________________________________________________________________
> 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.freenode.net
>
>
>
> -------------------------------------------------------
> SF.Net email is Sponsored by the Better Software Conference & EXPO
> September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
> Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
> Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
> _____________________________________________________________________
> 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.freenode.net
>