June 2011 - openSUSE Autoinstall - openSUSE Mailing Lists

AW: [suse-autoinstall] auto install with service pack
by Martin.Linten＠rzf.fin-nrw.de 15 May '25

15 May '25

Hallo Anas, hallo list! I am trying to install sles8 with service pack 2 in an automated way. The kernel and the inird from the sp2-CD (chosen because of hardware support) are booted via pxe. When checking the software selection I always get a long list of dependency errors beginning with "aaa_skel not available..." and so on. Please help and tell me how I can do better! I suppose it has nothing to do with the /UnitedLinux-i386-1 directory, but maybe I am wrong... My nfs-exported directory for linuxrc looks like this: |--boot | `--loader |--content (file from sles8) |--media.1 (from sles8) |--sles8 | |--UnitedLinux | |--boot | |--docu | |--dosutils | |--media.1 | |--media.2 | |--media.3 | |--suse | `--yast |--sp2 | |--UnitedLinux | |--boot | |--docu | |--i386 | |--images | |--linux | `--media.1 `--yast |--ul |--instorder (file) `--order (file) I011-52:/autoinst/suse/sles8sp2/yast # cat order /sles8 /sles8 /sp2 /sp2 I011-52:/autoinst/suse/sles8sp2/yast # cat instorder # I want to prefer sp2 packages if possible /sp2 /sp2 /sles8 /sles8 Thanks a lot, Martin -----Ursprüngliche Nachricht----- Von: Anas Nashif [mailto:nashif@suse.de] Gesendet am: Dienstag, 15. Juli 2003 09:39 An: Aaron McSorley Cc: suse-autoinstall(a)suse.com Betreff: Re: [suse-autoinstall] auto install with service pack Hi, It can be done in an automated way. For example, my nfs export for SLES8 i386 with SP2 looks like this: |-- SP2 | |-- UnitedLinux | |-- boot | |-- docu | |-- i386 | |-- images | |-- linux | `-- media.1 |-- SuSE-Linux-SLES-i386-8 | `-- CD1 | |-- boot | |-- docu | |-- media.1 | |-- suse | `-- yast |-- UnitedLinux-i386-1 | |-- CD1 | | |-- UnitedLinux | | |-- boot | | |-- docu | | |-- dosutils | | `-- media.1 | `-- CD2 | |-- UnitedLinux | |-- boot | `-- media.2 |-- boot | `-- loader |-- media.1 `-- yast `-- ul in the directory yast, there are 2 files: order and instorder This is the content which references the location of the root of every source. (where the media.1 directory is available) # cat yast/instorder /UnitedLinux-i386-1/CD1 /UnitedLinux-i386-1/CD1 /SP2 /SP2 /SuSE-Linux-SLES-i386-8/CD1 /UnitedLinux-i386-1/CD1 avicenna:/work/CDs/sles8-i386 # cat yast/order /SP2 /SP2 /SuSE-Linux-SLES-i386-8/CD1 /SuSE-Linux-SLES-i386-8/CD1 /UnitedLinux-i386-1/CD1 /UnitedLinux-i386-1/CD1 (delimiter is tab) more details can be found at http://www.suse.de/~nashif/autoinstall/8.1/html/advanced.html#AEN1251 Hope that helps... Anas Aaron McSorley wrote: > Is there a method for incorporating a service pack into an > auto install of SLES8. > > I tried putting the service pack in its own directory in my auto install > repository > and giving it preference in the order and instorder directories. > The install starts ok but, after package install I get alot of package > install failures. > After hitting ok to the fail log it prompts me to insert the service > pack cdrom. > > I thought about just replacing the original packages with the new ones > from the service pack but, > I would like to keep the service pack separate from the original > repository so I can > install without it if I want. > > thanks > -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

3 2

linuxrc - netdevice=<hwaddress>
by John Willis 18 Dec '12

18 Dec '12

Does anyone know if any of the SLES releases 9 or 10 support passing the linuxrc option netdevice=<hardware mac address> ? I noticed Red Hat has had this for sometime and it seems totally missing in SuSE which seems really odd. I'm still scratching my head if we really are still passing only by kernel interface name. I read in the change log for linuxrc-1.8.6-3 a change that "sounds" like this feature. * Mon Mar 14 2005 - snwint(a)suse.de - s390: fix segfault in net_list_s390_devs() - extra root image was sometimes not used - allow netdevices to be specified by hwaddress But it looks like linuxrc-1.8.6-3 is only available in SuSE Professional 9.3. "any" commentary would be sincerely appreciated the feature also seems to be fairly minor since any delimiter seperating the octets in the hwaddr string could be used to identify the difference between an interface name and interface hw address if i could figure out a generic method of overriding the linuxrc with a custom script and daisy chain it back into linuxrc after setting up the interface name, I would.. and have a slight idea on how to do that.. but i'd rather find out i'm just missing something and the feature is already there Thanks!

3 2

[opensuse-autoinstall] autoyast with multiple LVM Volume Groups
by big beer 07 Sep '12

07 Sep '12

Hello, I'm trying to have autoyast setup some LVM volume groups. I can get things setup with a single volume group, but if try to add 2 volume groups I seem to be running into some issue. I'm using the following xml inside the partitioning section to setup the PVs and add to the volume groups. . . . <drive> <device>/dev/sdb</device> <partitions config:type="list"> <partition> <lvm_group>firstvg</lvm_group> <partition_type>primary</partition_type> <size>max</size> </partition> </partitions> <use>all</use> </drive> <drive> <device>/dev/sdc</device> <partitions config:type="list"> <partition> <lvm_group>secondvg</lvm_group> <partition_type>primary</partition_type> <size>max</size> </partition> </partitions> <use>all</use> </drive> . . . The problem is that both disks are configured as PVs in the same VG. Both sdb and sdc will be added to firstvg and secondvg will not exist. Am I trying this wrong or am I hitting some sort of bug? thanks -- bigbeer -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

5 7

[opensuse-autoinstall] Repository Priority
by Tim Kirby 28 Sep '11

28 Sep '11

Repository Priority is obviously a useful thing to be able to manipulate. Yast lets me set it and zypper lets me set it. Yet, if I have multiple repositories defined at the beginning of my autoyast (including update repos so I get an up to date system built out of the box), I don't seem to have any control over the respective repository priorities - they're all defaulted. Or did I miss a subtle option somewhere? Tim -- Tim Kirby 651-605-9074 trk(a)cray.com Cray Inc. Information Systems -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

3 2

[opensuse-autoinstall] Identification of NICs by MAC address
by Sebastian Wenner 24 Aug '11

24 Aug '11

Hi, is there a way of identifying NICs by MAC address rather than by interface name? We have several multi-nic machines where we run into trouble with "normal" interface names. They have e.g. 4 onboard nics, powered by the bnx2 driver and an additional quad-port card powered by the e1000 driver. If the e1000 gets loaded before the bnx2, the first onboard (which is our usual link into the install network) comes up as eth4 instead of eth0. Identifying the adapter by its mac address would do a great job to avoid this confusion... Is there a way of specifying this in the autoyast file and at the boot prompt? Best regards Sebastian -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

10 20

[opensuse-autoinstall] Partition/sector boundary alignment
by Paul 12 Aug '11

12 Aug '11

Hi, Can anyone suggest how to ensure AutoYAST creates partitions that are aligned to 4K boundaries? As far as I can tell, AY doesn't allow for specifying start sectors -- only by size. I understand that without such alignment the disk I/O subsystem will be worked harder than it needs to be in order to satisfy requests. My build will be SLES11sp1 on both physical and VMware. Thanks, -Paul -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

4 4

[opensuse-autoinstall] linuxrc udev.rule with two rules
by michael.leu＠mgb.ch 19 Jul '11

19 Jul '11

Hello How can you specify more than one udev rule with linuxrc? All examples I have found so far show only a single rule being specified. I tried it with a space, but this does not seem to work. udev.rule="mac=de:ad:00:00:be:ef,name=eth0 mac=de:ad:00:00:be:ee,name=eth1" Thanks Michael -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

4 8

[opensuse-autoinstall] Specifying a local (i.e. on DVD) Add-On Repository in add_on_products.xml for SLES 11 SP1
by Jason Babicka 18 Jul '11

18 Jul '11

Hello! My employer is looking to move to SLES 11 SP1 for hosting one of our products. In addition to default packages that are included with the SLES 11 SP1 Installation DVD, they want to include several 3rd Party RPMs and package all of this on one DVD to send to our clients. From reading Uwe Gansert's Blog, I followed the instructions that he listed (FAQ 2.4) for setting up a YaST Repository that can be included on the DVD. After doing this, I created the add_on_products.xml per Uwe's blog (The one entitled "SLES 11 and add-ons"). After doing this, I was able to build an ISO that contained all of the original SLES 11 SP1 files and the additional 3rd Party RPMs. When we perform an onsite installation, we use a predefined autoinstall.xml file that is located on a USB Drive. Unfortunately, when I tried doing this the installation screen printed a message that said "Unable to add product cd:////updates?devices=/dev/sr0". When I saw this, my first thought was that perhaps I had the format of the add_on_products.xml file incorrect. Here is a copy of my add_on_products.xml file: <?xml version="1.0"?> <add_on_products> <product_items config:type="list"> <product_item> <name>Updates</name> <url>relurl:///updates</url> </product_item> </product_items> </add_on_products> Like I had mentioned above, I need to include the add-on repository so that it is located on the installation DVD. The updates directory-which contains the 3rd Party RPM Packages-is located at the root level of the DVD. Per Uwe's suggestion in a comment on his blog, I used "relurl://" so that AutoYaST knew to look on the installation source for the add-on repository. Also, since this is probably relevant as well. We use an autoinstall.xml file to perform an automatic installation of the OS. We do this by choosing the Installation option when the system boots up and specifying "autoyast=usb:///autoinstall.xml" as the command line option. In order to keep this email from being too long, I will not include any snippets from the /var/log/YaST2/y2log right now. If this would be useful, please let me know which parts I can provide to help with this issue. I would appreciate any help that anyone might be able to offer in helping to resolve this issue that I am seeing. -Jason This transmission may contain information that is privileged, confidential, and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 9

[opensuse-autoinstall] Finding the autoyast xml file no matter what the CD device name
by Froggatt David 17 Jun '11

17 Jun '11

Hi, Installing SLES 10.3, I'd like to pull the autoyast xml file from the small custom ISO/CD I've booted from, whilst using an FTP site as the location for the install files. For a particular machine I can do this OK with something like this in the isolinux.cfg: autoyast=device://hdc/autoinst.xml install=ftp://<server_name>/sles10.sp3.64/ However, depending on the machine the CD might actually be hda or sr0 or something else, in which case I'll get an error saying the profile can't be found. I'd therefore like a more general 'autoyast=' statement that will find the xml file no matter what the CD's device name. Using 'autoyast=default' doesn't seem to work, as I think the fact that my installation source is FTP means that it's looking there rather than the CD. I realise that I could also grab the xml file via FTP, but the way we install servers it would me much more convenient to have it on the CD. Any suggestions as to how I can always find the xml file no matter what the CD device name gratefully received. Regards, David IMPORTANT NOTICE: This message is intended for the addressee only. The content may be confidential, legally privileged and protected by law. Unauthorised use, copying or disclosure of any of it may be unlawful. If you are not the intended recipient please notify the sender and remove it from your system. Internet emails are not necessarily secure. Although we have taken steps to ensure this email and attachments are free from any virus, we advise that in keeping with good computing practice you should ensure they are actually virus free. The right to monitor email communications through our network is reserved by us. Sopra Group Limited (Registered in England, No. 1588948) with Registered Offices at: Middlesex House, Meadway Technology Park, Rutherford Close, Stevenage, Hertfordshire, SG1 2EF. VAT No. 366 9784 84. -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 4

[opensuse-autoinstall] Can't get online update to work in autoyast install
by winfried_mb2＠xmsnet.nl 15 Jun '11

15 Jun '11

I'm trying to let autoyast do an online update during installation. First I tried with <do_online_update config:type="boolean">true</do_online_update> but that didn't work. Moreover I read here http://lists.opensuse.org/opensuse-autoinstall/2009-04/msg00028.html that if you want to add repositories you should do the update at the end of the installation. So now I'm trying to do it in a post-install script (see below), but then I get the following feedback: +zypper ar -f http://download.opensuse.org/update/11.4 updates System management is locked by the application with pid 2579 (y2base). Close this application before trying again. +zypper ar -f ftp://download.nvidia.com/opensuse/11.4/ nvidia System management is locked by the application with pid 2579 (y2base). Close this application before trying again. +zypper --non-interactive --gpg-auto-import-keys update --auto-agree-with-licenses --force-resolution System management is locked by the application with pid 2579 (y2base). Close this application before trying again. So what is the best time to do the update? Thanks a lot in advance for any help, Winfried autoinstall.xml snippet: <scripts> <post-scripts config:type="list"> <script> <source> <![CDATA[ zypper ar -f http://download.opensuse.org/update/11.4 updates zypper ar -f ftp://download.nvidia.com/opensuse/11.4/ nvidia zypper --non-interactive --gpg-auto-import-keys update --auto-agree-with-licenses --force-resolution ]]> </source> <network_needed config:type="boolean">true</network_needed> <interpreter>shell</interpreter> <notification>Please wait while online update is running ...</notification> <feedback config:type="boolean">true</feedback> </script> </post-scripts> </scripts> -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

3 3