July 2006 - openSUSE Autoinstall - openSUSE Mailing Lists

RE: [suse-autoinstall] SLES 10 RC2 remove-packages section?
by Matt Gillard 05 Mar '08

05 Mar '08

I dont have kinternet installed. This is what doesnt seem to work: <software> <patterns config:type="list"> <pattern>default</pattern> <pattern>Basis-Devel</pattern> <pattern>x11</pattern> </patterns> <packages config:type="list"> <packages>perl-libwww-perl</packages> <packages>net-snmp</packages> <packages>kernel-source</packages> </packages> <remove-packages config:type="list"> <packages>pptp</packages> <packages>smpppd</packages> <packages>ppp</packages> <packages>wvdial</packages> <packages>mutt</packages> </remove-packages> </software> In y2log it mentions that those packages should be removed, but it goes ahead and installs them anyway. I can do it manually on the command line: # rpm -e pptp smpppd ppp wvdial mutt and that works fine so I know I have no dependency problems. matt > -----Original Message----- > From: Uwe Gansert [mailto:ug@suse.de] > Sent: Friday, 30 June 2006 12:50 AM > To: suse-autoinstall(a)suse.com > Subject: Re: [suse-autoinstall] SLES 10 RC2 remove-packages section? > > > On Thursday 29 June 2006 16:45, Manfred Hollstein wrote: > > > If that fails, you have kinternet installed; add that to > the list and it > > should work. > > good point. > <remove-packages> can not break dependencies and so it's very > likely that > there is still a package that needs those packages. > I did a very small installation with no X - so it worked for me. > > -- > ciao, Uwe Gansert > > Uwe Gansert, Server Technologies Team > SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nuernberg, Germany > Fax: +49-(0)911-74053-476, Web: http://www.suse.de/~ug > now playing Covenant - Wasteland > > -- > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > For additional commands, e-mail: suse-autoinstall-help(a)suse.com > > This email and any attachments may contain privileged and confidential information and are intended for the named addressee only. If you have received this e-mail in error, please notify the sender and delete this e-mail immediately. Any confidentiality, privilege or copyright is not waived or lost because this e-mail has been sent to you in error. It is your responsibility to check this e-mail and any attachments for viruses. No warranty is made that this material is free from computer virus or any other defect or error. Any loss/damage incurred by using this material is not the sender's responsibility. The sender's entire liability will be limited to resupplying the material.

4 6

Scripting dirinstall?
by Teun 25 Feb '07

25 Feb '07

Does anyone know if it is possible to use the 'dirinstall' from the command line? For instance i would like to be able to do something like: # yast dirinstall -d /someroot -s mypackages.sel If i do yast -h it says: "Usage: /sbin/yast [OPTIONS] [MODULE] [module specific parameters]" But is there a way to find out what 'module specific parameters' are available for a specific module? Thanks, Teun

3 2

Problems with bootloader configuration in autoyast SLES10 RC3
by Matt Gillard 13 Sep '06

13 Sep '06

I have logged SR#10273247971 for this but I thought I would get peoples thoughts here as well. Problem is with the <default> global parameter in the <bootloader> section of autoyast. This works fine: <bootloader> <loader_type>lilo</loader_type> <location>mbr</location> </bootloader> Default kernel is SLES_10 as expected. This doesnt work, during boot loader installation an error is given that there is no default value given in lilo.conf. This occurs if I put an entry in the <default> tag or not. <bootloader> <global> <default>SLES_10</default> <gfxmenu></gfxmenu> <prompt>1</prompt> <timeout config:type="integer">5</timeout> </global> <loader_type>lilo</loader_type> <location>mbr</location> </bootloader> ie: This also gives the same error for the default tag. It should default to SLES_10 - I should not have to specify it. <bootloader> <global> <default></default> <gfxmenu></gfxmenu> <prompt>1</prompt> <timeout config:type="integer">5</timeout> </global> <loader_type>lilo</loader_type> <location>mbr</location> </bootloader> And this also the same error: <bootloader> <global> <gfxmenu></gfxmenu> <prompt>1</prompt> <timeout config:type="integer">5</timeout> </global> <loader_type>lilo</loader_type> <location>mbr</location> </bootloader> The reason I am doing this is because I do *not* want a graphical menu so I want to specify nothing for <gfxmenu> which seems to work ok. The text of the error during the bootloader config/installation phase is: "Value expected for 'default' at or above line 11 in file /etc/lilo.conf." And sure enough in /mnt/etc/lilo.conf at that point of the installation default has no value. thanks -- Matt Gillard UNIX Systems Engineer Coles Myer Ltd | Lvl 4 236 Bourke St | +61 3 963 51926 This email and any attachments may contain privileged and confidential information and are intended for the named addressee only. If you have received this e-mail in error, please notify the sender and delete this e-mail immediately. Any confidentiality, privilege or copyright is not waived or lost because this e-mail has been sent to you in error. It is your responsibility to check this e-mail and any attachments for viruses. No warranty is made that this material is free from computer virus or any other defect or error. Any loss/damage incurred by using this material is not the sender's responsibility. The sender's entire liability will be limited to resupplying the material.

4 13

SLES 10: more than one primary partition?
by Holger Reif 21 Aug '06

21 Aug '06

Hi, I'm trying to use the partition scheme that used for partitioning SLES8 and SLES9 systems. The minimal autoinst.xml snippet looks like <partitioning config:type="list"> <drive> <initialize config:type="boolean">true</initialize> <partitions config:type="list"> <partition> <filesystem config:type="symbol">VAR_boot_filesystem</filesystem> <format config:type="boolean">true</format> <mount>/boot</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">1</partition_nr> <size>96M</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>8192M</size> </partition> <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">2</partition_nr> <size>max</size> </partition> </partitions> <use>all</use> </drive> What I expect is: 1st primary 96M /boot 2nd primary some 130G / 1st logical 6G swap What I get is: / # fdisk -l Disk /dev/cciss/c0d0: 146.8 GB, 146807930880 bytes 255 heads, 63 sectors/track, 17848 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/cciss/c0d0p1 1 13 104391 83 Linux /dev/cciss/c0d0p2 14 17848 143259637+ f W95 Ext'd (LBA) /dev/cciss/c0d0p5 14 16803 134865643+ 83 Linux /dev/cciss/c0d0p6 16804 17848 8393931 82 Linux swap / Solaris BTW. If I do not specify partition_id and partition_nr for swap then root get's first logical partion and swap second one. Is there any chance to force / to be a primary partition w/o using part.info? http://www.suse.de/~ug/autoyast_doc/CreateProfile.Partitioning.html#id25297… sugests that my snippet should do what I want... br Holger Reif -- Echte DSL-Flatrate dauerhaft für 0,- Euro*. Nur noch kurze Zeit! "Feel free" mit GMX DSL: http://www.gmx.net/de/go/dsl

2 2

SLES10 - Bootloader configuration
by tobias.mucke＠man-mit.com 02 Aug '06

02 Aug '06

Hi list, familiar with SuSE autoinstallation environments since ALICE I trying hard right now to implement an AutoYaST environment with SLES10. Understanding that there are some changes compared to AutoYaST delivered with SLES9 I guess the following scenario is a nice starting point. 1. Install a standard system manually 2. Clone this system with AutoYaST (last option before installation is finished) 3. Try to understand the XML configuration step by step 4. Implement AutoYaST environment by rules and classes Right now I have the following problem: Starting with a whole file called autoinst.xml I cut out (without any changes) the bootloader section to copy it into another file called bootloader.xml. This one is included through the rules concept which works fine for other configuration items. If I don't include the bootloader.xml not right at the beginning GRUB is not configured! Man, that was quite hard to find out (first I used classes and met the same failure). I would like to track the problem, so that we come from a very undetailed view "GRUB is not configured, because of XML include failure" to the real technical problem. What can I do to support the development? Thanks a lot. Mit freundlichen Grüßen Tobias Mucke ------------------------------------------------------------------------------- MAN IT Services GmbH Abt. MIT-EE Linux-System-Technik Ohmstr. 12 D-85757 Karlsfeld Büro: Dachauer Str. 667 D-80995 München Tel.: +49 (0) 89 1580 5269 mailto:tobias.mucke@man-mit.com http://www.man.de ------------------------------------------------------------------------------- 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 2

CD Creator
by Paul DiSciascio 31 Jul '06

31 Jul '06

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?

1 0

Re: [suse-autoinstall] sax2 in a post-install script
by Laura Jordana 31 Jul '06

31 Jul '06

Thank you Lee and Uwe, using the full path worked like a charm! Lee Mayes wrote: > Hi Laura, > > I use the following snippet in the scripts stanza, it seems to work: > > <chroot-scripts config:type="list"> > <script> > <chrooted config:type="boolean">true</chrooted> > <filename>sax-config</filename> > <interpreter>shell</interpreter> > <location></location> > <source><![CDATA[#!/bin/bash > test -x /usr/sbin/sax2 || exit 0 > /usr/sbin/sax2 --auto > ]]></source> > </script> > </chroot-scripts> > > Best Regards, > > Lee > On Fri, 2006-07-28 at 13:16 -0700, Laura Jordana wrote: >> This is happening even when I put it in the post-script. I don't get it, >> because once the system boots I can run sax2 just fine. I must be >> missing something. >> >> Laura Jordana wrote: >>> I found the culprit - /var/adm/autoinstall/logs tells me sax2 is not >>> being found. Should it be in a post-install script in this case? I'll >>> try that again and then see what the logs say. >>> >>> Uwe Gansert wrote: >>>> On Monday 03 July 2006 19:38, Laura Jordana wrote: >>>> >>>>> 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? >>>> take a look at /var/adm/autoinstall/logs >>>> there you can find some logs about the scripts running >>>> Maybe there is something useful in them. >>>>

1 0

Including NVIDIA Driver into autoinstall
by André Hirschi 31 Jul '06

31 Jul '06

Good evening I'm still on my way to a fully automated SuSE 10.1 Installation. I'm currently stuck with the NVIDIA Driver. Has anybody managed to do that? I tried to do it with several ways, like including a small script into my autoinst.xml, but everything fails. The last thing I tried was going with "init-scripts", but that gave me the error: WARNING: Skipping the runlevel check (the utility 'runlevel' failed to run). Next error is that I appear to be running an X server etc (what is wrong, default runlevel is 3). Any suggestions on how to solve this? Kind regards André

3 4

How to install all packages at once?
by Trond Eivind Glomsrød 31 Jul '06

31 Jul '06

Scenario: Automated installs of SLES10 from a repository with "CD1" etc, installdir given as http://<...>/os_sles10_x8664/CD1 We're trying to run some chroot scripts, which according to the docs are run after all packages are installed. Unfortunately, that's not correct - some packages (from other CDs) are installed after boot (with no further interaction, even). And one of those packages is needed for the post script. In order to work around this.... * Is there a way to make it behave like one would expect: install all packages before booting? Yast knows about the repositories containing CD2-4. * alternatively, is there a way to make autoyast run the chroot script when it actually has installed all the packages instead of when it currently does it? (before the boot) Or failing that, is there an easy way to create a "DVD"-repository from the CDs, to work around this behaviour? The repository docs only mentions how to create it from CDs. -- Trond Eivind Glomsrød Technical Manager Scali - www.scali.com Scaling the Linux Datacenter

2 1

locations of classes
by Michael T. Halligan 31 Jul '06

31 Jul '06

Quick question about classes. If I create a class file say for general partitioning, and then do a network install from a path of ftp://10.10.10.10/SUSE .. with my control fiel in ftp://10.10.10.10/SUSE/blah.xml, would I just call class.xml from blah.xml without a path, and put class.html into the same directory that blah.xml resides in?

2 1

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

9.2 with new modules (bnx2, megaraid_sas)
by Lee Hartley 26 Jul '06

26 Jul '06

I need do autoinstalls of 9.2 onto dell 1950s...I can not find patches to patch the source for these drivers to compile against the 2.6.8 kernel...I have considering trying to upgrade my install system to the one from 10.1 as the drivers are already there...I don't know how many changes will have to be made to my autoyast setup to deal with this...any thoughts or advice? thanks Lee Hartley

1 0

Re: [suse-autoinstall] Including NVIDIA Driver into autoinstall
by Hans-Joachim Ehlers 26 Jul '06

26 Jul '06

At least in german http://de.opensuse.org/Xgl_unter_SUSE_Linux_verwenden and installation note in english http://www.suse.de/~sndirsch/nvidia-installer-HOWTO.html So just check the sites. On SLES 9 and newer hardware ( dual core intel ) i have got for ATI the problem that during installation the kernel type is not the same as after installation. For this reason i created a script which does the configuration after the first reboot of the suse system. extract from the postinstall script included in the xml file. .... echo "INFO: Preparing ATI fglrx drivers for first reboot - " echo " init 3 if uname -a | grep -w smp ; then echo \"Configure and installing ATI Driver.\" rpm -Uvh http:// . . . :/export/suse/sles9-32/x86addon/fglrx_4_3_0-8.24.8-1.i386.rpm rpm -Uvh http:// . . . :/export/suse/sles9-32/x86addon/fglrx_4_3_0_SLES9-8.24.8-1.i386.rpm /usr/X11R6/bin/sax2 -a -r -m 0=fglrx -b /usr/share/doc/packages/fglrx/sax2-profile /usr/X11R6/bin/aticonfig --initial --force /usr/X11R6/bin/aticonfig --iagp=on # /usr/X11R6/bin/aticonfig --agpl=off /usr/X11R6/bin/aticonfig --dtop=horizontal --overlay-on=1 mv /etc/rc.d/rc3.d/S99ATI.config /etc/rc.d/rc3.d/s99ATI.config.done # mv /etc/rc.d/rc3.d/s99Xquery /etc/rc.d/rc3.d/S99Xquery echo \"System will reboot now ! ATI Configuration is done. \" sleep 5 else echo \"System must be rebooted to install the ATI Driver !\" sleep 5 fi shutdown -Fr now " > /etc/rc.d/rc3.d/S99ATI.config chmod 755 /etc/rc.d/rc3.d/S99ATI.config ..... Maybe you have a similar problem with the nvidia driver. hth Hajo >>> André Hirschi <ahirschi(a)visonys.com> 26/07/2006 17:44 >>> Good evening I'm still on my way to a fully automated SuSE 10.1 Installation. I'm currently stuck with the NVIDIA Driver. Has anybody managed to do that? I tried to do it with several ways, like including a small script into my autoinst.xml, but everything fails. The last thing I tried was going with "init-scripts", but that gave me the error: WARNING: Skipping the runlevel check (the utility 'runlevel' failed to run). Next error is that I appear to be running an X server etc (what is wrong, default runlevel is 3). Any suggestions on how to solve this? Kind regards André -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

Automatic,configuration via DHCP?
by André Hirschi 25 Jul '06

25 Jul '06

Good afternoon I'm currently setting up my config file for the autoinstall. Everything works fine, except for one thing. I always get the pop up if I want to use DHCP or not. "Automatic configuration via DHCP?" Yes, I want! But I'd like to have this set automatically. If I choose yes it continues until the installation is done, without any further problems. I tried adding the parameters DHCP=1, UseDHCP=1. Both at the same time and one without the other. Then I get the message that there was no network interface found, so I thought it might help if I add "insmod=tg3" to the parameters. No luck though. What do I have to do to use DHCP without the setup asking? Thanks in advance. André --------------------------------------------------------------------- André Hirschi Phone +41 44 366 88 43 Systems Administrator Fax +41 44 366 88 99 Visonys AG Mobile +41 78 626 22 09 Ottikerstrasse 59 andre.hirschi(a)visonys.com CH-8006 Zürich Switzerland www.visonys.com --------------------------------------------------------------------- safe and swiss.

2 2

autoyast install SLES9 from dos
by Stephen Mah 21 Jul '06

21 Jul '06

Hello, I'm trying to install SLES9 SP3 from dos using linld. Loadlin seems to make the installer kernel panic. I think it's a memory issue. See linld reference: http://lists.suse.com/archive/suse-autoinstall/2005-Oct/0031.html my boot arguments are the following: linld image=linux initrd=initrd "cl=ramdisk_size=65536 install=nfs://<ip-address>/deploy/suse/sles9 autoyast=http://<ip-address>/sles9.xml" The installer comes up and has a warning: You computer does not fulfill all requirements for a graphical installation. There is less than 96 MB memory or the X server couldn not be started. So the text front-end is used. When you hit OK, linuxrc probes for hardware and does not find the hard disk. It does not even get to the control file part. The same installation server / autoyast control file works fine from CD rom on the same machine. any ideas? steve

1 0

Re: [suse-autoinstall] Network didn't work
by Michael Schulz 21 Jul '06

21 Jul '06

Hi, now I connected the server and client with a new switch and now it works with the IP thanks to all. The netwait is in my case with the bcm5700 not needed. The only think which didn't work in the moment is the profil file. The bootscreen displa "Searching for info File...". But this will not be used. I created a own disk based on SP3 into this image I copied the info file into / that is correct or? Must I modify the autoinst.xml file also? If I give the parmaeter as bootoptions it work. Regards -- Echte DSL-Flatrate dauerhaft für 0,- Euro*! "Feel free" mit GMX DSL! http://www.gmx.net/de/go/dsl

1 0

Re: [suse-autoinstall] Network didn't work
by Hans-Joachim Ehlers 21 Jul '06

21 Jul '06

>>> "Michael Schulz" <problems(a)gmx.net> 20/07/2006 23:19 >>> > Hi there I'm again, But do you listen ? > ... >What can be the difference? time > Have anybody an idee what can be go wrog? As i have experince by myself the tg3 driver needs the netwait option because it initialization time is to long for yast. So the option ' netwait=5 ' should do the trick. Since for you it does not work and your command line is pretty long i assume that the command line IS to long. Again - this happens to me also in the beginning Solution: Put all static stuff into the /info file and the rest on the command line Currently my info file looks like: textmode: 1 insmod: ext3 language: en_US instmode: nfs netdevice: eth0 netwait: 5 netmask: 255.255.0.0 broadcast: 10.11.255.255 gateway: 10.11.0.1 server: 10.11.0.225 serverdir: /export/suse/9.3/x86 domain: my.domain autoyast: nfs://10.11.0.225/export/suse/9.3/autoinstall/ On the command line i just issue hostname=.... hostip=.... Documentation about autoyast - its a MUST to read can be found at Uwe's website http://www.suse.de/~ug/autoyast_doc/index.html hth Hajo

1 0

Confirm Driver Activation
by Michael Schulz 21 Jul '06

21 Jul '06

Hi, after the hardwarescan I have to accept the following modules usb-storag,dm-mod and dm-snapshot. How can I load or cancel this modules automaticly. Because so there is no sense for autoyast. I hope that anybody can help me. Regards -- "Feel free" – 10 GB Mailbox, 100 FreeSMS/Monat ... Jetzt GMX TopMail testen: http://www.gmx.net/de/go/topmail

2 1

Network didn't work
by Michael Schulz 20 Jul '06

20 Jul '06

Hi there I'm again, now i will describe my problem detailed. I try to setup an 64Bit system with autoyast. I give the module for the NIC as bootparameter insmod=tg3 or instmod=bcm5700 (in a regular environment both modules work). I will install from an NFS Share and so I give also the hostip,netmask,install,autoyast,netdevice,netwait parameters as bootptions. But the problem is that the connection between the NFS Server and the autoyast client can not be build. I get the error that the NFS-Server is not available. So i tried it also witht the bootoption dhcp=1 that doesn' work also. But If I install the system from CD than it's possible to connect to the NFS-Share after the Hardware scan (konsole on tty) the module which are loaded for the nic is bcm5700. What can be the difference? Have anybody an idee what can be go wrog? Regares -- Echte DSL-Flatrate dauerhaft für 0,- Euro*! "Feel free" mit GMX DSL! http://www.gmx.net/de/go/dsl

1 0

RE: [suse-autoinstall] No IP
by GUNREBEN, PETER (Peter) 20 Jul '06

20 Jul '06

Michael, Michael Schulz schrieb: > Looking for a network server > ........... > ........... > Automatic setup not possible > > there are my boot parameters > > kernel linux > append initrd=initrd insmod=bcm5700 > autoyast=nfs://10.10.10.248/srv/nfs/sles9-sp3/setup.xml > install=nfs://10.10.10.248/srv/nfs/sles9-sp3/64bit > netmask=255.255.248.0 hostip=10.10.10.247 netdevice=eth0 netwait=300 > Bei mir funktioniert das so über grub: ifconfig --server=<SERVERIP> --gateway=<GATEWAY> --mask=<NETMASK> --address=<TOINSTALLIP> kernel linux hostip=<TOINSTALLIP> gateway=<GATEWAY> ramdisk_size=65536 insmod=3c59x autoyast=nfs://<SERVERIP>/<PATH_TO_XML> initrd initrd boot und dann habe ich noch ein "info" file im /-Verzeichnis mit folgendem Inhalt (ist wahrscheinlich nicht alles nötig): ================ install=nfs://<SERVERIP> serverdir: <PATH_TO_RPMS> netdevice: eth0 netmask: <GATEWAY> server: <SERVERIP> =================== Gruss, Peter.

1 0

Re: [suse-autoinstall] No IP
by Michael Schulz 20 Jul '06

20 Jul '06

Now I have seen on the 3 console that the client will not try to connect to 10.10.10.248/share but 0.0.0.0/share. From where can this mistake come? Regares -- Echte DSL-Flatrate dauerhaft für 0,- Euro*! "Feel free" mit GMX DSL! http://www.gmx.net/de/go/dsl

1 0

Re: [suse-autoinstall] No IP
by Hans-Joachim Ehlers 20 Jul '06

20 Jul '06

I have had problem with fewer then 256 bytes. Like i said: Use and info file. For me it works perfectly. BTW: Is the bcm5700 the correct driver because i think the tg3 is the current one for broadcom ? What kind of network hardware are you using ? Hajo >>> "Michael Schulz" <problems(a)gmx.net> 20/07/2006 17:23 >>> >The boot command line might getting to long. Start using an info file. I think it can up to 256 characters >A simple test is a >cat /proc/cmdline >and verify that It this time I don't have a shell, or? >and a netwait of 5 should be enough. Maybe 300 is not even supported I tried also with 5. For me it's verry importent to solve this problem, but in the moment I don't have an Idea where I should begin. regards >hth >Hajo >>> "Michael Schulz" <problems(a)gmx.net> 20/07/2006 17:09 >>> I tried it with netwait=300 but it doesnt work. The last message whch i get is the following. Looking for a network server ........... ........... Automatic setup not possible there are my boot parameters kernel linux append initrd=initrd insmod=bcm5700 autoyast=nfs://10.10.10.248/srv/nfs/sles9-sp3/setup.xml install=nfs://10.10.10.248/srv/nfs/sles9-sp3/64bit netmask=255.255.248.0 hostip=10.10.10.247 netdevice=eth0 netwait=300 Have anybody an idea? Regards -- Echte DSL-Flatrate dauerhaft für 0,- Euro*! "Feel free" mit GMX DSL! http://www.gmx.net/de/go/dsl -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com * Previous message: Michael Schulz: "Re: [suse-autoinstall] No IP" * Maybe in reply to: Michael Schulz: "[suse-autoinstall] No IP" * Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ] This archive was generated by hypermail 2.1.7 : Thu Jul 20 2006 - 17:14:49 CEST -- Echte DSL-Flatrate dauerhaft für 0,- Euro*! "Feel free" mit GMX DSL! http://www.gmx.net/de/go/dsl

1 0

Re: [suse-autoinstall] No IP
by Michael Schulz 20 Jul '06

20 Jul '06

>The boot command line might getting to long. Start using an info file. I think it can up to 256 characters >A simple test is a >cat /proc/cmdline >and verify that It this time I don't have a shell, or? >and a netwait of 5 should be enough. Maybe 300 is not even supported I tried also with 5. For me it's verry importent to solve this problem, but in the moment I don't have an Idea where I should begin. regards >hth >Hajo >>> "Michael Schulz" <problems(a)gmx.net> 20/07/2006 17:09 >>> I tried it with netwait=300 but it doesnt work. The last message whch i get is the following. Looking for a network server ........... ........... Automatic setup not possible there are my boot parameters kernel linux append initrd=initrd insmod=bcm5700 autoyast=nfs://10.10.10.248/srv/nfs/sles9-sp3/setup.xml install=nfs://10.10.10.248/srv/nfs/sles9-sp3/64bit netmask=255.255.248.0 hostip=10.10.10.247 netdevice=eth0 netwait=300 Have anybody an idea? Regards -- Echte DSL-Flatrate dauerhaft für 0,- Euro*! "Feel free" mit GMX DSL! http://www.gmx.net/de/go/dsl -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com * Previous message: Michael Schulz: "Re: [suse-autoinstall] No IP" * Maybe in reply to: Michael Schulz: "[suse-autoinstall] No IP" * Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ] This archive was generated by hypermail 2.1.7 : Thu Jul 20 2006 - 17:14:49 CEST -- Echte DSL-Flatrate dauerhaft für 0,- Euro*! "Feel free" mit GMX DSL! http://www.gmx.net/de/go/dsl

1 0

Re: [suse-autoinstall] No IP
by Hans-Joachim Ehlers 20 Jul '06

20 Jul '06

The boot command line might getting to long. Start using an info file. A simple test is a cat /proc/cmdline and verify that and a netwait of 5 should be enough. Maybe 300 is not even supported hth Hajo >>> "Michael Schulz" <problems(a)gmx.net> 20/07/2006 17:09 >>> I tried it with netwait=300 but it doesnt work. The last message whch i get is the following. Looking for a network server ........... ........... Automatic setup not possible there are my boot parameters kernel linux append initrd=initrd insmod=bcm5700 autoyast=nfs://10.10.10.248/srv/nfs/sles9-sp3/setup.xml install=nfs://10.10.10.248/srv/nfs/sles9-sp3/64bit netmask=255.255.248.0 hostip=10.10.10.247 netdevice=eth0 netwait=300 Have anybody an idea? Regards -- Echte DSL-Flatrate dauerhaft für 0,- Euro*! "Feel free" mit GMX DSL! http://www.gmx.net/de/go/dsl -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

Re: [suse-autoinstall] No IP
by Michael Schulz 20 Jul '06

20 Jul '06

I tried it with netwait=300 but it doesnt work. The last message whch i get is the following. Looking for a network server ........... ........... Automatic setup not possible there are my boot parameters kernel linux append initrd=initrd insmod=bcm5700 autoyast=nfs://10.10.10.248/srv/nfs/sles9-sp3/setup.xml install=nfs://10.10.10.248/srv/nfs/sles9-sp3/64bit netmask=255.255.248.0 hostip=10.10.10.247 netdevice=eth0 netwait=300 Have anybody an idea? Regards -- Echte DSL-Flatrate dauerhaft für 0,- Euro*! "Feel free" mit GMX DSL! http://www.gmx.net/de/go/dsl

1 0

Re: [suse-autoinstall] No IP
by Hans-Joachim Ehlers 20 Jul '06

20 Jul '06

try as an boot option: netwait=5 Some nework adapter need some time for configuration hth Hajo >>> "Michael Schulz" <problems(a)gmx.net> 20/07/2006 16:27 >>> Hi I have the following problem, when my Autoyastclient try do connect to the NFS Server I get an errot that the server is not available and I will be switched in the manual mode. If I try to connect again with the same settings from there it works. How can I configure the client that it will be longer time try to connect the NFS-Server? Regards -- Echte DSL-Flatrate dauerhaft für 0,- Euro*! "Feel free" mit GMX DSL! http://www.gmx.net/de/go/dsl -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

No IP
by Michael Schulz 20 Jul '06

20 Jul '06

Hi I have the following problem, when my Autoyastclient try do connect to the NFS Server I get an errot that the server is not available and I will be switched in the manual mode. If I try to connect again with the same settings from there it works. How can I configure the client that it will be longer time try to connect the NFS-Server? Regards -- Echte DSL-Flatrate dauerhaft für 0,- Euro*! "Feel free" mit GMX DSL! http://www.gmx.net/de/go/dsl

1 0

Problem with the order of disks
by Michael Schulz 19 Jul '06

19 Jul '06

Hi List, I want to bring up an autoyast environment with SLES 9. The Systems have a local Raid and "SAN" Disk. Now i have the following Problem, the installation setup will find the SAN Disk at first. But I will install the linux on the local Raid Disk. Can anybody tell me how I can setup autoyast so that it will use the Raid Disk as sda? I know It's alos possible to connect the systems later to the san but the other way I will like more. Regards -- Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer

3 2

SLES files not found! (root cause: Network configuration ?)
by Jonathan Meller 17 Jul '06

17 Jul '06

Ave! I want to perform an installation on a machine with the following network configuration: eth0 connected on a 10.*.*.* subnet eth1 connected on a 192.168.0.* subnet eth0 is used to boot a linux image by pxe. eth1 is used to access SLES files by nfs. When the system is rebooted and autoyast is started, the SLES files are not found by autoyast. I suppose it is because autoyast uses the eth0 to get the SLES files, and in this case the eth0 is the PXE subnet. When I change the cables and eth0 becomes the SLES repository, it works. Is there some way to configure autoyast to recognize all subnets during its execution? Thus, I haven't care about the networks order. -- Jonathan Meller jonathan.meller(a)tteng.com.br ======================================================= Tools & Technologies - T&T Engenheiros Associados Ltda. Projetos de SW - Desenvolvendo soluções. Rua Riachuelo, 1098 Conj. 901 Centro - Porto Alegre - CEP 90010-272 Fone DDR: (51)3220-3268 Fone/Fax: (51)3220-3220 / 3220-3206 http://www.tteng.com.br/ tet(a)tteng.com.br =======================================================

1 0

RE: [suse-autoinstall] Problem with Printer setup
by GUNREBEN, PETER (Peter) 17 Jul '06

17 Jul '06

Frank, GUNREBEN, PETER (Peter) schrieb: > fschuett schrieb: > > Am Mittwoch, 12. Juli 2006 14:36 schrieb GUNREBEN, PETER (Peter): > > > Hi, > > > > > > my autoinstallation of SuSE 10.1 interrupts with an error message > > > stating the the CUPS server could not be contacted. > > > However, if I finish the installation I can setup the > > > printers with yast2 in the same way as I did it in the autoyast > > > configurator and do not face any problems. > > > > > I do face the same problem and did already report it as bug to > > bugzilla. It seems to appear, if one installs lpd printers. > > Actually, I'm trying to install to two lpd printers, but the > autoinstallation procedure does not work as expected. I've attached your bug report for easier reference: https://bugzilla.novell.com/show_bug.cgi?id=190173 Thanks, Peter.

1 0

RE: [suse-autoinstall] Problem with Printer setup
by GUNREBEN, PETER (Peter) 17 Jul '06

17 Jul '06

Hi fschuett, fschuett schrieb: > Am Mittwoch, 12. Juli 2006 14:36 schrieb GUNREBEN, PETER (Peter): > > Hi, > > > > my autoinstallation of SuSE 10.1 interrupts with an error message > > stating the the CUPS server could not be contacted. > > However, if I finish the installation I can setup the printers with > > yast2 in the same way as I did it in the autoyast configurator > > and do not face any problems. > > > I do face the same problem and did already report it as bug > to bugzilla. It seems to appear, if one installs lpd printers. Actually, I'm trying to install to two lpd printers, but the autoinstallation procedure does not work as expected. Peter.

1 0

Problem with Printer setup
by GUNREBEN, PETER (Peter) 17 Jul '06

17 Jul '06

Hi, my autoinstallation of SuSE 10.1 interrupts with an error message stating the the CUPS server could not be contacted. However, if I finish the installation I can setup the printers with yast2 in the same way as I did it in the autoyast configurator and do not face any problems. Here's the y2log snippet: 2006-07-11 18:47:12 <1> felix11(3831) [YCP] clients/inst_autoconfigure.ycp:96 current resource: printer 2006-07-11 18:47:12 <1> felix11(3831) [YCP] clients/inst_autoconfigure.ycp:107 Writing configuration for printer 2006-07-11 18:47:12 <1> felix11(3831) [YCP] clients/inst_autoconfigure.ycp:134 Calling auto client with: $["cups_installation":`server, "default":"default", "printcap":[$["ff":false, "info":"Canon iR2200", "location":"1-G327", "manufacturer":"Canon", "model":" imageRunner 330s", "name":"default", "nick":"Canon imageRunner 330s Foomatic/ljet4 (recommended)", "ppd_options":[$["key":"HalftoningAlgorithm", "value":"Standard"], $["key":"InputSlot", "value":"Default"], $["key":"PageSize", "value":"A4"], $["key":"Resolution", "value":"600x600dpi"]], "raw":false, "uri":"lpd://GE1884COFPS2/dexx100418prtca08"], $["ff":false, "info":"Xeroc Document Center CS50", "location":"1-G327", "manufacturer":"Xerox", "model":" DocuPrint C55", "name":"color", "nick":"Xerox DocuPrint C55 Foomatic/Postscript (recommended)", "ppd_options":[$["key":"Duplex", "value":"None"], $["key":"PageSize", "value":"A4"], $["key":"PreFilter", "value":"No"], $["key":"Resolution", "value":"default"]], "raw":false, "uri":"lpd://GE1884COFPS2/CC58404C1"]], "spooler":"cups"] 2006-07-11 18:47:12 <1> felix11(3831) [YCP] clients/inst_autoconfigure.ycp:38 current step: 27 2006-07-11 18:47:12 <2> felix11(3831) [Parser] printer/misc.ycp:729 Warning: find(...) is deprecated, please fix 2006-07-11 18:47:12 <2> felix11(3831) [Parser] printer/misc.ycp:729 Warning: find(...) is deprecated, please fix 2006-07-11 18:47:12 <2> felix11(3831) [Parser] printer/misc.ycp:729 Warning: find(...) is deprecated, please fix 2006-07-11 18:47:12 <1> felix11(3831) [wfm] Y2CCWFM.cc(createInLevel):153 Parsing finished 2006-07-11 18:47:12 <1> felix11(3831) [Interpreter] printer/dialogs.ycp:333 Calling YaST client printer_auto (arguments: ["Write"]) 2006-07-11 18:47:12 <1> felix11(3831) [YCP] Printer.ycp:1411 Write called; spooler: cups, cups inst type: `server 2006-07-11 18:47:12 <1> felix11(3831) [YCP] Printer.ycp:1419 Daemon will run for this configuration: true 2006-07-11 18:47:13 <1> felix11(3831) [YCP] CUPS.ycp:219 CUPS settings read: $["BrowseAllow":["@LOCAL"], "BrowseDeny":["All"], "Group":["lp"], "LogLevel":["info"], "Port":["631"], "Printcap":["/etc/printcap"], "RunAsUser":["Yes"], "User":["lp"]] 2006-07-11 18:47:13 <1> felix11(3831) [YCP] CUPS.ycp:220 CUPS permissions read: $["/":$["Allow":["127.0.0.1", "127.0.0.2", "@LOCAL"], "Deny":["All"], "Order":["Deny,Allow"]], "/admin":$["Allow":["127.0.0.1"], "AuthClass":["Group"], "AuthGroupName":["sys"], "AuthType":["BasicDigest"], "Deny":["All"], "Order":["Deny,Allow"]]] 2006-07-11 18:47:13 <1> felix11(3831) [YCP] CUPS.ycp:256 CUPS settings writing success: true 2006-07-11 18:47:13 <3> felix11(3831) [agent-cups] PrintersConf.cc(readSettings):32 PrintersConf::getPrinters failed 2006-07-11 18:47:13 <3> felix11(3831) [agent-cups] CupsCalls.cc(setPrinter):53 Error while contacting CUPS server occured. 2006-07-12 12:48:34 <3> felix11(3831) [agent-cups] PrintersConf.cc(readSettings):32 PrintersConf::getPrinters failed 2006-07-12 12:48:34 <3> felix11(3831) [agent-cups] CupsCalls.cc(setPrinter):53 Error while contacting CUPS server occured. 2006-07-12 12:48:40 <3> felix11(3831) [agent-cups] CupsCalls.cc(setDefaultDest):473 Error while contacting CUPS server occured and the .xml snippet <printer> <cups_installation config:type="symbol">server</cups_installation> <default>default</default> <printcap config:type="list"> <printcap_entry> <ff config:type="boolean">false</ff> <info>Canon iR2200</info> <location>1-G327</location> <manufacturer>Canon</manufacturer> <model> imageRunner 330s</model> <name>default</name> <nick>Canon imageRunner 330s Foomatic/ljet4 (recommended)</nick> <options config:type="list"/> <ppd_options config:type="list"> <ppd_option> <key>HalftoningAlgorithm</key> <value>Standard</value> </ppd_option> <ppd_option> <key>InputSlot</key> <value>Default</value> </ppd_option> <ppd_option> <key>PageSize</key> <value>A4</value> </ppd_option> <ppd_option> <key>Resolution</key> <value>600x600dpi</value> </ppd_option> </ppd_options> <raw config:type="boolean">false</raw> <uri>lpd://GE1884COFPS2/dexx100418prtca08</uri> </printcap_entry> <printcap_entry> <ff config:type="boolean">false</ff> <info>Xeroc Document Center CS50</info> <location>1-G327</location> <manufacturer>Xerox</manufacturer> <model> DocuPrint C55</model> <name>color</name> <nick>Xerox DocuPrint C55 Foomatic/Postscript (recommended)</nick> <options config:type="list"/> <ppd_options config:type="list"> <ppd_option> <key>Duplex</key> <value>None</value> </ppd_option> <ppd_option> <key>PageSize</key> <value>A4</value> </ppd_option> <ppd_option> <key>PreFilter</key> <value>No</value> </ppd_option> <ppd_option> <key>Resolution</key> <value>default</value> </ppd_option> </ppd_options> <raw config:type="boolean">false</raw> <uri>lpd://GE1884COFPS2/CC58404C1</uri> </printcap_entry> </printcap> <server_hostname></server_hostname> <spooler>cups</spooler> </printer>

2 1

Custom Add-On Source twice in Installation Sources
by Goetz Rieger 13 Jul '06

13 Jul '06

Hi, I do autoinstalls using an HTTP source and packages from a custom add-on source. After installation the entry for the add-on exists twice in YaST2 Installation Sources. Not that this is doing any harm, I just wonder why. Cheers, Goetz

2 1

SLED10: Install Older Package Version
by Goetz Rieger 12 Jul '06

12 Jul '06

Hi guys, I would like to install an older version of a package (actually it's the Groupwise client) then the one included on the SLED10 DVD. So I created an add-on source with the older RPM and added the add-on to the control file. Naturally now the autoinstall installs the newest version. I can think of some ways to get the older version installed but I really want to do it the proper way (TM). So I will stay away from trying to delete the newer version from the DVD package database or the like. Now, what is the proper way? ;-)) Thanks in advance, Goetz

2 2

post install scripts with prompts
by Simon Crute 12 Jul '06

12 Jul '06

Hi, I'm trying to install some RPMs during the post install script using rug (the ati drivers) However, they require the agreement to a license agreement. Has anyone figured out a way of agreeing to this automatically ? -- Simon Crute IS&T Bracknell Novell UK Ltd

1 0

URL encoding in rules.xml
by Luzian Scherrer 11 Jul '06

11 Jul '06

Hi there, This URL part from rules.xml ... <result> <profile>controlfiles/getcontrolfile.xml?mac=@mac@</profile> <continue config:type="boolean">true</continue> </result> ... gets converted to controlfiles/getcontrolfile.xml%3fmac%3d... from (as far as I understand) SuSE 10.1 on. This conversion did not happen in earlier versions. In my opinion this is wrong; users should be able to add parameters using the http-get syntax in rules.xml. Is this fact already known and if so, is it considered a feature or will it be changed? Thanks, -Luzian

3 3

Integrating patches in 10.1
by Beat Rubischon 11 Jul '06

11 Jul '06

Hello! I'm still fighting against Autoyast to get fresh installed SuSE 10.1 systems containing all recent patches. Before the libzypp update I was able to add an local copy of the update directory using "rug service-add" and "rug subscribe -a" - A "rug update" did then the job. Since the libzypp update [1] this approach is no longer possible as the update does not install. I need to use YaST in an unscripteable way. An approach like in 10.0 using the command line "online_update -u nfs://192.0.1.1/export/suse/updates -V -l en" is also not possible as this binarie does no longer exist. [1] http://lists.suse.com/archive/suse-security-announce/2006-Jun/0004.html My next try was to integrate the updates into the installsource. I found several more or less usable postings in this mailinglist - the only way it works is to get a local mirror of the current updates and integrate them into the installsource using create_update_source.sh [2] and create_package_descr [3]. I followed the instructions in the scripts and added a add_on_products in the install directory as described in the FAQ [4]. [2] http://www.suse.com/~ug/tools/create_update_source.sh [3] http://www.suse.com/~ug/tools/create_package_descr [4] http://www.suse.com/~ug/AutoYaST_FAQ.html#b9 To avoid the dialog about unsigned packages, I added the needed statements to my autoyast file: <general> <signature-handling> <accept_unsigned_file config:type="boolean">true</accept_unsigned_file> <accept_file_without_checksum config:type="boolean">true</accept_file_without_checksum> </signature-handling> </general> I even patched my installsource using the root image updater [5] - I followed the instruction that the utility must be run on a x86_64 system to provide an update for those architecture. The YaST logfile shows that the configuration entrys are parsed - but the dialog [6] still appears :-( [5] http://lists.suse.com/archive/suse-autoinstall/2006-Jun/0109.html [6] http://www.0x1b.ch/~beat/autoyast.png Any other solution? Delivering systems to a customer without patches is quite often a security problem and It does not make a good impression when the customer needs to run YaST twice with a reboot between it and download half a Gig of patches - on the other hand, we need a way to integrate those patches without user intervention. SLES10 - when finished - is only a solution for customers who are willing to pay the license... Beat Rubischon -- Beat Rubischon <beat.rubischon(a)dalco.ch> DALCO AG, Industriestrasse 28, 8604 Volketswil

2 2

Howto export the package-selection in 10.1
by Guido Kölsch 11 Jul '06

11 Jul '06

Hi, i have to migrate from SuSE 9.3 to 10.1 and i want to use the old package-selection from 9.3. I want to upgrade one old 9.3 to 10.1 so that yast create the new software-selection based on the old selection. This method works from 8.2 to 9.3 but not for 10.1 because in yast there is no function to export the current selection. Is there a different way to keep the old package-selection and migrate it to 10.1? Regards Guido Kölsch -- ------------------------------------------------------------------------ Guido Kölsch -Rechenzentrum- Max-Planck-Institut fuer Radioastronomie Phone: +49 (0)228 525 164 Auf dem Huegel 69, D-53121 Bonn, Germany FAX : +49 (0)228 525 229 email: gkoelsch(a)mpifr-bonn.mpg.de ------------------------------------------------------------------------

1 1

SLES 9.3 geometry and initialize after Windows install
by John Willis 10 Jul '06

10 Jul '06

Hi, I've come across a curious effect and have a solution, but would like some confirmation, or commentary. Symptom: hardware - 32 bit i386 SLES9.3, fibre channel volume using qla2300 hba, devoid of any partition table. Windows 2000 is installed upon it then SLES 9.3 is installed upon it, completely wiping out windows partitions using autoyast and <initialize> true. Installation proceeds for a while then halts with the message "insufficient space to continue". Using ALT+F6 to get to the console, the root partition / is sized to 1.1 GB out of 10 GB where autoyast was told to use <auto> and <max> for the partitions, it should be much larger, a lot of the disk space is unpartitioned. If the SLES 9.3 installation is tried again, it succeeds, and the partitions now use the whole disk. Solution: Looking over /var/log/YaST/y2log, the hardware detect phase seems to detect the drive geometry based on something the Windows 2000 install leaves in the partition table, and makes its calculations based on that. Even if none of the windows partitions are saved, and then the partition table is <re-initialized> with a linux partition table. Using <initialize> true </initialize> causes the problem. Using <initialize> false </initialize> does not cause the problem. Thoughts: browsing the y2log file of a failure and success, it appears the disk geometry is acquired "before" the partition is re-initialized with a linux partition "type" table, in the windows->sles9.3 failure the cyclinders are reported as 1274, in the sles9.3->sles9.3 success they are reported as 9997. They are both correct as the windows type geometry has one set of CHS and the linux type geometry has a different set of CHS. the solution wouldn't bother me except the thought of having no control over the actual disk geometry used by the autoyast installer, is there a way of overriding the hardware detection of disk geometry? or a way of triggering a new disk geometry acquisition after the partition table is initialized and before the partitions are auto-calculated? (I'd guess the right thing would have been for "initialize" to occur before hardware geometry detect.) but i think my preference would be access from a pre-script to modify or provide the values I choose for CHS to the autoyast installer, but I don't know how to access the hardware detect information thats acquired before the pre-script. Would it be in a staging log somewhere? Thanks for any considerations. And I sincerely apologize if this belongs in a developers forum.

2 1

Custom RPMs SLED 10 RC3
by Goetz Rieger 08 Jul '06

08 Jul '06

Hi list, I'm trying to add some custom RPM's to a SLED10 autoinstall using a customized DVD. The basic autoinstall works well. I understand that the simple recreation of the package database and the <package>rpm</package> section in autoinst.xml is not working for this anymore. So I have created a directory in the DVD root with a new tree using the create_update_source.sh script, copied a test RPM there and build the package database. As stated in the docs. And I even disabled the signature check. The add_on_products file in the DVD root looks like dvd:///updates It is not really clear to me how the add-on stuff works. So I did add a <addons config:type="list"> <addon>updates</addon> </addons> to the xml file. It's not working and I will spare the details because I think I am doing something wrong. Do I need to add more to the xml file? Like a selection? The docs are a pretty secretive on this, could someone shine a bit of light on this?. Cheers, Goetz

3 5

RE: [suse-autoinstall] where do I get a usable 10.1 ISO image
by Matt Gillard 06 Jul '06

06 Jul '06

All those files should exist - the ones under x86_64 anyway. What do you see under x86_64 ? Perhaps bad apache config? Bad permissions? > -----Original Message----- > From: Lonni J Friedman [mailto:netllama@gmail.com] > Sent: Thursday, 29 June 2006 8:36 AM > To: Jesus Gonzalez > Cc: suse-autoinstall(a)suse.com > Subject: Re: [suse-autoinstall] where do I get a usable 10.1 ISO image > > > On 6/28/06, Jesus Gonzalez <jgjnet(a)gmail.com> wrote: > > 2006/6/27, Lonni J Friedman <netllama(a)gmail.com>: > > > > > I feel like i'm talking to myself on this list. I'm > trying to used > > > autoyast to install suse-10.1, yet all I keep getting are > errors which > > > seem to suggest that I'm not using a valid installation > source. I've > > > tried the DVD image from the opensuse.org website, and also tried > > > pointing directly at a mirror (mirrors.kernel.org) Neither is > > > working. Surely I'm missing something very obvious, yet I can't > > > figure out what. > > > > > > The same autoyast.xml just works for both 10.0 & 9.3. > > > > > > Please, can someone point me to a known good installation > source for > > > 10.1 (x86 & x86_64) that autoyast won't barf at? many thanks. > > > > > > > > Perhaps you are facing the same "signature nightmare" I > found the first time > > I tried this new version. > > > > Try to add the following to your autoyast.xml: > > > > <general> > > <signature-handling> > > <accept_unsigned_file > > config:type="boolean">true</accept_unsigned_file> > > <accept_file_without_checksum > > config:type="boolean">true</accept_file_without_checksum> > > <accept_verification_failed > > config:type="boolean">true</accept_verification_failed> > > <accept_unknown_gpg_key > > config:type="boolean">true</accept_unknown_gpg_key> > > </signature-handling> > > </general> > > Tried this, no luck. I still get the same failure: > Could not set patterns/selections: Basis-Devel, > GNome,Kde,Kde-Desktop,Kernel-devel > > In y2log I see: > Bad media attach point: http://10.31.40.58/distros/suse/os/10.1/x86_64/ If I check the apache server's on 10.31.40.58 error_log I see the following: File does not exist: /storage/distributions/distros/suse/os/10.1/x86_64/media.1/installfiles File does not exist: /storage/distributions/distros/suse/os/10.1/x86_64/media.1/info.txt File does not exist: /storage/distributions/distros/suse/os/10.1/x86_64/part.info File does not exist: /storage/distributions/distros/suse/os/10.1/x86_64/driverupdate Anyone know why yast is looking for those files when they do not exist in the 10.1 installation source? -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ L. Friedman netllama(a)gmail.com LlamaLand http://netllama.linux-sxs.org -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com This email and any attachments may contain privileged and confidential information and are intended for the named addressee only. If you have received this e-mail in error, please notify the sender and delete this e-mail immediately. Any confidentiality, privilege or copyright is not waived or lost because this e-mail has been sent to you in error. It is your responsibility to check this e-mail and any attachments for viruses. No warranty is made that this material is free from computer virus or any other defect or error. Any loss/damage incurred by using this material is not the sender's responsibility. The sender's entire liability will be limited to resupplying the material.

4 12

FYI: adding own RPMs to a SLES10 inst. source
by Uwe Gansert 06 Jul '06

06 Jul '06

Hi, here is a small documentation how to add own RPMs to a SLES10/SL10.1 installation source. To create a tree with RPMs in parallel of your other installation source, use at least version 20060418 of create_update_source.sh from my SUSE Homepage (http://www.suse.de/~ug) The latest autoyast2-utils RPM will contain that script too. You can find documentation on how to use that script on my homepage. After you have created the tree with your own RPMS, you have two options· to tell autoyast about that new installation source. Either in the autoyast profile like this: > <add-on> > <add_on_products config:type="list"> > <listentry> > <media_url>http://192.168.66.1/SLES10/updates</media_url> > <product>SuSE-Linux-Updates</product> > <product_dir>/</product_dir> > </listentry> > </add_on_products> > </add-on> You can do that with the autoyast UI on SLES10/SL10.1 too. Or another option is to create a file called "add_on_products" on the main installation source. So it looks like this (the "updates" directory was created by the script): > #:/space/SLES10 # tree -L 1 > . > |-- ARCHIVES.gz > |-- COPYING > |-- COPYING.de > |-- COPYRIGHT > |-- COPYRIGHT.de > |-- ChangeLog > |-- INDEX.gz > |-- LICENSE.TXT > |-- NEWS > |-- README > |-- README.BETA > |-- README.BETA.DOS > |-- README.DOS > |-- add_on_products > |-- boot > |-- content > |-- control.xml > |-- directory.yast > |-- docu > |-- dosutils > |-- gpg-pubkey-0dfb3188-41ed929b.asc > |-- gpg-pubkey-1d061a62-427a396f.asc > |-- gpg-pubkey-307e3d54-44201d5d.asc > |-- gpg-pubkey-3d25d3d9-36e12d04.asc > |-- gpg-pubkey-9c800aca-40d8063e.asc > |-- ls-lR.gz > |-- media.1 > |-- pubring.gpg > |-- suse > `-- updates > > #:/space/SLES10 # cat add_on_products > http://192.168.66.1/SLES10/updates With that file on the installation source, you don't need to specify the additional installation sources in the autoyast profile. You can mix those two options. So it's possible to specify one installation source in the autoyast profile and another one in the "add_on_products"-file. The "add_on_products"-file is not supported by autoyast in RC1 but will be with later versions. I hope that helps. -- 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

1 2

Autoyast + SLED 10 RC3
by Bernd Nies 04 Jul '06

04 Jul '06

Hi, I'm trying to get SLED 10 RC3 to be installed with Autoyast. At the point where Autoyast configures the software selections I get this error message: Warning: Could not set patterns or selections: Basis-Devel, apparmor, ccb, desktop-base, desktop-gnome, desktop-kde, documentation, x11 The software section of the Autoyast XML file is: <software> <patterns config:type="list"> <pattern>desktop-base</pattern> <pattern>ccb</pattern> <pattern>documentation</pattern> <pattern>desktop-kde</pattern> <pattern>desktop-gnome</pattern> <pattern>apparmor</pattern> <pattern>apparmor</pattern> <pattern>Basis-Devel</pattern> <pattern>x11</pattern> </patterns> </software> Which is the new syntax of SLES 10 with patterns instead of selections and without <configure> and <install> sections anymore. Is this a known bug or am I doing something wrong? Bye Bernd

2 2

Re: [suse-autoinstall] Autoyast + SLED 10 RC3
by Bernd Nies 04 Jul '06

04 Jul '06

Hi Tim, > I had this problem with Beta 7 but it's been since fixed. You may want to > check the md5sums of your DVD image as this also causes this error in RC2 > (due to a bad download). I have RC3 installing fine with a similar > patterns XML structure to you. Thanks. I checked the MD5 checksums of all five disks. They are okay. Installation without Autoyast directly from CD works fine. Regards, Bernd

1 0

Problem with patterns in sles10
by Rainer Krienke 03 Jul '06

03 Jul '06

Hello, I tried to convert my SLES9 autoyast file to one that is usable for a SLES10 installation. There is a problem with the software selection. In my sles9 autoyast file I had: <software> <addons config:type="list"> <addon>Base-System</addon> <addon>Basis-Devel</addon> <addon>File-Server</addon> <addon>Linux-Tools</addon> <addon>YaST2</addon> <addon>analyze</addon> </addons> <base>Minimal</base> <packages config:type="list"> <package>rdist</package> <package>findutils-locate</package> </packages> </software> This worked. Now I tried the one shown below for sles10 which results in an error message I cannot interpret. Here a screen shot of the error: http://www.uni-koblenz.de/~krienke/tmp/sles10.jpg (80Kb) Here the software section part of the sles10 autoyast file: <software> <patterns config:type="list"> <pattern>gnome-64bit</pattern> <pattern>apparmor</pattern> <pattern>base-64bit</pattern> <pattern>apparmor-64bit</pattern> <pattern>base</pattern> <pattern>64bit</pattern> <pattern>Basis-Devel</pattern> <pattern>Basis-Devel-64bit</pattern> </patterns> <packages config:type="list"> </packages> </software> I took this from an autoyast file generated during cloning of a SLES10 system, added the two Devel-section patterns and removed all package entries. But this seems to be wrong somehow. What is wrog with this config? Thanks Rainer -- --------------------------------------------------------------------------- Rainer Krienke, Universitaet Koblenz, Rechenzentrum, Raum A022 Universitaetsstrasse 1, 56070 Koblenz, Tel: +49 261287 -1312, Fax: -1001312 Mail: krienke(a)uni-koblenz.de, Web: http://www.uni-koblenz.de/~krienke Get my public PGP key: http://www.uni-koblenz.de/~krienke/mypgp.html ---------------------------------------------------------------------------

3 4