August 2006 - openSUSE Autoinstall - openSUSE Mailing Lists

No catalog found
by Stephen Mah 07 Aug '06

07 Aug '06

Hi, I'm simply trying to create a network installation source with Suse 10.1 I found instructions on the web. created CD{1,2,3,4,5} directories and copied each ISO into them. linked the CD1/boot, content, control.xml, media.1, suse, etc... wrote to yast/instorder, order, and directory.yast. I get No catalog found at "nfs://servername/path/" I even tried the makeSUSEDVD utility to create the directories. Any ideas?

2 1

WG: [suse-autoinstall] Swap as an LVM volume not working ?
by tobias.mucke＠man-mit.com 07 Aug '06

07 Aug '06

Hi Bruno, what version of SuSE do you use? Have a look at "[suse-autoinstall] LVM configuration with SLES10". We do not configure swap in LVM but use also an LVM layout with lots of PVs und some LVs. Do you have similar problems, too? I will try to configure swap in LVM and tell you my experience later this day. Tobias ----- Weitergeleitet von Tobias Mucke/MIT/DE/MAN-Group am 07.08.2006 07:41 ----- "Bruno Marcondes" <bmarcondes@gmail .com> An suse-autoinstall(a)suse.com 04.08.2006 21:32 Kopie Thema [suse-autoinstall] Swap as an LVM volume not working ? Hello guys, i'm trying to make a fs layout with swap as a LVM logical volume, my autoyast configuration is something like this <partitioning> ... <drive> <device>/dev/vol</device> <is_lvm_vg config:type="boolean">true</is_lvm_vg> <partitions config:type="list"> <partition> <lv_name>swap</lv_name> <mount>swap</mount> <size>1gb</size> </partition> <partition> ....  ... </drive> .... </partitioning> During the installation process YaST tries to mount /dev/vol/swap as an reiserfs partition and got error code "-3003" :( Am I doing something wrong , missing some configuration ? Removing this swap partition under the /dev/vol device makes it all work... Thanks in advance ! []'s -- "If you really want something in this life, you have to work for it. Now, quiet! They're about to announce the lottery numbers..." - Homer Simpson This message and any attachments are confidential and may be privileged or otherwise protected from disclosure. If you are not the intended recipient, please telephone or email the sender and delete this message and any attachment from your system. If you are not the intended recipient, you must not copy this message or attachment or disclose the contents to any other person.

1 0

autoinst.xml fails with xen in SLES-10-GMC
by Post, Gary 04 Aug '06

04 Aug '06

I have been evaluating Xen in SLES-10. I have been installing from a DVD and using the clone in /root/autoinst.xml for replicating. We have a pxe build server and I loop mount the GMC.iso on the build server and copy the contents into the pxe install tree and then use the autoinst.xml from the previous installation to create essentially identical installations on different types of platforms. I find that when I tried it with either the 32-bit or 64-bit SLES-10-GMC, the autoyast install is missing the xen paragraph in /boot/grub/menu.lst [ /boot/grub/menu.lst ] # Modified by YaST2. Last modification on Fri Aug 4 19:42:57 UTC 2006 color white/blue black/light-gray default timeout 8 gfxmenu (hd0,1)/boot/message ###Don't change this comment - YaST2 identifier: Original name: linux### title SUSE Linux Enterprise Server 10 root (hd0,1) kernel /boot/vmlinuz root=/dev/hda2 vga=0x31a resume=/dev/hda1 splash=silent ip=192.101.22.217:192.101.1.8:192.101.1.254:255.255.0.0 showopts initrd /boot/initrd ###Don't change this comment - YaST2 identifier: Original name: failsafe### title Failsafe -- SUSE Linux Enterprise Server 10 root (hd0,1) kernel /boot/vmlinuz root=/dev/hda2 vga=normal showopts ide=nodma apm=off acpi=off noresume edd=off 3 initrd /boot/initrd here is the revelent section in autoinst.xml ( appears identically in /var/adm/autoinstall/cache/installedSystem.xml on the installed box also ) <loader_device>/dev/hda2</loader_device> <loader_type>grub</loader_type> <location>boot</location> <repl_mbr config:type="boolean">false</repl_mbr> <sections config:type="list"> <section> <append>resume=/dev/hda1 splash=silent showopts</append> <initial>1</initial> <initrd>/boot/initrd</initrd> <kernel>/boot/vmlinuz</kernel> <lines_cache_id>1</lines_cache_id> <name>SUSE Linux Enterprise Server 10</name> <original_name>linux</original_name> <root>/dev/hda2</root> <type>image</type> <vga>0x31a</vga> </section> <section> <append>resume=/dev/hda1 splash=silent showopts</append> <initrd>/boot/initrd-xen</initrd> <kernel>/boot/vmlinuz-xen</kernel> <lines_cache_id>2</lines_cache_id> <name>XEN</name> <original_name>xen</original_name> <root>/dev/hda2</root> <type>image</type> <vga>0x31a</vga> <xen>/boot/xen.gz</xen> <xen_append></xen_append> </section> <section> <append>showopts ide=nodma apm=off acpi=off noresume edd=off 3</append> <initrd>/boot/initrd</initrd> <kernel>/boot/vmlinuz</kernel> <lines_cache_id>3</lines_cache_id> <name>Failsafe -- SUSE Linux Enterprise Server 10</name> <original_name>failsafe</original_name> <root>/dev/hda2</root> <type>image</type> <vga>normal</vga> </section> </sections> I have stepped back and installed SLES-10-GMC with all defaults EXCEPT adding the xen package - the install from DVD gives the correct menu.lst file. The automated install does not. Beta8, RC2, RC2.5, RC3 all work. I strongly feel that something has changed. Divine guidance greatly appreciated gary

1 0

Re: [suse-autoinstall] SELS 10 GM vs. SLES 10 RC2 autoyast changes?
by Pete Nishimoto 04 Aug '06

04 Aug '06

Uwe, Putting all the stuff from the DVD at the 'root' level cleared it up for 32 and 64 bit (using the DVD generated from makeSUSEdvd). I had just assumed that the old SELS9 directory structure was going to continue to be in use (especially after it worked for SLES 10 RC2). Thanks. Pete At 09:09 AM 8/3/2006, Uwe Gansert wrote: >On Thursday 03 August 2006 15:06, you wrote: > > > ls -ls > > total 76 > > 4 -rwxr--r-- 1 root root 4075 Aug 1 14:46 > > autoinst-sun.xml 0 lrwxrwxrwx 1 root root 11 Jul 27 > > 12:27 boot -> sles10/boot > > 0 lrwxrwxrwx 1 root root 14 Jul 27 12:27 content > > -> sles10/content > > 0 lrwxrwxrwx 1 root root 18 Jul 27 12:28 > > content.asc -> sles10/content.asc > > 0 lrwxrwxrwx 1 root root 18 Jul 27 12:28 > > content.key -> sles10/content.key > > 0 lrwxrwxrwx 1 root root 18 Jul 27 12:28 > > control.xml -> sles10/control.xml > > 0 lrwxrwxrwx 1 root root 14 Jul 27 12:29 media.1 > > -> sles10/media.1 > > 4 drwxr-xr-x 7 root root 4096 Jul 27 12:28 sles10 > > 0 lrwxrwxrwx 1 root root 11 Jul 27 12:29 suse -> > > sles10/suse > >why the level above? >Why don't you use the sles10 directory directly instead of linking some >files? > >-- >ciao, Uwe Gansert > >Uwe Gansert, Server Technologies Team >SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nuernberg, Germany >Business: http://www.suse.de/~ug >now playing The Retrosic - Sphere

1 0

customized packages/create_package_descr destroys install source
by Frank Steiner 04 Aug '06

04 Aug '06

Hi, I'm not sure if I maybe misunderstood the HOWTO for autoyast on 10.1. About adding custom packages to an installation source, is it *only* possible with "add_on_products" on SuSE 10.1? Is it no longer possible to copy packages to the standard SuSE sources and then recreate the package database with create_package_desrc? We used to copy our own kernel packages into the suse/i586/ dir of the NFS source dir, then call create_package_descr and choose e.g. our own kernel-source package with <packages config:type="list"> <package>kernelbio-source</package> </packages> When I do this on 10.1, autoyast complains it can't find the package in the installation source. But this also for every package that I enter in the <packages> list. Looking at the y2log I see that autoyast complains, that the suse/setup/descr/packages file has a different checksum than expected. For that reason, AY rejects to create a source for the NFS source directory. That sounds like I'm not allowed to change the packages file in the original source, and then I could add packages only via add_on_products. Is that correct, or is this checksum rejection a bug in AY? 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

RE: [suse-autoinstall] CD Creator
by aschanz＠lcsc.dfs.de 03 Aug '06

03 Aug '06

The CD-Creator Yast Plugin is obviously not working. We have opened a Service Request for this issue. In the meantime we will have to manually create our AutoYast DVD/CD. Here are some details about the Problems: 1. The <Pattern> Part of the XML is not interpreted correctly. This results in Missing RPM in the Source-tree. For example a normal installation should have about 650 RPM. CD-Creator only copies 55-61 Packages. 2. Checking 'Only copy needed Files' has no impact on anything. 3. ISO creation results in a 38KB *.ISO image where the complete Source-Tree is 278 MB. 4. The XML Template (DTD) has not been adopted for the new <pattern> Object resulting in error messages when auto-checking the XML in YAST (autoYast Plugin). Alexander

1 0

RE: [suse-autoinstall] CD Creator
by Paul DiSciascio 03 Aug '06

03 Aug '06

Is anyone else creating CDs for autoinstalls? If so, how are you creating the appropriate RPM list with dependencies included? The software section of my autoinst.xml is below, and I am having an awful time getting the rpm list right...and the installer of course will not continue unless it can resolve all the dependencies for the patterns correctly. <software> <patterns config:type="list"> <pattern>ccb</pattern> <pattern>base</pattern> <pattern>apparmor</pattern> </patterns> </software> ~Paul -----Original Message----- From: Paul DiSciascio (PJM - UnixSysSupt) [mailto:discip@pjm.com] Sent: Tuesday, August 01, 2006 7:21 AM To: suse-autoinstall(a)suse.com Subject: RE: [suse-autoinstall] CD Creator I should have mentioned this is SLES 10. -----Original Message----- From: Paul DiSciascio (PJM - UnixSysSupt) [mailto:discip@pjm.com] Sent: Monday, July 31, 2006 3:45 PM To: suse-autoinstall(a)suse.com Subject: [suse-autoinstall] CD Creator Has anyone had any luck using the CD Creator interface to roll a CD from an autoinst.xml file? I tried it, but what it created is complete junk: lots of files missing. So then I attempted to loop through the pattern files I want to use and just copy all the appropriate rpms onto my CD, but I wind up missing lots of dependencies that way, and sorting through them is taking a long time. Any help is appreciated. Thanks, Paul P.S. is there a command-line interface to the CD Creator? -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

WG: Re: [suse-autoinstall] What is the Minimal Install Achievable by Autoinst.xml on SLES10
by tobias.mucke＠man-mit.com 03 Aug '06

03 Aug '06

Hi list, here is our solution to this problem (KISS). Thanks to Uwe for his clear answer to this question.  <scripts> <init-scripts config:type="list"> <script> <filename>autoyast_install_custom_rpms.sh</filename> <interpreter>shell</interpreter> <source> <![CDATA[ #!/bin/sh ERASE_RPMS="lilo dhcpcd hfsutils jfsutils ntfsprogs xfsprogs" INSTALL_RPMS="" echo "Erase custom RPM packages ..." if [ -n "${ERASE_RPMS}" ]; then for RPM in ${ERASE_RPMS}; do echo "Erase of ${RPM}.rpm ... " rpm -e ${RPM} echo "... ${RPM}.rpm erased."; done; fi echo "Install custom RPM packages ..." if [ -n "${INSTALL_RPMS}" ]; then for RPM in ${INSTALL_RPMS}; do echo "Install ${RPM}.rpm ... " yast2 -i ${RPM} echo "... ${RPM}.rpm installed."; done; fi exit ${?} ]]> </source> </script> </init-scripts> </scripts> Bye Tobias This message and any attachments are confidential and may be privileged or otherwise protected from disclosure. If you are not the intended recipient, please telephone or email the sender and delete this message and any attachment from your system. If you are not the intended recipient, you must not copy this message or attachment or disclose the contents to any other person.

1 0

[suse-autoinstall] What is the Minimal Install Achievable by Autoinst.xml on SLES10
by tobias.mucke＠man-mit.com 02 Aug '06

02 Aug '06

Hi, I want to do the same: just the packages I know I need! (and besides that, the packages needed to solve rpm dependencies, which I do not want to define). What is working in SLES9 no way in SLES10. Just a little example: I don't need lilo as a bootloader, we are using grub. I have no pattern in my autoinst.xml! Just a list of packages. Lilo is selected anyway. I add lilo to the remove-package list: lilo is selected anyway! Any other chance? Bye Tobias ----- Weitergeleitet von Tobias Mucke/MIT/DE/MAN-Group am 01.08.2006 07:50 ----- Uwe Gansert <ug(a)suse.de> An 31.07.2006 11:41 suse-autoinstall(a)suse.com Kopie Thema Re: [suse-autoinstall] What is the Minimal Install Achievable by Autoinst.xml on SLES10 On Wednesday 26 July 2006 00:50, Seal Me wrote: > So here comes the question, is there any way I can force Yast to > install exactly what I list in the autoinst.xml? even with an empty software section, a minimum set of packages is installed. The product (SLES10 in your case) decides how this minimum set of packages looks like. -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nuernberg, Germany Business: http://www.suse.de/~ug now playing Covenant - Feedback -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com This message and any attachments are confidential and may be privileged or otherwise protected from disclosure. If you are not the intended recipient, please telephone or email the sender and delete this message and any attachment from your system. If you are not the intended recipient, you must not copy this message or attachment or disclose the contents to any other person.

2 1

perl in init-scripts
by Simon Crute 02 Aug '06

02 Aug '06

Hi, I'm just moving my post-script to an init-script to I can call rug. However, it looks like it calls this script as a bash script, not a perl script, even though <interpreter>perl</interpreter> is in the script tags. Another bugzilla ? -- Simon Crute IS&T Bracknell Novell UK Ltd

3 3