On 12/12/2013 1:58 AM, Alkis Georgopoulos wrote:
> Στις 11/12/2013 11:33 μμ, ο/η John Hupp έγραψε:
>> So for my case with ltsp-pnp, I would understand that the base directory
>> is not /opt/ltsp but /, and that it would default to copying kernels
>> from /boot.
> Yes, but not exactly. See how it goes:
>
> ltsp-pnp is just an easy name to refer to some LTSP administration
> techniques, it's not a separate implementation of LTSP.
>
> The relevant command is:
> ltsp-update-image -c <path>
>
> For ltsp-pnp, <path> is /.
> For NFS or other shares, it could be /path/to/nfs/share.
> For VMs, it could be /path/to/mounted/vdi/image.
>
> In all those cases, /opt/ltsp/images/image-name.img is generated and of
> course the kernel from <path>/boot is copied inside it.
>
> So yeah, ltsp-pnp copies /boot/vmlinuz inside the image.
>
>
> But then ltsp-update-kernels doesn't care about the initial <path>.
> It loop-mounts the image and extracts the kernels from inside it.
>
>
> So there's no "ltsp-update-kernels <kernel-path>" option, and for NBD,
> it wouldn't make sense to have a <kernel-path> parameter there, to
> select a kernel that isn't inside the image, because the necessary
> modules would be missing then.
>
I wrote "the base directory is not /opt/ltsp but /" but later saw that
this was confusing base directory and chroot path.
Nonetheless I next thought that since the syntax of ltsp-update-image is
ltsp-update-image [OPTION] [CHROOT...]
and since it supports
ltsp-update-image -c /
thereby supporting '/' as a chroot path designation, then
ltsp-update-kernels might well do likewise, since its syntax is
ltsp-update-kernels [OPTION] [CHROOT...]
But my test last night and your post now confirms that this won't work.
And for the good reason that you describe: "So there's no
"ltsp-update-kernels <kernel-path>" option, and for NBD, it wouldn't
make sense to have a <kernel-path> parameter there, to select a kernel
that isn't inside the image, because the necessary modules would be
missing then." (I learned in the past few days that kernel modules are
in the initrd-img, not in the vmlinuz. So your observation brings a few
things together for me.)
Conclusion: There is no shortcut that avoids the bigger job. To make a
newly installed kernel available for client booting, one must run
ltsp-update-image.
Thanks, Alkis.
------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear picture of how application performance
affects their revenue. With AppDynamics, you get 100% visibility into your
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
_____________________________________________________________________
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
