Re: [Kiwi-devel] [opensuse] openSUSE 10.3 and LTSP
On Jan 15, 2008 4:41 PM, Marcus Schäfer <ms@suse.de> wrote:
@Cyberorg: you use your own ltsp initrd. Did you make the adaptions I posted in a former e-mail:
We are using unmodified kiwi netboot image, so this must be old description. @Roger, please update all kiwi packages, that should fix the neboot not building issue.
-------------- snip ----------- Those of you who are using their own _boot_ image descriptions and not the native ones provided by kiwi need to change the following to be able to use kiwi >= 2.06 successfully:
1) remove the config/ directory 2) edit the file images.sh and add the function call
suseStripKernel
as first call in this script
I did the adaptions for all kiwi provided boot images so you can have a look at for example /usr/share/kiwi/image/netboot/suse-10.3/images.sh to see how I changed it -------------------------------
Regards, Marcus -- Public Key available gpg --keyserver gpg-keyserver.de --recv-keys 0xCCE3C6A2 ------------------------------------------------------- Marcus Schäfer (Res. & Dev.) SUSE LINUX Products GmbH Tel: 0911-740 53 0 Maxfeldstrasse 5 FAX: 0911-740 53 479 D-90409 Nürnberg GF: Markus Rex HRB: 16746 (AG Nürnberg) http://www.suse.de Germany -------------------------------------------------------
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
xOn Tue, 2008-01-15 at 16:45 +0530, CyberOrg wrote:
@Roger, please update all kiwi packages, that should fix the neboot not building issue.
I will do so as soon as the repositories come back to life. FYI, I currently have installed: kiwi-desc-vmxboot-1.64-22 kiwi-1.64-22 kiwi-desc-xenboot-1.64-22 kiwi-pxeboot-2.08-28.1 kiwi-desc-ltsp-0.3.12-3.1 kiwi-desc-isoboot-1.64-22 kiwi-desc-netboot-2.08-28.1 kiwi-desc-usbboot-1.64-22 At least these are the ones with kiwi in the name. Are there others? -- 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: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Jan 15, 2008 5:27 PM, Roger Oberholtzer <roger@opq.se> wrote:
xOn Tue, 2008-01-15 at 16:45 +0530, CyberOrg wrote:
@Roger, please update all kiwi packages, that should fix the neboot not building issue.
I will do so as soon as the repositories come back to life. FYI, I currently have installed:
kiwi-1.64-22
You kiwi version is too old, you need something greater than kiwi-2.07. Best update all the kiwi packages to the latest available on openSUSE:Tools repo. Cheers -J -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tue, 2008-01-15 at 22:35 +0530, CyberOrg wrote:
On Jan 15, 2008 5:27 PM, Roger Oberholtzer <roger@opq.se> wrote:
xOn Tue, 2008-01-15 at 16:45 +0530, CyberOrg wrote:
@Roger, please update all kiwi packages, that should fix the neboot not building issue.
I will do so as soon as the repositories come back to life. FYI, I currently have installed:
kiwi-1.64-22
You kiwi version is too old, you need something greater than kiwi-2.07. Best update all the kiwi packages to the latest available on openSUSE:Tools repo.
OK. This got me much further, I think. Not that I am booting anything. But I think it is completing whatever it wanted to do. I have some dhcp/pxelinux/tftpboot questions: (First let me say that I use these three tools a lot, so I am familiar with how I use it. My questions are more what KIWI/LTSP are up to) 1. How do I get the build to NOT clobber any existing /etc/dhcpd.conf file? It seems that anything that was already there is now gone. This seems like a bad thing. I wonder what other files were mercilessly clobbered. I see things like /etc/pam.d/common-session being copied. I assume that is to the new system? I can see no reason for changing anything in the host system beyond dhcpd/pxelinux. Or am I missing something. 2. Should the build have placed a pxelinux image or pxelinux.cfg somewhere? I do not see them. If the generic pxelinux is used, I am ok. The contents of the pxelinux.cfg file could be interesting. 3. I would prefer to have the pxelinux and boot stuff in /tftpboot. I make a directory there for each type of diskless thing I have (thinstation, gentoo, embedded device FLASH images, whatever). Is it OK for me to just move things there? Or do I have to use the settings in /etc/sysgonfig? That is enough questions for now. I will have more, I am sure, when I try to actually boot something.
Cheers
-J
-- 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: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Jan 17, 2008 8:59 PM, Roger Oberholtzer <roger@opq.se> wrote:
I have some dhcp/pxelinux/tftpboot questions:
1. How do I get the build to NOT clobber any existing /etc/dhcpd.conf file? It seems that anything that was already there is now gone. This seems like a bad thing. I wonder what other files were mercilessly clobbered. I see things like /etc/pam.d/common-session being copied. I assume that is to the new system? I can see no reason for changing anything in the host system beyond dhcpd/pxelinux. Or am I missing something.
Just run kiwi-ltsp-setup without any options to know what different things it offers to do, there are options that just build images and not set up any config files. KIWI-LTSP sets up /etc/dhcpd.conf, /etc/exports, /etc/nbd-server/config, /etc/xinetd.d/tftp and /srv/tftpboot. Check out /usr/share/kiwi/image/ltsp/suse-10.3/kiwi-ltsp-functions.sh for all the changes it carries out.
2. Should the build have placed a pxelinux image or pxelinux.cfg somewhere? I do not see them. If the generic pxelinux is used, I am ok. The contents of the pxelinux.cfg file could be interesting.
/srv/tftpboot
3. I would prefer to have the pxelinux and boot stuff in /tftpboot. I make a directory there for each type of diskless thing I have (thinstation, gentoo, embedded device FLASH images, whatever). Is it OK for me to just move things there? Or do I have to use the settings in /etc/sysgonfig?
/srv/ is a proper place, but you can put it where ever you prefer, change the kiwi-ltsp config accordingly. Do boot up clients and let us know what worked, try different hardwares as client, even normal pc pxebooted. Ciao -J -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Fri, 2008-01-18 at 00:10 +0530, CyberOrg wrote:
On Jan 17, 2008 8:59 PM, Roger Oberholtzer <roger@opq.se> wrote:
I have some dhcp/pxelinux/tftpboot questions:
1. How do I get the build to NOT clobber any existing /etc/dhcpd.conf file? It seems that anything that was already there is now gone. This seems like a bad thing. I wonder what other files were mercilessly clobbered. I see things like /etc/pam.d/common-session being copied. I assume that is to the new system? I can see no reason for changing anything in the host system beyond dhcpd/pxelinux. Or am I missing something.
Just run kiwi-ltsp-setup without any options to know what different things it offers to do, there are options that just build images and not set up any config files.
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. How do I get the pxelinux stuff to be done? As a minimum, what would the pxelinux.cfg entry for a NBD setup be? When I run kiwi-ltsp-setup -t, I get: KIWI-LTSP: 2008-01-18 09:50:28: ====== Starting ====== KIWI-LTSP: 2008-01-18 09:50:28: Setting up KIWI PXE support. /usr/share/kiwi/image/ltsp/suse-10.3/kiwi-ltsp-functions.sh: line 356: /srv/tftpboot/KIWI/config.default: No such file or directory KIWI-LTSP: 2008-01-18 09:50:28: ====== Setup completed ====== -- 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: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Jan 18, 2008 2:21 PM, Roger Oberholtzer <roger@opq.se> 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. 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. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Fri, 2008-01-18 at 14:45 +0530, CyberOrg wrote:
On Jan 18, 2008 2:21 PM, Roger Oberholtzer <roger@opq.se> 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: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Jan 18, 2008 3:36 PM, Roger Oberholtzer <roger@opq.se> 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: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Fri, 2008-01-18 at 15:58 +0530, CyberOrg wrote:
On Jan 18, 2008 3:36 PM, Roger Oberholtzer <roger@opq.se> 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 :)
Not until I know more. We don't need the blind leading the blind!
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.
Indeed. I prefer to have a single squasfs file to manage. I was worried when you mentioned setting the type to NFS.
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.
Ahh. I could very well have deleted them. I thought the pxelinux files in /srv/tftpboot were copied there in the build, from wherever the kiwi-pxeboot package had the original files. This is why I should not be let loose on the wiki... -- 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: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Progress: I get the kernel to boot. It makes device nodes and then is doing the KIWI setup. It then complains that some things cannot be found. One odd thing it complains about is that the tftp server cannot be found. It is looking for 192.168.0.254. I changed the SERVER_IP in /etc/sysconfig to what I want. 192.168.0.254 does not exist in the file. So I wonder where it is getting this from. Why is it using the tftp server after the kernel boots and after the initrd is loaded? I though all the rest was in the NBD image served by the nbd-server. -- 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: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Jan 18, 2008 7:20 PM, Roger Oberholtzer <roger@opq.se> wrote:
Progress:
I get the kernel to boot. It makes device nodes and then is doing the KIWI setup. It then complains that some things cannot be found.
One odd thing it complains about is that the tftp server cannot be found. It is looking for 192.168.0.254. I changed the SERVER_IP
It only reads /etc/sysconfig/kiwi-ltsp when creating images and configuring server, changing it after everything does not have any effect at all. grep for 192.168.0.254 in dhcpd.conf and /srv/tftpboot/pxelinux.cfg/default or /srv/tftpboot/KIWI/* -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Fri, 2008-01-18 at 19:44 +0530, CyberOrg wrote:
On Jan 18, 2008 7:20 PM, Roger Oberholtzer <roger@opq.se> wrote:
Progress:
I get the kernel to boot. It makes device nodes and then is doing the KIWI setup. It then complains that some things cannot be found.
One odd thing it complains about is that the tftp server cannot be found. It is looking for 192.168.0.254. I changed the SERVER_IP
It only reads /etc/sysconfig/kiwi-ltsp when creating images and configuring server, changing it after everything does not have any effect at all.
This I understood.
grep for 192.168.0.254 in dhcpd.conf and /srv/tftpboot/pxelinux.cfg/default or /srv/tftpboot/KIWI/*
It was on the kernel command line in /srv/tftpboot/pxelinux.cfg/default. After I changed that, it finds the tftp server. Then it is looking for network config files. Which it does not find. So it waits 60 secs and tries again. And again... -- 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: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Jan 18, 2008 7:53 PM, Roger Oberholtzer <roger@opq.se> wrote:
It was on the kernel command line in /srv/tftpboot/pxelinux.cfg/default. After I changed that, it finds the tftp server. Then it is looking for network config files. Which it does not find. So it waits 60 secs and tries again. And again...
It is looking for /srv/tftpboot/KIWI/config.default Instead of going through all the files that are not configured due to original misconfiguration, let us start over. * Make sure you are using all the latest kiwi packages available * disable firewall * Mount i386 DVD5 media somewhere * Get /etc/sysconfig/kiwi-ltsp right according to your setup * run "kiwi-ltsp-setup -s" and let it configure everything for you * boot client Cheers -J -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Fri, 2008-01-18 at 20:03 +0530, CyberOrg wrote:
On Jan 18, 2008 7:53 PM, Roger Oberholtzer <roger@opq.se> wrote:
It was on the kernel command line in /srv/tftpboot/pxelinux.cfg/default. After I changed that, it finds the tftp server. Then it is looking for network config files. Which it does not find. So it waits 60 secs and tries again. And again...
It is looking for /srv/tftpboot/KIWI/config.default
Instead of going through all the files that are not configured due to original misconfiguration, let us start over.
* Make sure you are using all the latest kiwi packages available * disable firewall * Mount i386 DVD5 media somewhere * Get /etc/sysconfig/kiwi-ltsp right according to your setup * run "kiwi-ltsp-setup -s" and let it configure everything for you * boot client
I will do this. I do think it is this way. But I will try again. The system did eventually come up with a GUI login. And I can ssh to it. So things are looking up. I was just surprised that 'df' foes not exist. And that 'mount' lists nothing. Now that I get this far, I want to do more! Like mounting an NFS volume. Now the fun begins... -- 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: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Jan 18, 2008 8:23 PM, Roger Oberholtzer <roger@opq.se> wrote:
The system did eventually come up with a GUI login. And I can ssh to it.
Glad you made it :)
So things are looking up. I was just surprised that 'df' foes not exist. And that 'mount' lists nothing.
The image is about 150MB skeleton that has just enough juice to get your LDM (LTSP Display Manager), once you log in you are using all the resources on the server.
Now that I get this far, I want to do more! Like mounting an NFS volume. Now the fun begins...
Have fun! -J -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Fri, 2008-01-18 at 20:03 +0530, CyberOrg wrote:
On Jan 18, 2008 7:53 PM, Roger Oberholtzer <roger@opq.se> wrote:
It was on the kernel command line in /srv/tftpboot/pxelinux.cfg/default. After I changed that, it finds the tftp server. Then it is looking for network config files. Which it does not find. So it waits 60 secs and tries again. And again...
It is looking for /srv/tftpboot/KIWI/config.default
Instead of going through all the files that are not configured due to original misconfiguration, let us start over.
* Make sure you are using all the latest kiwi packages available * disable firewall * Mount i386 DVD5 media somewhere * Get /etc/sysconfig/kiwi-ltsp right according to your setup * run "kiwi-ltsp-setup -s" and let it configure everything for you * boot client
I have done all this and things are better. I think the following were the problems: 1) some file in /srv/tftpboot that are needed only come from a package install. If they are deleted, you are sol. This makes cleaning up the /srv directory problematic in that there is no obvious way to remove generated files, leaving those only installed by a package alone. So I made an archive of this when the packages were freshly installed. 2) nbd must be restarted when the image it is to serve changes. If not, you get a Negotiation: prompt when the boot tries to mount the image. Perhaps the generation script should do this? Or perhaps something else is really the problem. After sorting these things out, things were better. The system boots promptly. There are still some odd complaints about read-only file system. But nothing that seems to keep the system from coming up. I tried to mount an nfs volume, but I get this error right away: mount: bad fs type, bad option, bad superblock on 10.1.5.1:/opt/rsoft etc... I can mount this from everywhere else. I have tried a share from a suse 10.0 and a 10.3 system. The response is so quick, I get the feeling it has not eve tried. nfs is listed in /proc/filesystems. Perhaps there is some additional RPM that I need to allow nfs mounting?
Cheers
-J
-- 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: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Jan 22, 2008 12:03 AM, Roger Oberholtzer <roger@opq.se> wrote:
I have done all this and things are better. I think the following were the problems:
1) some file in /srv/tftpboot that are needed only come from a package install. If they are deleted, you are sol. This makes cleaning up the /srv directory problematic in that there is no obvious way to remove generated files, leaving those only installed by a package alone. So I made an archive of this when the packages were freshly installed.
Manual cleaning is not required, kiwi-ltsp-setup when run second time moves the old installation as /srv/kiwi-ltsp-nfs.<date>
2) nbd must be restarted when the image it is to serve changes. If not, you get a Negotiation: prompt when the boot tries to mount the image. Perhaps the generation script should do this? Or perhaps something else is really the problem.
NBD should be restarted when you run fully automated mode (kiwi-ltsp-setup -s)
I tried to mount an nfs volume, but I get this error right away:
mount: bad fs type, bad option, bad superblock on 10.1.5.1:/opt/rsoft etc...
try mount with -o nolock or start rpc.statd. NFS is not recommended and meant only for testing purpose, so do not expect it to work as well as NBD root. Ciao -J -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tue, 2008-01-22 at 10:57 +0530, CyberOrg wrote:
On Jan 22, 2008 12:03 AM, Roger Oberholtzer <roger@opq.se> wrote:
I have done all this and things are better. I think the following were the problems:
2) nbd must be restarted when the image it is to serve changes. If not, you get a Negotiation: prompt when the boot tries to mount the image. Perhaps the generation script should do this? Or perhaps something else is really the problem.
NBD should be restarted when you run fully automated mode (kiwi-ltsp-setup -s)
Seems no to do the trick. I ran that command yet had to restart the nbd server by hand.
I tried to mount an nfs volume, but I get this error right away:
mount: bad fs type, bad option, bad superblock on 10.1.5.1:/opt/rsoft etc...
try mount with -o nolock or start rpc.statd.
NFS is not recommended and meant only for testing purpose, so do not expect it to work as well as NBD root.
I want to add RPMS to my LTSP (as well as eventually get rid of X). I tried the link on the SUSE WIKI for info on customization (given link is wrong: should now be http://doc.ubuntu.com/edubuntu/edubuntu/handbook/C/ ). But this info seems to be at a higher level where one manipulates that happens with the RPMs already there. I tried adding a package to the config.xml, but then the build fails claiming that it failed reading the config file. I am missing something. Where is this documented? -- 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: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tue, 2008-01-22 at 16:38 +0100, Roger Oberholtzer wrote: OK. I give up. Where is there documentation on how to add an RPM to KIWI/LTSP? If I add it to the config.xml, the build fails claiming that it failed reading the config file. So there is obviously more to it than that. The only info on LTSP I can find is runtime stuff about what services/features LTSP should enable. My concern is back when the LTSP images are being created. Of course, maybe LTSP is not the best vehicle for getting a minimal diskless SUSE up and running. Maybe there is a more appropriate KIWI project for this? I thought I would start with LTSP since it is not so far off from what I want, and fiddle from there. But my fist fiddling failed. -- 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: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Jan 28, 2008 5:38 PM, Roger Oberholtzer <roger@opq.se> wrote:
On Tue, 2008-01-22 at 16:38 +0100, Roger Oberholtzer wrote:
OK. I give up. Where is there documentation on how to add an RPM to KIWI/LTSP? If I add it to the config.xml, the build fails claiming that it failed reading the config file. So there is obviously more to it than that. The only info on LTSP I can find is runtime stuff about what services/features LTSP should enable. My concern is back when the LTSP images are being created.
/usr/share/doc/packages/kiwi.pdf is the best place to look. Package names are added to config.xml. Be careful of xml tags :) You can post on kiwi-devel mailing list if you want more information/help on how to build kiwi images. Cheers -J -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Mon, 2008-01-28 at 18:20 +0530, CyberOrg wrote:
On Jan 28, 2008 5:38 PM, Roger Oberholtzer <roger@opq.se> wrote:
On Tue, 2008-01-22 at 16:38 +0100, Roger Oberholtzer wrote:
OK. I give up. Where is there documentation on how to add an RPM to KIWI/LTSP? If I add it to the config.xml, the build fails claiming that it failed reading the config file. So there is obviously more to it than that. The only info on LTSP I can find is runtime stuff about what services/features LTSP should enable. My concern is back when the LTSP images are being created.
/usr/share/doc/packages/kiwi.pdf is the best place to look. Package names are added to config.xml. Be careful of xml tags :)
You can post on kiwi-devel mailing list if you want more information/help on how to build kiwi images.
I have joined the kiwi list. But my problem seems to have been sorted out in a recent KIWI update. After the latest update, it now works. I can add nfs-client. I will now take any further discussions to that list. See you there :) Thanks for the help thus far. -- 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: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (2)
-
CyberOrg -
Roger Oberholtzer