Στις 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.

------------------------------------------------------------------------------
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

Reply via email to