July 2006 - openSUSE Autoinstall - openSUSE Mailing Lists

What is the Minimal Install Achievable by Autoinst.xml on SLES10
by Seal Me 31 Jul '06

31 Jul '06

I used to be able to pull off less than 450 mb package size with SLES10 GMC(maybe it was Beta 10). The final release is kind of a shock when I realize the autoinst file I was using bloated to a whopping 880mb package size. Yast parses my control file, does a little magic, and comes up with a bloated package list. So here comes the question, is there any way I can force Yast to install exactly what I list in the autoinst.xml? PS. I have done a manual install with exactly what I need, however autoyast failed to generate a working autoinst.xml. The software section was omitted. Thanks a lot. Any help is appreciated. Seal

2 1

$PATH during installation
by Thomas Mieslinger 31 Jul '06

31 Jul '06

Hello, I've added some HP rpms to a custom installdisk. The postinstallscripts HP worte require $PATH to be set because they don't use absolut Paths ("touch /file" instead of "/bin/touch /file") to the commands. Any chance to have $PATH during installation? regards Thomas

2 1

SELS 10 GM vs. SLES 10 RC2 autoyast changes?
by Pete Nishimoto 31 Jul '06

31 Jul '06

Hi, I had downloaded SLES 10 RC2 and got it to work with our PXE server using some site specific autoyast.xml files. I then downloaded SLES 10 GM, set it up on the PXE server in exactly the same way I setup SLES 10 RC2 (that is, the directory structure, etc.) and then just copied the autoyast.xml files from the SLES 10 RC2 tree to the SLES 10 GM tree. However, when I attempt an install, YAST now claims that it cannot find the package specified. Have things changed between RC2 and GM? Has the directory layout changed? Pete

2 2

routes question
by Joe Landman 31 Jul '06

31 Jul '06

Hi folks: At the end of an autoinstall with 10.x, yast overwrites my routes with a default route that happens to be incorrect. Is there a way to fix this in the autoyast file? 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 or +1 866 888 3112 cell : +1 734 612 4615

2 1

Is it wise to wait for SLED 10 oder opensuse 10.2 before relying on autoyast ?
by Johannes Pöhlmann 31 Jul '06

31 Jul '06

I try to remaster the opensuse 10.1 installation medium to a 4.5 GIG DVD and to add auf autoinst.xml to it. So I removed suse/x86_64 and a couple of i586 packages. I tried to use a explicit package list in autoinst.xml, because I wanted it to be usable in opensuse 10.1 and SLES10/ Opensuse10.2. So i commented out addons and base clauses (is that legal ?): <software>  <packages config:type="list"> <package>alsa-firmware</package> .... <package>yast2-repair</package> </packages> </software> Remastering the DVD went fine using using docu under: http://de.opensuse.org/Erstellen_einer_DVD_aus_den_CDs#Von_Hand_eine_DVD_au… o create_package_descr o mkisofs Then I run into Problems: 1. I learned the hard way that you MUST add exactly this to the kernel command line: instmode=cd autoyast=file:///autoinst.xml This should be documented better. 2. Now start of Problem: -The dvd booted fine, fired up yast you "started autoinstall". - While looking for "catalogs" or such, a huge list of missing packages is displayed. Clicking away that warning gets a "no catalogs on medium ... " error. Should I use makeSUSEdvd <http://sourceforge.net/project/showfiles.php?group_id=146800&package_id=163…> instead ? Should I wait for SLED 10 oder opensuse 10.2 ? Johannes -- Dipl.-Inf. Johannes Poehlmann Innovationszentrum Telekommunikationstechnik GmbH Am Weichselgarten 5 D-91058 Erlangen Tel. +49-(0)-9131-4800-159 Fax: +49-(0)-9131-4800-199 mailto:Johannes.Poehlmann@izt.fraunhofer.de http://www.izt-gmbh.de

2 1

sax2 in a post-install script
by Laura Jordana 31 Jul '06

31 Jul '06

Is there something wrong? I put this directly under an existing chroot script. After the </chroot-scripts> tag of course. It's all in between the <configure> tags so I can't figure out why it doesn't seem to be running. I tried commenting out the <X11> section as well, and that didn't seem to do anything either. Any suggestions? <post-scripts config:type="list"> <script> <filename>post_script.sh</filename> <interpreter>shell</interpreter> <source><![CDATA[#!/bin/sh #run sax2 to configure x11 sax2 --auto]]></source> </script> </post-scripts>

3 5

Updating versions in SLES9 SP3
by Michael T. Halligan 28 Jul '06

28 Jul '06

I've been struggling with a pretty bad bug in the sata_nv driver included in the 2.6.5-* kernel. This bug appears to have gone away with the 2.6.16 kernel from SLES10. I'm trying to put together an updated SLES repository right now, and I'm not quite sure how to add the newer version of the kernel .. Basically, because with kernels after 2.6.9 /dev/hd* sata devices get addressed as /dev/sd, I need to make sure that the 2.6.5 kernel never actually gets installed. How would I go about replacing the kernel in the distribution with this newer kernel? I've already made new bootdisks with the new kernel & kernel modules that work fine, however I need to make sure the newer kernel rpm, as well as the updated perl-Bootloader rpm get installed.

1 0

upgrade install kernel
by Lee Hartley 28 Jul '06

28 Jul '06

anyone know how to upgrade the kernel (initrd and root image too?) for the install system? any help or thoughts would be great thanks Lee

1 0

Re: [suse-autoinstall] SLES 10 GM/SLED 10 GM: "could not set patterns or selections : default"
by Pete Nishimoto 28 Jul '06

28 Jul '06

Lonni, I'll give that a shot, but I thought that you just had to get the pattern from the ./suse/setup/descr directory, or was that just a dumb/lucky guess on my part? Pete At 01:18 PM 7/28/2006, Lonni J Friedman wrote: >Hi Pete, >Yes, unfortunately the patterns changed, which I also found out hte >hard way. SuSE hasn't done a very good job of documenting them (as >far as i could tell). > >The following worked for me with SLED10: > <software> > <patterns config:type="list"> > <pattern>Basis-Devel</pattern> > <pattern>Gnome</pattern> > <pattern>default</pattern> > <pattern>Kde</pattern> > <pattern>base</pattern> > <pattern>X11</pattern> > </patterns> > >If that doesn't help you, you should prolly post your autoyast.xml > >On 7/28/06, Pete Nishimoto <peten(a)east.sun.com> wrote: >>Hi, >> >> I had downloaded SLES 10 RC2 and got it to work with our PXE server >> using some site specific autoyast.xml files. >> >> I then downloaded SLES 10 GM, set it up on the PXE server >> in exactly the >> same way I setup SLES 10 RC2 (that is, the directory >> structure, etc.) and >> then just copied the autoyast.xml files from the SLES 10 RC2 tree to >>the SLES 10 GM >> tree. >> >> However, when I attempt an install, YAST now claims >> >> "could not set patterns or selections : default" >> >> I get the same results with SLED 10, using the same autoinst.xml. >> >> The software section is as follows: >> >> <software> >> <patterns config:type="list"> >> <pattern>default</pattern> >> </patterns> >> </software> >> >> Have things changed between RC2 and GM? Has the directory >> layout changed? >> Are there other files/links from the root directory required? >> >> I ask this 2nd part because when I 'snoop', the NFSLOOKUP activity >>for RC2 (working) >> and the GM (not-working) installs access the same files, >> in the same order up >> to a point -- RC2 will look at the file 'content' and 'content.asc' >>and then start opening >> up pattern files, but GM does not. >> >> Note that I've setup this installation directory using a DVD made >>from 0.34-1 of makeSUSEdvd, >> as well as using the official GM CD iso images, and I always get the >>same results. >> >> Another datapoint is that I did an install using the generated DVD >>and then took the >> autoinst.xml file that was generated and put that in the PXE >>directory and tried the network >> install using this generated autoinst.xml file -- same results. > > >-- >~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >L. Friedman netllama(a)gmail.com >LlamaLand http://netllama.linux-sxs.org

2 1

SLES 10 GM/SLED 10 GM: "could not set patterns or selections : default"
by Pete Nishimoto 28 Jul '06

28 Jul '06

Hi, I had downloaded SLES 10 RC2 and got it to work with our PXE server using some site specific autoyast.xml files. I then downloaded SLES 10 GM, set it up on the PXE server in exactly the same way I setup SLES 10 RC2 (that is, the directory structure, etc.) and then just copied the autoyast.xml files from the SLES 10 RC2 tree to the SLES 10 GM tree. However, when I attempt an install, YAST now claims "could not set patterns or selections : default" I get the same results with SLED 10, using the same autoinst.xml. The software section is as follows: <software> <patterns config:type="list"> <pattern>default</pattern> </patterns> </software> Have things changed between RC2 and GM? Has the directory layout changed? Are there other files/links from the root directory required? I ask this 2nd part because when I 'snoop', the NFSLOOKUP activity for RC2 (working) and the GM (not-working) installs access the same files, in the same order up to a point -- RC2 will look at the file 'content' and 'content.asc' and then start opening up pattern files, but GM does not. Note that I've setup this installation directory using a DVD made from 0.34-1 of makeSUSEdvd, as well as using the official GM CD iso images, and I always get the same results. Another datapoint is that I did an install using the generated DVD and then took the autoinst.xml file that was generated and put that in the PXE directory and tried the network install using this generated autoinst.xml file -- same results. Please help. Pete

2 1