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

RE: [suse-autoinstall] 2 lilo bugs with 10.0RC1
by Robison, Jonathon (M.) 23 Sep '05

23 Sep '05

RC4 isn't released yet. --Jon Robison -----Original Message----- From: Uwe Gansert [mailto:ug@suse.de] Sent: Thursday, September 22, 2005 10:06 AM To: suse-autoinstall(a)suse.com Subject: Re: [suse-autoinstall] 2 lilo bugs with 10.0RC1 On Thursday 22 September 2005 15:58, Frank Steiner wrote: > Thus, at the moment I don't find any way to install lilo at all :-/ if you want to report bugs please use RC4 (the final version) and please use https://bugzilla.novell.com That makes it possible for me to track bugs and to assign them to other people if needed. It's hard for me to reassign bugs that are just reported to the mailinglist. I have to create a bug in bugzilla by myself and then be the "man in the middle" of bugzilla and mailinglist if more infos are needed. If I'm responsible for the bug anyway, that's no problem but often I have to reassign the bug to someone else who is not even on the mailinglist. -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nuernberg, Germany e-mail: uwe.gansert(a)suse.de, Tel: +49-(0)911-74053-0, Fax: +49-(0)911-74053-476, Web: http://www.suse.de -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

2 lilo bugs with 10.0RC1
by Frank Steiner 22 Sep '05

22 Sep '05

Hi, I'm using the following profile for the bootloader: <bootloader> <global> <global_entry> <key>append</key> <value>vga=0x0301 apic apm=power-off splash=0</value> </global_entry> </global> <loader_device>/dev/hda</loader_device> <loader_type>lilo</loader_type> <location>custom</location> <kernel_parameters>vga=0x0301 apic apm=power-off splash=0</kernel_parameters> </bootloader> Two errors occur: 1) I'm using the global append entry and kernel_parameters, because later I remove all append-lines from the sections (in a post-install script) to have just one global append line. However, to get my parameters in for the first reboot, kernel_parameters is needed, too, because autoyast always creates append lines per section in lilo.conf. So the global append is useless until the section append-lines are removed, however, I want to include it already here. This worked with earlier versions, but with 10.0RC1 no append line is created in the global section of the lilo.conf. 2) autoyast creates a "default" entry without a rhs, i.e. the lilo.conf contains ... default ... causing autoyast to complain it could not setup the bootloader. 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 5

10.0RC1 choosing wrong kernel
by Frank Steiner 22 Sep '05

22 Sep '05

Hi, I'm running autoyast 10.0RC1 on an AMD64 host with 4GB RAM and one AMD64 4000+ CPU. However, I'm installing the 32bit version, not the x86_64 version, because we don't have a concept for parallel usage of 32 and 64bit versions (just working on this). Autoyast selects the kernel-bigsmp package for installation instead of kernel-default. In y2log I find ProbeKernel: non SMP board Physical memory: 3758096384 Kernel switch: mem >= 4GB && PAE ProbeKernel determined: ["kernel-bigsmp"] I don't think this makes sense, because kernel-default is configured with CONFIG_HIGHMEM4G=y, while kernel-bigsmp is using CONFIG_HIGHMEM64G=y So why would one want a SMP kernel configured for up to 64GB RAM on a single-cpu machine with 4GB RAM, instead of a single-cpu kernel configured for up to 4GB RAM? Yes, I know I can force the kernel, but I would prefer the probing to take the correct choice :-) 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. *

1 0

RAID building in autoyast
by Joe Landman 21 Sep '05

21 Sep '05

Hi folks I am looking for an example of a simple md based raid. I need to build a machine with 2 drives, sda and sdb being partitioned in a particular way, with a large /dev/md0 set up as a RAID0 with specific chunksize for this application. Is there such an example floating around? I looked through the docs/faqs on the suse site and didn't see it, though I might have missed it. If you know of this somewhere, please send a pointer. Thanks! -- Joe Landman landman(a)scalableinformatics.com http://www.scalableinformatics.com

2 1

Bugs in opensuse 10.0
by Frank Steiner 21 Sep '05

21 Sep '05

Hi, currently testing opensuse 10.0 rc1, I found the following bugs in autoyast: - The hostname variable still contains the IP and not the hostname, at least when booting with PXE/DHCP. So the following rule <rule> <hostname> <match>cantor</match> <match_type>exact</match_type> </hostname> <result> <profile>profiles/part_cantor_create.xml</profile> <continue config:type="boolean">true</continue> </result> </rule> results in this code (from y2log): 2005-09-21 10:15:49 <1> linux(3662) [YCP] AutoInstallRules.ycp:386 Bash return: if ( [ "$hostname" = "cantor" ] ) ; then exit 0; else exit 1; fi ($["exit":1, "stderr":"", "stdout":""]) ($["arch":"i386", "hostname":"141.84.x.xx"]) So hostaddress and hostname both contain the IP. - in bootloader.dtd there is a definition <!ELEMENT kernel_parameters (#PCDATA)> but this element is not listed in the bootloader element: <!ELEMENT bootloader (activate?, global?, initrd_modules?, loader_device?, loader_type?, location?, repl_mbr?, sections?)> In earlier versions it was listed behing the "location" and according to the documentation it still should... - the html documentation in the package still describes the tags "<install>" and "<configure>", but the dtds don't contain them anymore. - accidentally, I put a bash comment in an xml file instead of the xml comment signs, i.e.: <chroot-scripts config:type="list" > <script> # nfs fetching disabled for now  The line with the # causes autoyast to segfault when parsing the script tags. Of course this line is wrong here, but it should complain, not segfault I guess :-) 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 1

PXE-based autoinstall and problems with rescue boot variant
by John Line 20 Sep '05

20 Sep '05

Having got PXE-based network installation of SLES9 working some time ago, I was surprised recently to find that the corresponding rescue-mode boot configuration failed (just when I needed it, having made a change that caused booting to fail). I think that's a consequence of having added SP1 & SP2 to the installation source; I'm fairly sure rescue mode "just worked" when I first set it up, using only the original SLES9 CDs. I've found some workarounds, but having set up the installation source using YaST, it seems strange that it doesn't "just work", and there may be better solutions than the ones I've found. The problem arises with an (HTTP) installation source set up using YaST (from ISO images of the original SLES9 release plus SP1 and SP2). All of the symlinks in the top-level SLES9 install source directory point at the original SLES9 release's directories, except for the driverupdate symlink which points into an SP2 directory. The TFTP directory used to get installation or whatever started is configured with copies of the linux and initrd files from the boot/loader directory on SP2's CD1. While installation works just fine (and breaks if I try using the linux and initrd files from the original SLES9 CD1), rescue mode boots OK but is totally useless because its /lib/modules directory contains only modules for the installation kernel version from the original SLES9 release, rather than for the SP2 kernel that it's actually running. In consequence, it can't access e.g. ext3 or ReiserFS partitions on the system's hard drives, and is useless for rescuing the system. Some experimentation revealed that * Replacing the "rescue" symlink in the boot directory of the original SLES9 CD1 directory with a symlink pointing at the SP2 equivalent worked * Alternatively, specifying a URL in the rescue= kernel option (instead of rescue=1) works, though not as I originally expected. The catch there is that it does NOT use the URL I supply, it adds /boot/rescue to the end of the URL. I'd set up a "rescue" symlink in the top level SLES9 installation source directory and tried a URL pointing at that, but it got a 404 (not found) error. The only way to get it to work was to use a URL pointing at the SLES9 SP2 CD1 directory so it would find /boot/rescue there. I don't really like that solution, as it seems far more likely to get overlooked after e.g. adding SP3 than if it were a symlink in the installation source directory. I had previously tried simply replacing the "boot" symlink with one pointing at the SP2 CD1 "boot" directory, and rescue mode then worked but autoinstallation failed, presumably because it needed other files from the original SLES9 "boot" directory. Questions: (1) Why doesn't YaST set up the installation source so that rescue mode will "just work", when service packs are added? Bug or oversight? (2) Is there a better solution than either of the ones that I've found and described above? [My primary source of information for setting up PXE installation etc., was http://www.suse.de/~nashif/autoinstallation/9.1/autoyast.pdf . Unlike the official SLES9 version (which scarcely mentions PXE), it includes most of the important details for setting up PXE booting/installation. However, a lot of the "fine details" are left unstated, and with regard to the rescue= setting, it just says "the URL variant specifies the location of the rescue image explicitly". That's misleading, since the URL you specify is NOT what is actually used - /boot/rescue gets appended.] John Line -- John Line - web & news development, University of Cambridge Computing Service

1 0

Re: [suse-autoinstall] partitioning with pre-install script
by Tom Scholl 20 Sep '05

20 Sep '05

(this was my reply to the first msg in this thread, but smtp errors delayed it, bah. Should still be relevant ;) Getting SuSE 9.3 (or similar) to read paritioning info from an /etc/fstab you've just created on a freshly-formatted disk... You need some extra stuff other than an /etc/fstab file for suse to recognise it as a root partition. By reading some of the autoyast scripts, and experimenting, I found I needed: /bin/bash, in the correct executable format for that architecture. ie, 64 bit for amd64 machines, 32 bit for anything else. Directories for mount points. You'll at least need to make /proc, and probably more for any extra partitions you have listed in fstab. I had a second extra partition mounted as /scratch, which I needed to make a directory for. I'm guessing you'll need to make them for things like /var as well... Good luck, Tom Scholl

1 0

partitioning with pre-install script
by boris.kornder＠gmx.net 20 Sep '05

20 Sep '05

hi there, because we have a lot of different and often changing disc-layouts i tried to use the partitioning_advanced + fstab option but autoyast does not regocnize any slice as root partition. szenario is the following: i'm using a pre-install script that reads disk-partition information (e.q. sda1 / ext3 3000M \n sda2 /var ext3 1000M etc.) as input for fdisk to part the disc, set boottable flag and format the needed filesystems. then write a fstab file on the root filesystem. this works fine. but when YaST tries to check the partitiontables it ends up with a message like 'no root partition found' and stops. any idea ? Greets Boris -- GMX DSL = Maximale Leistung zum minimalen Preis! 2000 MB nur 2,99, Flatrate ab 4,99 Euro/Monat: http://www.gmx.net/de/go/dsl

2 3

Re: [suse-autoinstall] Autoyast network configuration: "ifcfg-eth--" invalid configuration file.
by Frederico Muñoz 18 Sep '05

18 Sep '05

Hello, Thank you for your answer. On 9/18/05, Hans-Joachim Ehlers <HansJoachim.Ehlers(a)eumetsat.int> wrote: > Hi Frederico, > i have got once on a DELL Client a similar problem. > in the file /etc/sysconfig/hardware-bus-pci-........ there was not an entry for the network card. > E.a the value for the attribut ' MODULE='MyNetworkCardModule' was missing. After adding the value ( the correct network card module name ) and restarting/rebooting the machine everythink worked fine. I forgot to see that file, as I said SuSE manual network configuration method is not something that I know very well yet. I can, however, happily announce that I have it sorted, more or less: incredible as it may sound it started working (both interfaces fully configured) after I changed from "Full Installation" to "Minimal". I also changed the LVM config to the new format, but the thing that appears to make a difference is the package selection. Totally bizarre, I can't imagine what can be the interference between this two configuration options. Now that I have everything working I can leave some suggestiong on things that can probably take a bit more fine tunning: o The before mentioned eth-- problem, of course. o When creating the LV's with the new syntax I now get a "lvremove" error on some lv's, complaining about "no such device or address". Everything works if I just ignore the warning. o GRUB refuses to install in some servers (the DL380, actually). The error message I get trough the ILO console is only the GRUB version banner, and no manual ammount of fiddling with the parameters will make it work; installing LILO is the only way to ger past that point. o Not SuSE or autoyast related, but I might as well take the opportunity in the chance that this can be useful to someone: don't ever assume that the PXE boot will go trough the eth0 interface; I had to deconfigure all the VLAN's to make PXE boot to work since it seams to use the interfaces in an absolutely random order. This is something awful not only during th actuall PXE boot, but also during the "pxeboot" DHCP request: not adding a "netdevice=eth2" on some servers would make them request an IP address in a 192.168.0.0 network and it would just freeze. All in all, apart from the above glitches that did take their toll in time, autoyast was very helpful; I was used to FAI and Solaris Jumpstart, and autoyast is a useful adittion to my automatic installation knowledge. Best regards, Frederico Muñoz

1 0

Re: [suse-autoinstall] Autoyast network configuration: "ifcfg-eth--" invalid configuration file.
by Hans-Joachim Ehlers 18 Sep '05

18 Sep '05

Hi Frederico, i have got once on a DELL Client a similar problem. in the file /etc/sysconfig/hardware-bus-pci-........ there was not an entry for the network card. E.a the value for the attribut ' MODULE='MyNetworkCardModule' was missing. After adding the value ( the correct network card module name ) and restarting/rebooting the machine everythink worked fine. hth Hajo' >>> Frederico Muñoz <fsmunoz(a)gmail.com> 09/17/05 5:38 pm >>> Hello, I've set up a SuSE install server to automatically install around 15 servers.Everything is working except one crucial thing, the network configuration. I've been struggling with this for hours, and already did so many installs in a test machine that I am close to just giving up on it and just do the network configuration manually on every server. The error is always the same: everything works great (congrats to SuSE and autoyast developers in particular) until it tries to bring up the network that was configured: it becomes obvious from the messages that eth0 and eth1 aren't configured and that instead a single "eth--" interface was created. It stays some seconds "Waiting for mandatory interface: eth--". Upon reboot and a closer inspection a "/etc/sysconfig/network/ifcfg-eth--" exists with the network details of the first interface configured in the autoyast profile. No other interface configuration file is present. I'm still not entirely proficient on the way network configurations are done in SuSE, but something is clearly amiss. I'm attaching my autoyast profile; it's one of the many variations I have been using: with 1 or 2 interfaces, with and without the "modules" part, with and without the routing, etc. Every time I get the same error. I would welcome any help with this; I found a previous mention of something that looks the same problem at http://lists.suse.com/archive/suse-autoinstall/2005-Jan/0104.html , but, alas, no solution. Best regards, Frederico Muñoz PS: For future reference, are all the fields (network, broadcast...) in the profile required or can I assume that with the IP address and the netmaks the other values will be extrapolated?

1 0

Autoyast network configuration: "ifcfg-eth--" invalid configuration file.
by Frederico Muñoz 17 Sep '05

17 Sep '05

Hello, I've set up a SuSE install server to automatically install around 15 servers.Everything is working except one crucial thing, the network configuration. I've been struggling with this for hours, and already did so many installs in a test machine that I am close to just giving up on it and just do the network configuration manually on every server. The error is always the same: everything works great (congrats to SuSE and autoyast developers in particular) until it tries to bring up the network that was configured: it becomes obvious from the messages that eth0 and eth1 aren't configured and that instead a single "eth--" interface was created. It stays some seconds "Waiting for mandatory interface: eth--". Upon reboot and a closer inspection a "/etc/sysconfig/network/ifcfg-eth--" exists with the network details of the first interface configured in the autoyast profile. No other interface configuration file is present. I'm still not entirely proficient on the way network configurations are done in SuSE, but something is clearly amiss. I'm attaching my autoyast profile; it's one of the many variations I have been using: with 1 or 2 interfaces, with and without the "modules" part, with and without the routing, etc. Every time I get the same error. I would welcome any help with this; I found a previous mention of something that looks the same problem at http://lists.suse.com/archive/suse-autoinstall/2005-Jan/0104.html , but, alas, no solution. Best regards, Frederico Muñoz PS: For future reference, are all the fields (network, broadcast...) in the profile required or can I assume that with the IP address and the netmaks the other values will be extrapolated?

1 0

RE: [suse-autoinstall] Selecting packages for autoinstall
by Veenbaas, Pete 16 Sep '05

16 Sep '05

Greetings, I figured out that I must have removed the CORE CD1 dir as well as the SLES 9 CD1 dir. Now I've got the multiple choice back. I would still like to know how the Autoinstall session knows what type of config file to create (e.g. nld9 vs. sles9) when selecting something like 'default system' Thx in advance!!! -----Original Message----- From: Veenbaas, Pete [mailto:pveenbaa@ugs.com] Sent: Friday, September 16, 2005 10:43 AM To: suse-autoinstall(a)suse.com Subject: [suse-autoinstall] Selecting packages for autoinstall Greetings, I currently have an SLE9 32 bit server running as my install server for various flavors of SuSE. I have the following 'enabled' install sources: syslinux3:/suse9 # /usr/bin/installation_sources -s Installation Sources: SUSE SLES 9 Service-Pack Version 1 (http://syslinux3//suse9/sles9_amd64/SUSE-SLES-9-Service-Pack-Version-1/ CD1) SUSE SLES Version 9 (http://syslinux3//suse9/sles9_amd64) Novell Linux Desktop Version 9 (http://syslinux3//suse9/nld9) Novell Linux Desktop Version 9 (http://syslinux3//suse9/nld9_32 <http://syslinux3/suse9/nld9_32> ) When I run 'yast2':'Misc':'Autoinstallation' and then select 'Software':'Package Selection' from the configuration tree I see that no base/add-on/individual selected packages are selected. I then click the 'configure' button, and in the 'software' box where I would expect to see: Minimum Minimum graphical system No KDE) Full intallation Default system I see only GNOME KDE What happened to my previous choices? How does autoinstall know which type of config file to create if I want to install a default system for SLES9 SP1 vs. NLD9? Does it know? Any help would be appreciated!

1 0

Selecting packages for autoinstall
by Veenbaas, Pete 16 Sep '05

16 Sep '05

Greetings, I currently have an SLE9 32 bit server running as my install server for various flavors of SuSE. I have the following 'enabled' install sources: syslinux3:/suse9 # /usr/bin/installation_sources -s Installation Sources: SUSE SLES 9 Service-Pack Version 1 (http://syslinux3//suse9/sles9_amd64/SUSE-SLES-9-Service-Pack-Version-1/ CD1) SUSE SLES Version 9 (http://syslinux3//suse9/sles9_amd64) Novell Linux Desktop Version 9 (http://syslinux3//suse9/nld9) Novell Linux Desktop Version 9 (http://syslinux3//suse9/nld9_32 <http://syslinux3/suse9/nld9_32> ) When I run 'yast2':'Misc':'Autoinstallation' and then select 'Software':'Package Selection' from the configuration tree I see that no base/add-on/individual selected packages are selected. I then click the 'configure' button, and in the 'software' box where I would expect to see: Minimum Minimum graphical system No KDE) Full intallation Default system I see only GNOME KDE What happened to my previous choices? How does autoinstall know which type of config file to create if I want to install a default system for SLES9 SP1 vs. NLD9? Does it know? Any help would be appreciated!

1 0

The service that wouldn't die [powersaved on 9.3 pro]
by Marlier, Ian 16 Sep '05

16 Sep '05

Building an autoinstall for SuSE 9.3 Professional. I really don't want powersaved to run. I have tried both of the following to try to keep it from becoming active: <service> <service_name>powersaved</service_name> </service> and <service> <service_name>powersaved</service_name> <service_status>disable</service_status> </service> Yes, I can add a post-script like chkconfig powersaved off /etc/init.d/powersaved stop and that'll do the trick. But I feel like it shouldn't need to go into a script.. Format 2 -- with service_status = disable -- has always worked in the past. But it doesn't work with this one particular service. Anyone have any idea why? What am I missing? Thanks, Ian

1 0

selecting package architecture
by Jeromy Smith 15 Sep '05

15 Sep '05

Is there any way to specify 32-bit vs 64-bit when selecting software packages? I am installing a 64-bit system but I would like to install the 32-bit gsl libraries (gsl-1.5-3.i586.rpm). It seems like a pretty simple thing but I can't figure it out. Jeromy __________________________________ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com

2 1

rules.xml and <memsize> parameter
by Reynold L Demarco 15 Sep '05

15 Sep '05

I am unable to get my memsize rules working properly. It states in the documentation that the memsize is recognized in megabytes, but that doesn't seem to be the case. Every value I use for memsize seems to match any system, until I get to 10000000000000000000 or greater. In other words, with the below rules.xml, the first rule matches all systems(which is what I want so that every system uses the default.xml file). However, all systems match the next two rules as well, so that all 3 xml files are merged. But I only want the first rule file and one of the 2 next rules files merged based on memory being either less than 3000MB or greater than 3000MB. So I end up getting a merged rules file of all 3. I copied the syntax directly from the example in the autoyast guide. Is there a bug in the memsize option? I am using the below rules.xml file..... <?xml version="1.0"?> <!DOCTYPE autoinstall SYSTEM "/usr/share/autoinstall/dtd/rules.dtd"> <autoinstall xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <rules config:type="list"> <rule> <memsize> <match>128</match> <match_type>greater</match_type> </memsize> <result> <profile>default.xml</profile> <continue config:type="boolean">true</continue> </result> </rule> <rule> <disksize> <match>/dev/cciss/c0d0 1000</match> <match_type>greater</match_type> </disksize> <result> <profile>cciss.xml</profile> <continue config:type="boolean">true</continue> </result> </rule> <rule> <disksize> <match>/dev/cciss/c0d0 1000</match> <match_type>greater</match_type> </disksize> <memsize> <match>3000</match> <match_type>greater</match_type> </memsize> <result> <profile>cciss4g.xml</profile> <continue config:type="boolean">true</continue> </result> </rule> <rule> <disksize> <match>/dev/cciss/c0d0 1000</match> <match_type>greater</match_type> </disksize> <memsize> <match>5000</match> <match_type>greater</match_type> </memsize> <result> <profile>cciss6g.xml</profile> <continue config:type="boolean">true</continue> </result> </rule> </rules> </autoinstall>

3 16

Re: [suse-autoinstall] rules.xml and <memsize> parameter
by Reynold L Demarco 15 Sep '05

15 Sep '05

I do want default.xml to match all the time, that is done on purpose. It contains all of my default settings. The others match on specific things like memory amounts and disk size. The rules.xml is actually just a test case I ran. My real rules file is much larger. Thx, Renny Michael Marion wrote: >On 13 Sep, Reynold L Demarco wrote: > >I've read the other replies, but I think your logic is backwards anyway. > >The rules and xml files are done in order, IME, and so you'll get default.xml >every time even if the other rules are matched or not, and the result is an >accumulation of all the files that match. I use this to match a site value >for site specific software/scripts and disk sizes for partitioning. > >I think you need to change your rules so that the default one is the last one >so only things that never match above will even try it, and set the other >rules to continue=false so that they don't keep trying to match each other >value.. and check from higher values to lower, or you'll match the first one >that's valid. > >Then there's the problem of the nested rules the other reply mentioned but >that's another issue. > >So I'd redo the rules as: > ><?xml version="1.0"?> ><!DOCTYPE autoinstall SYSTEM "/usr/share/autoinstall/dtd/rules.dtd"> ><autoinstall xmlns="http://www.suse.com/1.0/yast2ns" >xmlns:config="http://www.suse.com/1.0/configns"> ><rules config:type="list"> > <rule> > <disksize> > <match>/dev/cciss/c0d0 1000</match> > <match_type>greater</match_type> > </disksize> > <memsize> > <match>5000</match> > <match_type>greater</match_type> > </memsize> > <result> > <profile>cciss6g.xml</profile> > <continue config:type="boolean">false</continue> > </result> > </rule> > <rule> > <disksize> > <match>/dev/cciss/c0d0 1000</match> > <match_type>greater</match_type> > </disksize> > <memsize> > <match>3000</match> > <match_type>greater</match_type> > </memsize> > <result> > <profile>cciss4g.xml</profile> > <continue config:type="boolean">false</continue> > </result> > </rule> > <rule> > <disksize> > <match>/dev/cciss/c0d0 1000</match> > <match_type>greater</match_type> > </disksize> > <result> > <profile>cciss.xml</profile> > <continue config:type="boolean">true</continue> > </result> > </rule> > <rule> > <memsize> > <match>128</match> > <match_type>greater</match_type> > </memsize> > <result> > <profile>default.xml</profile> > <continue config:type="boolean">true</continue> > </result> > </rule> ></rules> ></autoinstall> > > >Not sure if the cciss.xml one should continue or not. > >I'd suggest doing like I did and breaking up the memory and disk sizes to >completely different rules and xml files anyway. > > >

1 0

How do we implement rules.xml in SELS 8.0
by Jayesh Patel 15 Sep '05

15 Sep '05

HI, I need help on setting the rules.xml setup for our SLES 8 machines. Any alternative for rules.xml will be useful, even if it requires scripting. The thought here is depending on the disk being ide (hda), scsi (sda) or other (c0t0d0) I need to supply the proper autoinstall.xml file. Has any one done a similar setup? Thanks, Jayesh Patel.

2 1

Package selection with autoyast on SuSE 9.3 prof.
by Ian Grant 14 Sep '05

14 Sep '05

I am having a frustrating time here. If I use the autoinstallation option of yast2 to generate an autoyast specification I get a software section like this: <software> <addons config:type="list"> <addon>Basis-Devel</addon> <addon>Basis-Sound</addon> <addon>Kde-Desktop</addon> <addon>Latex</addon> <addon>Min</addon> <addon>Office</addon> <addon>SuSE-Documentation</addon> <addon>X11</addon> </addons> <base>Minimal</base> <packages config:type="list"> <package>autofs</package> <package>lprng</package> </packages> </software> But if I put that in an otherwise working install specification (i.e. with all the other stuff like keyboards, network, X1 config etc.) then, when autoyast halts for me to confirm installation, the 'Software' section of the 'Installation Settings' screen of YaST sows two bullets: The first is '?' and the second is 'Size of packages to install 158.4 MB' and when I go in to the 'Software Selection' screen, I get no base specification shown (i.e. all radio buttons are un-checked) and the list of selected packages under 'Detailed Selection' is blank. If I go ahead with the install it fails trying to install lvm2 because the sed package is missing. Consistent with no base packages being loaded. Does anyone have an example of a working autoyast software specification .xml file for 9.3? I'm using the version of autoyast on the distributed CDs which is 2.11.13-3

3 7

RE: [suse-autoinstall] Package selection with autoyast on SuSE 9.3 prof.
by Marlier, Ian 13 Sep '05

13 Sep '05

I'm just not using the "<addon>" section -- just adding the additional packages that I want as additional <package> lines. That seems to work fine. > -----Original Message----- > From: ig206(a)hermes.cam.ac.uk [mailto:ig206@hermes.cam.ac.uk] On Behalf Of > Ian Grant > Sent: Tuesday, September 13, 2005 10:54 AM > To: suse-autoinstall(a)suse.com > Subject: [suse-autoinstall] Package selection with autoyast on SuSE 9.3 > prof. > > I am having a frustrating time here. If I use the autoinstallation > option of yast2 to generate an autoyast specification I get a > software section like this: > > <software> > <addons config:type="list"> > <addon>Basis-Devel</addon> > <addon>Basis-Sound</addon> > <addon>Kde-Desktop</addon> > <addon>Latex</addon> > <addon>Min</addon> > <addon>Office</addon> > <addon>SuSE-Documentation</addon> > <addon>X11</addon> > </addons> > <base>Minimal</base> > <packages config:type="list"> > <package>autofs</package> > <package>lprng</package> > </packages> > </software> > > But if I put that in an otherwise working install specification (i.e. > with all the other stuff like keyboards, network, X1 config etc.) > then, when autoyast halts for me to confirm installation, the > 'Software' section of the 'Installation Settings' screen of YaST sows > two bullets: The first is '?' and the second is 'Size of packages to > install 158.4 MB' and when I go in to the 'Software Selection' > screen, I get no base specification shown (i.e. all radio buttons are > un-checked) and the list of selected packages under 'Detailed > Selection' is blank. If I go ahead with the install it fails trying > to install lvm2 because the sed package is missing. Consistent with > no base packages being loaded. > > Does anyone have an example of a working autoyast software > specification .xml file for 9.3? I'm using the version of autoyast on > the distributed CDs which is 2.11.13-3 > > > > > -- > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > For additional commands, e-mail: suse-autoinstall-help(a)suse.com >

1 0

Workshop "automatic installation" at Linuxhotel
by Ingo Wichmann 13 Sep '05

13 Sep '05

Hi! There will be a workshop on the topic of "automatic installation" at the linuxhotel ( http://www.linuxhotel.de ), essen, germany from Friday, Oktober 7 to Sunday Oktober 9. Its a pet-project of mine, i just want to spend a weekend hacking and comparing the different approaches to this topic ( fai, m23, autoyast, kickstart ). So if you want to join, feel free to do so. Prizing: 10 Euros for the drinks and stuff. 50 Euros per night in a shared room for 2 persons. ( Developers who can prove relevant commitments to a relevant projekt on this topic are welcome to stay at the hotel for free ) Just send an email if you want to join. Here is my announcement in German: Hallo Leute! Ich habe grade unheimlich Spaß daran gefunden, automatisch Linux-Rechner zu installieren. Wem das genauso geht, oder wer das interessant findet und ausreichend Vorkenntnisse hat, den lade ich herzlich zu einem Bastel-Wochende vom 07.10. bis zum 09.10. hier ins Linuxhotel ein. Programm: ========= Freitag, 07.10.: 20:00 Uhr bis ca. 21:30 Uhr Vortrag / Demo von mir: Einführung in das Thema, Praxisbeispiel Installation Netzwerkboot mit syslinux/pxelinux, dhcpd und passendem Kernel. Samstag, 08.10: 10:00 bis 17:00 Uhr: Bastel-Session in Eigenregie im wesentlichen mit mitgebracher Hardware. Ein paar Test-Notebooks, Switches und Kabel kann ich auch beisteuern, aber besser ist, jeder bringt selbst genug Rechner bzw. VMware-Lizenzen mit. Ich will in der Zeit verschiedene Varianten austesten ( FAI für Debian, m23 für Debian, autoYast für SuSE, Kickstart für Fedora/RedHat, grub statt pxelinux ) und mich mit Euch austauschen was wofür gut ist. Achtung: das alles ist nicht für Linux-Einsteiger gedacht. Ich freue mich über Leute, die so wie ich selbst mindestens schon erste Erfahrungen mit dem Thema gesammelt haben; gerne auch mehr als das ... es geht mir um einen Austausch auf Gegenseitigkeit. Sonntag, 10:00 bis 16:00 Uhr das selbe wie am Samstag :-) Kosten: ======= 10 Euro für Getränke (Kaffee, Kola, ...) [1] Wer im Linuxhotel übernachten will zahlt noch mal 50 Euro pro Nacht im halben Doppelzimmer. Leute, die zu einem relevanten Projekt ( fai, m23, ... ) in relevantem Umfang beigetragen haben zahlen nix. [2] Plätze: ======= Ich denke mit mehr als 20 Leuten macht das alles keinen Sinn. Anmeldung: ========== Bitte eine Mail an iw at linuxhotel.de deren Betreff das Wort "workshop" enthält und die folgende Fragen beantwortet: Wie heißt Du? Von wann bis wann möchtest Du teilnehmen? Möchtest Du im Linuxhotel übernachten? Aktuellere Infos: ================= https://wiki.villa-vogelsang.de/doku.php?id=autoinstall:start Viele Grüße, Ingo Wichmann [1] wer das nicht zahlen kann: daran soll es auch nicht scheitern ... bitte mich ansprechen. [2] Bitte mit mir absprechen, wer sich dieser Gruppe zugehörig fühlt :-)

1 0

partitioning problem
by Sven Geipel 12 Sep '05

12 Sep '05

Hello, I try to auto-install 9.2 and leave my first (windows) partition untouched. How can I do that? When autoyast is partitioning my disk, it deletes the extended partition no. 2 (ok). Then it tries to create first linux partition at start cylinder 0 but there is my windows partition. It should start after end of first partition: device size F type mountpoint start end /dev/hda 37.2GB 0 4864 /dev/hda1 9.9GB NTFS 0 1303 /dev/hda2 39.2MB F ext3 /boot 0 4 /dev/hda3 1GB F swap swap 5 135 ... What I'm doing wrong? Here's the partition part of my autoinst.xml: <partitioning config:type="list"> <drive> <device>/dev/hda</device> <initialize config:type="boolean">false</initialize> <partitions config:type="list"> <partition> <create config:type="boolean">false</create> <format config:type="boolean">false</format> <partition_nr config:type="integer">1</partition_nr> <size>10g</size> </partition> <partition> <crypt>twofish256</crypt> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <loop_fs config:type="boolean">false</loop_fs> <mount>/boot</mount> <partition_id config:type="integer">131</partition_id> <partition_type>primary</partition_type> <size>32m</size> </partition> <partition> <crypt>twofish256</crypt> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <loop_fs config:type="boolean">false</loop_fs> <mount>swap</mount> <partition_id config:type="integer">130</partition_id> <partition_type>primary</partition_type> <size>1g</size> </partition> <partition> <crypt>twofish256</crypt> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <loop_fs config:type="boolean">false</loop_fs> <mount>/</mount> <partition_id config:type="integer">131</partition_id> <size>12g</size> </partition> <partition> <crypt>twofish256</crypt> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <loop_fs config:type="boolean">false</loop_fs> <mount>/save</mount> <partition_id config:type="integer">131</partition_id> <size>max</size> </partition> </partitions> <use>2</use> </drive> </partitioning> -- best regards Sven Geipel

2 4

Syntax to get autoyast to leave existing partitions untouched?
by Paul Beltrani 12 Sep '05

12 Sep '05

I have reviewed the documentation included with autoyast2 v2.11.13 but have been unable to generate a control file which will reuse partitions on an IDE drive. I used autoyast to do an automated install of 9.3Pro on a workstation and had it automatically create, format and mount the following partitions: Part, type, size, FS, mount point 1, primary, 5GB, reiser, / 2, primary, 512MB, swap 3, primary, 512MB, reiser, /var 4, primary, <remainder of drive>, reiser, /export This worked exactly as expected. I then tried to rebuild the system as 10.0RC1 using the exact same control file with the following changes: 1) Do NOT create any of the partitions 2) Only format partitions 1,2 and 3, NOT partition 4 i.e. Do not change the partition layout and do not touch the filesystem on partition 4. When attempting the rebuild yast states it will first delete all 4 partitions then recreate them. In effect it is completely rebuilding the drive and wiping all info. This is not what I would like to happen. I expect this may have something to do with the <use>all</use> property of the second file. However if I specify any value other than "all" or leave it out completely yast fails with the msg "Error while configuring partitions. Try again". Does anyone have a suggestion as to where the error may be? The partitioning portions of control files follow: Initial build: <partitioning config:type="list"> <drive> <device>/dev/hda</device> <partitions config:type="list"> <partition> <partition_type>primary</partition_type> <partition_nr config:type="integer">1</partition_nr> <partition_id config:type="integer">131</partition_id> <create config:type="boolean">true</create> <format config:type="boolean">true</format> <filesystem config:type="symbol">reiser</filesystem> <mount>/</mount> <size>5GB</size> </partition> <partition> <partition_type>primary</partition_type> <partition_nr config:type="integer">2</partition_nr> <partition_id config:type="integer">130</partition_id> <create config:type="boolean">true</create> <format config:type="boolean">true</format> <filesystem config:type="symbol">swap</filesystem> <mount>swap</mount> <size>512MB</size> </partition> <partition> <partition_type>primary</partition_type> <partition_nr config:type="integer">3</partition_nr> <partition_id config:type="integer">131</partition_id> <create config:type="boolean">true</create> <format config:type="boolean">true</format> <filesystem config:type="symbol">reiser</filesystem> <mount>/var</mount> <size>512MB</size> </partition> <partition> <partition_type>primary</partition_type> <partition_nr config:type="integer">4</partition_nr> <partition_id config:type="integer">131</partition_id> <create config:type="boolean">true</create> <format config:type="boolean">true</format> <filesystem config:type="symbol">reiser</filesystem> <mount>/export</mount> <size>auto</size> </partition> </partitions> <use>all</use> </drive> </partitioning> Re-build: <partitioning config:type="list"> <drive> <device>/dev/hda</device> <partitions config:type="list"> <partition> <partition_type>primary</partition_type> <partition_nr config:type="integer">1</partition_nr> <partition_id config:type="integer">131</partition_id> <create config:type="boolean">false</create> <format config:type="boolean">true</format> <filesystem config:type="symbol">reiser</filesystem> <mount>/</mount> </partition> <partition> <partition_type>primary</partition_type> <partition_nr config:type="integer">2</partition_nr> <partition_id config:type="integer">130</partition_id> <create config:type="boolean">false</create> <format config:type="boolean">true</format> <filesystem config:type="symbol">swap</filesystem> <mount>swap</mount> </partition> <partition> <partition_type>primary</partition_type> <partition_nr config:type="integer">3</partition_nr> <partition_id config:type="integer">131</partition_id> <create config:type="boolean">false</create> <format config:type="boolean">true</format> <filesystem config:type="symbol">reiser</filesystem> <mount>/var</mount> </partition> <partition> <partition_type>primary</partition_type> <partition_nr config:type="integer">4</partition_nr> <partition_id config:type="integer">131</partition_id> <create config:type="boolean">false</create> <format config:type="boolean">false</format> <filesystem config:type="symbol">reiser</filesystem> <mount>/export</mount> </partition> </partitions> <use>all</use> </drive> </partitioning>

3 2

which script-language for pre-inst.script?
by Boris Wokurka 09 Sep '05

09 Sep '05

Hello list, I want to partition the disc via sfdisk in a pre-install-script. The docu tells me only not to use shell or perl, but not what I can use. My shell-script did not work (BTW, it's the first time I used sfdisk...), it looks like this: <configure> <scripts> <pre-scripts config:type="list"> <script> <interpreter>shell</interpreter> <filename>pre-inst.sh</filename> <source><![CDATA[ #!/bin/sh sfdisk /dev/sda << EOF ,8069,L ,,E ,48381,L ,48172,L ,4102,S ,2023,L ,2008,L ; EOF ]]> </source> </script> </pre-scripts> </scripts> Any hints? Thank You, Boris

3 3

How to install 9.3 from network using DVD and samba?
by HG 08 Sep '05

08 Sep '05

Hi! Hopefully somebody here has done this... could not find anything from google. My main computer crashed (well it was an old one...). So now I'm setting up a "new" computer (another old PIII :-). I have the DVD for SuSE 9.3 Pro, but the computer does not have a DVD player. Another Windows laptop does have. So, what I though I'd do is to start the installation over the network using windows sharing of the DVD. >From SuSE netowkr installation cd: "Start Installation of System" + "network" + "SMB / CIFS (Windows share)" and then use DHCP. Now the installation asks for the samba information. This is what I tried to enter: IP: 192.168.1.101 (obviously home network address" share name: suse (this is also correct) directory on the server: I have no idea what to put here. The default is /. Then comes the login information for the server. Now, if I leave the directory empty, the installation will not start. If I enter the default /, the installation starts and I see network sage from the Windows laptop using task manager. So the share works. Well, this far it is. After that I'll get to the YaST. Language settings and then Installation settings. Everything else looks there just like I expected... except the Software selection, which states: "No source found at "smb://USER:PASSWORD@192.168.1.101/suse//;workgroup=home" and "ERROR: No proposal" What now? What am I doing wrong? -- HG.

2 1

partitioning problem
by Boris Wokurka 08 Sep '05

08 Sep '05

Hello list, I have problems with partitioning and autoinstall on SuSE 9.3. What I want to do on my 120gb SATA disk: sda1 => primary, 8gb, ext3, / sda2 => extended, 8gb sda3 => primary, ext3, 48gb, /home sda4 => primary, ext3, rest (=max), /daten2 sda5 => logical, 4gb, swap sda6 => logical, 2gb, /var, ext3 sda7 => logical, 2gb, /tmp, ext3 What I get is: sda1 => primary, 8gb, ext3, / sda2 => primary, 8gb, unformatted sda3 => primary, ext3, 48gb, /home sda4 => extended, 8gb sda5 => logical, ext3, 40gb, /daten2 sda6 => logical, 4gb, swap sda7 => logical, 2gb, /var, ext3 sda8 => logical, 2gb, /tmp, ext3 My autoinst.xml-partitons section lokks like this: <partitioning config:type="list"> <drive> <initialize config:type="boolean">true</initialize> <device>/dev/sda</device> <partitions config:type="list"> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <mount>/</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">1</partition_nr> <partition_type>primary</partition_type> <size>8gb</size> </partition> <partition> <partition_id config:type="integer">15</partition_id> <partition_nr config:type="integer">2</partition_nr> <partition_type>extended</partition_type> <size>8gb</size> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <mount>/home</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">3</partition_nr> <partition_type>primary</partition_type> <size>48gb</size> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <mount>/daten2</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">4</partition_nr> <partition_type>primary</partition_type> <size>max</size> </partition> <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">5</partition_nr> <size>4gb</size> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <mount>/var</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">6</partition_nr> <size>2gb</size> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <mount>/tmp</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">7</partition_nr> <size>2gb</size> </partition> </partitions> <use>all</use> </drive> </partitioning> I have tried various possibilities (leaving the <partition_type>extended</partition_type>, different sorting etc.) without success. In other words: is it impossible to have an extended partition sda2 with autoyast? Is there a way how to do it? Maybe with pre-install-scripts? Any help would be highly appreciated! Thank you, Boris

4 5

Re: [suse-autoinstall] partitioning problem
by Hans-Joachim Ehlers 08 Sep '05

08 Sep '05

The solution from autoyast make sense for me because afaik the partition order is first the primary and then the extended partition. Also is might be not a good idea to define a patition in the middle of your configyration file with the MAX option. So think about your requriement and do not try to get a extended partition in the middle of primary partitions. BTW: In our environment we do not use primary partitions. hth Hajo >>> Boris Wokurka <boris.wokurka(a)zamg.ac.at> 09/08/05 10:32 am >>> Hello list, I have problems with partitioning and autoinstall on SuSE 9.3. What I want to do on my 120gb SATA disk: sda1 => primary, 8gb, ext3, / sda2 => extended, 8gb sda3 => primary, ext3, 48gb, /home sda4 => primary, ext3, rest (=max), /daten2 sda5 => logical, 4gb, swap sda6 => logical, 2gb, /var, ext3 sda7 => logical, 2gb, /tmp, ext3 What I get is: sda1 => primary, 8gb, ext3, / sda2 => primary, 8gb, unformatted sda3 => primary, ext3, 48gb, /home sda4 => extended, 8gb sda5 => logical, ext3, 40gb, /daten2 sda6 => logical, 4gb, swap sda7 => logical, 2gb, /var, ext3 sda8 => logical, 2gb, /tmp, ext3 My autoinst.xml-partitons section lokks like this: <partitioning config:type="list"> <drive> <initialize config:type="boolean">true</initialize> <device>/dev/sda</device> <partitions config:type="list"> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <mount>/</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">1</partition_nr> <partition_type>primary</partition_type> <size>8gb</size> </partition> <partition> <partition_id config:type="integer">15</partition_id> <partition_nr config:type="integer">2</partition_nr> <partition_type>extended</partition_type> <size>8gb</size> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <mount>/home</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">3</partition_nr> <partition_type>primary</partition_type> <size>48gb</size> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <mount>/daten2</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">4</partition_nr> <partition_type>primary</partition_type> <size>max</size> </partition> <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">5</partition_nr> <size>4gb</size> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <mount>/var</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">6</partition_nr> <size>2gb</size> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <mount>/tmp</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">7</partition_nr> <size>2gb</size> </partition> </partitions> <use>all</use> </drive> </partitioning> I have tried various possibilities (leaving the <partition_type>extended</partition_type>, different sorting etc.) without success. In other words: is it impossible to have an extended partition sda2 with autoyast? Is there a way how to do it? Maybe with pre-install-scripts? Any help would be highly appreciated! Thank you, Boris -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

YOU wants to install patches that are already installed by multiple source autoinstall
by Teun 07 Sep '05

07 Sep '05

Hello, After a lot of trouble setting up an installation server, serving both a SuSE 9. 3 Pro source and an update source, i finally was able to autoinstall a machine which installed all packages and updates in one go. (So it installs the updated packages straight away and not first the older version.) However, when i then run YaST Online Update on the machine it still wants to install all the updates that are already on the system. It even reports that the installed version of a particular package is the exact same package as the one it wants to install. I already found that if i move a file from /var/lib/YaST2/you/mnt/i386/update/9. 3/patches to /var/lib/YaST2/you/installed the problem is solved for that particular package. But the first directory also contains files for packages that are not installed at all, so just copying all of them would not work. I really hope there is a clean solution to fix this? Any help would be highly appreciated. Regards, Teun

1 1

AutoYAST not using provided updates
by Charles Duffy 07 Sep '05

07 Sep '05

I'm trying to do an autoinstall from a number of sources: - SLES9 base - SLES9 SP1 - Custom updates folder Each of these sources has a different version of rug (which is behaving poorly for me): SLES9 base has 2.0.2 SLES9 SP1 has 2.4.4 updates has 2.4.8 When I install my system, however, I find that it has rug 2.4.4 installed, rather than rug 2.4.8! The "updates" folder was created using create_update_source.sh. Any ideas as to what I may be doing wrong? yast/order: /updates /updates /SUSE-SLES-Version-9-SP1/CD1 /SUSE-SLES-Version-9-SP1/CD1 /SUSE-SLES-Version-9-SP1/CD2 /SUSE-SLES-Version-9-SP1/CD2 /SUSE-SLES-Version-9/CD1 /SUSE-SLES-Version-9/CD1 /SUSE-CORE-Version-9/CD1 /SUSE-CORE-Version-9/CD1 / yast/instorder: /updates /SUSE-SLES-Version-9-SP1/CD1 /SUSE-SLES-Version-9-SP1/CD2 /SUSE-SLES-Version-9/CD1 /SUSE-CORE-Version-9/CD1 /

2 1

Media files
by Robison, Jonathon (M.) 07 Sep '05

07 Sep '05

Can anyone tell me which files on a CD describe which CD an rpm is on? i.e. how does YaST know which CD to ask for during installation? --Jon Robison

2 1

RE: [suse-autoinstall] Media files
by Ness, Todd 07 Sep '05

07 Sep '05

suse/setup/descr/packages* Look at the line the starts =Loc -----Original Message----- From: Robison, Jonathon (M.) [mailto:jrobiso2@ford.com] Sent: Wednesday, September 07, 2005 7:48 AM To: suse-autoinstall(a)suse.com Subject: [suse-autoinstall] Media files Can anyone tell me which files on a CD describe which CD an rpm is on? i.e. how does YaST know which CD to ask for during installation? --Jon Robison

1 0

how do I ...
by Joe Landman 05 Sep '05

05 Sep '05

insert additional RPMs into the base installation? I would like to add some non-SuSE provided bits to the installation, and the documentation I have found thus far does not seem to cover this case. Basically, I have an RPM (call it abc-1.2.3-1.noarch.rpm) that I would like to install during the installation process. The naive method of placing it into the appropriate directory prior to the installation and adding a <package>abc</package> to the autoyast file used for installation does not work. The documentation is vague on how to go about doing this. Any thoughts? Has anyone done this? Is it simple to do? Did I miss the "this is how you solve that problem" document? Thanks. Joe -- Joseph Landman, Ph.D Founder and CEO Scalable Informatics LLC, email: landman(a)scalableinformatics.com web : http://www.scalableinformatics.com phone: +1 734 786 8423 fax : +1 734 786 8452 cell : +1 734 612 4615

3 2

Has anyone had sucess with loadlin and 9.3 installation?
by GrueMaster 01 Sep '05

01 Sep '05

I need to add Suse 9.3 installation to our OS test suite (aotuoyast issues resolved - thanks), but the non-Linux people want to add it to the existing dos boot menu (we already have RedHat AS4 & Fedora Core 4). From what I can tell through my testing, loadlin doesn't allocate enough memory for the large initrd file used for installation (same issue reported back in 8.x) Has anyone had better luck with this? Tobin --------------------------------- Start your day with Yahoo! - make it your home page

1 0

question about info file options for linuxrc
by Reynold L Demarco 01 Sep '05

01 Sep '05

Is there any way to set a wait for http in the info file similar to the BOOTPWait option such that after network card activation, it will wait a period before trying to retrive its http files in the case of an http autoyast build? I am running into a similar problem that others have on this list with the auto-install functionality not quite working until I manually select the network option and tell it to accept my information I've already entered. Then the process moves on almost automatically, except I do still have to repspond to a couple of driver loads at the beginning and one more time at the end of the install process. Thanks in advance for any help.

1 0

Re: [suse-autoinstall] right steps to initiate autoinstall by booting from an USB stick
by Hans-Joachim Ehlers 01 Sep '05

01 Sep '05

Create ./classes/autoinstall.xlm Create ./classes/MyPC.xml ( For each PC ) Create ./rules/rules.xml to parse the autoinstall.xml and the host part. Creata a file named 'info' and put it into ./boot/loader/initrd of your USB Stick ( Have to rebuild initrd ) After booting from the USB Stick select 'installation' and add on the command line : hostname=MyPC hostip=MyIP Where hostname + .xml must match the xml file name on your server BTW: For your environment you should change at least everything that has the name 'CHANGEME' in the attached files. Documentation: http://yast.suse.com/autoinstall/index.html http://lists.suse.com/archive/suse-autoinstall/2005-Aug/0010.html Have fun Hajo >>> Stefan Pfeiffer <stefan.pfeiffer(a)ilt.fraunhofer.de> 09/01/05 1:10 pm >>> Hello! For usage in a rather small PC cluster i would like to trigger an autoinstall of client nodes by letting them boot from an USB stick. The clients have no floppy drive and no CDROM drive. The SuSE 9.3 image resides on a central server that is accessible by NFS. I would like to avoid PXE booting and messing around with the dhcpd. I think of some kind of very basic system on the stick together with the necessary control files to start the installation on its own without getting something from the server via TFTP. Only the installation source should be NFS. I am not quite sure what are the right steps to accomplish that. Looking on the web, i only find references to boot disks that initiate installation using TFTP, or to rather obscure instructions on how to put a complete runnable system on a stick (that does not initiate an autoinstall to hard drive). Stick size would be "what is needed", up to 512MB or 1G if absolutely necessary. I assume it is rather easy to do for someone who has some insight into that matter. I do not need a step-by-step description, just a little push in the right direction or towards the right resource. Thank you in advance. Regards, Stefan Pfeiffer -- # Dipl.-Phys. Stefan Pfeiffer # Abteilung Modellierung und Simulation # Fraunhofer Institut f. Lasertechnik # Steinbachstr. 15, D-52074 Aachen, Germany. # Tel: + 49 (241) 8906 153 , Fax: +49 (241) 8906 121 # EMail: pfeiffer(a)ilt.fhg.de, WWW: http://www.ilt.fhg.de/nld/ -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com ============================ Hans-Joachim Ehlers UNIX Systems Engineer EUMETSAT Am Kavalleriesand, 31 64295, Darmstadt, Germany Tel : +49 6151 807-7307 eMail : hansjoachim.ehlers(a)eumetsat.int iNet : www.eumetsat.de

1 0

right steps to initiate autoinstall by booting from an USB stick
by Stefan Pfeiffer 01 Sep '05

01 Sep '05

Hello! For usage in a rather small PC cluster i would like to trigger an autoinstall of client nodes by letting them boot from an USB stick. The clients have no floppy drive and no CDROM drive. The SuSE 9.3 image resides on a central server that is accessible by NFS. I would like to avoid PXE booting and messing around with the dhcpd. I think of some kind of very basic system on the stick together with the necessary control files to start the installation on its own without getting something from the server via TFTP. Only the installation source should be NFS. I am not quite sure what are the right steps to accomplish that. Looking on the web, i only find references to boot disks that initiate installation using TFTP, or to rather obscure instructions on how to put a complete runnable system on a stick (that does not initiate an autoinstall to hard drive). Stick size would be "what is needed", up to 512MB or 1G if absolutely necessary. I assume it is rather easy to do for someone who has some insight into that matter. I do not need a step-by-step description, just a little push in the right direction or towards the right resource. Thank you in advance. Regards, Stefan Pfeiffer -- # Dipl.-Phys. Stefan Pfeiffer # Abteilung Modellierung und Simulation # Fraunhofer Institut f. Lasertechnik # Steinbachstr. 15, D-52074 Aachen, Germany. # Tel: + 49 (241) 8906 153 , Fax: +49 (241) 8906 121 # EMail: pfeiffer(a)ilt.fhg.de, WWW: http://www.ilt.fhg.de/nld/

2 1