On Fri, 2008-01-18 at 14:45 +0530, CyberOrg wrote: > On Jan 18, 2008 2:21 PM, Roger Oberholtzer <[EMAIL PROTECTED]> wrote: > > > This explains a bit. "kiwi-ltsp-setup -s", as suggested on > > opensuse.org/LTSP, says that the machine is a dedicated LTSP box. Which > > would imply that any files that should be modified can be modified. > > Yikes! I really think the LTSP page should tell what the suggested > > command assumes! I wonder how many other unsuspecting folk have had > > files replaced. This is especially important as you run this command as > > root! Of course, one should not just blindly run commands as root, but > > the suggestion to do so is coming from opensuse.org. > > People who know what they are doing, also know that networking, nbd, > dhcp, tftp servers and firewall etc has to be configured, the LTSP > wiki page cannot cover the tutorial for all of those and assume that > the prior knowledge of the servers and configuration involved from the > sysadmins.
Not my point. I am not thinking of those who do or do not know dhcp and all. I am thinking of those who do NOT know KIWI. You know, the type of people who would be at this web page in the first place. Of course you can set these things up. It is nice that there is such an option. My concern is that the web page makes a suggestion that you use an option with kiwi-ltsp-setup that replaces system config files - without telling 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. > For the users who don't know anything about the various services > involved, it is best that we do it for them and they can poke the > configuration files later if they are interested. > > With virtualization it is easy to have dedicated LTSP server on which > no other service is configured, so we can replace/enhance/configure > any configuration file that is required for LTSP set up to just work. > > > > > How do I get the pxelinux stuff to be done? > > Only configuration file you need to work with is > /etc/sysconfig/kiwi-ltsp (IMAGETYPE="NFS") and switches for > kiwi-ltsp-setup ( -t). Do not change TFTPBOOTPATH as /srv/tftpboot is > where kiwi installs boot images. 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 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? -- Roger Oberholtzer OPQ Systems / Ramböll RST Ramböll Sverige AB Kapellgränd 7 P.O. Box 4205 SE-102 65 Stockholm, Sweden Office: Int +46 8-615 60 20 Mobile: Int +46 70-815 1696 -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
