January 2006 - openSUSE Autoinstall - openSUSE Mailing Lists

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

Problem with AutoInstallRules.ycp and merge.xslt
by Luzian Scherrer 16 Mar '06

16 Mar '06

Hello, I think there is a typo in AutoInstallRules.ycp (version 1.34.4.9 that comes with SLES9 SP2): the xsltproc to merge classes is called with the following param there (line 733): --param dontmerge \"'package, addon'\" and I'm quite sure that it sould be: --param dontmerge \"'package'\" --param dontmerge2 \"'addon'\" The result of this typo is that neither <package> nor <addon> are correctly aggregated, which is the desired effect I believe and I also hope. Quick demonstration: idhpb02:/ # cat /tmp/a.xml <?xml version="1.0"?> <!DOCTYPE profile SYSTEM "/usr/share/autoinstall/dtd/profile.dtd"> <profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http:// www.suse.com/1.0/configns"> <install> <software> <addons config:type="list"> <addon>addon-A</addon> </addons> <packages config:type="list"> <package>package-A</package> </packages> </software> </install> </profile> idhpb02:/ # cat /tmp/b.xml <?xml version="1.0"?> <!DOCTYPE profile SYSTEM "/usr/share/autoinstall/dtd/profile.dtd"> <profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http:// www.suse.com/1.0/configns"> <install> <software> <addons config:type="list"> <addon>addon-B</addon> </addons> <packages config:type="list"> <package>package-B</package> </packages> </software> </install> </profile> Calling it the wrong way: idhpb02:/ # xsltproc --novalid --param replace "'false'" --param dontmerge "'package, addon'" --param with "'/tmp/b.xml'" /usr/share/ autoinstall/xslt/merge.xslt /tmp/a.xml <?xml version="1.0"?> <ns1:profile xmlns:ns1="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns" xmlns="http:// www.suse.com/1.0/yast2ns"> <ns1:install> <ns1:software> <ns1:addons config:type="list"> <ns1:addon>addon-B</ns1:addon> </ns1:addons> <ns1:packages config:type="list"> <ns1:package>package-B</ns1:package> </ns1:packages> </ns1:software> </ns1:install> </ns1:profile> Calling it the (as I think) right way: idhpb02:/ # xsltproc --novalid --param replace "'false'" --param dontmerge "'package'" --param dontmerge2 "'addon'" --param with "'/ tmp/b.xml'" /usr/share/autoinstall/xslt/merge.xslt /tmp/a.xml <?xml version="1.0"?> <ns1:profile xmlns:ns1="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns" xmlns="http:// www.suse.com/1.0/yast2ns"> <ns1:install> <ns1:software> <ns1:addons config:type="list"> <ns1:addon>addon-A</ns1:addon><ns1:addon>addon-B</ns1:addon> </ns1:addons> <ns1:packages config:type="list"> <ns1:package>package-A</ns1:package><ns1:package>package-B</ ns1:package> </ns1:packages> </ns1:software> </ns1:install> </ns1:profile> Could this be fixed? Or is it already known and possibly a workaround in existance? Thanks in advance, -Luzian

4 6

How to modify the install server layout to include SP3 (without using YaST2)?
by Christian Goetze 30 Jan '06

30 Jan '06

Anyone have a link to docs or an explanation of what I need to do to deploy SP3 onto an existing install server layout, assuming I need to do this by hand, and cannot use YaST2 (since the server is a different platform altogether)? I assume that simply replacing CD1 with the SP3 CD1 is incorrect... -- cg

2 1

RE: [suse-autoinstall] Auto detection of sound card in 10.0 ?
by Frank van Tol 27 Jan '06

27 Jan '06

narrowed the issue down to: alsasound is not started on boot. If I do that manually, sound works for root as the permssions require a normal user to be part of the audio group. I set the permissions on /dev/snd/* to a+rw with a script as I have 22000 potential users that I can not all add to the audio group. -----Original Message----- From: Uwe Gansert [mailto:ug@suse.de] Sent: donderdag 26 januari 2006 15:45 To: suse-autoinstall(a)suse.com Subject: Re: [suse-autoinstall] Auto detection of sound card in 10.0 ? On Thursday 26 January 2006 10:50, Frank van Tol wrote: > I can not get the autodetect working with suse 10.0 to produce sound > in gnome/kde. seems to be hardware related because it's working here. -- 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 -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

JFYI SL 10.1 beta2 is ready
by Uwe Gansert 27 Jan '06

27 Jan '06

Hi, this is just for your information. SUSE Linux 10.1 beta2 is ready. Feel free to download it: http://www.opensuse.org/Development_Version A list of changes in autoyast can be found here: http://www.suse.de/~ug/autoyast_changes.html The last three changes: * one can clone a system more than one time now with the UI * proof readed texts for the UI (thanx Rebecca) * pre, chroot and post scripts can show feedback now in a popup will be available in beta3, not in the current beta2 -- 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 0

RE: [suse-autoinstall] SPAM: Partioning problems, SLES9 RC5.....SOLVED!
by Schumacher, Gordon 26 Jan '06

26 Jan '06

# From: Colin Topliss [mailto:Colin.Topliss@three.co.uk] # Sent: Thursday, January 26, 2006 9:24 AM # To: Uwe Gansert; suse-autoinstall(a)suse.com # Subject: RE: [suse-autoinstall] SPAM: Partioning problems, SLES9 RC5.....SOLVED! # # Hi Uwe, # # It was a cut'n'paste problem..... # # However, I had a blinding inspiration....... # # I was playing with some rules a while ago, and I had two files still in # the rules directory. The install appears to pick these files up (not # sure which one, had one called cciss_36.xml and one called rules.xml). # Moved them out, tried again and it worked! # # These rules were there from testing with SuSE 9.2 (which never did show # this particular problem). See the documentation regarding "rules.xml": http://forgeftp.novell.com///yast/doc/SL10.0/autoinstall/rulesandclass.html

1 0

RE: [suse-autoinstall] SPAM: Partioning problems, SLES9 RC5.....SOLVED!
by Colin Topliss 26 Jan '06

26 Jan '06

Hi Uwe, It was a cut'n'paste problem..... However, I had a blinding inspiration....... I was playing with some rules a while ago, and I had two files still in the rules directory. The install appears to pick these files up (not sure which one, had one called cciss_36.xml and one called rules.xml). Moved them out, tried again and it worked! These rules were there from testing with SuSE 9.2 (which never did show this particular problem). Thanks for taking the time to look at this. Colin. -----Original Message----- From: Uwe Gansert [mailto:ug@suse.de] Sent: 26 January 2006 15:48 To: suse-autoinstall(a)suse.com Subject: Re: [suse-autoinstall] SPAM: Partioning problems, SLES9 RC5..... On Thursday 26 January 2006 16:39, Colin Topliss wrote: > The partition part is as follows: > > <partitioning config:type="list"> > <drive> > <device>/dev/cciss/c0d0</device> > <partitions config:type="list"> > <partition> > <filesystem config:type="symbol">reiser</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>300mb</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">2</partition_nr> > <size>4gb</size> > </partition> > <partition> > <partition_id config:type="integer">15</partition_id> > <partition_nr config:type="integer">3</partition_nr> > <size>max</size> > </partition> drop the partition above from the profile. Don't configure the extended partition. > <partition> > <filesystem config:type="symbol">reiser</filesystem> > <format config:type="boolean">true</format> > <mount>/</mount> > <partition_id config:type="integer">131</partition_id> > <partition_nr config:type="integer">5</partition_nr> > <size>1gb</size> > </partition> > <partition> > <filesystem config:type="symbol">reiser</filesystem> > <format config:type="boolean">true</format> > <mount>/home</mount> > <partition_id config:type="integer">131</partition_id> > <partition_nr config:type="integer">6</partition_nr> > <size>300mb</size> > </partition> > <partition> > <partition> why two times "partiton"? copy and paste bug? > Can anyone see anything obvious I'm missing? that's all I saw by quickly browsing your data. Fix that and if that does not help, post your complete profile. -- 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 -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com ________________________________________________________________________ This e-mail message (including any attachment) is intended only for the personal use of the recipient(s) named above. This message is confidential and may be legally privileged. If you are not an intended recipient, you may not review, copy or distribute this message. If you have received this communication in error, please notify us immediately by e-mail and delete the original message. Any views or opinions expressed in this message are those of the author only. Furthermore, this message (including any attachment) does not create any legally binding rights or obligations whatsoever, which may only be created by the exchange of hard copy documents signed by a duly authorised representative of Hutchison 3G UK Limited.. ________________________________________________________________________

1 0

SPAM: Partioning problems, SLES9 RC5.....
by Colin Topliss 26 Jan '06

26 Jan '06

Hi all, I have a problem with partitioning under SLES9, x86_64 (on a DL380-G4). I'm using a SLES9 RC5 disk to boot from, then I am attempting an install via an http server. The install fails when trying to set up the partition plan (an error occurred while trying to create the partitioning plans. Make sure the control file has the correct syntax and values) - trouble is it doesn't appear to indicate why (or else I'm not looking for the info in the correct place). I certainly couldn't see anything obvious in the y2log. The partition part is as follows: <partitioning config:type="list"> <drive> <device>/dev/cciss/c0d0</device> <partitions config:type="list"> <partition> <filesystem config:type="symbol">reiser</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>300mb</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">2</partition_nr> <size>4gb</size> </partition> <partition> <partition_id config:type="integer">15</partition_id> <partition_nr config:type="integer">3</partition_nr> <size>max</size> </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <mount>/</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">5</partition_nr> <size>1gb</size> </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <mount>/home</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">6</partition_nr> <size>300mb</size> </partition> <partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <mount>/opt</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">7</partition_nr> <size>2gb</size> </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <mount>/tmp</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">8</partition_nr> <size>1gb</size> </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <mount>/usr</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">9</partition_nr> <size>3gb</size> </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <mount>/var</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">10</partition_nr> <size>2gb</size> </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <mount>/var/opt</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">11</partition_nr> <size>1gb</size> </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <mount>/var/log</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">12</partition_nr> <size>1gb</size> </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <mount>/var/tmp</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">13</partition_nr> <size>1gb</size> </partition> </partitions> <use>all</use> </drive> </partitioning> I also tried to use a profile created by yast autoyast - but I get the same error. I even tried a minimal partition definition - and got the same error. I tried different combinations of syntax from the AutoYaST guides with no success. No matter what I try I get this partition error. Its driving me crazy! Xmllint isn't showing up any problems with the profile in general. Can anyone see anything obvious I'm missing? Or has anyone got a working example? If not, I'm facing the possibility of an error elsewhere in the (rather long) config :-( Thanks. Colin Topliss ________________________________________________________________________ This e-mail message (including any attachment) is intended only for the personal use of the recipient(s) named above. This message is confidential and may be legally privileged. If you are not an intended recipient, you may not review, copy or distribute this message. If you have received this communication in error, please notify us immediately by e-mail and delete the original message. Any views or opinions expressed in this message are those of the author only. Furthermore, this message (including any attachment) does not create any legally binding rights or obligations whatsoever, which may only be created by the exchange of hard copy documents signed by a duly authorised representative of Hutchison 3G UK Limited.. ________________________________________________________________________

2 1

Problem: switching to text based screen
by Frank van Tol 26 Jan '06

26 Jan '06

After I made some changes, not related at all to display etc, autoyast starts of with the normal graphical install, showing the slides etc but after the reboot, phase 2 is suddenly in text mode. It still installs as before but I can't figure out why it changed it's behaviour ? What determines which installer UI you get ? Happy to attach autoyast.xml if that helps.. Best regards Frank

2 1

Auto detection of sound card in 10.0 ?
by Frank van Tol 26 Jan '06

26 Jan '06

I can not get the autodetect working with suse 10.0 to produce sound in gnome/kde. Tried this without success. <configure> ... <sound> <autoinstall config:type="boolean">true</autoinstall> <configure_detected config:type="boolean">true</configure_detected> </sound> ... </configure> However, Yast sound add and yast sound playtest work just fine.

2 1

empty raid
by Dejan Muhamedagic 24 Jan '06

24 Jan '06

Hello, This is a simple disk configuration, two hard disks with two partitions each, the first partition containing the root fs and the two second partitions reserved for the sw raid. The installation stops with this message: echo y | /sbin/pvcreate -ff -M2 /dev/md0 /dev/md0: Couldn't find device. because autoyast tries to create the raid with no partitions. The autoyast found both /dev/sda2 and /dev/sdb2 as raid members, but then didn't put them in the /etc/raidtab: Jan 20 15:21:46 sisyphus yast2[2269]: <1> [YCP] partitioning/raid_lib.ycp:122 dev:/dev/md0 type:raid1 Jan 20 15:21:46 sisyphus yast2[2269]: <1> [YCP] partitioning/raid_lib.ycp:126 partition_list:[$["create":true, "device":"/dev/sda2", "devkey":"2//dev/sda", "format":false, "fs_options":$[], "fsid":253, "fstype":"Linux RAID", "maindev":"/dev/sda", "mount":"", "nr":2, "raid_name":"/dev/md0", "raid_type":"raid1", "region":[66, 2146], "size_byte":17650352128, "size_str":" 16.4 GB", "type":`primary, "used_fs":`unknown], $["create":true, "device":"/dev/sdb2", "devkey":"2//dev/sdb", "format":false, "fs_options":$[], "fsid":253, "fstype":"Linux RAID", "maindev":"/dev/sdb", "mount":"", "nr":2, "raid_name":"/dev/md0", "raid_type":"raid1", "region":[66, 2146], "size_byte":17650352128, "size_str":" 16.4 GB", "type":`primary, "used_fs":`unknown]] Jan 20 15:21:59 sisyphus yast2[2269]: <1> [YCP] partitioning/raid_lib.ycp:855 RAID_: # autogenerated /etc/raidtab by YaST2 raiddev /dev/md0 raid-level 1 nr-raid-disks 0 nr-spare-disks 0 persistent-superblock 1 chunk-size 32 Jan 20 15:21:59 sisyphus yast2[2269]: <1> [YCP] partitioning/raid_lib.ycp:875 created raids: [0] Jan 20 15:22:04 sisyphus yast2[2269]: <1> [YCP] partitioning/raid_lib.ycp:905 success for: /sbin/mkraid -c /etc/raidtab --really-force /dev/md0 The system is SLES9 with SP3 and here's the relevant xml part: <partitioning config:type="list"> <drive> <device>/dev/sda</device> <initialize config:type="boolean">true</initialize> <partitions config:type="list"> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <mount>/</mount> <partition_id config:type="integer">131</partition_id> <partition_type>primary</partition_type> <size>512M</size> </partition> <partition> <format config:type="boolean">false</format> <partition_id config:type="integer">253</partition_id> <partition_type>primary</partition_type> <raid_name>/dev/md0</raid_name> <raid_type>raid1</raid_type> <size>max</size> </partition> </partitions> <use>all</use> </drive> <drive> <device>/dev/sdb</device> <initialize config:type="boolean">true</initialize> <partitions config:type="list"> <partition> <crypt_fs config:type="boolean">false</crypt_fs> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <mount>/rootcopy</mount> <partition_id config:type="integer">131</partition_id> <partition_type>primary</partition_type> <size>512M</size> </partition> <partition> <format config:type="boolean">false</format> <partition_id config:type="integer">253</partition_id> <partition_type>primary</partition_type> <raid_name>/dev/md0</raid_name> <raid_type>raid1</raid_type> <size>max</size> </partition> </partitions> <use>all</use> </drive> <drive> <device>/dev/md</device> <partitions config:type="list"> <partition> <format config:type="boolean">false</format> <lvm_group>rootvg</lvm_group> <partition_id config:type="integer">142</partition_id> <partition_nr config:type="integer">0</partition_nr> <raid_options> <chunk_size>32</chunk_size> <parity_algorithm>left-asymmetric</parity_algorithm> <raid_type>raid1</raid_type> </raid_options> </partition> </partitions> <use>all</use> </drive> BTW, the partitioning is sourced using <classes>. Thanks. Dejan

2 2

Re: AW: [suse-autoinstall] Re: Login incorrect
by Michael Schulz 19 Jan '06

19 Jan '06

Thanks for the Answer, is there no way that I can use a Autoyast installation with the password from the original System? Regards Am Thursday 19 January 2006 12:53 schrieben Sie: > Hi, > > the reference profile uses the crypted passwords of your reference system, > but does not set the flag for encryption. Try using your crypted password > from your reference system. > > Mit freundlichen Grüßen / kind regards > SoftService GmbH > > Holger Meyers > Consulting > > Tel 0211 977 09 69 > Fax 0211 977 09 27 > Mobil 0172 2740969 > http://www.softservice.de > > > ________________________________ > > Von: Michael Schulz [mailto:problems@gmx.net] > Gesendet: Do 19.01.2006 12:35 > An: suse-autoinstall(a)suse.com > Betreff: [suse-autoinstall] Re: Login incorrect > > > > Hi List, > > i have the following problem: > > I created with the "Reference Profile Tool" an xml file. > All works fine but after the installation I can't login with > both automatic created users. What can be the reasons > for this. > > I use SLES9 without any SP. > > Regards > > -- > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > For additional commands, e-mail: suse-autoinstall-help(a)suse.com

2 4

Re: Login incorrect
by Michael Schulz 19 Jan '06

19 Jan '06

Hi List, i have the following problem: I created with the "Reference Profile Tool" an xml file. All works fine but after the installation I can't login with both automatic created users. What can be the reasons for this. I use SLES9 without any SP. Regards

1 0

device.map issue
by Karl Merritts 17 Jan '06

17 Jan '06

I am currently seeing an issue with specifying my device.map inside of the bootloader menu for autoyast. Each time I type in the device (/dev/sda) and hit save, exit autoyast and reopen the autoinst.xml file. The device is always gone once I reopen the file. Save as has also been tried. I am still using SuSE 9.2 and the bug has probably been fixed in later versions. All I am looking is what the xml block will look like inside of the file. Attached is my configuration file. -Karl

1 0

Autoyast SuSE 10.0 erro.
by Rodrigo_Albert_Fedosi 17 Jan '06

17 Jan '06

Hi, Already there is solution for the bug ? OpenSuSE 10.0 error in autoyast: > Error > Storage modification failed. > System error code was -6002. > Failure occured during following action: > Creating software RAID /dev/md0." Att. Rodrigo Albert Fedosi Suporte TI Tel: (31) 3419-8854 Fax: (31) 3419-8803 rodrigo(a)bhz.jamef.com.br www.jamef.com.br

2 1

AutoYast rules.xml and <profile> location?
by Chris Bradshaw 16 Jan '06

16 Jan '06

Hi.... I was just wondering if someone could tell me if it is possible to have something like the following for a rules.xml file: <?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> <custom1> <script><![CDATA[ #!/bin/sh wget -q -O /tmp/dynamic.xml http://autoyast/cgi-bin/ay_gen.pl?hostname=${hostname}\&hostnetmask=${Netma… echo -n "modified" ]]></script> <match>*</match> <match_type>exact</match_type> </custom1> <result> <profile>/tmp/dynamic.xml</profile> <continue config:type="boolean">true</continue> </result> </rule> </rules> </autoinstall> Specifically I am retrieving the rules.xml file via http as part of an autoyast suse install and I want to use wget in the rules.xml file to retrieve a dynamic control file which I save in /tmp/dynamic.xml and then in the <result><profile> section I would like my rules.xml file to point at this local file. The wget works and does download the file correctly, but the <profile> section doesn't seem to let me refer to a local file.....it keeps trying to wget the file from the same URL where the rules/rules.xml file resides. I have tried just specifying /tmp/dynamic.xml (as shown above) and also file:///tmp/dynamic.xml but neither of these work. Is there any way I can get this to work? Thanx in advance. Chris Bradshaw.

2 7

NLD and SP2
by Rob Thompson 16 Jan '06

16 Jan '06

Hello, I am setting up an Autoyast server to deploy Novell Linux Desktop and I am doing this using iso files. The autoyast server allows me to specify the NLD files fine, but it never asks for the SP2 iso's? I check the box to specify additional cd's but I cannot get Autoyast to prompt for the SP2 files? Anyone know how to solve this? Thanks, Rob

1 0

Missing system users
by Frank Steiner 16 Jan '06

16 Jan '06

Hi, I'm running autoyast on opensuse 10.0.42 (10.1 alpha 4). The installation works fine, but most of the system users are missing although the rpms got installed, e.g.: /root/tmp# rpm -q dhcpcd dhcpcd-1.3.22pl4-212 /root/tmp# grep dhcp /etc/passwd /root/tmp# /root/tmp# rpm -q at at-3.1.8-909 /root/tmp# grep ^at /etc/passwd /root/tmp# In y2logRPM I find entries like this: 2006-01-10 17:58:37 at-3.1.8-909.i586.rpm installed ok Additional rpm output: warning: user at does not exist - using root warning: group at does not exist - using root warning: user at does not exist - using root warning: group at does not exist - using root warning: user at does not exist - using root warning: group at does not exist - using root I can see the reason in y2logRPM: pwdutils are installed quite late, after e.g. at and dhcpd. But I don't understand why: the packages file in my SuSE/setup/descr/ directory has this entry for at: =Pkg: at 3.1.8 909 x86_64 +Req: /usr/sbin/useradd /usr/sbin/groupadd fillup coreutils ... So, Yast should install pwdutils first! Any ideas? cu, Frank -- Dipl.-Inform. Frank Steiner Web: http://www.bio.ifi.lmu.de/~steiner/ Lehrstuhl f. Bioinformatik Mail: http://www.bio.ifi.lmu.de/~steiner/m/ LMU, Amalienstr. 17 Phone: +49 89 2180-4049 80333 Muenchen, Germany Fax: +49 89 2180-99-4049 * Rekursion kann man erst verstehen, wenn man Rekursion verstanden hat. *

2 2

software raid initrd fstab problem
by Paul Ingram 12 Jan '06

12 Jan '06

Hi, I am in the process of installing SuSe 10 on a bunch of amd64 boxes, each with 2 sata drives and I wish to configure them as s/w raid 1, mirrored with a /dev/md device for each partition of /boot, / swap and /home. I can install ok onto a single sata device but the s/w raid is being a little more troublesome. After trying to find an optimal way of setting up the autoinstall file, I now have a hybrid file. I started by running an autogeneration script from my install server, as it is the same config, but then I found that the s/w raid was not being set up correctly. As being reported on the 'net the s/w raid support is sparse in autoyast. I managed to manipulate the file with regards to disk partitioning and it seems to have got further. Now I have the s/w raid building correctly I think but at the end of cd1 I get an error 'mkinitrd line 2880 /etc/fstab no such file or directory, no / mountpoint in /etc/fstab' I suspect it may be a grub problem because the setup screen isn't exactly the same as the server but I don't know how to make it the same. I can post my autoinstall file here but it is quite long. ?? Any advice would be gratefully received. Paul -- Paul Ingram Technical Support WorkstationsUK Ltd, Amersam, England www.workstationsuk.co.uk Tel. 01494 724 498 Fax. 01494 433 375

1 0

Changing installation-kernel
by Thomas Rensing 12 Jan '06

12 Jan '06

Hi! I am trying to install Suse 10.0 using "AutoYast". Everything works fine, but since i have to install it on an FSC AMD64 PC with SIS761 chipset, autoinstallation does no longer work. the problem is, that the kernel-version loaded into ramdisk does not support this chipset (especially the sata-chipset), since it is to old. That's why i have got the following question: Is it possible to change the kernel loaded into ramdisk by the installation-routine into a newer one? I think since Kernel 2.6.13 it should recognize the SIS-chipset. I googled a lot but found noting regarding this problem... I installed SuSE 10.1 alpha just for testing and everything worked fine. Thanks a lot, Thomas Rensing

1 0

SLES and LVM error
by Rob Thompson 11 Jan '06

11 Jan '06

Hi, I am trying to use autoyast and format 5 LVM partitions during install (dont ask ;-). The control file is read correctly, and when I look in the Partitioning portion of the YAST installer everything looks proper - but when I choose accept and autoyast begins formating the drives I get the following error: LVM ERROR echo y|/sbin/pvcreate -ff -M2 /dev/sda5 /dev/sda5: Couldn't find device. Here is my XML file: Thanks, Rob </general> <partitioning config:type="list"> <drive> <device>/dev/sda</device> <initialize config:type="boolean">true</initialize> <partitions config:type="list"> <partition> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <loop_fs config:type="boolean">false</loop_fs> <mount>/boot</mount> <partition_id config:type="integer">131</partition_id> <partition_type>primary</partition_type> <size>+100MB</size> </partition> <partition> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <loop_fs config:type="boolean">false</loop_fs> <mount>swap</mount> <partition_id config:type="integer">131</partition_id> <partition_type>primary</partition_type> <size>+16GB</size> </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <loop_fs config:type="boolean">false</loop_fs> <mount>/</mount> <partition_id config:type="integer">131</partition_id> <partition_type>primary</partition_type> <size>+10GB</size> </partition> <partition> <format config:type="boolean">false</format> <loop_fs config:type="boolean">false</loop_fs> <partition_id config:type="integer">130</partition_id> <partition_type>extended</partition_type> <size>max</size> </partition> <partition> <lvm_group>VG00</lvm_group> <loop_fs config:type="boolean">false</loop_fs> <partition_id config:type="integer">142</partition_id> <size>+35GB</size> </partition> </partitions> </drive> <drive> <device>/dev/VG00</device> <is_lvm_vg config:type="boolean">true</is_lvm_vg> <partitions config:type="list"> <partition> <mount>/home</mount> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <lv_name>lvm01</lv_name> <lvm2 config:type="boolean">true</lvm2> <size>+10GB</size> </partition> <partition> <mount>/tmp</mount> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <lv_name>lvm02</lv_name> <lvm2 config:type="boolean">true</lvm2> <size>+5GB</size> </partition> <partition> <mount>/var</mount> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <lv_name>lvm03</lv_name> <lvm2 config:type="boolean">true</lvm2> <size>+5GB</size> </partition> <partition> <mount>/usr</mount> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <lv_name>lvm04</lv_name> <lvm2 config:type="boolean">true</lvm2> <size>+5GB</size> </partition> <partition> <mount>/opt</mount> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <lv_name>lvm05</lv_name> <lvm2 config:type="boolean">true</lvm2> <size>+10GB</size> </partition> </partitions> <use>all</use> <pesize>4M</pesize> </drive> </partitioning> <software>

2 3

software raid through autoyast
by Reynold L Demarco 11 Jan '06

11 Jan '06

Has anyone been able to successfully setup a software raid using autoyast? I've seen a bunch of posts with questions on getting it working, but I haven't seen any successful responses. Specifically I'm trying to mirror /boot, /, and swap without using LVM. I want to keep it simple before I get advanced. It parses my xml file fine, it just can't configure my software RAID. Below is my parititioning section. I've tried many variations on it with no success. Any help is appreciated. My typical error is... "Could not format /dev/md2. You can continue if you know what you are doing, but, to prevent damage your file systems, it is safer to cancel and reboot." <partitioning config:type="list"> <drive> <device>/dev/hde</device> <partitions config:type="list"> <partition> <format config:type="boolean">false</format> <partition_id config:type="integer">253</partition_id> <raid_name>/dev/md0</raid_name> <raid_type>raid1</raid_type> <size>512M</size> </partition> <partition> <format config:type="boolean">false</format> <partition_id config:type="integer">253</partition_id> <raid_name>/dev/md1</raid_name> <raid_type>raid1</raid_type> <size>2g</size> </partition> <partition> <format config:type="boolean">false</format> <partition_id config:type="integer">253</partition_id> <raid_name>/dev/md2</raid_name> <raid_type>raid1</raid_type> <size>200g</size> </partition> </partitions> <use>all</use> </drive> <drive> <device>/dev/hdg</device> <partitions config:type="list"> <partition> <format config:type="boolean">false</format> <partition_id config:type="integer">253</partition_id> <raid_name>/dev/md0</raid_name> <raid_type>raid1</raid_type> <size>512M</size> </partition> <partition> <format config:type="boolean">false</format> <partition_id config:type="integer">253</partition_id> <raid_name>/dev/md1</raid_name> <raid_type>raid1</raid_type> <size>2g</size> </partition> <partition> <format config:type="boolean">false</format> <partition_id config:type="integer">253</partition_id> <raid_name>/dev/md2</raid_name> <raid_type>raid1</raid_type> <size>200g</size> </partition> </partitions> <use>all</use> </drive> <drive> <device>/dev/md</device> <partitions config:type="list"> <partition> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <mount>/boot</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">0</partition_nr> <raid_options> <chunk_size>4</chunk_size> <parity_algorithm>left-asymmetric</parity_algorithm> <raid_type>raid1</raid_type> </raid_options> </partition> </partitions> <use>all</use> </drive> <drive> <device>/dev/md</device> <partitions config:type="list"> <partition> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">false</format> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">1</partition_nr> <raid_options> <chunk_size>4</chunk_size> <parity_algorithm>left-asymmetric</parity_algorithm> <raid_type>raid1</raid_type> </raid_options> </partition> </partitions> <use>all</use> </drive> <drive> <device>/dev/md</device> <partitions config:type="list"> <partition> <filesystem config:type="symbol">reiserfs</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> <raid_options> <chunk_size>4</chunk_size> <parity_algorithm>left-asymmetric</parity_algorithm> <raid_type>raid1</raid_type> </raid_options> </partition> </partitions> <use>all</use> </drive> </partitioning> -- Reynold De Marco Scientific Computing Services

4 5

A better error message...
by Frank Steiner 10 Jan '06

10 Jan '06

Hi, if there's any parse error in rules.xml, autoyast just complains that no profile could be found. It would be very very helpful, if autoyast could tell the reason for that, i.e. "Parse error in rules.xml. Could not find any profile" or sth. I've gone mad searching for this cause :-) cu, Frank -- Dipl.-Inform. Frank Steiner Web: http://www.bio.ifi.lmu.de/~steiner/ Lehrstuhl f. Bioinformatik Mail: http://www.bio.ifi.lmu.de/~steiner/m/ LMU, Amalienstr. 17 Phone: +49 89 2180-4049 80333 Muenchen, Germany Fax: +49 89 2180-99-4049 * Rekursion kann man erst verstehen, wenn man Rekursion verstanden hat. *

3 3

profile file not being accepted
by joe.richter＠gmx.net 10 Jan '06

10 Jan '06

hello everyone, the exact error message is "A profile for this machine could not be found or retrieved. Check that you entered the correct location on the command line and try again. Because of this error, you can only enter a URL to a profile and not a directory. If you are using rules or host name-based control files, restart the installation process and make sure the control files are accessible." I generated a config file using yast autoyast within NLD9 (SP2). DTD check says it's okay. And yast is retrieving the file upon its installation attempt: [5] Tue 10Jan06 10:34:15 - (000009) Connected to x.x.x.77 (Local address x.x.x.10) [5] Tue 10Jan06 10:34:15 - (000009) ANONYMOUS logged in, password: CURL_BY_DANIEL(a)HAXX.SE [3] Tue 10Jan06 10:34:15 - (000009) Sending file f:\ftproot\nld9\xml\autoyast.xml [3] Tue 10Jan06 10:34:15 - (000009) Sent file f:\ftproot\nld9\xml\autoyast.xml successfully (338 kB/sec - 4501 Bytes) [5] Tue 10Jan06 10:34:15 - (000009) Closing connection for user ANONYMOUS (00:00:00 connected) Still I get the error message quoted above.. so what's wrong? my very basic 'just getting started' profile file: <?xml version="1.0"?> <!DOCTYPE profile SYSTEM "/usr/share/autoinstall/dtd/profile.dtd"> <profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <configure> <networking> <dns> <dhcp_hostname config:type="boolean">true</dhcp_hostname> <dhcp_resolv config:type="boolean">true</dhcp_resolv> </dns> <interfaces config:type="list"> <interface> <bootproto>dhcp</bootproto> <device>eth0</device> <startmode>onboot</startmode> </interface> </interfaces> <modules config:type="list"> <module_entry> <device>static-0</device> <module></module> <options></options> </module_entry> </modules> <routing> <ip_forward config:type="boolean">false</ip_forward> </routing> </networking> </configure> <install> <bootloader> <activate config:type="boolean">false</activate> <global config:type="list"/> <loader_device></loader_device> <loader_type>grub</loader_type> <location>mbr</location> <repl_mbr config:type="boolean">false</repl_mbr> <sections config:type="list"/> </bootloader> <partitioning config:type="list"> <drive> <device>/dev/hda</device> <initialize config:type="boolean">false</initialize> <partitions config:type="list"> <partition> <crypt>twofish256</crypt> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <loop_fs config:type="boolean">false</loop_fs> <mount>swap</mount> <partition_id config:type="integer">130</partition_id> <partition_type>primary</partition_type> <size>auto</size> </partition> <partition> <crypt>twofish256</crypt> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <loop_fs config:type="boolean">false</loop_fs> <mount>/</mount> <partition_id config:type="integer">131</partition_id> <partition_type>primary</partition_type> <size>max</size> </partition> </partitions> <use>all</use> </drive> </partitioning> <software> <addons config:type="list"> <addon>Novell-Software</addon> <addon>SuSE-Documentation</addon> <addon>Office</addon> <addon>Gnome_Desktop</addon> </addons> <base>Gnome</base> </software> </install> </profile> best regards /JR. -- 10 GB Mailbox, 100 FreeSMS/Monat http://www.gmx.net/de/go/topmail +++ GMX - die erste Adresse f�r Mail, Message, More +++

2 1

LVM and autoyast
by LDB 10 Jan '06

10 Jan '06

If you configure autoyast to produce LVM partitions, is there anything in addition that must be done in addition to what is in autoyast.xml. For example, a script or something that must be executed during the post-installation phase. I ask because my autoyast installation completed without any intervention but LVM did not quite make it when I logged in. Any suggestions would be great .. Thanks, LDB

2 3

LVM and autoyast on SuSE 10.0
by LDB 08 Jan '06

08 Jan '06

Below you find a portion of my autoyast.xml file specifying an LVM setup. When the autoinstallation gets to this point and says, "Error: A logical volume with the requested size could not be created." What am I doing wrong? <partitioning> ... <drive> <device>/dev/sdb</device> <partitions config:type="list"> <partition> <lvm_group>apps</lvm_group> <partition_type>primary</partition_type> <size>max</size> </partition> </partitions> <use>all</use> </drive> <drive> <device>/dev/apps</device> <is_lvm_vg config:type="boolean">true</is_lvm_vg> <partitions config:type="list"> <partition> <lv_name>var_spool_lv</lv_name> <filesystem config:type="symbol">reiser</filesystem> <mount>/var/spool</mount> <size>50gb</size> </partition> <partition> <lv_name>srv_lv</lv_name> <mount>/srv</mount> <filesystem config:type="symbol">reiser</filesystem> <size>5gb</size> </partition> </partitions> <pesize>4M</pesize> </drive> .... </partitioning>

1 1

Re: [suse-autoinstall] Placing autoyast.xml on boot CD
by LDB 08 Jan '06

08 Jan '06

Anton Altaparmakov wrote: > On Sun, 8 Jan 2006, LDB wrote: >> I am not making myself clear. The autoyast.xml file is on the boot CD. The >> installation media is elsewhere. When it comes time for the autoyast.xml file >> to be recognized it is not found by the installer. The directives >> autoyast=file:///autoyast.xml does not work. >> >> This is what my installation root looks on the CD, >> >> drwxr-xr-x 5 root root 176 2006-01-07 23:30 ./ >> drwxrwxrwt 45 root root 2456 2006-01-08 11:45 ../ >> -rw-r--r-- 1 root root 17360 2006-01-07 23:30 autoyast.xml >> drwxr-xr-x 3 root root 328 2005-09-14 21:04 boot/ >> -r--r--r-- 1 root root 692 2005-09-14 19:34 content >> drwxr-xr-x 2 root root 152 2005-09-14 19:55 media.1/ >> drwxr-xr-x 2 root root 48 2005-09-14 21:04 suse/ >> >> Am I wrong in thinking it can be recognized on the boot CD? > > You are right in that but you are doing it wrong. You have to place the > file in the initrd of the cd not in the root directory of the cd if you > want to use the autoyast=file syntax. > > If you place it in the root of the cd, then the correct syntax is: > > autoyast=device://hda/autoyast.xml > > Assuming hda is your cdrom drive (which it is on a scsi/sata only + pata > cd/dvd-rom drive system). > > That works fine for me. > > Best regards, > > Anton Excellent .. thank you ... LDB

1 0

Placing autoyast.xml on boot CD
by LDB 08 Jan '06

08 Jan '06

I have placed autoyast.xml in the root of my boot CD. I have passed in the correct parameters in, boot/loader/isolinux.cfg which is, append initrd=initrd showopts install=ftp://suse.mirrors.tds.net/pub/opensuse/distribution/SL-10.0-OSS/in… autoyast=default load_ramdisk=1 textmode=1 So, is it possible to put the autoyast.xml file on the boot CD while the installation source is elsewhere? Thanks, LDB

2 2

SLES9-SP3: SATA-driver not installed?
by suselist＠nlsn.nu 06 Jan '06

06 Jan '06

Hi everyone, I have successfully installed SLES9 SP2 via autoyast and are now switching to SLES9 SP3 install-source. Install goes fine, but after reboot I get: Waiting for device /dev/sda5 to appear: .....not found -- device nodes: <list of devices, no sda> No root device found: exiting to bin/sh It a machine with SATA-controller, and it seems like SATA-support is missing from the installed kernel? I read in the docs that the system with drivers has changed, now a custom initrd is built during install. Seems like it cannot identify the correct driver for the SATA-card and does add that to the initrd. How do I add this driver myself during install? ( Or, is this really another problem? ) Regards Daniel

5 4

keytable
by Frank Steiner 06 Jan '06

06 Jan '06

Hi, since 10.0 the keytable-keyword doesn't work in the info file. I used to have Language: de_DE Display: color Keytable: us in the info file that we put into the initrd. But during the installation, the keymap is german when I switch to e.g. Alt+F2. Also lilo is using german as default keymap after installation. Grepping for "keytable" in the files from the autoyast2(-installation) rpms, I don't find any entry for keytable anymore (except for the docu which still lists the option, while there used to be some like AutoinstLinuxrc.ycp: keytable = settings["keytable"]:""; for earlier versions, like on SuSE 9.0. Has this option been dismissed? Any way to set the keyboard and the language independently? cu, Frank -- Dipl.-Inform. Frank Steiner Web: http://www.bio.ifi.lmu.de/~steiner/ Lehrstuhl f. Bioinformatik Mail: http://www.bio.ifi.lmu.de/~steiner/m/ LMU, Amalienstr. 17 Phone: +49 89 2180-4049 80333 Muenchen, Germany Fax: +49 89 2180-99-4049 * Rekursion kann man erst verstehen, wenn man Rekursion verstanden hat. *

3 9

JFYI - Autoyast on SUSE Linux 10.1 / SLES10
by Uwe Gansert 05 Jan '06

05 Jan '06

Hi, We'll have SUSE Linux 10.1 beta1 soon - the last SUSE Linux before SLES10. With this eMail I want to encourage you to take part of the beta test of SUSE Linux. Especially for you, as administrator of an autoinstallation environment, it's important to find problems and bugs during the beta phase. As soon as the 10.1 is gold, we can't do any fixes anymore for autoyast because that requires a patch for the installation system which is on the CD/DVD. So official online updates for autoyast are hardly an option then. To make changes in autoyast a little bit more visible for you I've started a brief overview of what has changed in autoyast since 10.0 The current state (post alpha4) of what has changed can be found here: http://www.suse.de/~ug/autoyast_changes.html If you want to download the latest test version of SUSE Linux, you can download it here: http://www.opensuse.org/Development_Version If you think you've hit a bug you can either write a mail to this list or (even better) you can use bugzilla to report a bug: https://bugzilla.novell.com Thanks in advance for testing SUSE Linux. -- 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

2 3

RE: [suse-autoinstall] Custom media, no first reboot
by Ness, Todd 05 Jan '06

05 Jan '06

So can I assume that technically it is ok if the system does not reboot after disk1? I was just concerned about the change in behavior. My systems seem ok, they are functioning properly all RPMS appear to be installed, and I assume that the installer is getting all dependencies taken care of. I have to do http installs because of firewall restrictions. So I am ok with the reboot. I have this in my mode section... <mode> <installation config:type="boolean">true</installation> <confirm config:type="boolean">false</confirm> <forceboot config:type="boolean">true</forceboot> <interactive_boot config:type="boolean">false</interactive_boot> <interactive config:type="boolean">false</interactive> <reboot config:type="boolean">true</reboot> <upgrade config:type="boolean">false</upgrade> </mode> Thanks for getting back to me. Todd -----Original Message----- From: Uwe Gansert [mailto:ug@suse.de] Sent: Thursday, January 05, 2006 6:53 AM To: suse-autoinstall(a)suse.com Subject: Re: [suse-autoinstall] Custom media, no first reboot On Thursday 05 January 2006 14:33, Ness, Todd wrote: > I have JDS which in based off SLES8. > > Any idea of how to get the initial reboot to happen after Disk1 of JDS > and Disk1 of my patches are installed? I hope got you right but even then, I'm not sure if I can help. First you can try to add: <install> <general> <mode> <forceboot config:type="boolean">true</forceboot>** </mode> </general> </install> And if this does not help, you can try to install from an NFS source (I guess you are using ftp or http or something like this at the moment?) With NFS the RPMs are not getting copied to the local machine and so you don't need that much memory. -- 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 -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

2 1

Custom media, no first reboot
by Ness, Todd 05 Jan '06

05 Jan '06

I have asked this before and either missed the reply or did not get an answer. I have JDS which in based off SLES8. I have a bunch of new patches, plus some other RPMs that I want to add to the install media, and I am have made my own yast directory with installorder and order file, everything works mostly as expected. But, one thing is different. During the very first boot of the system installation starts, and all of the RPMS get installed on this one boot, there is not a boot after the RPMS from Disk1 have been installed. I don't think this is causing me any issues, the StarOffice RPM is the only RPM that installs (during network installs only) after the initial boot. Any idea of how to get the initial reboot to happen after Disk1 of JDS and Disk1 of my patches are installed? Todd

2 1

autoinstall suddenly fails
by T. Ribbrock 04 Jan '06

04 Jan '06

Hi all, I just ran into a bizzare problem: I'm currently creating/testing our auto-install, hence, I'm re-running it many, many times on two PCs. So far, I always used a floppy with "info" and "autoinst.xml" and a copy of CD 1 to boot. I would then select "Install", the installer would find "info" on the floppy and the rest would happen magically from there. In fact, I have reinstalled the second of the two PCs that way just yesterday. Today, however, I'm trying to reinstall the first PC - and am getting nowhere. It starts the install, I can see the message "searching for info file" (or suchlike) on the screen and the floppy drive spins up. Then it proceeds into the graphical installer (my auto-install uses text-only) and prepares for auto-installation (so it *must* have found the info file as such) - but hangs, asking for a profile for the machine. If I give "floppy:///autoinst.xml" as answer to that, it will happily continue, though it tries to install from CD-ROM (instead of via network, as defined in the info file). If I choose "Network Install" manually right at the start, I can get the autoinstall working. It looks as if it *does* find 'info' on the floppy (hence starts in auto-install mode), but for some odd reasons refuses to read the actual contents. I'm completely puzzled as to why this would happen, as I have installed that very machine several times that way. Hence, if there is anyone out there with a brainwave as to where to look to fix (or even just investigate) this, I'd be most grateful... Cheerio, Thomas

2 8

ex: chosing host-specific profile (pxe-based)
by Frank Steiner 04 Jan '06

04 Jan '06

Hi, here's sth. which didn't work in some earlier versions (don't remember when I last tried it) but is working at least in 10.1 alpha4. I can now use this rule in rules.xml to chose a profile for each host based on its name. This works only if the host gets its name via dhcp, so this is sth. especially nice for pxe-based installations. I provide this as example for other people and hope that someone can make use of it :-) This is a solution for the non-working <hostname> matching, because the <hostname> tag contains the IP and not the hostname, even when using pxe/dhcp. <rule> <custom1> <script> <![CDATA[ #!/bin/sh . /var/lib/dhcpcd/dhcpcd-eth0.info echo -n $HOSTNAME ]]> </script> <match>*</match> <match_type>exact</match_type> </custom1> <result> <profile>profiles/part_@custom1@.xml</profile> <continue config:type="boolean">true</continue> </result> </rule> I use this to store partition information per host in a file part_<hostname>.xml in the profile subdir. No need to change the rules.xml anymore, just create the profile with the partition information. In these profiles, I always keep partitions, formatting only / and /var. In case I really really want to destroy and recreate partitions for a specific host, I add another rule afterwards, e.g. <rule> <custom1> <script> <![CDATA[ #!/bin/sh . /var/lib/dhcpcd/dhcpcd-eth0.info echo -n $HOSTNAME ]]> </script> <match>riemann</match> <match_type>exact</match_type> </custom1> <result> <profile>profiles/part_riemann_createnew.xml</profile> <continue config:type="boolean">true</continue> </result> </rule> or, IP-based: <rule> <hostaddress> <match>141.x.x.x</match> <match_type>exact</match_type> </hostaddress> <result> <profile>profiles/part_riemann_keep.xml</profile> <continue config:type="boolean">true</continue> </result> </rule> to override the common selection. Have fun! cu, Frank -- Dipl.-Inform. Frank Steiner Web: http://www.bio.ifi.lmu.de/~steiner/ Lehrstuhl f. Bioinformatik Mail: http://www.bio.ifi.lmu.de/~steiner/m/ LMU, Amalienstr. 17 Phone: +49 89 2180-4049 80333 Muenchen, Germany Fax: +49 89 2180-99-4049 * Rekursion kann man erst verstehen, wenn man Rekursion verstanden hat. *

1 0

32/64bit with 10.1
by Frank Steiner 04 Jan '06

04 Jan '06

Hi, checking out opensuse 10.1a4, I see that the boot/ directory now has two subdirectories with different initrds and kernels for i386 and x86_64. I wonder what that means for autoyast installation via pxe. Is the intention to setup two different pxe configurations with two different kernels/initrds for 32 and 64bit hosts? In contrast to just one initrd on 10.0 where the installer would chose 32 or 64bit installation from a common source automatically? cu, Frank -- Dipl.-Inform. Frank Steiner Web: http://www.bio.ifi.lmu.de/~steiner/ Lehrstuhl f. Bioinformatik Mail: http://www.bio.ifi.lmu.de/~steiner/m/ LMU, Amalienstr. 17 Phone: +49 89 2180-4049 80333 Muenchen, Germany Fax: +49 89 2180-99-4049 * Rekursion kann man erst verstehen, wenn man Rekursion verstanden hat. *

1 0

Parameter name in autoyast.xml to change default filesystem "reiserfs"
by Tob_Sch＠gmx.de 03 Jan '06

03 Jan '06

Hi, how can I change the default filesystem type "reiserfs" to for example "xfs" with autoyast? The effect should be among other things for example that the yast-GUI auto-proposes this filesystem when you create a new logival volume with LVM. Thanks in advance. -- Lust, ein paar Euro nebenbei zu verdienen? Ohne Kosten, ohne Risiko! Satte Provisionen f�r GMX Partner: http://www.gmx.net/de/go/partner

2 3

autoyast.xml from an existing system
by LDB 03 Jan '06

03 Jan '06

Can you create an autoyast.xml file from an existing system (with minimal effort) that you want other servers to mimic? Does that make sense? Thanks, LDB

2 4

Module cd creator
by Rodrigo_Albert_Fedosi 02 Jan '06

02 Jan '06

It is possible install the Yast module "cd creator" of the Suse enterprise server in the Suse professional. If it will go as I do? Att. Rodrigo Albert Fedosi Suporte TI Tel: (31) 3419-8854 Fax: (31) 3419-8803 rodrigo(a)bhz.jamef.com.br www.jamef.com.br

2 1

Updating drivers and dealing with patches in AutoYast
by aquajtk-suse＠yahoo.com 02 Jan '06

02 Jan '06

Hello, I'm having 3 questions : 1. I've tried to install SLES9 SP2 on an IBM x306 however i was having problems with the installation cuz it did not recognize the raid controller and it showed both physical drives instead of the logical drive. I had to manually install this server using a driver update disk. Needless to say, but i also want to automatically deploy SLES9 SP2 on this server. I've checkout this document : http://mirror.mcs.anl.gov/suse-people/hvogel/Update-Media-HOWTO/Update-Medi… It states that i will need to put a file 'driverupdate' in the root of my repository. (I assume that's the driver update disk image i can download from IBM's support site). How can i use several update disks if they all should be named 'driverupdate'? 2. Say I have an http repository which contains the installation sources for SLES9 SP2. One day Novell releases a critical security patch and I'd like to integrate this patch in my repository so i don't need to install these patches after installing a server. Is there a way to do this (besides doing this with post-install scripts that just run rpm-commands)? Replacing the package in the repository won't work i think, cuz (if i'm not wrong) there is a list of packages on the install sources. 3. Currently i'm using a file in pxelinux.cfg which contains references to the kernel- and initrdimage and also the linuxrc command line parameters. AutoYasts documentation mentiones an info file that contains these parameters. Where do i place such an info file? Can i combine the info file and the command line parameters? eg i could put all parameters that are not unique for a given server in the info file and then put the server specific option in the file in pxelinux.cfg. Thanks a lot! Johan

2 1

Earning from Internet
by vinay dhillon 02 Jan '06

02 Jan '06

Hi Friends, Check this website its working great. Earn from Internet. We are Earning Rs. 1500/- to Rs. 5000/- Per day,Every day 24x7. Just to surf for 6min a day. Register Free www.12dailypro.com/?ref=125012 For more information call 09224598813. vinay dhillon mumbai Send instant messages to your online friends http://in.messenger.yahoo.com

2 1

Possible bug with LVM and <size>max</size>
by Luzian Scherrer 02 Jan '06

02 Jan '06

Hello, The size-part of this controlfile-section doesn't work with SuSE 10.0 AutoYaST: <partition> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <lv_name>root</lv_name> <mount>/</mount> <size>max</size> </partition> However, when I change 'max' to an absolute size (like '4096MB') it works. Defining the size as 'max' did work with SLES 9 SP2 AutoYaST. Is this a feature? ;) PS: Is this mailing-list the correct place to submit AutoYaST bugs or is there a bug-tracking system? Thanks, -Luzian

2 1