September 2005 - openSUSE Autoinstall - openSUSE Mailing Lists

RE: [suse-autoinstall] Supplementary installation-sources and version numbers
by Marlier, Ian 18 Oct '05

18 Oct '05

I'd grab the .src RPM, and change the name of the package. Leave the deps and everything alone, but if it's got a different package name then it shouldn't be overwritten. (ie, call is drdb-lars-0.7.13-0) -----Original Message----- From: Lars Neyjahr [mailto:lars.neyjahr@bcc.de] Sent: Tue 9/27/2005 9:17 AM To: suse-autoinstall(a)suse.com Subject: [suse-autoinstall] Supplementary installation-sources and version numbers Hi there, I have a few questions about installation of different versions of RPM-packages during auto-install. I use an additional installation-source which was added by "installation_sources -ea ftp://..." and I'd like to install an older (by version-number) package from this source rather than from my local SuSE-mirror. Here is an example: drbd-0.8.0-3 <= original SuSE-package which I don't want drbd-0.7.13-0.ln.0 <= my own package which I want to install How can I install a specific version - 0.7.13-0.ln.0 in this case - if the original version number is higher and how do i prevent any following online-update from installing the newer version? Thanks in advance. Bye... ...Lars -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

2 1

Prompt for partition configuration
by Jonathan 29 Sep '05

29 Sep '05

G'Morning! I have a PXE server with installs for various flavors of linux that I do testing with here at work. Something I have RedHat and Fedora doing is request the partition setup manually, and everything else is automated. (Unless there are multiple NICs, then it asks which one to do the NFS install over). I have not had any success in finding the option to tell YaST2 to prompt for partitioning setup. Currently most of the systems have a 9GB partition and a 1GB partition, then the rest of the drive as a FAT32 extended partition. Used for holding windows images that we need for testing. If a vendor/oem/manufacturer uses a particular line of technology and has problems; then it is likely that it will come to us for testing and verification before it goes to a developer. Any and all suggestions would be helpful... even better if someone told me that I could do something like... install/partitioning/drive/ <use>prompt</use>. Thanks! Jonathan

2 1

RE: [suse-autoinstall] package selection question
by Marlier, Ian 29 Sep '05

29 Sep '05

> -----Original Message----- > From: Stefan Voss [mailto:stefan.voss@itellium.com] > Sent: Thursday, September 29, 2005 11:21 AM > To: suse-autoinstall(a)suse.com > Subject: Re: [suse-autoinstall] package selection question > > Am Donnerstag, den 29.09.2005, 17:11 +0200 schrieb Joe Landman: > > Is it possible to list all the packages we want in the install > > rather > > than use one of the pre-selected package groups? I will check for > > dependencies, but I want to trim down the install we are doing (on a > > linux cluster node). Thanks. > > Like this? > > <software> > <base>Minimal+X11</base> > <packages config:type="list"> > <package>bindutil</package> > <package>bonnie</package> > ... > </packages> > </software> > I think the question is whether it's possible to skip the <base>Minimal</base> part, and explicitly state every package that you want installed. Short answer, I don't think so...and you're just going to end up with the entire Minimal set anyway. There might be a couple of packages that aren't necessary, but almost everything in that set is necessary if you're going to end up with a bootable install.

3 2

package selection question
by Joe Landman 29 Sep '05

29 Sep '05

Is it possible to list all the packages we want in the install rather than use one of the pre-selected package groups? I will check for dependencies, but I want to trim down the install we are doing (on a linux cluster node). Thanks. -- Joe Landman email: landman(a)scalableinformatics.com web : http://www.scalableinformatics.com

2 1

Re: [suse-autoinstall] rules merging vs classes merging
by Stefan Voss 28 Sep '05

28 Sep '05

Am Mittwoch, den 28.09.2005, 16:43 +0200 schrieb u: > On 9/28/05, Stefan Voss <stefan.voss(a)itellium.com> wrote: > > Hi, > > > [...] > > > > > Does somebody have a working classes example? Is merging classes > > different to merging profiles? > > > > > > > > > > Gruss, > > Stefan Voss > > > > -- > > Stefan Voss > > > > > > > > > > -- > > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > > For additional commands, e-mail: suse-autoinstall-help(a)suse.com > > > > > Stefan: > could you share the xml file for - machines with one disk: > partitioning consists of a small /boot partition and a big LVM type > partition containing logical volumes for /, swap, /usr, /var? > Here's the <partitioning> part: <partitioning config:type="list"> <drive> <device>/dev/sda</device> <initialize config:type="boolean">false</initialize> <partitions config:type="list"> <partition> <crypt_fs config:type="boolean">false</crypt_fs> <crypt_key></crypt_key> <mount>/boot</mount> <format config:type="boolean">true</format> <filesystem config:type="symbol">ext3</filesystem> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">1</partition_nr> <size>50MB</size> </partition> <partition> <crypt_fs config:type="boolean">false</crypt_fs> <crypt_key></crypt_key> <mount /> <format config:type="boolean">false</format> <lvm_group>systemvg</lvm_group> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">2</partition_nr> <size>max</size> </partition> </partitions> <use>all</use> </drive> <drive> <device>/dev/systemvg</device> <is_lvm_vg config:type="boolean">true</is_lvm_vg> <partitions config:type="list"> <partition> <filesystem config:type="symbol">reiser</filesystem> <lv_name>lvroot</lv_name> <mount>/</mount> <size>1000mb</size> </partition> <partition> <filesystem config:type="symbol">swap</filesystem> <lv_name>lvswap</lv_name> <mount>swap</mount> <size>2000mb</size> </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <lv_name>lvhome</lv_name> <mount>/home</mount> <size>250mb</size> </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <lv_name>lvopt</lv_name> <mount>/opt</mount> <size>1000mb</size> </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <lv_name>lvtmp</lv_name> <mount>/tmp</mount> <size>1000mb</size> </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <lv_name>lvusr</lv_name> <mount>/usr</mount> <size>3000mb</size> </partition> </partitions> <pesize>4M</pesize> <use>all</use> </drive> </partitioning> Gruss, Stefan Voss -- Stefan Voss

1 0

rules merging vs classes merging
by Stefan Voss 28 Sep '05

28 Sep '05

Hi, I already have working xml files (for SuSE 9.3) that installs ok for two types of machines: - machines with one disk: partitioning consists of a small /boot partition and a big LVM type partition containing logical volumes for /, swap, /usr, etc. - machines with two disks: partioning of these disks each consists of a small raid type partition and a big raid type partition. A RAID1 device is created from the two small partitions which holds /boot and another RAID1 device is created from the two big partions to hold an LVM volume group with logical volumes for /, swap, /usr, etc. Apart from the partitioning the machine setups are the same. I want to consolidate these files into the following: - one_disk.xml: Contains partitioning for 1-disk machines - two_disk.xml: Contains partitioning for 2-disk machines - common.xml: Contains everything else including LVM configuration. So a machine with one disk would be the merge of one_disk.xml + common.xml and a machine with two disks would be the merge of two_disk.xml + common.xml. I tried using rules but ran into problems because the LVM configuration is done inside <partitioning> section. A volume group is defined as another <drive> inside the <partitioning> section. When e.g. one_disk.xml and common.xml are selected via rules the merge produces a result that autoyast cannot understand. Merging works best if the files to merge don't intersect like in the rules example by Frank Steiner (http://www.bio.ifi.lmu.de/~steiner/ayex.tgz ). In Frank's example lmu.xml contains <profile> -> <configure> sections, lilo-i386.xml contains <profile> -> <install> -> <bootloader> sections and part_zassenhaus_keep.xml contains <profile> -> <install> -> <partitioning> sections. Merging them produces a valid autoyast xml file. Does somebody have a working classes example? Is merging classes different to merging profiles? Gruss, Stefan Voss -- Stefan Voss

1 0

can we use nbgrub rather than ordinary grub in the install?
by Joe Landman 27 Sep '05

27 Sep '05

Hi folks: We are setting up a cluster, and I would like to know if it is possible during the autoyast session to use nbgrub (network bootable grub) rather than ordinary grub for the bootloader. The current bootloader section looks something like this: <install> <bootloader> <activate config:type="boolean">false</activate>   <loader_device>/dev/sda</loader_device> <loader_type>grub</loader_type> <location>mbr</location> <repl_mbr config:type="boolean">false</repl_mbr> <sections config:type="list"> ... Can we replace <loader_type>grub</loader_type> with <loader_type>nbgrub</loader_type> or is there something different we need to do? The idea is that we would like to have a re-install entry for the node set up via grub, and we have the PXEboot -> autoyast installation working fine. What I would like to have is an entry in the grub menu look like this: title install-suse9-AMD64 dhcp root (nd) kernel (nd)/linux64 noapic debug verbose vga=791 install=nfs://192.168.0.1/srv/os/suse93 autoyast=nfs://192.168.0.1/srv/os/suse93/autoyast-config initrd (nd)/initrd64 Note: I have this working with nbgrub and pxeboot now for machines without a bootable image. I would like it for those with a bootable image using grub/nbgrub on the disk. -- Joe Landman email: landman(a)scalableinformatics.com web : http://www.scalableinformatics.com

3 2

Supplementary installation-sources and version numbers
by Lars Neyjahr 27 Sep '05

27 Sep '05

Hi there, I have a few questions about installation of different versions of RPM-packages during auto-install. I use an additional installation-source which was added by "installation_sources -ea ftp://..." and I'd like to install an older (by version-number) package from this source rather than from my local SuSE-mirror. Here is an example: drbd-0.8.0-3 <= original SuSE-package which I don't want drbd-0.7.13-0.ln.0 <= my own package which I want to install How can I install a specific version - 0.7.13-0.ln.0 in this case - if the original version number is higher and how do i prevent any following online-update from installing the newer version? Thanks in advance. Bye... ...Lars

1 0

Autoyast and LVM
by Danny Attar 23 Sep '05

23 Sep '05

I'm trying to create a mixture or normal and LVM partitions on a blank hard disc using Autoyast on SLES9. It creates the non-LVM partitions OK but fails with the LVM partition, saying that the Volume Group does not exist. If I switch to another virtual console and run 'pvcreate' and 'vgcreate', then switch back and press 'Retry', the installation succeeds. The partitioning section of the control file looks like this: <partitioning config:type="list"> <drive> <device>/dev/cciss/c0d0</device> <initialize config:type="boolean">true</initialize> <partitions config:type="list"> <partition> <mount>/</mount> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <partition_id config:type="integer">131</partition_id> <partition_type>primary</partition_type> <size>501MB</size> </partition> <partition> <mount>/var</mount> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <partition_id config:type="integer">131</partition_id> <size>2000MB</size> </partition> <partition> <mount>/usr</mount> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <partition_id config:type="integer">131</partition_id> <size>1500MB</size> </partition> <partition> <mount></mount> <partition_id config:type="integer">130</partition_id> <size>2048MB</size> </partition> <partition> <lvm_group>vg01</lvm_group> <partition_id config:type="integer">142</partition_id> <size>max</size> </partition> </partitions> </drive> <drive> <device>/dev/vg01</device> <is_lvm_vg config:type="boolean">true</is_lvm_vg> <partitions config:type="list"> <partition> <mount>/home</mount> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <lv_name>lv_home</lv_name> <lvm2 config:type="boolean">true</lvm2> <size>500MB</size> </partition> </partitions> </drive> </partitioning> Can anyone tell me what I am doing wrong?

2 2

Severe partitioning bugs in AY 10.0RC1
by Frank Steiner 23 Sep '05

23 Sep '05

Hi, I already read about the other problem with partition in RC1, but I think the problems I have are different. It seems that the partition_nr statement is completely ignored: This profile <partitioning config:type="list"> <drive> <device>/dev/hda</device> <partitions config:type="list"> <partition> <create config:type="boolean">true</create> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <fstopt>defaults</fstopt> <mount>swap</mount> <partition_nr config:type="integer">2</partition_nr> <size>1gb</size> </partition> </partitions> <use>all</use> </drive> </partitioning> should result in a hard disk with just /dev/hda2 as swap. But it creates /dev/hda1 as swap. In a more complicated profile, I used partition_nr to setup this partition table: /dev/hda2 swap swap defaults 1gb /dev/hda3 / ext3 defaults 15gb /dev/hda5 /local ext3 defaults 8gb /dev/hda6 /home ext3 defaults 20gb /dev/hda7 /usr/local/storage ext3 defaults max I specified all partition like above (with create, format, partition_nr). In SuSE 9.0 this would automatically create /dev/hda4 as extended partition,. With 10.0RC1 it created 4 primary partition, using /local as /dev/hda3, /home as /dev/hda4 and then failed to create another partition for /usr/local/storage (of course). I don't know if this is due to the problem with the partition_nr or if autoyast lost the functionality to autodetect that /dev/hda4 must be an extended partition. So I tried to specify another entry <partition> <create config:type="boolean">true</create> <partition_nr config:type="integer">4</partition_nr> <partition_id config:type="integer">5</partition_id> <size>max</size> </partition> according to the html documentation. This leads to /dev/hda1 swap /dev/hda2 / /dev/hda3 <extended partition> /dev/hda5 <no mount point> /dev/hda6 /local /dev/hda7 /home /dev/hda8 /usr/local/storage So this gets completely messed up :-) Especially this not-mounted /dev/hda5 partition is very very strange. So at the moment, partitioning is almost impossible with 10.0RC1 :-) I have all the y2log files available, please let me know for which examples you need them (if any). 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. *

2 8