February 2006 - openSUSE Autoinstall - openSUSE Mailing Lists

adding custom packages - could not set add-on selection error
by Dave 23 Feb '06

23 Feb '06

Hello, Please excuse me if this question has been answered before, but I've read the documentation, and after following the steps about adding custom packages, we are still having difficulties. I also read the FAQ but didn't see this problem addressed there. Unfortunately, the list archives are not searchable so I'm not really able to go through them all to see if this has been answered. Here's the goal: + Have AutoYAST install additional RPM packages that I specify in an ".sel" file. Here's what we tried: according to http://www.suse.de/~nashif/autoinstallation/9.1/html/CreateProfile.Software… + created custom-9.3-83.noarch.sel in /9.3/suse/setup/descr and added package names to "+Ins:" section + added custom-9.3-83.noarch.sel entry to selections file in /9.3/suse/setup/descr + added custom-9.3-83.noarch.sel entry to directory.yast file in /9.3/suse/setup/descr + updated MD5SUMS file in /9.3/suse/setup/descr to reflect new MD5's for files directory.yast, selections, and custom-9.3-83.noarch.sel + modified control file to included an addon directive <addon>custom</addon> Here's the error we get during the software selection phase of AutoInstall: "Could not set add-on selection: custom" I can send the files along as attachments if that is helpful in diagnosing the problem. If someone knows the solution, we would love to hear it! Thanks, Dave __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

3 3

Bug? "Adding complete configurations"
by KOEHLER, SVEN - PFHO 23 Feb '06

23 Feb '06

List, the configuration files added in the control file get stored in /var/adm/files/ but if i'm adding two php.ini's (/etc/php5/apache2/php.ini and /etc/php5/cli/php.ini) only one appears in a fully installed system. does the first of them get overwritten? as far as i can see is the content of the files in etc correct. greetz sven

1 0

Re: [suse-autoinstall] autoyast - defining additional installation sources
by Yan Fitterer 23 Feb '06

23 Feb '06

> If I am correct the yast/order and yast/instorder files list directories > relative to the network boot location - still searching for a description of Yes. The yast directory needs to be in the directory you specify as the installation source. > how yast/order and yast/instorder are treated. Here's a typical content: # cat yast/instorder /SUSE-SLES-9-Service-Pack-Version-1/CD1 /SUSE-SLES-Version-9/CD1 /SUSE-CORE-Version-9/CD1 # cat yast/order /SUSE-SLES-9-Service-Pack-Version-1/CD1 /SUSE-SLES-9-Service-Pack-Version-1/CD1 /SUSE-SLES-Version-9/CD1 /SUSE-SLES-Version-9/CD1 /SUSE-CORE-Version-9/CD1 /SUSE-CORE-Version-9/CD1 Yan

2 1

Re: [suse-autoinstall] adding custom packages - could not set add -on selection error
by KOEHLER, SVEN - PFHO 23 Feb '06

23 Feb '06

hi dave, just a hint: the list is searchable through google. you just have to add an "site:http://lists.suse.com/archive/suse-autoinstall/" after your search keywords. this works with this list as well as with all other sites indexed by google. unfortunately i can't tell anything regarding your problem greetz sven -----Ursprüngliche Nachricht----- Von: Dave [mailto:davo_muc@yahoo.com] Gesendet: Donnerstag, 23. Februar 2006 12:19 An: suse-autoinstall(a)suse.com Betreff: [suse-autoinstall] adding custom packages - could not set add-on selection error Hello, Please excuse me if this question has been answered before, but I've read the documentation, and after following the steps about adding custom packages, we are still having difficulties. I also read the FAQ but didn't see this problem addressed there. Unfortunately, the list archives are not searchable so I'm not really able to go through them all to see if this has been answered. Here's the goal: + Have AutoYAST install additional RPM packages that I specify in an + ".sel" file. Here's what we tried: according to http://www.suse.de/~nashif/autoinstallation/9.1/html/CreateProfile.Software. html#id2515639 + created custom-9.3-83.noarch.sel in /9.3/suse/setup/descr and added + package names to "+Ins:" section + added custom-9.3-83.noarch.sel entry to selections file in + /9.3/suse/setup/descr added custom-9.3-83.noarch.sel entry to + directory.yast file in /9.3/suse/setup/descr updated MD5SUMS file in + /9.3/suse/setup/descr to reflect new MD5's for files directory.yast, selections, and custom-9.3-83.noarch.sel + modified control file to included an addon directive + <addon>custom</addon> Here's the error we get during the software selection phase of AutoInstall: "Could not set add-on selection: custom" I can send the files along as attachments if that is helpful in diagnosing the problem. If someone knows the solution, we would love to hear it! Thanks, Dave __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

2 1

RE: [suse-autoinstall] suse 10.0 nfs install
by Gunreben, Peter (Peter) 22 Feb '06

22 Feb '06

Roger, Roger Oberholtzer wrote: > > The install kernel boots. At some point it wants to get a DHCP address > for the ethernet card. This 'should' be working as it got an address > when it first booted. I see this in the server's > /var/log/messages. But > this seems to timeout. My dhcp entry is: > > host jboc1 { > > filename "/suseInstall/pxelinux.0"; > fixed-address 192.30.105.204; > hardware ethernet 00:30:48:56:38:B2; > next-server 192.30.105.201; > option host-name "jboc1"; > } > > 192.30.105.201 is the server for everything (dhcp, pxe, suse install) > > After this, I get a message that the SUSE installation source > cannot be > found. When trying to set it up by hand (nice it does that), > I see that > the default values it offers are the ones I expect (despite > the probable > DHCP oddness). But when it tries to mount the nfs install source, it > fails with 'unknown error -1'. Have you checked whether the nfs-export works properly, e.g. by mounting it manually? I had a similar problem, where I tried to export a loop-mounted directory tree. Only, a userspace-nfsserver can do that. Peter.

2 1

suse 10.0 nfs install
by Roger Oberholtzer 22 Feb '06

22 Feb '06

Are there any known issues with using the OpenSUSE 10.0 original distro to do an NFS install to a PXE-booted client? Any show stopping bugs that require an update? I have set up dhcp ok, pxelinux.0 runs and uses my default file. All options as described in the SUSE online docs have been used. But I do not quite get the install to start: The install kernel boots. At some point it wants to get a DHCP address for the ethernet card. This 'should' be working as it got an address when it first booted. I see this in the server's /var/log/messages. But this seems to timeout. My dhcp entry is: host jboc1 { filename "/suseInstall/pxelinux.0"; fixed-address 192.30.105.204; hardware ethernet 00:30:48:56:38:B2; next-server 192.30.105.201; option host-name "jboc1"; } 192.30.105.201 is the server for everything (dhcp, pxe, suse install) After this, I get a message that the SUSE installation source cannot be found. When trying to set it up by hand (nice it does that), I see that the default values it offers are the ones I expect (despite the probable DHCP oddness). But when it tries to mount the nfs install source, it fails with 'unknown error -1'. Why is it looking for a DHCP server when I add the hostip= command to the kernel command line? This option seems to be ignored. -- Roger Oberholtzer OPQ Systems AB Ramböll Sverige AB Kapellgränd 7 P.O. Box 4205 SE-102 65 Stockholm, Sweden Tel: Int +46 8-615 60 53 Fax: Int +46 8-31 42 23

2 3

autoyast - defining additional installation sources
by Andrew Bramble 22 Feb '06

22 Feb '06

Hello , Firsttime poster. I'm super impressed by yast autoinstall - having got it operating nicely with pxe in almost no time. One thing I cannot discover though is how to define additional sources via an autoinstall.xml profile. Reading the DTD's has not enlightened me either. Is there any way to define more installation sources for autoyast? AB

2 4

RE: [suse-autoinstall] Installing multiple SuSE versions over NFS using Autoyast
by Gunreben, Peter (Peter) 22 Feb '06

22 Feb '06

Richard, Richard Hobbs wrote: > We currently have one DHCP server, one TFTP server and one > NFS server. Using > these, we install 64-bit SuSE 10.0 onto all of our 64-bit machines. > > However, we will soon need to start installing 64-bit SuSE onto some > machines and 32-bit SuSE onto other machines. > > As I understand it, the installation source (in this case the > 64-bit DVD > files) is specified in "/tftpboot/pxelinux.cfg/default", and > while I can > change this to the 32-bit DVD, I can't see an obvious way of > configuring > both. The DHCP Server specifies the TFTP server to boot from, > and specified > the kernel to boot from (in this case > "tftpserver:/tftpboot/pxelinux.0"). Hmmm, I'm not sure whether I really got your problem. When the DHCP server knows the MAC-adresses of the machines it can also use a specific tftp-server and/or kernel/initrd. Just boot the 32-bit computers with kernel/initrd and the 64-bit computers with kernel64/initrd64. In your case you also need to specify the installation source, e.g. by putting an info-file into the initrd. See for example: http://marc.theaimsgroup.com/?l=suse-autoinstall&m=113042352724245&w=2 If you are using the combined 32-bit/64-bit DVD, you only need to boot the specific kernel/initrd for 32/64-bit installation. I hope I hit the point. Peter.

1 0

Installing multiple SuSE versions over NFS using Autoyast
by Richard Hobbs 22 Feb '06

22 Feb '06

Hello, We currently have one DHCP server, one TFTP server and one NFS server. Using these, we install 64-bit SuSE 10.0 onto all of our 64-bit machines. However, we will soon need to start installing 64-bit SuSE onto some machines and 32-bit SuSE onto other machines. As I understand it, the installation source (in this case the 64-bit DVD files) is specified in "/tftpboot/pxelinux.cfg/default", and while I can change this to the 32-bit DVD, I can't see an obvious way of configuring both. The DHCP Server specifies the TFTP server to boot from, and specified the kernel to boot from (in this case "tftpserver:/tftpboot/pxelinux.0"). Is there an easy way of booting some machines into a 32-bit installation and other machines into a 64-bit installation? Thanks in advance! :-) Richard. -- Richard Hobbs (Systems Administrator) Toshiba Research Europe Ltd. - Speech Technology Group Web: http://www.toshiba-europe.com/research/ Normal Email: richard.hobbs(a)crl.toshiba.co.uk Mobile Email: mobile(a)mongeese.co.uk Tel: +44 1223 376964 Mobile: +44 7811 803377 _____________________________________________________________________ This e-mail has been scanned for viruses by Verizon Business Internet Managed Scanning Services - powered by MessageLabs. For further information visit http://www.mci.com

1 0

Re: [suse-autoinstall] autoyast/info file problem
by KOEHLER, SVEN - PFHO 22 Feb '06

22 Feb '06

I discovered problems with the floppy protocol. linuxrc found everything right, but then yast couldn't find the file. autoyast=device://fd0/info (bootparameter) resp. autoyast: device://fd0/info (linuxrc) worked for me. @dave: did you intentionally leave the comments (# start_linuxrc_conf / # end_linuxrc_conf) out? greetz sven -----Ursprüngliche Nachricht----- Von: Yan Fitterer [mailto:yfitterer@novell.com] Gesendet: Dienstag, 21. Februar 2006 23:44 An: dbellis(a)mmm.com Cc: suse-autoinstall(a)suse.com Betreff: Re: [suse-autoinstall] autoyast/info file problem Actually - I've made a mistake myself. It should be: autoyast: floppy:///control.xml Note the extra / I read somewhere as well that there was a bug somewhere that prevented this from working (confirmed on SuSE 9.3). The workaround was to use: autoyast: device://fd0/control.xml As well, I don't believe you need the autoyast=floppy boot option. If the info file is found by linuxrc on the floppy (as it should), then that will be enough. Specifying the option on the command line may override what you put in the info file (not sure...). Yan >>> On 21/02/2006 at 22:12, in message >>> <43FB9052.6718.008C.0(a)novell.com>, "Yan Fitterer" <yfitterer(a)novell.com> wrote: > You have some redundancy, and a couple of mistakes. Try: > > install: nfs://169.10.63.215/instserv/9.0_x64 > hostip: 169.10.248.36 > netmask: 255.255.255.0 > gateway: 169.10.248.1 > nameserver: 169.10.8.4 > autoyast: floppy://control.xml > > I think "ip:" might be deprecated. Try "HostIP:" as above. > autoyast: floppy://file.xml needs to point to the actual path and name > for > the control file. > > See > > http://www.suse.com/~ug/autoyast_doc/invoking_autoinst.html#id2543177 > > and > > http://www.suse.com/~ug/autoyast_doc/info_file_format.html > > Yan > >>>> On 21/02/2006 at 21:41, in message > <OFB9BC1F12.CDE5BBF5-ON8625711C.00762869-8625711C.007720BB(a)mmm.com>, > <dbellis(a)mmm.com> wrote: >> I am new to SUSE and am trying to setup an AutoYaST install using the >> SUSE Linux CD1 to boot with the autoyast=floppy boot option. >> >> On the floppy disk I have the autoinst.xml file and an info file. >> >> The info file contains the following: >> >> install: nfs://169.10.63.215/instserv/9.0_x64 >> netdevice: eth0 >> server: 169.10.63.215 >> serverdir: /instserv/9.0_x64 >> ip: 169.10.248.36 >> netmask: 255.255.255.0 >> gateway: 169.10.248.1 >> nameserver: 169.10.8.4 >> autoyast: floppy >> >> I can mount the nfs share manually, but when I run the install >> process it fails with the following message: >> >> "Could not find the SUSE Linux Enterprise Server 9 Installation >> Source" >> >> Does anyone have an idea what I am doing wrong? >> >> Any help would be greatly appreciated. >> >> Thanks, >> Dave Bellis >> -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0