June 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

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

Missing Default timeout in bootp
by Folkhard Mueller 29 Jun '06

29 Jun '06

Dear Comrade Admins, 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

3 6

Re: [suse-autoinstall] where do I get a usable 10.1 ISO image
by Lonni J Friedman 29 Jun '06

29 Jun '06

On 6/28/06, Matt Gillard <Matt.Gillard(a)colesmyer.com.au> wrote: > > post your autoyast.xml file as well. ok, i've uploaded my autoyast.xml to http://netllama.linux-sxs.org/autoyast.xml thanks -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ L. Friedman netllama(a)gmail.com LlamaLand http://netllama.linux-sxs.org

1 0

RE: [suse-autoinstall] SLES 10 RC2 remove-packages section?
by Matt Gillard 29 Jun '06

29 Jun '06

Anyone got this to work for SLES10 RC3 ? I tried and it didnt seem to work...trying to get rid of: ppp smpppd pptp wvdial (to start with anyway) matt > -----Original Message----- > From: Uwe Gansert [mailto:ug@suse.de] > Sent: Tuesday, 20 June 2006 2:12 AM > To: suse-autoinstall(a)suse.com > Subject: Re: [suse-autoinstall] SLES 10 RC2 remove-packages section? > > > On Thursday 01 June 2006 14:45, Timothy Wright wrote: > > > 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> > > fixed for RC3 > > -- > 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 > > -- > 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.

3 3

script/rule?
by Salbeck, Christian, MSOP51 29 Jun '06

29 Jun '06

Hi there mailing-list, I try to install with autoyast and i do not have that much experience with it! Here's what I need your help for: I want to source a script as a post install script, but I don't want to edit each of my .xml-file (about 100). Can't I put that script on the install server? thanx for any help! mit freundlichen Grüssen Salbeck Christian Dipl.-Ing.(FH) www.eads.com <http://www.eads.com/> EADS Deutschland GmbH Coastal Surveillance Systems MSOP51 Landshuter Straße 26 85716 Unterschleißheim Germany <http://link2.map24.com/?street0=Landshuter+Str.+26&zip0=85716&city0=Untersc…> Phone: +49 (089) 3179 - 2102 E-Mail christian.salbeck(a)eads.com <mailto:christian.salbeck@eads.com>

2 1

script/rule?
by Salbeck, Christian, MSOP51 29 Jun '06

29 Jun '06

Hi there mailing-list, I try to install with autoyast and i do not have that much experience with it! Here's what I need your help for: I want to source a script as a post install script, but I don't want to edit each of my .xml-file (about 100). Can't I put that script on the install server? thanx for any help! mit freundlichen Grüssen Salbeck Christian Dipl.-Ing.(FH) www.eads.com <http://www.eads.com/> EADS Deutschland GmbH Coastal Surveillance Systems MSOP51 Landshuter Straße 26 85716 Unterschleißheim Germany <http://link2.map24.com/?street0=Landshuter+Str.+26&zip0=85716&city0=Untersc…> Phone: +49 (089) 3179 - 2102 E-Mail christian.salbeck(a)eads.com <mailto:christian.salbeck@eads.com>

1 0

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

How to install all packages before reboot
by hanpingtian＠gmail.com 23 Jun '06

23 Jun '06

hi list, We are testing autoyast on sles10 now. We find that sles10 autoyast would install some packages after first rebooting. But we find that we need to install all packages before first reboot now. Is this preformable? What should we do ? Thanks!

2 1

RAID-1 without specifying devices
by Darin Perusich 23 Jun '06

23 Jun '06

hello all, is it possible to setup RAID-1 mirrors in autoyast without specifying the device? i'm able to mirror all of the partitions when i specify the devices but when i remove the device, <device>/dev/sda</device> the installer fails because no devices have been specified. i'm running SuSE 9.3. thanks -- Darin Perusich Unix Systems Administrator Cognigen Corporation 395 Youngs Rd. Williamsville, NY 14221 darinper(a)cognigencorp.com

2 1

automated installation interrupted
by Arvid Walter 23 Jun '06

23 Jun '06

Hi, The autoyast installation stops and asks me to accept the settings [1][2] without any warning or error message appearing on the screen or in the logs. [1] http://img90.imageshack.us/my.php?image=autoyast4bt.jpg [2] http://img214.imageshack.us/my.php?image=autoyast26rv.jpg By the way, the autoyast generated xml files are not valid and cannot be verified using the dtd. I checked it myself with eclipse+oxygenxml - very many problems.

2 1

rules
by Pablo Gomez 23 Jun '06

23 Jun '06

Hello everyone, while i am a quite experiencied user of autoyast, it is the first time I use <rules>! From the docs I understand you should remove "autoyast=...", is it?. If I do this I get a manual installation, what seems reasonable as my new system knows nothing about where to fetch a control file! If, alternatively, I pass a "autoyast=http://10.7.5.100/autoinstall/", being this directory both valid and the container of a unique xml file (control.xml), that is: <?xml version="1.0"?> <!DOCTYPE autoinstall SYSTEM "/usr/share/autoinstall/dtd/rules.dtd"> <autoinstall xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <rules config:type="list"> <rule> <mac> <match>*</match> <match_type>exact</match_type> </mac> <result> <profile>default.xml</profile> <continue config:type="boolean">true</continue> </result> </rule> </rules> </autoinstall> pls have in mind I am still testing, and with this file I only pretend to use the whole default.xml (http://10.7.5.100/autoinstall/rules/default.xml) but it doesn't work. By the way, default.xml is a complete, valid and working control file, that has been previously tested in a "autoyast=http://10.7.5.100/autoinstall/default.xml" installation. Any help? Thanks in advance! Pablo Gomez

2 3

Adding custom selections to a network installation source
by Danilo Godec 21 Jun '06

21 Jun '06

Hi, I'd like to create some custom package selections so users that (re)install their machines would have an easier job doing so. We're going to use SuSE 10.1. Now since I don't have that many machines to install (up to 10/month) I don't really want to mess with whole autoinstall/autoyast deal. I tried 'the simple way' - created a couple of '.sel' files, added those to the file 'selections'. I also added MD5 sums to the MD5SUMS file (and corrected the sum for 'selections' file). Then I tried installing from this network source - boot the machine with the CD, setup the NFS installation source. But when it comes to package evaluation/selection, the installation cannot find any packages. The log file reveal complaints about corrupted installation source... Is there a right way to do this? Thanks, Danilo

2 1

I want to use remove-packages
by Erik Streb 19 Jun '06

19 Jun '06

Hello. I'm using suse-autoinstall with Suse Linux 10.1. In the software section of the xml-file I put some packages to remove (to not install). But after installation the packages are installed anyway. Why? Looks like this: <software> <addons config:type="list"> <addon>Kde-Desktop</addon> <addon>Min</addon> </addons> <base>Minimal</base> <remove-packages config:type="list"> <package>OpenOffice_org-de-templates</package> <package>OpenOffice_org-Quickstarter</package> <package>OpenOffice_org-de</package> <package>OpenOffice_org-kde</package> <package>OpenOffice_org</package> <package>beagle-firefox</package> <package>MozillaFirefox-translations</package> <package>MozillaFirefox</package> <package>acroread</package> <package>RealPlayer</package> <package>amarok</package> <package>amarok-helix</package> <package>flash-player</package> </remove-packages> </software> All of the packages in the remove-packages section are installed to my regret. Thanks Erik Streb

2 1

Order of network interfaces?
by Johan Kielbaey 17 Jun '06

17 Jun '06

Hello, I'm using a http repository with tftp and dhcp. The environment i'm working in has meanly IBM servers, but from different models (x346, x306m, x366, ...). For each model i need to investigate which interface used by pxe maps to which ethX interface in linux. This gets even worse if with a new delivery there is another type of network card in the PCI slot. How are you handling different hardwaremodels? Is there a way to make sure that the 1st onboard interface also maps to eth0? This is my pxe-config file : #default label linux kernel linux-9sp3 append initrd=initrd-9sp3 ramdisk_size=65536 insmod=bcm5700 install=http://192.168.71.1/rp/x86/SLES9SP3 instmode=http bootpwait=10 dhcptimeout=120 usedhcp=1 textmode=1 autoyast=http://192.168.71.1/cf/sltr001/cf Thanks, Johan Mvg - Rgds Johan <johankielbaey(a)yahoo.com>

2 2

more complex rules.xml examples?
by John SJ Anderson 14 Jun '06

14 Jun '06

I apparently need to use rules.xml to accomplish some of the gnarlier things I'd like to do with the autoinstaller. Unfortunately, the examples in the autoyast.pdf I have are pretty simple. Does anybody have pointers to more complex examples? (Like, ones that use multiple rule matches, config file merging, etc. etc.) thanks, john. -- "A new scientific truth does not triumph by convincing its opponents and making them see the light, but rather because its opponents eventually die, and a new generation grows up that is familiar with it." - physicist Max Planck

2 1

Mounting a previously made sw raid partition
by Serge Wroclawski 14 Jun '06

14 Jun '06

Hello, I'm sorry if this is the wrong forum, but I'm having an issue with Autoyast that I can't explain. I have two disks, sda and sdb. I am partitioning them and making a software RAID, md0 and md1. md0 (which is /)'s entry in Autoyast says: <format config:type="boolean">true</format> and it works fine. For md1 (which is /var) I'd like it not to format the partition, so I set it to <format config:type="boolean">false</format> It goes through the installer, but when I boot into the OS, it doesn't mount the partition. If I log in and run "mount -a", it mounts fine. I've tried changing the false to true, and if I do that, everything works fine- so there's something involved in telling Autoyast not to format the raid unit that keeps it from mounting properly. Since running mount manually works, it would seem that the raid device is fine, but it never mounts during the normal proces. Looking at /etc/fstab shows a line for /var that's good- with default mount options and 1 for dump, and 2 for passno. I'm really unsure of what could be the problem, but since the difference starts with autoyast, I'm starting here. Any help would be appreciated, - Serge

2 3

RE: [suse-autoinstall] Network Installation nightmares
by fraser_bailey＠agilent.com 14 Jun '06

14 Jun '06

I found that I had to boot from the SP3 CD, once SP3 was in my depot. Booting from the base distro CD filaed, although I can't now remember what the error was. -----Original Message----- From: Francois Uldry [mailto:fu-laptop@hors-la-loi.ch] Sent: Tuesday, June 13, 2006 12:28 PM To: suse-autoinstall(a)suse.com Subject: [suse-autoinstall] Network Installation nightmares Hello, This is driving me nuts, I am trying to get a simple Network Installation Server (over NFS) to work. What I have done : - Through the control centre, on a SLES 9 SP3, used the control panel to create a SLES Network Installation Image as documented, used the SLES 9 original CDs as delivered by Novell. Added the SP 3 CDs to the tree. - Configured DHCP and TFTP to allow network boot. (that works perfectly fine) I have : /install/SLES9, which is the root of the exported filesystem. My problem : - Booting from the network, Yast cannot find package description. Has anyone had that much trouble just getting to a network installation server ? Any help, question, idea welcome ! Best regards, François -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

2 2

sgnature-handling
by Lars Stavholm 13 Jun '06

13 Jun '06

The signature-handling override for additional packages as specified in the autoyast doco section 4.5.4 doesn't work for me. I specify all four items (accept_unsigned_file, accept_file_without_checksum, accept_verification_failed, and accept_unknown_gpg_key) as "true" in my autoinst.xml in hope of avoiding the confirmation prompt. The confirmation prompt still appears. Anyone? R /Lars Stavholm

2 6

Custom CDs & autoinst.xml
by Don Coffin 13 Jun '06

13 Jun '06

I'm building custom installation CDs for SLES9, and I'd like them to autoinstall. I've created an autoinst.xml file per the docs at: http://www.suse.com/~ug/autoyast_doc/index.html In section 7.2.2 ("Booting From CD-ROM"), there's this tempting sentence: "It is also possible to create customized CD-ROMs to hold only the package you need in addition to the control file which also can be saved on the CD-ROM." I've got an "install server" environment setup already, although I don't plan on doing any network installs. Instead, I hope to create custom installation ISOs using cd-creator. My question is this: where do you place the autoinst.xml file in the installation tree for creating install ISOs? In the top level of the first SLES9 CD? Any pointers are greatly appreciated. Thanks much!

3 3

Re: [suse-autoinstall] adding online_update without /etc/youservers
by Darin Perusich 13 Jun '06

13 Jun '06

Stanislav Visnovsky wrote: >> when i used --type=YUM to add the source 'rug up' worked. > > But I was trying to point out to use --type=zypp ;-) ahh, i will give it a try shortly. >> the next question that i've been pondering over is what happens when SuSE >> 10.2 becomes available, am i going to have to remove this source and add >> another? > > --type=YUM does not sync the source to YaST. Thus, after the upgrade to 10.2, > YaST will not see the source, only ZMD/rug/zen-updater will. If you use > --type=zypp, the source will survive the upgrade. but i don't want this source to survive because it's specificly for 10.1 updates. >> this is what was nice about /etc/youservers, one only needed to >> provide the url to the base of the update tree. > > I'm sorry, I don't know how /etc/youservers worked :( cat /etc/youservers # This file is read by the YaST Online Update (YOU) to build the list of # servers used for getting updates. It may contain URLs to the base # directories where an update tree is located. # # Examples: # #ftp://ftp.suse.com/pub/suse #cd:/// #dir:///var/lib/YaST2/you/mnt http://my.local.repot/pub/suse YOU would then figure out where it needed to get the updates from. -- Darin Perusich Unix Systems Administrator Cognigen Corporation 395 Youngs Rd. Williamsville, NY 14221 darinper(a)cognigencorp.com

1 0

Re: [suse-autoinstall] adding online_update without /etc/youservers
by Darin Perusich 13 Jun '06

13 Jun '06

stano, Stanislav Visnovsky wrote: > > Rug type 'nu' is for Novell Updates exclusively. Use --type=zypp to > add your own YUM or SUSEtags sources. There is also a rug type 'yum', > but if you use 'zypp', the source will be propagated to YaST as well, > so you will get support in both YaST and ZMD stacks. when i used --type=YUM to add the source 'rug up' worked. the next question that i've been pondering over is what happens when SuSE 10.2 becomes available, am i going to have to remove this source and add another? this is what was nice about /etc/youservers, one only needed to provide the url to the base of the update tree. -- Darin Perusich Unix Systems Administrator Cognigen Corporation 395 Youngs Rd. Williamsville, NY 14221 darinper(a)cognigencorp.com

1 0

Network Installation nightmares
by Francois Uldry 13 Jun '06

13 Jun '06

Hello, This is driving me nuts, I am trying to get a simple Network Installation Server (over NFS) to work. What I have done : - Through the control centre, on a SLES 9 SP3, used the control panel to create a SLES Network Installation Image as documented, used the SLES 9 original CDs as delivered by Novell. Added the SP 3 CDs to the tree. - Configured DHCP and TFTP to allow network boot. (that works perfectly fine) I have : /install/SLES9, which is the root of the exported filesystem. My problem : - Booting from the network, Yast cannot find package description. Has anyone had that much trouble just getting to a network installation server ? Any help, question, idea welcome ! Best regards, François

1 0

RE: [suse-autoinstall] xmllint
by fraser_bailey＠agilent.com 13 Jun '06

13 Jun '06

Absolutely not. The DTDs have not been correct since I started using SLES about 3+ years ago. I suspect they aren't tested. I don't think yast always generates a valid autoyast xml file either. I've always had to edit mine until autoyast will read it back in again without error. -----Original Message----- From: Lars Stavholm [mailto:stava@telcotec.se] Sent: Tuesday, June 13, 2006 7:27 AM To: suse-autoinstall(a)suse.com Subject: [suse-autoinstall] xmllint For sake of completeness I try to validate my autoinst.xml on SuSE Linux 10.1 using "xmllint --noout --validate autoinst.xml". Loads of errors are displayed. But the basis of my autoinst.xml is produced by autoyast by means of cloning (Create Reference Profil). Q: Is this supposed to work? I.e. are the DTD's up-to-date? R /Lars -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

3 2

How can I configure a static ip address of network adpapter
by Zhan Xiang 13 Jun '06

13 Jun '06

Hi, I have a question about network configuration(maybe quite simple). I want to set a static ip address for the adpater which was used to install SLES10. But there maybe more than one adpaters in node, and I cannot confirm what adapter was used to do installation before installing. I even probably cannot know the MAC address of the installing adpater, since the node can be identified by its UUID, instead of a MAC address. If I use a chroot-script to set the ip address after installation, the ip address will be reset by autoyast after creating boot loader. So I'd like to add some information in autoyast profile to config them. Thank you. Walkinmud _________________________________________________________________ 享用世界上最大的电子邮件系统― MSN Hotmail。 http://www.hotmail.com

2 1

adding online_update without /etc/youservers
by Darin Perusich 12 Jun '06

12 Jun '06

now that YOU has been replaced with libzypp there is no longer the /etc/youservers for specifying your list of servers. is there an equivalent to the /etc/youservers file? -- Darin Perusich Unix Systems Administrator Cognigen Corporation 395 Youngs Rd. Williamsville, NY 14221 darinper(a)cognigencorp.com

3 4

additional rpms
by Lars Stavholm 11 Jun '06

11 Jun '06

I've added my own rpms following Uwe's instructions... create_update_source.sh myInstSrc cp my rpm's into myInstSrc/updates/suse/ cd myInstSrc/updates/suse create_package_descr cd setup/descr ls > directory.yast echo 'http://install/suse/...' > myInstSrc/add_on_products ...and it all works just great. Doing a manual (network) install, I can find my added rpms (using Search) and the select them to be installed as needed. Doing an automated install over the network, with my rpm's specified explicitly in the autoinst.xml file, my added rpm's gets installed as well. However, I wonder if there's any way one can add a selection like "MyAddons" using a "MyAddons.sel" file as was the case in previous versions of autoyast? Reason being that when doing a manual install, I would like to have a selection "MyAddons" already on the first page so the user doesn't have to worry about the exact rpm's that is contained in that selection (the way all the other selections work, like Min, Minimal+X11, etc.). Another reason is that this is what my users are used to from our SuSE 9.3 days. Anyone? R /Lars Stavholm

1 1

network configuration not applied
by Dejan Muhamedagic 09 Jun '06

09 Jun '06

Hello, After successful (more or less) auto installation, the resulting network configuration on the target hosts consists of what was defined for netdevice in linuxrc and not what was configured in the autoyast XML file. The configuration is definitely good and autoyast reports no errors. Is linuxrc wrong place to specify the network interface configuration for installation? Should one try with the info file? This is on SLES9 SP3. Boot is from a CD, but the sources and autoyast files are accessed over HTTP. BTW, I tried similar static network configuration, but with network boot using DHCP/PXE/tftp and the resulting network config was fine. Cheers, Dejan

2 2

Autoinstall 3ware-Supplied 3w-9xxx Module?
by Don Coffin 09 Jun '06

09 Jun '06

Howdy, all. I'm brand new to SuSE (specifically using SLES9 + SP3). I'm trying to create an autoinstall script for some custom SLES9+SP3 installation CDs. The problem I'm having is that the 3ware-supplied module is on a floppy disk and not in a packaged form. As I'm just learning how YAST2 and SuSE installation servers and such work, I haven't yet been able to figure out how to roll in the vendor-supplied driver to the "installation tree". Can anyone tell me how this is done? It looks like the module comes with a pre-install script, and I can't figure out where in the "installation tree" i need to place the script, either. Is it possible to create custom installation CDs that have 3rd party modules on them? I'm trying to put this together for a client who is very keen to keep using SLES9, otherwise I'd have them upgrade. Any help is greatly appreciated. Thanks!

2 1

encrypted partitions with 10.1 autoyast?
by Karsten Künne 08 Jun '06

08 Jun '06

Hi, I tried to use a profile from 9.3 in order to create an encrypted partition in 10.1 but it gave me a cryptic error (error code -3013, whatever that means) during installation and I ended up with an invalid partition table. Following is the piece from my profile: <partition> <crypt_fs config:type="boolean">true</crypt_fs> <crypt>twofish</crypt> <crypt_key>CRYPTOPASS</crypt_key> <filesystem config:type="symbol">xfs</filesystem> <format config:type="boolean">true</format> <loop_fs config:type="boolean">true</loop_fs> <mount>/home</mount> <partition_id config:type="integer">131</partition_id> <size>max</size> </partition> Do I have to do something different in 10.1? The online documentation doesn't mention encrypted partitions at all. Karsten.

2 2

sax2 --auto & keyboard set
by Stephen Mah 08 Jun '06

08 Jun '06

Hello, I'm new to autoyast. I've created a control file to automate sles9 sp3. Works great, except my keyboard character set is not coming up right. I'm not using autoyast to configure X11, but instead, running sax2 --auto in my post install script so it will auto detect my x11 config. All my keyboard keys are different, for example I type "/" and get "-" I've defined my keyboard as US. Any help would be appreciated. -regards steve

2 1

SELS 10 Network Installation Directory Layout?
by Pete Nishimoto 07 Jun '06

07 Jun '06

Hi, I'm trying to setup a PXE server to autoinstall SELS 10 and I'm running into a problem because I'm not sure how to layout the installation directories for the network install. I've setup the installation directories and links to sucessfully network install SELS 9 and I figured it would be pretty much the same. However, I've run into a problem. I've created a SELS 10 (Beta 9) installation directory much like a SLES 9 installation directory, with a sles10 directory (containing CD 1) and a core10 direcotry (containining the contents of CD 2-4 in the directories CD1-CD3). I'm able to install the first CD once I get a number of extra links (which wasn't in SELS 9), such as content.asc, content.key. I've found that I also need a link ./suse->sels10/CD1/suse to get the first CD to install. However, when the installation reboots (after installing CD1), and it start to go through the other packages, etc., it first looks for the media.2 file. Ok, so I put a link for media.2 to core10/CD1/media.2. But then it turns out that the installation procedure is trying to find the first package that I want to install (aalib) and it traverses the ./suse link to look for it. Since ./suse->sles10/CD1/suse, the aalib rpm is not there (it's in ./core10/CD1/suse). Of course, if I restart at this point and have ./suse->core01/CD1/suse, it can't find 'setup' and then the installation fails. So, I still need to know what's the right directory tree layout for SELS10. Is there any script/documentation/pointer to anything that can help me here? I'm stuck because of the problem with the ./suse link, and the installer wanting different contents for different times. I was thinking, does it have to do with the ./yast/instorder or ./yast/order files (are these still used?). Please help. I'm really close and just need a nudge in the right direction. I'll continue to search the mail lists, but a shortcut would be greatly appreciated. Pete

3 3

problems with ask
by Simon Crute 07 Jun '06

07 Jun '06

Hi, I'm trying to use the new Ask feature of autoyast, and prompt the user if they want their disk initialising. This is how the ask lines are looking in the /tmpautoinst.xml after the profiles have been merged etc. <ask-list config:type="list"> <listentry> <default>false</default> <path>partitioning,drive,initialize</path> <question>Do you want to remove all existing partitions ?</question> <stage>initial</stage> <title>Fdisk</title> <type>boolean</type> </listentry> </ask-list> However, I'm not seeing any popups during the install This is on SLED10-rc2 -- Simon Crute IS&T Bracknell Novell UK Ltd

2 6

adding net install source OSS-10.1
by Darin Perusich 07 Jun '06

07 Jun '06

hello all, has something changed when adding installation sources from 10.0 to 10.1 for network installation because it's not working as i expect it to? my directory structure layout is: /pub/suse/i386/SL-10.1 |-- inst-source |-- non-oss-inst-source |-- yast `-- instorder `-- order host:/pub/suse/i386/SL-10.1/inst-source/yast # cat instorder /non-oss-inst-source / host:/pub/suse/i386/SL-10.1/inst-source/yast # cat order /non-oss-inst-source /non-oss-inst-source / my setup for OSS-10.0 is nearly identical but it has 2 addition install sources, inst-source-extra and inst-source-java as appose to non-oss-inst-source. i've read thru Additional_YaST_Package_Repositories and Network_Installation_Source but nothing about this is mentioned so i'm a bit confused as to why this is not working. thanks -- Darin Perusich Unix Systems Administrator Cognigen Corporation 395 Youngs Rd. Williamsville, NY 14221 darinper(a)cognigencorp.com

2 5

Network installation of different service packs
by Jeremy Silver 05 Jun '06

05 Jun '06

I have an installation server for installation of SLES9 via http. Using the YaST Installation Server module I have added service packs 1-3 as they became available. They way the installation tree is setup the latest service pack gets installed with the an install source of http://x.x.x.x/autoyast/sles9/. However, for some systems I need to be able to install SP2 instead of SP3; I tried to specify the installation source as http://x.x.x.x/autoyast/sles9/SUSE-SLES-9-Service-Pack-Version-2/CD1/ as the installation source is listed for installing post-installation packages through YaST, but it does not work (drops me to the text install menu). Is there a way to do this just by specifying an alternate installation source? For reference, my pxe boot parameters are: label test kernel vmlinuz-SLES9-2 append initrd=initrd-SLES9-2.img ramdisk_size=65536 splash=silent showopts vga=788 install=http://x.x.x.x/autoyast/sles9 autoyast=http://x.x.x.x/autoyast/profile/test.xml loghost=x.x.x.x My sles9 tree is: -- Jeremy Silver jeremy(a)broadware.com This message (including any attachments) is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure, or distribution is prohibited. If you are not the intended recipient, please contact the sender and delete all copies.

1 0

How to save the list of installed packages?
by Pietro Mele 05 Jun '06

05 Jun '06

I installed SUSE 10.1 on a notebook (which does not have a floppy disk drive). Now I would like to save my system configuration and the list of packages I selected during the installation on a USB key (just in case I have to reinstall everything for any reason). During the installation process, I could find no indication about the possibility to make a backup of the list of packages I just selected. Can I do it now, once the system is up and running? How? Thank you, Pietro pietromele2(a)yahoo.com --------------------------------- Feel free to call! Free PC-to-PC calls. Low rates on PC-to-Phone. Get Yahoo! Messenger with Voice

3 2

Raid with hot spare using autoyast?
by Anton Altaparmakov 05 Jun '06

05 Jun '06

Hi, Using autoyast and trying to create a software raid device with a hot spare disk during installation. I have looked through the documentation, the list archives and through the partitioning.dtd and raid.dtd and am none the wiser, so am turning towards the list in the hope that someone can tell me if this is possible or not and if it is possible how to do it... Thanks a lot in advance! Best regards, Anton -- Anton Altaparmakov <aia21 at cam.ac.uk> (replace at with @) Unix Support, Computing Service, University of Cambridge, CB2 3QH, UK Linux NTFS maintainer / IRC: #ntfs on irc.freenode.net WWW: http://linux-ntfs.sf.net/ & http://www-stu.christs.cam.ac.uk/~aia21/

1 0

Re: [suse-autoinstall] autoyast does not remove old logical volumes
by Dejan Muhamedagic 02 Jun '06

02 Jun '06

On Fri, Jun 02, 2006 at 12:09:40PM +0100, Timothy Wright wrote: > If I understand the problem correctly, you may just need.... > > <drive> > ... > ... > <use>all</all> > </drive> It was there. What I did in the meantime is to put a pre-script which removes all LVs and the VG. The script did its thing, the installation failed again, because the partition table was not re-read, but after reboot autoinstallation worked fine. On subsequent autoinstalls, I have been getting the following messages: Jun 2 14:10:05 sapcl03 yast2[3750]: <1> [agent-storage] LvmAccess.cc(ExecuteLvmCmd):1621 lvm cmd execute:/sbin/vgchange -a y Jun 2 14:10:06 sapcl03 yast2[3750]: <1> [agent-storage] LvmAccess.cc(ExecuteLvmCmd):1650 lvm cmd output: /dev/sda1: open failed: No such device or address After pressing "Ignore" the installation, however, proceeded without problems. BTW, /dev/sda1 contains root fs and has nothing to do with LVM. Now, even though I removed that pre-script from the XML config, the installation always stops at this point with the "sda1: open failed" report. Sigh. Cheers, Dejan > > Cheers, > > Tim > > > Tim Wright > > Global Unix Engineering > Information Enterprise Services (IES) > Group Technology & Operations > > Deutsche Bank [/] - London > > Phone: +44 (0)20 754 70513 > Mobile: +44 (0)7765 894 194 > Email: timothy.wright(a)db.com > > > > Dejan Muhamedagic <dejanmm(a)fastmail.fm> > 02/06/2006 10:07 > Please respond to > Dejan Muhamedagic <dejanmm(a)fastmail.fm> > > > To > suse-autoinstall(a)suse.com > cc > > Subject > [suse-autoinstall] autoyast does not remove old logical volumes > > > > > > > Hi, > > Probably an old problem, but could not find a solution to it. > > Autoyast complains because it found logical volumes on the disk to > be configured: > > Jun 2 10:27:31 sapcl03 yast2[3736]: <3> [YCP] Report.ycp:391 Logical > volumes of group "rootvg" exist on unconfigured devices. Delete old volume > groups first or configure all devices containing physical volumes > belonging to this group. > > Subsequently, the installation aborts: > > Jun 2 10:27:31 sapcl03 yast2[3736]: <3> [YCP] Report.ycp:391 Error while > configuring partitions. Try again. > Jun 2 10:27:31 sapcl03 yast2[3736]: <3> [YCP] > clients/inst_autosetup.ycp:126 Aborting... > > Is there a way to tell autoyast to kill whatever LVs/VGs it finds > on the target disk? > > This was on the SLES9/SP3. I'll attach the relevant log and config. > > Cheers, > > Dejan > [attachment "disk.xml" deleted by Timothy Wright/DMGIT/DMG UK/DeuBa] -- > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > For additional commands, e-mail: suse-autoinstall-help(a)suse.com > > > > --- > > 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.

1 0

Avoid automatic partitioning in autoyast?
by Rainer Krienke 02 Jun '06

02 Jun '06

Hello, since suse10.1 (with its signed files, sigh) its quite hard to include additional RPMs in the installation process eg for doing postinstall tasks. Thats where I started trying autoyast for a basically standard installation with an additional postinstall script for each host I have. Basically this works fine. However I have one problem: The partitioning. I cloned an installed system and used this autoyast file (slightly modified) for installation. So it has sections for the partitions to be created. I also included a confirmation tag so that I have a way to change installation settings if I like before the installation begins. Since the cloned system was a IDE based one, the xml file has entries to create partions eg hda etc. Now when I start an autoyast installation on an IDE based system this works fine. But if I do the same on a SATA system the installation fails when creating the partioning plan because of the fact that there is no hda device but instead a sda. Actually I do not care about this failure since I would like to do this manually, but I cannot because of this error the complete installtion is stopped and I do not get to the point in yast where I could correct the partitioning and other installation parameters. Is there a way to tell autoyast not to take care of the partitioning because I am going to do this manually? This way I could use the same autoyast file for IDE and SATA and SCSI based systems. Else the only way I see is to use two autoyast files one for systems with hda devices and one for systems with sda devices. I tried an empy <partitioning config:type="list"></partitioning> section but this does not work either. autoyast still complains that partitioning did not work. Any other way? A second question is if there is a way to pause autoyast after the initial reboot, when in a standard yast installation the user is asked to do the printer, network, soundcard etc configuration. It would be nice (but not vital) if I could change things manually at this point too in the standard yast way. Any way to do this? 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 ---------------------------------------------------------------------------

4 5

autoyast does not remove old logical volumes
by Dejan Muhamedagic 02 Jun '06

02 Jun '06

Hi, Probably an old problem, but could not find a solution to it. Autoyast complains because it found logical volumes on the disk to be configured: Jun 2 10:27:31 sapcl03 yast2[3736]: <3> [YCP] Report.ycp:391 Logical volumes of group "rootvg" exist on unconfigured devices. Delete old volume groups first or configure all devices containing physical volumes belonging to this group. Subsequently, the installation aborts: Jun 2 10:27:31 sapcl03 yast2[3736]: <3> [YCP] Report.ycp:391 Error while configuring partitions. Try again. Jun 2 10:27:31 sapcl03 yast2[3736]: <3> [YCP] clients/inst_autosetup.ycp:126 Aborting... Is there a way to tell autoyast to kill whatever LVs/VGs it finds on the target disk? This was on the SLES9/SP3. I'll attach the relevant log and config. Cheers, Dejan

1 1