[frgeek-michiana] Re: Vector Linux on LTSP server....
- From: "Mike Cook" <mikecook@xxxxxxxxxxxx>
- To: <frgeek-michiana@xxxxxxxxxxxxx>
- Date: Fri, 24 Feb 2006 22:04:46 -0500
You may not have to recompile the kernel, but it looks like you need to
create an initrd.img
from http://www.ltsp.org/documentation/index.php
8.2. Build your own kernel
There are two ways to configure a kernel for LTSP. The default method is to
use something called an 'Initial Ram Disk', or initrd for short. The initrd
image is a small filesystem that is appended to the kernel. The initrd
filesystem image is loaded into memory, and once the kernel is booted, it
will mount the ramdisk as its root filesystem. There are a couple of
advantages of using an initrd image. First, we can compile the network
drivers as modules and load the correct module during bootup. This allows a
single kernel which will support virtually all network cards. The other
advantage is that we can run the DHCP client as a "user-land" program rather
than in kernel-space. Running the client in user-land provides better
control over the options requested and received from the server. Also, it
makes the kernel slightly smaller. The other way to configure the kernel is
without the initrd. Building a kernel without an initrd requires that the
specific network card driver be statically linked into the kernel, and it
also requires that IP-Autoconfig and "Root filesystem on NFS" are set when
building the kernel. The advantage of not using an initrd is that the kernel
is slightly smaller, and it will boot slightly faster. once the workstation
is up and running, there is virtually no difference in how the workstation
functions.
The standard kernel for LTSP includes an Initial Ramdisk (initrd) that takes
care of detecting the network card, and making a user-space DHCP request. A
major goal for the image was to make it as small as possible. So, we chose
the uClinux libc replacement library, and busybox for the utilities that we
need during the boot.
If you want to build your own kernels, you should download the
ltsp_initrd_kit package. It contains the root filesystem hierarchy, and a
script for building the image.
Hope this helps,
Mike
----- Original Message -----
From: "Richard Zimmerman" <csxt@xxxxxxxxxxx>
To: "Free Geek Michiana" <frgeek-michiana@xxxxxxxxxxxxx>
Sent: Friday, February 24, 2006 12:07 AM
Subject: [frgeek-michiana] Vector Linux on LTSP server....
> Ok, after some more looking I'm NOT looking for an NFS problem... I'm
> looking to find out *IF* Vector Linux used an initrd image and WHERE it
is?
>
> From what I can tell, VL is *NOT* compiled to take advantage of the
> initrd.img file.... It's a straight vmlinuz file!
>
> Also, the following error comes across, then a kernel panic:
>
> <error>
> RAMDISK: Couldn't find valid RAM disk image starting at 0.
> VFS: Cannot open root device "nfs" or unknown-block (0,255)
> Please append a correct "root=" boot option
> Kernel panic VFS: Unable to mount root fs on unknown-block (0,255)
> </error>
>
> I'm also assuming the Vector kernel wasn't compiled with the
> CONFIG_ROOT_NFS=YES flag set :)
>
> Sooo.... the concept of setting up multiple distros on separate
> partitions is a VALID idea, we'll just have to custom compile EACH
> distro for supporting netboot / nfs to run on the LTSP Server.... :(
>
> It's after midnight... I'm pooped...
>
> Later...
>
> Goose
>
>
>
> To post to the list send email to <frgeek-michiana@xxxxxxxxxxxxxx>
>
> You may unsubscribe or change your list settings by going to the list
website at <//www.freelists.org/webpage/frgeek-michiana>
>
>
To post to the list send email to <frgeek-michiana@xxxxxxxxxxxxxx>
You may unsubscribe or change your list settings by going to the list website
at <//www.freelists.org/webpage/frgeek-michiana>
Other related posts:
