On 12/9/2013 5:15 PM, Vagrant Cascadian wrote:
> On Sun, Dec 08, 2013 at 12:39:38PM -0500, John Hupp wrote:
>> On 12/7/2013 9:43 PM, Vagrant Cascadian wrote:
>>> On Thu, Dec 05, 2013 at 11:31:46AM -0500, John Hupp wrote:
>>>> Can I locate the init script somewhere on the server?
>>> Look in /opt/ltsp/<arch>/usr/share/initramfs-tools/ for all the code used to
>>> build the initramfs.
> ...
>> Thanks, Vagrant, for the useful info about initramfs. But under
>> *buntu, is the location /opt/ltsp/<arch>/usr/share/initramfs-tools?
>> I don't find that under Ubuntu/Lubuntu Saucy.
> Where <arch> is i386, amd64, armhf, etc. yes. Unless you're doing ltsp-pnp, in
> which case it would just be the server's /usr/share/initramfs-tools.
>
>
>> But here is one question about troubleshooting: As I was trying to
>> install kernels and test them on the client, I updated
>> /var/lib/tftpboot/ltsp/i386/pxelinux.cfg/default (so the new kernel
>> would be available during client boot) via ltsp-update-image, which
>> is a slow process. I'm thinking that I probably don't need that big
>> gun. You mention ltsp-update-kernels above -- is that all I really
>> need?
> ltsp-update-kernels in the version you're running may pull the tftp files
> from /opt/ltsp/images/i386.img or /opt/ltsp/i386/boot/. I *think* the logic
> was if both the client chroot and the image file are present, it pulls from
> the chroot, but I don't recall for sure.
>
> In the future I'd like to change it so it creates separate tftp files for the
> chroot and the image, but that's not yet implemented.
>
>
> live well,
> vagrant
>
I think I said in the original thread that I was using ltsp-pnp, but I
probably didn't repeat that in this offshoot thread.
And I can see now that the initramfs scripts are sitting right there in
open view at /usr/share/initramfs-tools. So I worked harder than I
needed to (opening the initrd-img archive) in order to get a look at those.
---------------------------
Regarding whether I must run ltsp-update-image, or whether
ltsp-update-kernels will suffice to make newly installed kernels
available on the client:
The ltsp-update-kernels manpage reads this way:
---------------------------------------------------------------
SYNOPSIS
ltsp-update-kernels [OPTION] [CHROOT...]
DESCRIPTION
ltsp-update-kernels copies the boot/ directory from LTSP chroots
to the
TFTP directories in order to make them available to PXE
clients.
Copying kernels from inside NBD images is also supported.
CHROOT can
be a full path or a subdirectory of the /opt/ltsp base
directory, and
if it's unset, all available chroots are processed.
OPTIONS
-b --base=
The LTSP base directory. Defaults to "/opt/ltsp".
---------------------------------------------------------------
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.
The remaining open question in my mind would be whether it also updates
/var/lib/tftpboot/ltsp/i386/pxelinux.cfg/default to include the newly
copied kernels. I suppose it must, and I can confirm that by just
trying it with the next kernel I test.
[Another related troubleshooting question would be whether I can
configure pxelinux.cfg/default so that it gives me a menu of kernel
choices during client boot. So far my method is to press Shift during
PXE boot to get a 'boot: ' prompt, where I must type the exact name of
one of the menuentry labels from pxelinux.cfg/default.]
------------------------------------------------------------------------------
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
