March 2005 - openSUSE Autoinstall - openSUSE Mailing Lists

RE: [suse-autoinstall] Yast Unattended Install - annoying network problem.
by Schumacher, Gordon 17 Mar '05

17 Mar '05

I have not had to do this (and I'm using HTTP, as I need to be able to traverse filesystems.) -----Original Message----- From: Mitko Haralanov [mailto:mitko@pathscale.com] Sent: Thursday, March 17, 2005 1:01 PM To: suse-autoinstall(a)suse.com Subject: Re: [suse-autoinstall] Yast Unattended Install - annoying network problem. On Thu, 17 Mar 2005 16:11:25 -0000 Colin Topliss <Colin.Topliss(a)three.co.uk> wrote: > The problem starts during the 'initializing hardware' section. It stops at > this point complaining that it can't find the SUSE Linux installation > source. Now some might think that I'd made a mistake - but this is certainly > not the case. I was getting the same thing until I put 'instmode=nfs' in the kernel boot line (I am installing over nfs). You might try appending 'instmode=http' to your append line... -- Mitko Haralanov mitko(a)pathscale.com http://www.pathscale.com ========================================== I cannot conceive that anybody will require multiplications at the rate of 40,000 or even 4,000 per hour ... -- F. H. Wales (1936) -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

2 1

FW: [suse-autoinstall] Dhcp Problems?
by Schumacher, Gordon 17 Mar '05

17 Mar '05

Sounds very much like Colin's problem ("Yast Unattended Install - annoying network problem") also, I suspect! -----Original Message----- From: Brad Hudson [mailto:brad.hudson@gmail.com] Sent: Thursday, March 17, 2005 1:03 PM To: Matt Poepping Cc: suse-autoinstall(a)suse.com Subject: Re: [suse-autoinstall] Dhcp Problems? Mitko is correct on that one. I battled that same issue and the spanning-tree option on the switch needed to be enabled for the ports we were plugged into. to dhcp boot correctly. On Fri, 4 Mar 2005 15:16:42 -0700, Matt Poepping <matt.poepping(a)xilinx.com> wrote: > Is there a way to tell dhcp to try again if it fails the first time. > > > -----Original Message----- > From: Matt Poepping [mailto:matt.poepping@xilinx.com] > Sent: Thursday, March 03, 2005 9:14 > To: suse-autoinstall(a)suse.com > Subject: [suse-autoinstall] Dhcp Problems? > > I am trying to autoyast a machine, and when it is plugged directly into > another machine it works fine, but when I plug it into the network, the > dhcp servers do not seem to be responding fast enough for it and then > install will fail to manual mode. In manual mode, it can then go out and > get a dhcp address. > > I have tried editing the linuxrc.config file within the initrd file, to > up the timeout, but that doesn't seem to work. I've also tried to point > to an info file with the same info, and that seems to be ignored also. > > Thanks, > Matt > > -- > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > For additional commands, e-mail: suse-autoinstall-help(a)suse.com > > -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

RE: [suse-autoinstall] Dhcp Problems?
by Matt Poepping 17 Mar '05

17 Mar '05

Is there a way to tell dhcp to try again if it fails the first time. -----Original Message----- From: Matt Poepping [mailto:matt.poepping@xilinx.com] Sent: Thursday, March 03, 2005 9:14 To: suse-autoinstall(a)suse.com Subject: [suse-autoinstall] Dhcp Problems? I am trying to autoyast a machine, and when it is plugged directly into another machine it works fine, but when I plug it into the network, the dhcp servers do not seem to be responding fast enough for it and then install will fail to manual mode. In manual mode, it can then go out and get a dhcp address. I have tried editing the linuxrc.config file within the initrd file, to up the timeout, but that doesn't seem to work. I've also tried to point to an info file with the same info, and that seems to be ignored also. Thanks, Matt

2 1

Yast Unattended Install - annoying network problem.
by Colin Topliss 17 Mar '05

17 Mar '05

Hi all, I have an odd problem which is causing me some grief, and I was wondering if anyone else has seen it. The problem (I think) leads to others in the process. Not as unattended as I would like! I am remotely installing SuSE 9.2 a Compaq DL380-G4. When I come to start the install, I am using (IPs changed to protect the guilty): initrd netdevice=eth0 HostIP=10.10.5.9 netmask=255.255.255.0 gateway=10.10.5.1 install=http://10.10.5.50/9.2 autoyast=http://10.10.5.50/conf/system.xml The problem starts during the 'initializing hardware' section. It stops at this point complaining that it can't find the SUSE Linux installation source. Now some might think that I'd made a mistake - but this is certainly not the case. If I now go through the steps: Select the language Choose a keyboard map Start Installation Or System Start Installation Or Update Network HTTP Your network is already configured. Keep this configuration (YES) Enter the IP address of the HTTP server (10.10.5.50) Use a HTTP proxy? (NO) I then get another error saying: connect: No route to host If I try again too quickly, I get the same error. If I wait 30 seconds or and it comes back and prompts for the installation directory (9.2) I'm not sure what causes the initial fault, but the subsequent one suggests a timeout period before the NIC comes on-line, and/or YaST is not waiting for the NIC to initialise before continuing. Now I can crack on with the install (though now its not exactly unattended anymore)! The third problem is that now I have to acknowledge a number of prompts (I think as a result of dropping out to manual mode earlier? - I think I saw that mentioned on the mailing list somewhere). The fourth problem comes after the first CD is finished with. The system reboots, and then goes on to CD2 - and here the system prompts me to load the second CD (a bit annoying as its all under HTTP control). Again, wait for 30 seconds and the install continues OK. Finally, once the system comes up, the network settings are incorrect (I override the one supplied on the command line with a new one in the xml). A reboot cures this, but the option to autoreboot (according to the manual, and bourne out by the fact I couldn't get it to work) appears to have been obsoleted. Has anyone seen this elsewhere, and any ideas on how to prevent the problem(s)? Thanks! Colin Topliss Senior UNIX Sys Admin Noli habere bovis, vir! ________________________________________________________________________ This e-mail message (including any attachment) is intended only for the personal use of the recipient(s) named above. This message is confidential and may be legally privileged. If you are not an intended recipient, you may not review, copy or distribute this message. If you have received this communication in error, please notify us immediately by e-mail and delete the original message. Any views or opinions expressed in this message are those of the author only. Furthermore, this message (including any attachment) does not create any legally binding rights or obligations whatsoever, which may only be created by the exchange of hard copy documents signed by a duly authorised representative of Hutchison 3G UK Limited. ________________________________________________________________________

3 2

RE: [suse-autoinstall] Yast Unattended Install - annoying network problem.
by Schumacher, Gordon 17 Mar '05

17 Mar '05

Sounds to me like your DHCP server is being slow to hand it an address, perhaps. Check your logs? (You might try setting up the remote logging option as described here: http://www.tcm.phy.cam.ac.uk/~mr349/suse/autoyast.html) -----Original Message----- From: Colin Topliss [mailto:Colin.Topliss@three.co.uk] Sent: Thursday, March 17, 2005 9:11 AM To: 'suse-autoinstall(a)suse.com' Subject: [suse-autoinstall] Yast Unattended Install - annoying network problem. Hi all, I have an odd problem which is causing me some grief, and I was wondering if anyone else has seen it. The problem (I think) leads to others in the process. Not as unattended as I would like! I am remotely installing SuSE 9.2 a Compaq DL380-G4. When I come to start the install, I am using (IPs changed to protect the guilty): initrd netdevice=eth0 HostIP=10.10.5.9 netmask=255.255.255.0 gateway=10.10.5.1 install=http://10.10.5.50/9.2 autoyast=http://10.10.5.50/conf/system.xml The problem starts during the 'initializing hardware' section. It stops at this point complaining that it can't find the SUSE Linux installation source. Now some might think that I'd made a mistake - but this is certainly not the case. If I now go through the steps: Select the language Choose a keyboard map Start Installation Or System Start Installation Or Update Network HTTP Your network is already configured. Keep this configuration (YES) Enter the IP address of the HTTP server (10.10.5.50) Use a HTTP proxy? (NO) I then get another error saying: connect: No route to host If I try again too quickly, I get the same error. If I wait 30 seconds or and it comes back and prompts for the installation directory (9.2) I'm not sure what causes the initial fault, but the subsequent one suggests a timeout period before the NIC comes on-line, and/or YaST is not waiting for the NIC to initialise before continuing. Now I can crack on with the install (though now its not exactly unattended anymore)! The third problem is that now I have to acknowledge a number of prompts (I think as a result of dropping out to manual mode earlier? - I think I saw that mentioned on the mailing list somewhere). The fourth problem comes after the first CD is finished with. The system reboots, and then goes on to CD2 - and here the system prompts me to load the second CD (a bit annoying as its all under HTTP control). Again, wait for 30 seconds and the install continues OK. Finally, once the system comes up, the network settings are incorrect (I override the one supplied on the command line with a new one in the xml). A reboot cures this, but the option to autoreboot (according to the manual, and bourne out by the fact I couldn't get it to work) appears to have been obsoleted. Has anyone seen this elsewhere, and any ideas on how to prevent the problem(s)? Thanks! Colin Topliss Senior UNIX Sys Admin Noli habere bovis, vir! ________________________________________________________________________ This e-mail message (including any attachment) is intended only for the personal use of the recipient(s) named above. This message is confidential and may be legally privileged. If you are not an intended recipient, you may not review, copy or distribute this message. If you have received this communication in error, please notify us immediately by e-mail and delete the original message. Any views or opinions expressed in this message are those of the author only. Furthermore, this message (including any attachment) does not create any legally binding rights or obligations whatsoever, which may only be created by the exchange of hard copy documents signed by a duly authorised representative of Hutchison 3G UK Limited. ________________________________________________________________________ -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

No Floppy option?
by Brian Corriveau 17 Mar '05

17 Mar '05

Hi, is there some way to specify in the xml control file that the system does not have a floppy or pcmcia? I've run into a problem where sometimes the probe is getting the wrong result. Tracking that down looks like a lot of work so I'm wondering if there is an xml solution. thanks brian

1 0

Root Password...SuSE 9.1
by Jeffrey Andrews 16 Mar '05

16 Mar '05

Below, I've included a portion of my autoinst.xml that sets up the password stuff. Why doesn't my root user get his password set? Am I missing something or specifying something incorrectly? <security> <console_shutdown>reboot</console_shutdown> <cwd_in_root_path>no</cwd_in_root_path> <cwd_in_user_path>no</cwd_in_user_path> <displaymanager_remote_access>no</displaymanager_remote_access> <enable_sysrq>no</enable_sysrq> <fail_delay>3</fail_delay> <faillog_enab>yes</faillog_enab> <gid_max>60000</gid_max> <gid_min>500</gid_min> <kdm_shutdown>root</kdm_shutdown> <lastlog_enab>yes</lastlog_enab> <obscure_checks_enab>no</obscure_checks_enab> <pass_max_days>99999</pass_max_days> <pass_max_len>16</pass_max_len> <pass_min_days>1</pass_min_days> <pass_min_len>6</pass_min_len> <pass_warn_age>14</pass_warn_age> <passwd_encryption>md5</passwd_encryption> <passwd_use_cracklib>yes</passwd_use_cracklib> <permission_security>secure</permission_security> <run_updatedb_as>nobody</run_updatedb_as> <system_gid_max>499</system_gid_max> <system_gid_min>100</system_gid_min> <system_uid_max>499</system_uid_max> <system_uid_min>100</system_uid_min> <uid_max>60000</uid_max> <uid_min>500</uid_min> </security> <users config:type="list"> <user> <username>root</username> <user_password>EE8863733EF4355A37D566F3DF2AD016</user_password> <encrypted config:type="boolean">true</encrypted> </user> -- Jeffrey Andrews <jandrews(a)lancope.com>

5 5

Full AutoYast tag list
by Mitko Haralanov 15 Mar '05

15 Mar '05

Is there some place where all the tags in the different sections are shown *and* described? The documentation contains only a few of them (as I am starting to notice) and the DTD is hardly the place to provide any insight into what the tags mean. Thanx -- Mitko Haralanov mitko(a)pathscale.com http://www.pathscale.com ========================================== IOT trap -- core dumped

1 0

RE: [suse-autoinstall] auto-installing with patched OS
by Suffin, Charles 15 Mar '05

15 Mar '05

Outstanding, Anas!!! Thank you so much for the rapid response and the correct fix for the problem. I'm sorry I wasn't able to try your new version of the script on Friday night when you published it, but I have had the opportunity today. Now, after rebuilding the update/ directory with your script, when installation runs, the additional CD shows up correctly as "SUSE SLES Updates" and it lists "CD 1: 00:10" (rdesktop is small). After the install is completed, the rdesktop application is automatically installed (I added it with <package> to my XML file. Apparently the incorrect permission of the content file created by the original script was indeed preventing the install source from being correctly utilized. I very much doubt I could've figured out how to set this up without the script (and your help), Anas. Folks, one thing to note... If you want to supply a source package along with a binary package, you need to create an updates/suse/src/ directory and put the source RPM in that (*not* in the iX86/ or noarch/ directories). I consulted the /var/log/YaST2/y2log file to figure out why my source RPM was failing (my little contribution to this effort). With the source located in src/ YaST2 can find it! Thanks! -- Charlie -----Original Message----- From: Anas Nashif [mailto:nashif@suse.de] Sent: Friday, March 11, 2005 5:49 PM To: Suffin, Charles Cc: suse-autoinstall(a)suse.com Subject: Re: [suse-autoinstall] auto-installing with patched OS Hi, I just found out that the permission of the content file under updates/ is wrong, it should be world readable. (chmod a+r content) I will update the script. Anas Suffin, Charles wrote: > Hi folks, > > I used Anas' create_update_source.sh on my SLES9 installation source. It > created an updates/ directory in that source, resulting in a directory > structure that looks like this: > > SLES9/ > SUSE-CORE-Version-9/ > SUSE-SLES-Version-9/ > boot > content > control.xml > media.1 > updates/ <-- this was newly-created by the script, as expected > yast/ > > After this, I followed the instructions in the script: > > 1. I moved my packages into SLES9/updates/suse/<arch> directories. > 2. I cd into SLES9/updates/suse. > 3. I ran /usr/bin/create_package_descr -x setup/descr/EXTRA_PROV > > OK, so then I do an autoinstall from this source on a targe machine. > > After the reboot, there is no sign of my package on the installed machine, > and if I search for the package using YaST2 "Install and Remove Software" it > is not found by its name. > > I think I'm missing a step somewhere to cause the installation to actually > install my package. What am I missing? Do I need to add a <package> line > to the XML file? Do I need to do some more mucking with the installation > source? > > -- Charlie > > -----Original Message----- > From: Anas Nashif [mailto:nashif@suse.de] > Sent: Tuesday, March 01, 2005 10:53 PM > To: Mark Acosta > Cc: suse-autoinstall(a)suse.com > Subject: Re: [suse-autoinstall] auto-installing with patched OS > > Hi, > I have a script for doing this you might want to try, see > > http://www.suse.de/~nashif/autoyast2/scripts/create_update_source.sh > > The script itself has some additional info on how to use it. > > The script uses the multiple source feature known from SLES, it will > register multiple sources and the latest version of packages available > in the original source and the new source will be installed. > > Give it a try and let me know if it works for you. any feedback is welcome. > > Anas > > > Mark Acosta wrote: >>I need to autoinstall a patched 2.6.8-24.11-default kernel (including >>patched utils) for Suse 9.2. The stock kernel is 2.6.8-24.10-default, >>but I can't find out how to patch/update to 2.6.8-24.11-default. How is >>the best accomplished? >> >>thanks, >>Mark >> >> >

2 1

RE: [suse-autoinstall] auto-installing with patched OS
by Suffin, Charles 14 Mar '05

14 Mar '05

Ooooh, one other bug I should tell you about. The script doesn't create a directory.yast file in the update/ directory itself. This causes the autoinstall to take an error (download failed, media: file not found) right when it's loading the new packages. I made a one line addition to your script, Anas... You might want to do this in your version on the web: Add the following line after line 140: create_dy . Put this between the "cd $UPDATES" and the for loop. -- Charlie -----Original Message----- From: Suffin, Charles [mailto:Charles.Suffin@stratus.com] Sent: Monday, March 14, 2005 3:27 PM To: suse-autoinstall(a)suse.com Subject: RE: [suse-autoinstall] auto-installing with patched OS Outstanding, Anas!!! Thank you so much for the rapid response and the correct fix for the problem. I'm sorry I wasn't able to try your new version of the script on Friday night when you published it, but I have had the opportunity today. Now, after rebuilding the update/ directory with your script, when installation runs, the additional CD shows up correctly as "SUSE SLES Updates" and it lists "CD 1: 00:10" (rdesktop is small). After the install is completed, the rdesktop application is automatically installed (I added it with <package> to my XML file. Apparently the incorrect permission of the content file created by the original script was indeed preventing the install source from being correctly utilized. I very much doubt I could've figured out how to set this up without the script (and your help), Anas. Folks, one thing to note... If you want to supply a source package along with a binary package, you need to create an updates/suse/src/ directory and put the source RPM in that (*not* in the iX86/ or noarch/ directories). I consulted the /var/log/YaST2/y2log file to figure out why my source RPM was failing (my little contribution to this effort). With the source located in src/ YaST2 can find it! Thanks! -- Charlie -----Original Message----- From: Anas Nashif [mailto:nashif@suse.de] Sent: Friday, March 11, 2005 5:49 PM To: Suffin, Charles Cc: suse-autoinstall(a)suse.com Subject: Re: [suse-autoinstall] auto-installing with patched OS Hi, I just found out that the permission of the content file under updates/ is wrong, it should be world readable. (chmod a+r content) I will update the script. Anas Suffin, Charles wrote: > Hi folks, > > I used Anas' create_update_source.sh on my SLES9 installation source. It > created an updates/ directory in that source, resulting in a directory > structure that looks like this: > > SLES9/ > SUSE-CORE-Version-9/ > SUSE-SLES-Version-9/ > boot > content > control.xml > media.1 > updates/ <-- this was newly-created by the script, as expected > yast/ > > After this, I followed the instructions in the script: > > 1. I moved my packages into SLES9/updates/suse/<arch> directories. > 2. I cd into SLES9/updates/suse. > 3. I ran /usr/bin/create_package_descr -x setup/descr/EXTRA_PROV > > OK, so then I do an autoinstall from this source on a targe machine. > > After the reboot, there is no sign of my package on the installed machine, > and if I search for the package using YaST2 "Install and Remove Software" it > is not found by its name. > > I think I'm missing a step somewhere to cause the installation to actually > install my package. What am I missing? Do I need to add a <package> line > to the XML file? Do I need to do some more mucking with the installation > source? > > -- Charlie > > -----Original Message----- > From: Anas Nashif [mailto:nashif@suse.de] > Sent: Tuesday, March 01, 2005 10:53 PM > To: Mark Acosta > Cc: suse-autoinstall(a)suse.com > Subject: Re: [suse-autoinstall] auto-installing with patched OS > > Hi, > I have a script for doing this you might want to try, see > > http://www.suse.de/~nashif/autoyast2/scripts/create_update_source.sh > > The script itself has some additional info on how to use it. > > The script uses the multiple source feature known from SLES, it will > register multiple sources and the latest version of packages available > in the original source and the new source will be installed. > > Give it a try and let me know if it works for you. any feedback is welcome. > > Anas > > > Mark Acosta wrote: >>I need to autoinstall a patched 2.6.8-24.11-default kernel (including >>patched utils) for Suse 9.2. The stock kernel is 2.6.8-24.10-default, >>but I can't find out how to patch/update to 2.6.8-24.11-default. How is >>the best accomplished? >> >>thanks, >>Mark >> >> > -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0