On Jan 18, 2008 3:36 PM, Roger Oberholtzer <[EMAIL PROTECTED]> wrote:

> that this will happen. I simply suggest that the web page say what the
> suggested -s option means and that system files will be replaced as a
> result of running it. No more than two lines of warning.

I've added the reminder, btw, it's a wiki, please improve :)


> I'm confused. (Granted that is not difficult to do.) I have an image
> type of NBD (the default). The dhcpd.conf file was written by
> kiwi-ltsp-setup to have clients boot with pxelinux. But there is no
> pxelinux nor pxelinux.cfg file. Can't the NBD image be served when the
> client boots with pxelinux? If not, why was the dhcpd.conf file set to

pxeboot is required for both, either NFS/NBD, NFS was just a
suggestion for a quick development setup. NFS is not recommended way
of serving LTSP5.

> use pxelinux? If so, where are the files?
>
> I tried running kiwi-ltsp-setup -n2. It ended with this:
>
> KIWI-LTSP: 2008-01-18 10:20:27: Fixing up the netboot initrd and kernel
> filenames
> rm: cannot remove
> `/srv/tftpboot/boot/initrd-netboot-suse-10.3-ltsp.*.kernel': No such
> file or directory
> mv: cannot stat
> `/srv/tftpboot/boot/initrd-netboot-suse-10.3-ltsp*.kernel.*': No such
> file or directory
> KIWI-LTSP: 2008-01-18 10:20:27: ====== Setup completed ======
>
>
> In fact, the files that exist are called:
>
> /srv/tftpboot/boot/initrd
> /srv/tftpboot/boot/initrd-netboot-suse-10.3.i686-2.1.1.kernel
> /srv/tftpboot/boot/initrd-netboot-suse-10.3.i686-2.1.1.kernel.2.6.22.5-31-default
>
> which are not quite the right thing. Maybe this error results in the
> pxelinux files not getting written?

Manually cp /srv/tftpboot/boot/initrd-netboot-suse-10.3.i686-2.1.1.kernel
/srv/tftpboot/boot/linux

pxelinux files are installed with kiwi-pxeboot package, should be in
/srv/tftpboot unless it is moved/removed manually. Reinstall the
package just in case and also update all kiwi packages to latest.

ciao

-J
-- 
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to