June 2006 - openSUSE Autoinstall - openSUSE Mailing Lists

autoyast and customer center configuration
by Simon Crute 29 Jun '06

29 Jun '06

Hi, I'm trying to configure the novell customer center via autoyast on sled10-rc3 I'm using the following in my rule file. <customer_center> <do_registration config:type="boolean">true</do_registration> <registration_data> <email>scrute(a)novell.com</email> </registration_data> <submit_hwdata config:type="boolean">true</submit_hwdata> <submit_optional config:type="boolean">true</submit_optional> </customer_center> However, it seems as if it's automatically downloading updates when I register. The current autoyat docs don't have anything covering the <customer_center> but yet, so is there any way to turn this off ? It is also failing to add the ati and nvidia installation sources, (and presumably, there needs to be a way to accept the importing of the ATI and nvidia keys (or not) ) Thanks. -- Simon Crute IS&T Bracknell Novell UK Ltd

2 3

Network installation with update rpms
by Olivier H 29 Jun '06

29 Jun '06

Hello, I have a working network installation of Suse 10.0 using autoyast. I downloaded tke KDE update rpms (version 3.5.3) at http://software.opensuse.org/download and I put them on a nfs server. I did a post install script to upgrade my system using these rpms. Is there a way to do that without using post install scripts, directly in autoyast ? _________________________________________________________________ www.windowslivemessenger.fr

2 1

where do I get a usable 10.1 ISO image
by Lonni J Friedman 28 Jun '06

28 Jun '06

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. -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ L. Friedman netllama(a)gmail.com LlamaLand http://netllama.linux-sxs.org

2 4

Merging multiple post-scripts with rules
by Jeremy Silver 27 Jun '06

27 Jun '06

I have just started using rules to handle the hardware/software combinations I have to build. I have a series of profiles to handle partitioning, a default profile to handle all of the other OS parameters, including a post install script to do some further customization. I also have several other post-install scripts I would like to run depending on a custom rule. The problem I have run into is that if my default.xml contains my standard post-install script (post.sh) and I try to have a rule to include another post-install script (bms.sh), only the post.sh script gets merged. When I remove post.sh from the default.xml, the bms.sh script gets merged. Is there a way to merge multiple post-scripts or are they supposed to be mutually exclusive? I am using SLES9 SP3. My rules file and profile files with the scripts are attached. Thanks for any insight anyone may have. -- Jeremy Silver jeremy(a)broadware.com

2 2

FYI: root image update for 10.1
by Uwe Gansert 27 Jun '06

27 Jun '06

Hi, I have created a patch for the root image of a 10.1 i386 and x86_64 system. You can find the root image on ftp://ftp.suse.com/pub/people/ug/autoyast fixed issues: * signature popup breaks the autoinstallation * disk nearly full popup breaks the autoinstallation * <remove-package> is fixed if you trigger a dependency conflict by the remove, the package will still be installed and not removed. * LVM max calculation is less aggressive * <import_gpg_key> added to the signature section, to import keys on the inst-source into the RPM database Go the the root of your installation server and run the script there. The root is where the "media.1" and the "suse" directory is. Don't run the script on an i586 hardware if the installation server is for x86_64 machines. Run the script on the x86_64 machine instead and copy the driverupdate file to the installation server. There is no official support for this patch. Use it on your own risk. The patch is reversible by deleting the file "driverupdate". I plan to do a second patch with EVMS support and more bugs fixed but version 0.1 addresses the most annoying bugs for the moment. -- 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 Fax: +49-(0)911-74053-476, Web: http://www.suse.de/~ug

1 0

SLES 10 RC2 remove-packages section?
by Timothy Wright 27 Jun '06

27 Jun '06

Hi, Is <remove-packages> supported in SLES 10 RC2? The following was setup to test... <software> <patterns config:type="list"> <pattern>base</pattern> <pattern>apparmor</pattern> </patterns> <remove-packages config:type="list"> <package>mutt</package> </remove-packages> </software> But on the installed system I still have the package. Any ideas, or do I have to create a customised pattern? There will potentially be many more packages to be removed, but we would prefer to do this in XML (to maintain a vanilla installation source). Cheers Tim --- This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.

3 4

more with rules
by Pablo Gomez 27 Jun '06

27 Jun '06

Hello again, after solving the first problem with <rules> usage, mostly file location originated, I face with a new one, that seems NOT TO BE the same, but... The effect is that files don't merge. The ibiza-3.0.xml, that should be merged anyway is not used, while the default.xml is perfectly read and used. As the system ends with a generic hostname, some parts of it are nor installed :-(. My new rules.xml: <!DOCTYPE autoinstall SYSTEM "/usr/share/autoinstall/dtd/rules.dtd"> <autoinstall xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <rules config:type="list"> <rule> <mac> <match>*</match> <match_type>exact</match_type> </mac> <result> <profile>rules/default.xml</profile> <continue config:type="boolean">true</continue>  </result> </rule> <rule> <mac>  <match>*</match>  <match_type>exact</match_type> </mac> <result>   <profile>rules/ibiza-3.0.xml</profile> <continue config:type="boolean">false</continue> </result> </rule>  </rules> </autoinstall> Meanwhile the ibiza-3.0.xml is (quite simple, hehe!): <networking> <dns> <hostname>ibiza</hostname> </dns> </networking> The default.xml <networking><dns> section is: <networking> <dns> <dhcp_hostname config:type="boolean">false</dhcp_hostname> <dhcp_resolv config:type="boolean">true</dhcp_resolv> <domain>mydomain.mydomain</domain>  <searchlist config:type="list"> <search></search> </searchlist> </dns> </networking> I can see on first install stages, in /tmp/profile/autoinst.xml that there is no <hostname> section on the used profile. By the way is there any "civilized" way of consulting this autoinst.xml once the system is completely installed? Thanks in advance. Pablo Gómez

2 2

autoinstall fails with 10.1 works with earlier versions
by Lonni J Friedman 26 Jun '06

26 Jun '06

Greetings, I'm trying to get an autoinstall working for SuSE-10.1 using the same autoyast.xml that has worked just fine for 10.0 and 9.3, and it keeps failing with an assortment of errors. Right now, the failure that I'm seeing occurs when the yast installer reaches the "Configure Software selections" portion, at which point I see the error: Could not set patterns/selections: Basis-Devel,Gnome,Kde,Kde-Desktop,Kernel-devel Here's what the relevant portion of my autoyast.xml looks like: <software> <addons config:type="list"> <addon>Basis-Devel</addon> <addon>Gnome</addon> <addon>Network</addon> <addon>Kde</addon> <addon>Kde-Desktop</addon> <addon>Kernel-Devel</addon> <addon>X11</addon> </addons> </software> I'm doing this installation over http from a local system which has the contents of the downloaded SUSE-Linux-10.1-GM-DVD-x86_64.iso image available via apache. thanks! -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ L. Friedman netllama(a)gmail.com LlamaLand http://netllama.linux-sxs.org

2 3

Changing the default boot selection (SUSE 10.1 w/ grub)
by Marlier, Ian 26 Jun '06

26 Jun '06

I'm working on an autoinstall profile for a set of machines that are all going to be running Xen, and thus need to use the -xen kernel. the .xml file has 4 sections, the first of which uses the standard -smp kernel, then the -xen kernel, then the floppy, and then the rescue system. Each of the sections works fine when selected at boot. The configurator thingy in YaST (on a running system) thinks I should be able to do something like this (trimmed quite a bit, but the point remains -- if the full xml would help, let me know and I can send it along): <bootloader> <global> <default>XEN</default> </global> <sections config:type="list"> <section> <name>SUSE Linux 10.1</name> </section> <section> <name>XEN</name> </section> <section> <name>Floppy</name> </section> <section> <name>SUSE 10.1 Rescue</name> </section> </sections> </bootloader> However, I seem to end up booted into whatever option is first in this list, regardless of what the "default" section reads. /boot/grub/menu.lst ends up with a line that looks like this: default when I think it should read default XEN or maybe default 1 So, my question: is this a bug? If so, is it a bug in the autoinstaller, or in the configurator thingy? Or am I just missing something? (I'm trying a workaround right now, just moving the XEN section to the top of the list, above the -smp section. That may work, does seem like less than ideal behavior, though...) Thanks, Ian

4 3

Missing Default timeout in initial boot
by Folkhard Mueller 26 Jun '06

26 Jun '06

Dear Comrade Admins, Second trial, since elmz turned me down ?! I have a small but nasty problem with autoinstall. I use SuSE Linux 10.0's autoyast. All is fine but after all packages are installed the system is prepared for the first initial boot. In this step there is obvioulsy the boot timeout set to 0 which means the system waits forever to boot. One Return plugged in on the Keyboard is enough and ibooting occurs successfully. The boot timeout in the final system is o.k. (set to 8 as defined in the bootlader section of the controlfile ) by: snip.. <global_entry> <key>timeout</key> <value config:type="integer">8</value> </global_entry> snap.. Any hints ? -- |\ _,,,---,,_ ZZZzz /,`.-'`' -. ;-;;,_ _______|,4- ) )-,_. ,\ (____-'_________________________________________ '---''(_/--' `-'\_) Dipl. Phys. F.Mueller EPCOS AG Surface Acoustic Wave Components Division SAW RD CAD P.O. Box 80 17 09 Phone: ++49 89 636 23316 D-81617 Munich Fax: ++49 89 636 27304 Germany mailto: Folkhard.Mueller(a)epcos.com Web: http://www.epcos.com

1 0