openSUSE Autoinstall October 2008

autoinstall@lists.opensuse.org

12 participants
13 discussions

by John Willis

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!

9 years, 7 months

[opensuse-autoinstall] pattern deselection

by Oliver Schweikert

Hi all, when i deselect a pattern in yast2 (SLES10-SP2), all its packages get marked as "auto-delete". If a package has any dependencies to other packages it gets not removed, which seems reasonable. But it seems that also a dependency to another "auto-delete" packages prevents it from being deleted. Is this a correct behaviour? You can test it, by installing and removing the "print_server" pattern of SLES 10. After deinstallation, the packages "cups" and "foomatic-filter" remain. Best regards, Oliver -- Oliver Schweikert Software Development HORIBA Europe Automation Division GmbH Zabergäustr. 3 73765 Neuhausen (Germany) Tel: +49 7158-933-413 Fax: +49 7158-933-613 Email: oliver.schweikert(a)horiba.com Geschäftsführer: Thomas E. Ehmann, Yuichi Muroga, Takashi Nagano Amtsgericht Stuttgart, HRB 213200 -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

13 years, 5 months

[opensuse-autoinstall] Mysterious grub hang with autoinstall

by Gary Lowell

Hi - I'm looking for some pointers on how to figure out why grub is hanging during autoyast install. The profile was created on the target system after installing from the OpenSuSE 11 DVD. Pretty much all options and package selections were the default. I did update to autoyast2-2.16.19-0.1 to generate the profile, as the installed version appeared to go into an infinite loop trying to resolve package dependencies. After wiping the disk, and starting a network install with that profile, it hangs installing the grub rpm post install scriptlet. If I kill that process and run the grub script by hand it succeeds, and the autoyast apparently proceeds normally. I've tried several variations of this all with the same result. The command in the script that hangs is: /usr/sbin/grub --batch < /etc/grub.conf >/dev/null 2>&1 and grub.conf is: setup --stage2=/boot/grub/stage2 (hd0) (hd0,1) quit The only thing at all unusual about the system is that boot/root disk is a hardware raid array managed by an LSISAS1068E chip on the motherboard. There is only one target, and that is correctly labeled as /dev/sda. /dev/sda1 is swap, and /dev/sda2 is root (with XFS filesystem). But this all works normally with a DVD install. Any pointers on how to track this down would be greatly appreciated. Thanks, Gary -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

13 years, 9 months

[opensuse-autoinstall] openSUSE 11.0: Booting from USB stick for network install & GRUB

by Bernd Nies

Hi, I tried this page here to create a bootable USB stick for workstations that don't have a DVD drive, just a CDROM: http://en.opensuse.org/SuSE_install_from_USB_drive It boots fine from Dell Precision workstations and one can perform a network based Autoyast installation by entering the hostip, gateway, autoyast and install parameters. The USB stick is removed as soon the installer has loaded. However, when the installation reaches the point where GRUB is installed, the installer thinks that the USB stick is still there and configures wrong device names. The first internal disk becomes hd1 instead of hd0. Then when it wants to boot for the first time, it does not work because GRUB wants to load from the second internal disk. When changing the root parameter from the boot menu, then it works. Is there a way to ignore/disable the USB stick during Autoyast GRUB configuration so that the first internal disk becomes hd0? I didn't find a hint in the Autoyast documentation. http://www.suse.com/~ug/autoyast_doc/CreateProfile.Bootloader.html The only I can think of is a chroot script that modifies /etc/grub.conf /boot/grub/device.map, /boot/grub/menu.lst and run grub-install. Sample GRUB config when USB stick was used for booting: adnws001:~ # cat /etc/grub.conf setup --stage2=/boot/grub/stage2 (hd1,0) (hd1,0) quit adnws001:~ # cat /boot/grub/device.map (fd0) /dev/fd0 (hd1) /dev/sda (hd2) /dev/sdb adnws001:~ # cat /boot/grub/menu.lst # Modified by YaST2. Last modification on Fri Oct 17 08:03:07 CEST 2008 default 0 timeout 8 gfxmenu (hd1,0)/message ##YaST - activate ###Don't change this comment - YaST2 identifier: Original name: linux### title openSUSE 11.0 - 2.6.25.16-0.1 (default) root (hd1,0) kernel /vmlinuz-2.6.25.16-0.1-default root=/dev/disk/by-id/scsi-SATA_ST380011A_3JV9NCQN-part3 resume=/dev/sda2 splash=silent showopts vga=0x31a initrd /initrd-2.6.25.16-0.1-default -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

13 years, 9 months

[opensuse-autoinstall] How can I fix network configuaration settins of multiple NIC cards using AutoYast on OpenSUSE 11.0

by Alan Keng

Hi, I configured 2 NICs on my system with 2 static IP in 2 different subnets. Then I used Autoinstallation to save the XML control file. <interfaces config:type="list"> <interface> <bootproto>static</bootproto> <device>eth0</device> <ipaddr>172.24.255.11</ipaddr> <name>CK804 Ethernet Controller</name> <netmask>255.255.0.0</netmask> <startmode>auto</startmode> <usercontrol>no</usercontrol> </interface> <interface> <bootproto>static</bootproto> <device>eth1</device> <ipaddr>172.19.1.1</ipaddr> <name>82541PI Gigabit Ethernet Controller</name> <netmask>255.255.0.0</netmask> <startmode>auto</startmode> <usercontrol>no</usercontrol> </interface> </interfaces> After many installations with AutoYast, most of the time the system would detect CK804 NIC (MAC address) as eth0 and 82541PI (MAC address) as eth1. However, it is not true all the time. So there would be the case that the eth0 with name of CK804 is set to the MAC address of 82541PI NIC and eth1 with name of 82541PI is set to the MAC address of CK804. (CK804 is an integrated NIC and 82541PI is a PCI NIC card). Is there a way to make sure the network settings would be the same after every installation using AutoYast?? (I would like to have one NIC with specific IP setting and the other one has another specific IP setting all the time)? If I use the XML control file to autoinstall on another system with different 2 NICs (not CK804 and 8254 PI anymore), what will happen? By the way, the Linuxrc would always see the CK804 NIC as eth1 and 82541PI as eth0 (at least so far). Is it possible you could kindly point me to some directions so that I could solve those problems. I am not sure how the NICs are detected as eth0, eth1, etc. Why the Linuxrc always detects CK804 as eth1 but most of the time the AutoYast would detect CK804 as eth0? Thank you so much for your time and I look forward to hearing from you. Sincerely, Alan -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

13 years, 9 months

[opensuse-autoinstall] CR: /etc/init.d/autoyast script that allows reboots and runs before xdm

by Bernd Nies

Hi, A change request for the /etc/init.d/autoyast script. Benefits: * Allows an init script to reboot the system (e.g. after an update) * Runs before display manager is started so that output is visible and no user logs in while the system is being installed. The current /etc/init.d/autoyast script in openSUSE 11.0 runs 'chkconfig autoyast off" after the for-loop for executing the init scripts. ==CUT== #! /bin/sh ### BEGIN INIT INFO # Provides: autoyast # Required-Start: $syslog $local_fs # Should-Start: $remote_fs $network $time ypbind sendmail hwscan # X-Start-Before: xdm # Required-Stop: # Should-Stop: # Default-Start: 3 5 # Default-Stop: 0 1 2 6 # Short-Description: A start script to execute autoyast scripts # Description: Execute autoyast scripts ### END INIT INFO LOG_DIR="/var/adm/autoinstall/logs" SCRIPT_DIR="/var/adm/autoinstall/scripts" INITSCRIPT_DIR="/var/adm/autoinstall/init.d" if [ ! -d "$INITSCRIPT_DIR" ]; then exit 1 fi for script in `find $INITSCRIPT_DIR -type f`; do CONTINUE=1 done if [ -z "$CONTINUE" ]; then chkconfig autoyast off exit 0 fi . /etc/rc.status rc_reset case "$1" in start) # Remember status and be verbose for script in `find $INITSCRIPT_DIR -type f |sort`; do echo -n "Executing AutoYaST script: $script" BASENAME=`basename $script` sh -x $script 2&> $LOG_DIR/$BASENAME.log mv -f $script $SCRIPT_DIR rc_status -v done ;; stop) # Do nothing ;; *) echo "Usage: $0 {start|stop}" exit 1 ;; esac rc_exit ==CUT== -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

13 years, 9 months

[opensuse-autoinstall] Autoyast and NFSv4?

by Werner Hack

Hi, I want to switch my Fileserver and all NFS clients to NFSv4. But I have to check it out first :) My Fileserver is also my Autoyast Installationserver. Unfortunately NFSv4 is not compatible to NFSv3, so my big question is: Can Autoyast handle NFSv4 mounts while doing an autoinstallation? If this is true how is it configured or does Autoyast automatically switch to NFSv4 protocol? Thanks, Werner -- -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

13 years, 9 months

[opensuse-autoinstall] Postinstall-Packages with Autoyast over PXE

by Daniel Spannbauer

Hello, we've build a AutoYast-Installation with some Packages in the Postinstall-Section so the Packages are installed after the first reboot. Now, we tried the hole process over PXE-Boot. This works well, but the Packages in the Postinstall-Section are not installed. Does anybody can explain me why? Or can anybody help me to debug this? Regards Daniel -- Daniel Spannbauer Systembetreuung marco Systemanalyse und Entwicklung GmbH Tel +49 8333 9233-27 Fax -11 Rechbergstr. 4 - 6, D 87727 Babenhausen Mobil +49 171 4033220 http://www.marco.de/ Email ds(a)marco.de Geschäftsführer Martin Reuter HRB 171775 Amtsgericht München -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

13 years, 9 months

[opensuse-autoinstall] pattern preference SLES10-SP2

by Oliver Schweikert

Hi all, I have 2 pattern "Oracle9" and "Oracle10", which provide both the same capability: +Prv: Oracle Oracle9 -Prv: +Prv: Oracle Oracle10 -Prv: Another pattern requires that common capability: +Req: Oracle -Req: How can i prefer one of these pattern while installation? I tried the suggestion tag +Sug: Oracle10 -Sug: and also the recommendation tag +Rec: Oracle10 -Rec: but it does not work. Always "Oracle9" gets installed. What am I doing wrong? Best Regards, Oliver -- Oliver Schweikert Software Development HORIBA Europe Automation Division GmbH Zabergäustr. 3 73765 Neuhausen (Germany) Tel: +49 7158-933-413 Fax: +49 7158-933-613 Email: oliver.schweikert(a)horiba.com Geschäftsführer: Thomas E. Ehmann, Yuichi Muroga, Takashi Nagano Amtsgericht Stuttgart, HRB 213200 -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

13 years, 10 months

[opensuse-autoinstall] Software RAID on Suse 10.0

by Bart Wahlgren

I'm working on creating a Suse 10.0 installation DVD that will have an autoyast control file included. I'm getting the system error code was -6002 when the partitions are being laid out with software RAID. I downloaded and ran the sles10_root_fix_v0.5 in the root of the installation source. It created the driverupdate file which I included on the installation disk. However I'm still getting the system error code so the installation is failing. Did this root fix include the RAID fix or do I need the SL10.0_fixRAID.sh script? Thanks Bart Wahlgren Network Administrator Speed Script Pharmacy Systems Direct: 913-643-2454 Fax: 913-894-1802 bwahlgren(a)speedscript.com www.speedscript.com Speed Script is a registered trademark of Digital Simplistics, Inc. This electronic message, including any attachments, may contain confidential or privileged information and is intended for the individual or entity named above. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. If you have received this electronic transmission in error, please notify the sender immediately and destroy all electronic and hard copies of the communication, including attachments. -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

13 years, 10 months

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

openSUSE Autoinstall October 2008