On Sat, Dec 20, 2008 at 02:36:43AM -0800, Slawek Drabot wrote:
> If that were true, the contents of /boot would be the same as
> /opt/ltsp/i386/boot and /var/lib/tftpboot/ltsp/i386
no.
> the content is different therefore the process for generating the relevant
> files must be different
if you install a custom kernel package in the chroot, there should be hooks in
the chroot that ensure that the generated initramfs is configured to handle
network booting; that's what handles the differences. at least that's how it's
implemented in debian and ubuntu, and i'm pretty sure the other distros mostly
follow suit. but the package containing the kernel doesn't need anything
LTSP specific.
> btw. using mknbi, the man page states:
>
> "If you are looking to boot using PXE, look no further, mknbi is not what you
> want. You probably want something like PXELINUX which is part of the SYSLINUX
> package."
>
> should I "look no further" or "mknbi is not what I want"?
>
> in other words, is that "look further, mknbi is not what you want" or "look
> no further, mknbi IS what you want"?
if you wanted to use Etherboot instead of PXE, then you might need mknbi,
mkelfimage, or another wrapper utility. if you just want to use the PXE
implementation that comes with most networking cards, then pxelinux is all you
should need.
live well,
vagrant
------------------------------------------------------------------------------
_____________________________________________________________________
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
