December 2006 - openSUSE Autoinstall - openSUSE Mailing Lists

RE: [opensuse-autoinstall] SUMMARY: Init-scripts and nfs location
by Andrew Laden 18 Dec '06

18 Dec '06

So what was the change that was made in response to [bug] init-script does not require network now > -----Original Message----- > From: Uwe Gansert [mailto:ug@suse.de] > Sent: Monday, December 18, 2006 5:28 AM > To: opensuse-autoinstall(a)opensuse.org > Subject: Re: [opensuse-autoinstall] SUMMARY: Init-scripts and > nfs location > > On Friday 15 December 2006 20:03, Andrew Laden wrote: > > > 6: Note that even your init scripts will not have the > network up when > > they run as of Sles10, sp1. > > (http://www.suse.com/~ug/autoyast_changes_SLES10SP1.html) > So if your > > init scripts need the network, you will have to bring it up in them. > > that's not true. If the network is configured, then it's > raised up before the init-script on SP1. > > -- > ciao, Uwe Gansert > > Uwe Gansert, Server Technologies Team > SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nuernberg, Germany > Business: http://www.suse.de/~ug > -- > To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org > For additional commands, e-mail: > opensuse-autoinstall+help(a)opensuse.org > > -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 1

[opensuse-autoinstall] SUMMARY: Init-scripts and nfs location
by Andrew Laden 18 Dec '06

18 Dec '06

To summarize the answers and solution. 1: At the time that the init-scripts are fetched, the network is not available. So you can not use <location>...</location> references with nfs, http, ftp etc. Only with file. Anyone who says they have it working has probably brought the network up in a previous script. 2: The following works. <scripts> <post-scripts config:type="list"> <listentry> <filename>fetch-init.sh</filename> <interpreter>shell</interpreter> <source><![CDATA[ /etc/init.d/network start /etc/init.d/portmap start /bin/mount -r 192.168.1.1:/vol/source /mnt /bin/cp /mnt/initfile.sh /tmp /bin/umount /mnt /etc/init.d/portmap stop /etc/init.d/network stop ]]></source> </listentry> </post-scripts> <init-scripts config:type="list"> <listentry> <filename>initscript.sh</filename> <location>file:///tmp/initfile.sh</location> </listentry> </init-scripts> </scripts> Notes: 1: The network has been configured at the point the postinstall runs (if you are just using autoyast to configure it), so this works even with dhcp, and DNS. 2: portmap is necessary for NFS. If you just want to use http or ftp, then you just need the network. (curl is available in a minimal install, wget is not) 3: The reason for putting it into tmp then using the init-script, is that if there are no init-scripts defined, then autoyast will not put the hook in to run them, even if there are scripts in /var/adm/aytoinstall/init.d 4: Yes the syntax is file:///path/file. 2 slashes, the the full path starting with a /. 5: What if you don't down the network? Probably nothing, but if you have later scripts that configure the network, and it is already up, your changes wont take affect. 6: Note that even your init scripts will not have the network up when they run as of Sles10, sp1. (http://www.suse.com/~ug/autoyast_changes_SLES10SP1.html) So if your init scripts need the network, you will have to bring it up in them. Thanks all -Andrew > -----Original Message----- > From: Andrew Laden [mailto:Andrew.Laden@tudor.com] > Sent: Tuesday, December 12, 2006 3:26 PM > To: opensuse-autoinstall(a)opensuse.org > Subject: [opensuse-autoinstall] Init-scripts and nfs location > > Using autoyast on Sles 9 SP3. pxebooting using dhcp. > Installing over NFS, Autoyast file served up via NFS, so I > know that all works fine. > Autoinstall all works fine. I get a fully installed ready to > go system. > > So now I am trying to use/configure some init scripts. I have > two of them. One I have placed the source in the xml, and the > other via NFS. > > <scripts> > <init-scripts config:type="list"> > <script> > <filename>init-zeus_bootstrap</filename> > <interpreter>shell</interpreter> > > <location>nfs://192.168.1.1/vol/prod_LinuxInstall_grn_x/zeus/z > eus_bootst > rap</location> > </script> > <script> > <filename>init-online-update.sh</filename> > <interpreter>shell</interpreter> > <source><![CDATA[ > /usr/bin/online_update -s -u http://lx4-adm.grn.tudor.com/YOU > -V > /var/tmp/online-update.out 2> /var/tmp/online-update.err > ]]></source> > </script> > </init-scripts> > </scripts> > > > The one with source works fine. The other doesn't seem to work. So > 1: Is the location paramter supported on Sles 9.3 for init scripts. > 2: Is this section parsed and the files created at a time > when the network is up, so that NFS is available? > 3: Are there some log files that will help me. Since the > script never runs, there is nothing in /var/adm/autoinstall. > It looks like the script never gets copied from NFS and > placed in there. > > Thanks > -Andrew > > -- > To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org > For additional commands, e-mail: > opensuse-autoinstall+help(a)opensuse.org > > -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 1

Re: [opensuse-autoinstall] how to create customized Install CD that have pre-defined installation so
by 张韡武 17 Dec '06

17 Dec '06

在 2006-12-16六的 15:14 +0000，Yan Fitterer写道： > install=ftp://host.name/path/to/network/install/source autoyast=ftp://host.name/path/to/autoinstall.xml > > Never created a CD myself, but those are the two critical parameters you need on the kernel command line to kick off an autoinstall. And of course a working network install source and a working autoyast .xml file. > > Good luck Ah, thank you very much! I do have tried to specify 'autoyats=' and also tired to specify 'install=' but never tired to use them together! That's because I started to think autoyast and installation are not related, otherwise install source should be a part of autoyast. Stupid I am. Anyway, problem solved. > Yan > > >>> 张韡武 <zhangweiwu(a)realss.com> 16/12/2006 14:18 >>> > Hello. right now I badly need to create customized SuSE mini-install CDR > that default to install from the http installation source we provide. > > Today and yesterday I have been struggling with autoyast and (what the > hell) I cannot find a way to specify default installation source for > creating customized mini-install CD. The autoyast document > (http://www.suse.com/~ug/autoyast_doc/) has a lot of pages and I read > through them, there are all options about how to partition, how to set > up RAID, how to setup user account and do software selection, but no > simple answer on how to specify network installation source URI. I also > tried to reach a lot of webpages about yast2-cd-creator, so far it seems > yast2-cd-creator can neither use network installation source nor can it > create CDR that can use network installation source. > > I also tried to create my own bootable CDROM and assign boot parameter > 'install=ftp://our.ftp.inst-source.mirror/opensuse/distribution/10.2' > and > 'install=ftp://our.ftp.inst-source.mirror:/opensuse/distribution/10.2' > in /boot/i386/loader/isolinux.cfg and create bootable CDR with 'mkisofs > -b .. -c ..' and both do not seem to work (after boot, still prompt me > for installation source and path, default path is '/' so my path setting > seems have no effect) > > So I am completely stuck here: I don't know how can I go on. What's > worse, tomorrow is the day when we collected a lot of new guys who wish > to try Linux together for a workshop, at which event we shall distribute > the CDR. > > Before the event I planned two days for working out this issue > (yesterday and today) and I don't understand why this problem look so > simple (create CD with pre-defined installation source URI) but this > difficult to do. I almost read every webpage I can google out. > > Any other hint you can give me or link that point me to go to? > -- 锐业软服（国内业务） http://www.realss.cn Real SoftService http://www.realss.com 销售咨询(Sales Department): 0086 592 20 99987 (Chinese, German, English) 国际业务(International Sales): 0086 10 8460 6011 (German and English) 联系：厦门大学科技园，嘉庚二号楼6楼邮政：厦门大学2312号信箱（邮编361005）

1 0

Re: [opensuse-autoinstall] how to create customized Install CD that have pre-defined installation so
by Yan Fitterer 16 Dec '06

16 Dec '06

install=ftp://host.name/path/to/network/install/source autoyast=ftp://host.name/path/to/autoinstall.xml Never created a CD myself, but those are the two critical parameters you need on the kernel command line to kick off an autoinstall. And of course a working network install source and a working autoyast .xml file. Good luck Yan >>> 张韡武 <zhangweiwu(a)realss.com> 16/12/2006 14:18 >>> Hello. right now I badly need to create customized SuSE mini-install CDR that default to install from the http installation source we provide. Today and yesterday I have been struggling with autoyast and (what the hell) I cannot find a way to specify default installation source for creating customized mini-install CD. The autoyast document (http://www.suse.com/~ug/autoyast_doc/) has a lot of pages and I read through them, there are all options about how to partition, how to set up RAID, how to setup user account and do software selection, but no simple answer on how to specify network installation source URI. I also tried to reach a lot of webpages about yast2-cd-creator, so far it seems yast2-cd-creator can neither use network installation source nor can it create CDR that can use network installation source. I also tried to create my own bootable CDROM and assign boot parameter 'install=ftp://our.ftp.inst-source.mirror/opensuse/distribution/10.2' and 'install=ftp://our.ftp.inst-source.mirror:/opensuse/distribution/10.2' in /boot/i386/loader/isolinux.cfg and create bootable CDR with 'mkisofs -b .. -c ..' and both do not seem to work (after boot, still prompt me for installation source and path, default path is '/' so my path setting seems have no effect) So I am completely stuck here: I don't know how can I go on. What's worse, tomorrow is the day when we collected a lot of new guys who wish to try Linux together for a workshop, at which event we shall distribute the CDR. Before the event I planned two days for working out this issue (yesterday and today) and I don't understand why this problem look so simple (create CD with pre-defined installation source URI) but this difficult to do. I almost read every webpage I can google out. Any other hint you can give me or link that point me to go to? -- 锐业软服（国内业务） http://www.realss.cn ( http://www.realss.cn/ ) Real SoftService http://www.realss.com ( http://www.realss.com/ ) 销售咨询(Sales Department): 0086 592 20 99987 (Chinese, German, English) 国际业务(International Sales): 0086 10 8460 6011 (German and English) 联系：厦门大学科技园，嘉庚二号楼6楼邮政：厦门大学2312号信箱（邮编361005） -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 0

[opensuse-autoinstall] how to create customized Install CD that have pre-defined installation source?
by 张韡武 16 Dec '06

16 Dec '06

Hello. right now I badly need to create customized SuSE mini-install CDR that default to install from the http installation source we provide. Today and yesterday I have been struggling with autoyast and (what the hell) I cannot find a way to specify default installation source for creating customized mini-install CD. The autoyast document (http://www.suse.com/~ug/autoyast_doc/) has a lot of pages and I read through them, there are all options about how to partition, how to set up RAID, how to setup user account and do software selection, but no simple answer on how to specify network installation source URI. I also tried to reach a lot of webpages about yast2-cd-creator, so far it seems yast2-cd-creator can neither use network installation source nor can it create CDR that can use network installation source. I also tried to create my own bootable CDROM and assign boot parameter 'install=ftp://our.ftp.inst-source.mirror/opensuse/distribution/10.2' and 'install=ftp://our.ftp.inst-source.mirror:/opensuse/distribution/10.2' in /boot/i386/loader/isolinux.cfg and create bootable CDR with 'mkisofs -b .. -c ..' and both do not seem to work (after boot, still prompt me for installation source and path, default path is '/' so my path setting seems have no effect) So I am completely stuck here: I don't know how can I go on. What's worse, tomorrow is the day when we collected a lot of new guys who wish to try Linux together for a workshop, at which event we shall distribute the CDR. Before the event I planned two days for working out this issue (yesterday and today) and I don't understand why this problem look so simple (create CD with pre-defined installation source URI) but this difficult to do. I almost read every webpage I can google out. Any other hint you can give me or link that point me to go to? -- 锐业软服（国内业务） http://www.realss.cn Real SoftService http://www.realss.com 销售咨询(Sales Department): 0086 592 20 99987 (Chinese, German, English) 国际业务(International Sales): 0086 10 8460 6011 (German and English) 联系：厦门大学科技园，嘉庚二号楼6楼邮政：厦门大学2312号信箱（邮编361005）

1 0

Re: Re: [opensuse-autoinstall] [SLES 10] error using autoyast=device://cciss/c0d0p1/autoinst.xml (nested devices)
by Petteri Hakkarainen 15 Dec '06

15 Dec '06

> The use of : autoyast=device://cciss/c0d0p1/autoinst.xml failed (profile file not found error in Yast) Throw in three slashes with device, i.e. ...device:///cciss/... This notation works with floppies, anyway. Petteri -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 0

Re: Re: [opensuse-autoinstall] Re: [suse-autoinstall] SuSE 10.2 problems
by Petteri Hakkarainen 15 Dec '06

15 Dec '06

Uwe, > > >autoyast=http:/server/path/to/autoyast.xml to the append line on my > >> Isn't there one slash missing (http://)? >yes, there is one missing. >Did you find that in the documentation somewhere? No I did not find that in documentation, unless my thoughts would be considered as such (hopefully not, of course). Actually, I based my note on a conclusion that with a network protocol I've always seen two slashes to be used. If you do not have the server part, then three slahes (eg. autoyast=floppy:///path/autoinst.xml). Petteri -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 0

RE: [opensuse-autoinstall] Init-scripts and nfs location
by Andrew Laden 14 Dec '06

14 Dec '06

> Andrew Laden wrote: > > Does this work with DHCP? If you set your interfaces to configure > > themselves with dhcp, then will a simple /sbin/ifup $nic have them get > > an IP address also? (I am going back and forth with the idea of giving > > all my servers static IP's or letting them all dhcp. If I let them all > > dhcp, then I can basically use 1 xml for all my machines. If I want > > static addresses, then I have to build an xml per machine.) > > > > Yes, it works with DHCP or static, basically just uses what > AutoYaST configured the nic for at install time. I realize > now I probably just could have done a /etc/init.d/network > start || stop to achieve the same thing, I can't remember why > I made it more complex. It's been a while and just works for > us. And at this point DNS is up and configured so that works as well. > So then, I should be able to write a post-install script that /etc/init.d/network start Mount nfs share Copy file over Do chkconfig voodoo to get it to run when I want in the boot. /etc/init.d/network stop Is it that simple. (I'll let you know after I test) -Andrew -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 0

RE: [opensuse-autoinstall] Init-scripts and nfs location
by Andrew Laden 14 Dec '06

14 Dec '06

> > Uwe Gansert wrote: > > On Wednesday 13 December 2006 11:25, Uwe Gansert wrote: > > > > > >>> 1: Is the location paramter supported on Sles 9.3 for > init scripts. > >>> > >> yes > >> > > > > sorry, a network location is not supported for init-scripts on SLES9 > > > > > >>> 2: Is this section parsed and the files created at a time > when the > >>> network is up, so that NFS is available? > >>> > >> yes, that works fine (I just tried it again to be sure) > >> > > > > my test was wrong. A big sorry for that but I accidently raised the > > network up during my test by myself. > > At the time where the init-script must be fetched, the > network is down > > on SLES9. So a network <location> does not work. > > You can try <location>file:///...</location> for the > init-script and > > fetch the script with a post-script (network_needed=true) I did not > > try that but it should work > > > > > Like a lot of folks, I grew weary of XML changes and kind of > went the other route. I have a very simplistic path through > my code to generate bare bones XML, really 2, one for > patterns, one for packages, and tend to do almost all of the > post install heavy lifting in a perl script. > It's just easier for me to maintain that way, your mileage may vary. > > I also give allow my users to layer in as much bash as they'd > like in post, so they can tweak things like SSH keys and > firewall rules based on what type server they are building. > So here's how I did it: > Does this work with DHCP? If you set your interfaces to configure themselves with dhcp, then will a simple /sbin/ifup $nic have them get an IP address also? (I am going back and forth with the idea of giving all my servers static IP's or letting them all dhcp. If I let them all dhcp, then I can basically use 1 xml for all my machines. If I want static addresses, then I have to build an xml per machine.) -Andrew > <scripts> > <post-scripts config:type="list"> > <script> > <filename>final</filename> > <interpreter>perl</interpreter> > <source> > <![CDATA[ > #Find a nic to activate for %post install my $nic; > opendir(DIR,"/etc/sysconfig/network"); > foreach my $file (readdir(DIR)) { > next unless ($file =~ /^ifcfg-eth/); > print "Found $file -"; > $file =~ s/^ifcfg-//; > $nic = $file; > last; > } > closedir(DIR); > print " calling /sbin/ifup $nic!\n"; > system "/sbin/ifup $nic"; > open(NIC,">/tmp/nic"); > print NIC "$nic\n"; > close(NIC); > > # A whole bunch of PERL that does stuff like configure apt or > yum, install 3rd party software like OpenView, # Data > protector, bond production nics, setup NTP server based on > location, apply patches, etc. > # I own this code, system managers can't touch/see it. > # At this point you could wget/execute your final script(s). > > ]]> > </source> > </script> > <script> > <filename>final-user</filename> > <interpreter>shell</interpreter> > <source> > <![CDATA[ > > # Here's where I put in the system manager's BASH. They do > things like tweak firewall rules, install # SSH keys, etc. > Since APT/YUM are installed and pointed out our internal > depots, they manage all this # stuff using RPMs for the most part. > > if [ -r "/tmp/nic" ] > then > NIC=`cat /tmp/nic` > /sbin/ifdown $NIC > fi > ]]> > </source> > </script> > </post-scripts> > </scripts> > > Yes, most of this could be done with AutoYast, but I'd have > to track every RTG/DTD change, and that got tedious for me. > This also works on 9.X/OpenSuSE as well as SLES, so it's how > we do it all. Does it take a little longer than doing it all > in AutoYast? Maybe, but we tend to install once, run for a > LONG time, so it's a don't care for me. > > There's more than one way to do it, I work for HP (so we're > an HP shop needless to say :). I know this works on > ProLiants and lots of different HP desktops/laptops. > > Hope that helps, > > Lee > -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 1

RE: [opensuse-autoinstall] Init-scripts and nfs location
by Andrew Laden 14 Dec '06

14 Dec '06

> > On Wednesday 13 December 2006 11:25, Uwe Gansert wrote: > > > > 1: Is the location paramter supported on Sles 9.3 for > init scripts. > > > > yes > > sorry, a network location is not supported for init-scripts on SLES9 That makes more sense. Though I geuss the docs need a serious updating. > > > 2: Is this section parsed and the files created at a time > when the > > > network is up, so that NFS is available? > > > > yes, that works fine (I just tried it again to be sure) > > my test was wrong. A big sorry for that but I accidently > raised the network up during my test by myself. > At the time where the init-script must be fetched, the > network is down on SLES9. So a network <location> does not work. > You can try <location>file:///...</location> for the > init-script and fetch the script with a post-script > (network_needed=true) I did not try that but it should work > At that point I don't need an init_script, I can just drop the script into /var/adm/autoinstall/init.d, things should work. So can you answer the following 1: For which script types is the network available when the scripts are fetched? 2: Where is the file system located at the time that "post-script (network_needed=true) runs? Is it / or /mnt? 3: Is the network available at run time for chroot scripts (Either pre or post chroot) Thanks -Andrew -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 0