February 2005 - openSUSE Autoinstall - openSUSE Mailing Lists

Keeping lvm-volumes over reinstallation
by Ragnar Kjørstad 16 Feb '05

16 Feb '05

Hi Is there a way to specify that existing LVM-volumes should not be deleted with autoyast in sles9? We have tried adding the volume to the autoyast-file with format=false, but the data on the volume is still lost. Our current partitioning-section looks like this: <partitioning config:type="list"> <drive> <partitions config:type="list"> <partition> <filesystem config:type="symbol">ext2</filesystem> <partition_type>primary</partition_type> <format config:type="boolean">true</format> <mount>/boot</mount> <size>100mb</size> </partition> <partition> <lvm_group>vg0</lvm_group> <partition_type>primary</partition_type> <size>max</size> </partition> </partitions> <use>all</use> </drive> <drive> <device>/dev/vg0</device> <is_lvm_vg config:type="boolean">true</is_lvm_vg> <partitions config:type="list"> <partition> <lvm_group>vg0</lvm_group> <lv_name>swap_lv</lv_name> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <size>2000mb</size> <mount>swap</mount> </partition> <partition> <lvm_group>vg0</lvm_group> <lv_name>root_lv</lv_name> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <mount>/</mount> <size>6000mb</size> </partition> <partition> <lvm_group>vg0</lvm_group> <lv_name>data</lv_name> <format config:type="boolean">false</format> <size>2000mb</size> </partition> </partitions> <pesize>4M</pesize> <use>all</use> </drive> </partitioning> -- Ragnar Kjørstad Software Engineer Scali - http://www.scali.com High Performance Clustering

1 0

RE: [suse-autoinstall] dynamically assign hostnames?
by Schumacher, Gordon 15 Feb '05

15 Feb '05

# From: Lisa Dong [mailto:lisad@scripps.edu] # Sent: Tuesday, February 15, 2005 10:22 AM # To: mfeilner(a)feilner-it.net # Cc: suse-autoinstall(a)suse.com # Subject: Re: [suse-autoinstall] dynamically assign hostnames? # # # Hi Markus, # # You can try to put the host name and IP in /etc/hosts file in # autoyast # post script. # # Lisa # # Markus Feilner wrote: # # >Hello List, # >I asked this before, but am still searching... is there a # way to avoid # >the autoinstall client naming himself "linux" ? # >If you install several boxes at the same time, the dhcp/dns # might get a # >little confused... # >;-) # >I was wondering if it's possible to name the autoinstallclient # >dynamically, with the mac-adress part of its name... any idea? I used the following - it's working well on 9.2 (obviously, you will need to change some of the name to suit your site): <post-scripts config:type="list"> <script> <filename>fix-hostname.sh</filename> <interpreter>shell</interpreter> <source><![CDATA[ #!/bin/bash suffix=$(hexdump -n 4 -e '"%x"' /dev/urandom) echo toolsgrp-$suffix.corp.mxtr.net >/etc/HOSTNAME cat >/etc/hosts <<@@@@End-Of-Hosts-File@@@@ # # hosts This file describes a number of hostname-to-address # mappings for the TCP/IP subsystem. It is mostly # used at boot time, when no name servers are running. # On small systems, this file can be used instead of a # "named" name server. # Syntax: # # IP-Address Full-Qualified-Hostname Short-Hostname # 127.0.0.1 localhost # special IPv6 addresses ::1 localhost ipv6-localhost ipv6-loopback fe00::0 ipv6-localnet ff00::0 ipv6-mcastprefix ff02::1 ipv6-allnodes ff02::2 ipv6-allrouters ff02::3 ipv6-allhosts 127.0.0.2 toolsgrp-$suffix.corp.mxtr.net toolsgrp-$suffix @@@@End-Of-Hosts-File@@@@ ]]> </source> </script> </post-scripts>

1 0

boot attribute on partition lost
by fraser_bailey＠agilent.com 15 Feb '05

15 Feb '05

Hi I install my system from CDs and layou the patirions as follows: a7lpp:/var/opt/mkcdrec # parted /dev/sda print Disk geometry for /dev/sda: 0.000-70007.199 megabytes Disk label type: msdos Minor Start End Type Filesystem Flags 1 0.031 1027.595 primary Linux-swap type=82 2 1027.595 11272.170 primary reiserfs type=83 3 11272.170 69994.138 primary reiserfs boot, type=83 However, when I regenerate the system using autoyast I get: Disk geometry for /dev/sda: 0.000-70007.199 megabytes Disk label type: msdos Minor Start End Type Filesystem Flags 1 0.031 1027.595 primary Linux-swap type=82 2 1027.595 11272.170 primary reiserfs type=83 3 11272.170 69994.138 primary reiserfs type=83 The boot attribute has been lost. How can I retain this attribute? Thanks My XML is as follows: <partitioning config:type="list"> <drive> <device>/dev/sda</device> <partitions config:type="list"> <partition> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <mount>swap</mount> <partition_id config:type="integer">130</partition_id> <partition_nr config:type="integer">1</partition_nr> <size>auto</size> </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <mount>/home</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">2</partition_nr> <size>10GB</size> </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <mount>/</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">3</partition_nr> <size>max</size> </partition> </partitions> <use>all</use> </drive> </partitioning>

1 0

RE: [suse-autoinstall] sizing swap automatically
by Campbell, Fraser 15 Feb '05

15 Feb '05

Anas Nashif wrote: > What values do you get with 'auto' set? On a machine with 3GB of RAM, "auto" sets swap to 1GB. Do you know the algorithm used for calculating the size of an auto partition? For now I'm setting swap up to my desired size with a post script like this: lvcreate -n swap -L `grep ^MemTotal /proc/meminfo | awk '{print $2}'`K vg00 mkswap /dev/vg00/swap swapon /dev/vg00/swap echo "/dev/vg00/swap swap swap pri=42 0 0" >> /etc/fstab Thanks, Fraser

2 1

dynamically assign hostnames?
by Markus Feilner 15 Feb '05

15 Feb '05

Hello List, I asked this before, but am still searching... is there a way to avoid the autoinstall client naming himself "linux" ? If you install several boxes at the same time, the dhcp/dns might get a little confused... ;-) I was wondering if it's possible to name the autoinstallclient dynamically, with the mac-adress part of its name... any idea? Thank You! -- Mit freundlichen Grüßen Markus Feilner --------------------------- Bitte beachten Sie unsere neuen Adressdaten! Vielen Dank. --------------------------- Feilner IT Linux & GIS Linux Solutions, Training, Seminare und Workshops - auch Inhouse Beraiterweg 4 93047 Regensburg fon +49 941 9465243 fax +49 941 9465244 mobil + +49 170 3027092 mail mfeilner(a)feilner-it.net web http://www.feilner-it.net

2 1

sizing swap automatically
by Campbell, Fraser 15 Feb '05

15 Feb '05

Hi, I'm wondering if there is a way to dynamically calculate a swap size. I'd like swapsize to match the size of physical memory, I had hoped that <size>auto</size> would do this but it doesn't appear to. I believe this might be possible with rules/classes but I have no idea where to start. Does any documentation exist other than that in /usr/share/doc/packages/autoyast2/html ... are there any HOWTOs on rules/classes? I am using SLES9 but network install server is SLES8. Thanks -- Fraser Campbell TD Securities, Enterprise Technology Solutions Phone: 416-308-9702 Cell: 416-568-5420

2 1

Mirror Creation with YaST
by Suffin, Charles 14 Feb '05

14 Feb '05

Guys, I'm trying to create a mirrored root disk volume (using LVM version 2) across two disks. It seems all I can do with YaST during the product installation is create stripes, not RAID1 mirrors... Does anyone know how to (or even if) I can do this? I would think this should be fairly simple, but the "Create Logical Volume" screen in YaST doesn't seem to provide an option for it. I've checked under SP1 as well, and it doesn't seem to be any different there. According to my kernel bretheren here at Stratus, mirrored root should be supported in the kernel. Is there something I can do in an autoyast XML control file that perhaps isn't available (yet) directly through YaST's menu system? Thanks in advance. -- Charlie ----- A. Charles Suffin Senior Software Engineer Stratus Technologies, Inc. 111 Powdermill Road Maynard, MA 01754-3409 US (978)461-7590

1 0

AW: [suse-autoinstall] SuSE Pro 9.2 tg3 vs bcm5700
by Andreas.Matthieu＠tfa.brandenburg.de 14 Feb '05

14 Feb '05

Hi, >Close, but has issues in postinstall. > SuSE Pro 9.2 uses bcm5700 for install, after the first reboot just before my > post install script runs tg3 is loaded somewhere. The code below does not > prevent tg3 from being loaded, but also loads bcm5700, however it is tg3 > that is being used. > Other attempts to alter files in the post install yield the same result. > i.e. I must reboot again after post install to get bcm5700. > The problem is that I have code in the post install that must use the NIC. > Attempts to unload the tg3 and load the bcm5700 in post install hang the > system because tg3 is in use for NFS install. > I think I need to remove tg3 from the install code. It is being > autodetected and used after the first reboot before postinstall. try insmod=bcm5700 at kernel cmdline for install and grub-config (see xml below). This works fine for my HPDL560 and SLES9SP1. Your network interface are activated at postinstall time? We must bring it up manually in our postinstall script, because at configuration step autoyast bring network first down, then configure it, then start postinstall and after finish all configure steps it boot the server and bring network up. Regards Andreas <?xml version="1.0"?> <!DOCTYPE profile SYSTEM "/usr/share/autoinstall/dtd/profile.dtd"> <profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <install> <bootloader> <global config:type="list"> <global_entry> <key>default</key> <value config:type="integer">0</value> </global_entry> </global> <initrd_modules config:type="list"> <initrd_module> <module>bcm5700</module> </initrd_modules> <loader_device>/dev/cciss/c0d0</loader_device> <loader_type>grub</loader_type> <location>mbr</location> <sections config:type="list"> <section config:type="list"> <section_entry> <key>title</key> <value>Linux</value> </section_entry> <section_entry> <key>kernel</key> <value>(hd0,0)/boot/vmlinuz root=6801 selinux=0 scsi=on resume=/dev/cciss/c0d0p2 splash=silent insmod=bcm5700 elevator=cfg showopts</value> </section_entry> <section_entry> <key>initrd</key> <value>(hd0,0)/boot/initrd</value> </section_entry> </section> </sections> </bootloader> </install> </profile> > -----Original Message----- > From: Andreas.Matthieu(a)tfa.brandenburg.de > [mailto:Andreas.Matthieu@tfa.brandenburg.de] > Sent: Friday, February 11, 2005 12:45 AM > To: egan(a)sense.net; suse-autoinstall(a)suse.com > Subject: AW: [suse-autoinstall] SuSE Pro 9.2 tg3 vs bcm5700 > > > Hi, > > > I am having problems with tg3 and must use bcm5700 with > SuSE Pro 9.2, > how do > > I tell autoyast not to use tg3 for install or runtime? > > > you must specify bcm5700 module for the eth0 config. Try the > following > example: > For device you can also specify: > - interface: <device>eth-id-MAC</device> > - module: <device>bus-pci-DEVICE-ID</device> > > <?xml version="1.0"?> > <!DOCTYPE profile SYSTEM "/usr/share/autoinstall/dtd/profile.dtd"> > <profile xmlns="http://www.suse.com/1.0/yast2ns" > xmlns:config="http://www.suse.com/1.0/configns"> > <configure> > <networking> > <interfaces config:type="list"> > <interface> > <bootproto>dhcp</bootproto> > <device>eth0</device> > <startmode>onboot</startmode> > </interface> > </interfaces> > <modules config:type="list"> > <module_entry> > <device>static-0</device> > <module>bcm5700</module> > <options></options> > </module_entry> > </modules> > </networking> > </configure> > </profile> > > Regards, > > Andreas Matthieu > > > -- > 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: AW: [suse-autoinstall] @import in XML file?
by Schumacher, Gordon 11 Feb '05

11 Feb '05

# From: Daniel [mailto:daniel@kerozene.de] # Sent: Friday, February 11, 2005 5:32 AM # To: suse-autoinstall(a)suse.com # Subject: Re: AW: [suse-autoinstall] @import in XML file? # # # Thanks for your help, but it doesn´t seem to work for me. # I tried it via http but my xml isn´t accepted by YaST. # # I have seen this some days ago, thougt it was something like # "@import" ....? I'm using this successfully in my setup: <profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns" xmlns:xinclude="http://www.w3.org/2001/XInclude"> ... ... <post-scripts config:type="list"> <script> <filename>get_username.sh</filename> <interpreter>shell</interpreter> <xinclude:include href="http://toolsgrp.corp.mxtr.net/autoinstall/scripts/get_username.xml" /> </script> </post-scripts> The file "scripts/get_username.xml" looks like this: <source> <![CDATA[#!/bin/sh /bin/chvt 3 exec < /dev/tty3 > /dev/tty3 ... ... /bin/chvt 1 ]]> </source> Basically, the key that I found is that the included XML file *must* have at least one XML tag enclosing it, or the parser will reject it.

1 0

AW: [suse-autoinstall] SuSE Pro 9.2 tg3 vs bcm5700
by Andreas.Matthieu＠tfa.brandenburg.de 11 Feb '05

11 Feb '05

Hi, > I am having problems with tg3 and must use bcm5700 with SuSE Pro 9.2, how do > I tell autoyast not to use tg3 for install or runtime? you must specify bcm5700 module for the eth0 config. Try the following example: For device you can also specify: - interface: <device>eth-id-MAC</device> - module: <device>bus-pci-DEVICE-ID</device> <?xml version="1.0"?> <!DOCTYPE profile SYSTEM "/usr/share/autoinstall/dtd/profile.dtd"> <profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <configure> <networking> <interfaces config:type="list"> <interface> <bootproto>dhcp</bootproto> <device>eth0</device> <startmode>onboot</startmode> </interface> </interfaces> <modules config:type="list"> <module_entry> <device>static-0</device> <module>bcm5700</module> <options></options> </module_entry> </modules> </networking> </configure> </profile> Regards, Andreas Matthieu -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

2 1