openSUSE Autoinstall February 2008

autoinstall@lists.opensuse.org

20 participants
28 discussions

[opensuse-autoinstall] breaking installs on SLES 9 and SLES 10
by John Willis 26 Feb '08

26 Feb '08

I'm pretty sure I need to open a TID for this but thought I'd ask here. SLES 9 and SLES 10 do not properly install from a network install source where all the iso images are copied on top of one another. That is if you treat SLES like Red Hat the result is maybe an install maybe not but missing packages and broken links in the file system. Is there a way to tell the installer to check the gpg keys per media before attempting an install and wasting a lot of time? I work with a couple SUSE Professional "experts" who claim it's "just like Red hat" and hate following directions. I'd rather it just broke. -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

4 3

[opensuse-autoinstall] Option: keep_install_network since opensuse 10.3
by Hans-Joachim Ehlers 25 Feb '08

25 Feb '08

Hi i just would like to know what the option really does and what not. The reason i ask is that i would like to keep hostname and ip from the network boot process provided by dhcp. Thus after the final installation the network configuration is static and does not depends on dhcp any more. Also i would like to know if this function will keep ALL network configuration ( dsn server, gateway and what soever ) or can the autoinst.xml have still some network options. Some example are appreciated tia and have a nice weekend Hajo ============================ Hans-Joachim Ehlers UNIX Systems Engineer EUMETSAT Am Kavalleriesand, 31 64295, Darmstadt, Germany Tel : +49 6151 807-7307 mailto:hansjoachim.ehlers@eumetsat.int http://www.eumetsat.int -- 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] How can I allow shutdown (hibernate,...) only for root?
by Markus Roeffen 20 Feb '08

20 Feb '08

Hi all, in my current autoyast configuration every user can shutdown (or hibernate) the installed computer. How can I prevent this and restrict these operations to the root account? Thanks in advance. Best Regards Markus -- ------------------------------- Markus Roeffen Institut für Wasserbau IWS Universität Stuttgart Pfaffenwaldring 61 70569 Stuttgart Tel: +49(0)711/685-67010 Fax: +49(0)711/685-67020 Mail: markus.roeffen(a)iws.uni-stuttgart.de -- 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] custom rules
by Frank Steiner 12 Feb '08

12 Feb '08

Hi, I need to match against some hostnames for selecting a profile. I have sth. like <rule> <custom1> <script> <![CDATA[ #!/bin/sh . /var/lib/dhcpcd/dhcpcd-eth0.info echo -n $HOSTNAME ]]> </script> <match>*</match> <match_type>exact</match_type> </custom1> <result> <profile>profiles/part_@custom1@_keep.xml</profile> <continue config:type="boolean">true</continue> </result> </rule> But now I want to select one profile for 10 certain hostnames. How can I do that in an elegant way? What I can do is rewrite the <custom1><script>...</script><match>...</custom1> part 10 times and AY will redo that script 10 times. But since AY saves the value of "$custom1" while working on rules.xml (seenin y2log), it should be possible to reuse the determined value instead of redefining it over and over again. However, <rule> <custom1> <match>turing</match> </custom1> ... </rule> redefines $custom1 to "" instead of working on the former value. Is it possible to re-use the value for custom1 when a former rule has defined it to some value? If not, I vote for adding this feature! cu Frank -- Dipl.-Inform. Frank Steiner Web: http://www.bio.ifi.lmu.de/~steiner/ Lehrstuhl f. Bioinformatik Mail: http://www.bio.ifi.lmu.de/~steiner/m/ LMU, Amalienstr. 17 Phone: +49 89 2180-4049 80333 Muenchen, Germany Fax: +49 89 2180-99-4049 * Rekursion kann man erst verstehen, wenn man Rekursion verstanden hat. * -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 3

[opensuse-autoinstall] lilo bug in SLES10 SP1 when using own kernel rpms
by Frank Steiner 12 Feb '08

12 Feb '08

Hi, we use our own kernel rpms. Installing them on a SLES10 SP1 system after AY finished works fine, it also works when selecting them for a SuSE 10.1 installation with AY (using the SLES10 SP1 installer (kernel/initrd)). But when installing a SLES10 SP1 system and trying to select our own kernel rpm as kernel package in AY, the generation of lilo.conf fails. It ends up like image = nts/instsys/boot/vmlinuz-2.6.16-12suse-bio-smp label = SLES_10_SP1 initrd = nts/instsys/boot/initrd-2.6.16-12suse-bio-smp In y2log I find: 2008-02-12 12:34:37 <1> 141.84.1.24(3834) [YCP] Bootloader.ycp:590 section SLES_10_SP1: converting old kernel parameter from /boot/vmlinuz to nts/instsys/boot/vmlinuz-2.6.16-12suse-bio-smp 2008-02-12 12:34:37 <1> 141.84.1.24(3834) [YCP] Bootloader.ycp:590 section SLES_10_SP1: converting old initrd parameter from /boot/initrd to nts/instsys/boot/initrd-2.6.16-12suse-bio-smp Uwe, do you have any idea what could go wrong here? cu, Frank -- Dipl.-Inform. Frank Steiner Web: http://www.bio.ifi.lmu.de/~steiner/ Lehrstuhl f. Bioinformatik Mail: http://www.bio.ifi.lmu.de/~steiner/m/ LMU, Amalienstr. 17 Phone: +49 89 2180-4049 80333 Muenchen, Germany Fax: +49 89 2180-99-4049 * Rekursion kann man erst verstehen, wenn man Rekursion verstanden hat. * -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 1

[opensuse-autoinstall] Support for partitionable md?
by Michael Leun 08 Feb '08

08 Feb '08

Hello, What about support of partitionable md devices (in opensuse / sles generally and autoyast)? -- MfG, Michael Leun -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 2

[opensuse-autoinstall] RAID 1 and LVM Autoinstall issue on SL 10.0
by Bart Wahlgren 08 Feb '08

08 Feb '08

Hello All I'm working on creating an auto-installation profile for servers that we use at my employers. Here is the my desired drive configuration from the machine I wish to duplicate: Device Size Type Mount /dev/sda1 133.3M Linux RAID /dev/sda2 186.1G Linux RAID /dev/sdb1 133.3M Linux RAID /dev/sdb2 186.1G Linux RAID /dev/md0 133.2M MD Raid /boot /dev/md1 186.1G MD Raid /dev/system 186.1G LVM2 system /dev/system/root 153.1G LV / /dev/system/swap 1.0G LV swap /dev/system/tmp 16.0G LV /tmp /dev/system/var 16.0G LV /var It appears to be doing an install the gui shows files being copied but I've noticed that there is no hard drive activity. After a few minutes of doing that the install locks up. Once this is locked I don't have any logs to show what went wrong is there a way to start autoyast in debug? When the machine is rebooted an fdisk utility shows that the RAID partitions have been created. What am I doing wrong? Thank you in advance for your assistance. Partitioning section of the control file. <partitioning config:type="list"> <drive> <device>/dev/md1</device> <lvm_group>system</lvm_group> <partitions config:type="list"> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <lv_name>root</lv_name> <mount>/</mount> <size>max</size> </partition> <partition> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <lv_name>swap</lv_name> <mount>swap</mount> <size>1gb</size> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <lv_name>tmp</lv_name> <mount>/tmp</mount> <size>16gb</size> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <lv_name>var</lv_name> <mount>/var</mount> <size>16gb</size> </partition> </partitions> <pesize>4M</pesize> <type config:type="symbol">CT_LVM</type> <use>all</use> </drive> <drive> <device>/dev/sdb</device> <initialize config:type="boolean">false</initialize> <partitions config:type="list"> <partition> <create config:type="boolean">true</create> <crypt>twofish256</crypt> <filesystem config:type="symbol">unknown</filesystem> <format config:type="boolean">false</format> <loop_fs config:type="boolean">false</loop_fs> <mount></mount> <partition_id config:type="integer">253</partition_id> <raid_name>/dev/md0</raid_name> <raid_options> <chunk_size>4096</chunk_size> <raid_type>raid1</raid_type> </raid_options> <size>+128Mb</size> <use>1</use> </partition> <partition> <create config:type="boolean">true</create> <crypt>twofish256</crypt> <format config:type="boolean">false</format> <loop_fs config:type="boolean">false</loop_fs> <partition_id config:type="integer">253</partition_id> <raid_name>/dev/md1</raid_name> <raid_options> <chunk_size>4096</chunk_size> <raid_type>raid1</raid_type> </raid_options> <size>max</size> <use>2</use> </partition> </partitions> <type config:type="symbol">CT_DISK</type> </drive> <drive> <device>/dev/sda</device> <initialize config:type="boolean">true</initialize> <partitions config:type="list"> <partition> <create config:type="boolean">true</create> <crypt>twofish256</crypt> <filesystem config:type="symbol">unknown</filesystem> <format config:type="boolean">false</format> <loop_fs config:type="boolean">false</loop_fs> <mount></mount> <partition_id config:type="integer">253</partition_id> <raid_name>/dev/md0</raid_name> <raid_options> <chunk_size>4096</chunk_size> <raid_type>raid1</raid_type> </raid_options> <size>+128mb</size> <use>1</use> </partition> <partition> <create config:type="boolean">true</create> <crypt>twofish256</crypt> <format config:type="boolean">false</format> <loop_fs config:type="boolean">false</loop_fs> <partition_id config:type="integer">253</partition_id> <raid_name>/dev/md1</raid_name> <raid_options> <chunk_size>4096</chunk_size> <raid_type>raid1</raid_type> </raid_options> <size>max</size> <use>2</use> </partition> </partitions> <type config:type="symbol">CT_DISK</type> </drive> </partitioning> -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 2

[opensuse-autoinstall] Prevent conflicting MAC addresses
by Ryan McCain 07 Feb '08

07 Feb '08

When I build my initial xml file using the clone feature it uses the MAC address of the server I created the xml file on. -snip- <interfaces config:type="list"> <interface> <bootproto>static</bootproto> <device>eth-id-00:1c:23:cb:7e:aa</device> <ipaddr>10.120.160.231</ipaddr> <netmask>255.255.254.0</netmask> <startmode>auto</startmode> <usercontrol>no</usercontrol> </interface> </interfaces> -snip- <FW_DEV_EXT>any eth-id-00:1c:23:cb:7e:aa</FW_DEV_EXT> -snip- ...Rather than using <ask> and having the person installing the OS manually enter the MAC address is there something I can replace the MAC address with? Possibly just "eth0"? Thanks -- 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] bootloader problem (10.3)
by Harry ten Berge 06 Feb '08

06 Feb '08

Hi, We're using AutoYaST for installing some servers. We've encountered a strange problem: installation on a HP DL380 works perfectly, as ware the same installation on a HP DL360 fails after the first reboot. It looks like grub isn't found on the disk. Both servers have the same SCSI controller (cciss). On a DL380 the following partition configuration is enough to work: <partitioning config:type="list"> <drive> <device>/dev/cciss/c0d0</device> <partitions config:type="list"> <partition> <filesystem config:type="symbol">swap</filesystem> <create config:type="boolean">true</create> <mount>swap</mount> <partition_nr config:type="integer">1</partition_nr> <size>4gb</size> </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <create config:type="boolean">true</create> <mount>/</mount> <partition_nr config:type="integer">2</partition_nr> <size>10gb</size> </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <create config:type="boolean">true</create> <mount>/HITT</mount> <partition_nr config:type="integer">3</partition_nr> <size>max</size> </partition> </partitions> <use>all</use> </drive> </partitioning> On a DL360 this fails. We've added a bootloader element like this: <bootloader> <activate config:type="boolean">true</activate> <loader_device>/dev/cciss/c0d0</loader_device> <loader_type>grub</loader_type> <location>mbr</location> <repl_mbr config:type="boolean">true</repl_mbr> </bootloader> <partitioning config:type="list"> <drive> <device>not_set</device> <initialize config:type="boolean">true</initialize> <partitions config:type="list"> <partition> <filesystem config:type="symbol">ext3</filesystem> <create config:type="boolean">true</create> <mount>/boot</mount> <partition_type>primary</partition_type> <size>100mb</size> </partition> <partition> <filesystem config:type="symbol">swap</filesystem> <create config:type="boolean">true</create> <mount>swap</mount> <partition_nr config:type="integer">1</partition_nr> <size>4gb</size> </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <create config:type="boolean">true</create> <mount>/</mount> <partition_nr config:type="integer">2</partition_nr> <size>10gb</size> </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <create config:type="boolean">true</create> <mount>/HITT</mount> <partition_nr config:type="integer">3</partition_nr> <size>max</size> </partition> </partitions> <use>all</use> </drive> </partitioning> But this doesn't work either. But now comes the strange part: if we take the 10.3 DVD and install this server by hand it works flawlessly! So any help is appreciated. We're completely lost :-( Regards Harry -- 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] Trying to set NTP w/ <ask> on SLES 10 SP1 (64bit)
by Ryan McCain 06 Feb '08

06 Feb '08

I'm trying to install SLES 10 SP1 (64bit) XML file below: <general> <ask-list config:type="list"> <ask> <path>ntp-client,peer,address</path> <question>Enter NTP server:</question> <stage>initial</stage> <default>timestate1.dss.la.gov</default> </ask> </ask-list> <ntp-client> <configure_dhcp config:type="boolean">false</configure_dhcp> <peers config:type="list"> <peer> <address>timeref.dss.la.gov</address> <initial_sync config:type="boolean">true</initial_sync> <options></options> <type>server</type> </peer> </peers> <start_at_boot config:type="boolean">true</start_at_boot> <start_in_chroot config:type="boolean">false</start_in_chroot> </ntp-client> .. .. </general> ..I get prompted to enter the NTP server and enter it at the start of the install. However, when the server finishes, timeref.dss.la.gov is in /etc/ntp.conf, not timestate1.dss.la.gov. Do I have things in the wrong order? Does <ntp-client> need to be in another part of the XML file? Any help is appreciated. Ryan -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

3 8

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

openSUSE Autoinstall February 2008