January 2010 - openSUSE Autoinstall - openSUSE Mailing Lists

AW: [suse-autoinstall] auto install with service pack
by Martin.Linten＠rzf.fin-nrw.de 15 May '25

15 May '25

Hallo Anas, hallo list! I am trying to install sles8 with service pack 2 in an automated way. The kernel and the inird from the sp2-CD (chosen because of hardware support) are booted via pxe. When checking the software selection I always get a long list of dependency errors beginning with "aaa_skel not available..." and so on. Please help and tell me how I can do better! I suppose it has nothing to do with the /UnitedLinux-i386-1 directory, but maybe I am wrong... My nfs-exported directory for linuxrc looks like this: |--boot | `--loader |--content (file from sles8) |--media.1 (from sles8) |--sles8 | |--UnitedLinux | |--boot | |--docu | |--dosutils | |--media.1 | |--media.2 | |--media.3 | |--suse | `--yast |--sp2 | |--UnitedLinux | |--boot | |--docu | |--i386 | |--images | |--linux | `--media.1 `--yast |--ul |--instorder (file) `--order (file) I011-52:/autoinst/suse/sles8sp2/yast # cat order /sles8 /sles8 /sp2 /sp2 I011-52:/autoinst/suse/sles8sp2/yast # cat instorder # I want to prefer sp2 packages if possible /sp2 /sp2 /sles8 /sles8 Thanks a lot, Martin -----Ursprüngliche Nachricht----- Von: Anas Nashif [mailto:nashif@suse.de] Gesendet am: Dienstag, 15. Juli 2003 09:39 An: Aaron McSorley Cc: suse-autoinstall(a)suse.com Betreff: Re: [suse-autoinstall] auto install with service pack Hi, It can be done in an automated way. For example, my nfs export for SLES8 i386 with SP2 looks like this: |-- SP2 | |-- UnitedLinux | |-- boot | |-- docu | |-- i386 | |-- images | |-- linux | `-- media.1 |-- SuSE-Linux-SLES-i386-8 | `-- CD1 | |-- boot | |-- docu | |-- media.1 | |-- suse | `-- yast |-- UnitedLinux-i386-1 | |-- CD1 | | |-- UnitedLinux | | |-- boot | | |-- docu | | |-- dosutils | | `-- media.1 | `-- CD2 | |-- UnitedLinux | |-- boot | `-- media.2 |-- boot | `-- loader |-- media.1 `-- yast `-- ul in the directory yast, there are 2 files: order and instorder This is the content which references the location of the root of every source. (where the media.1 directory is available) # cat yast/instorder /UnitedLinux-i386-1/CD1 /UnitedLinux-i386-1/CD1 /SP2 /SP2 /SuSE-Linux-SLES-i386-8/CD1 /UnitedLinux-i386-1/CD1 avicenna:/work/CDs/sles8-i386 # cat yast/order /SP2 /SP2 /SuSE-Linux-SLES-i386-8/CD1 /SuSE-Linux-SLES-i386-8/CD1 /UnitedLinux-i386-1/CD1 /UnitedLinux-i386-1/CD1 (delimiter is tab) more details can be found at http://www.suse.de/~nashif/autoinstall/8.1/html/advanced.html#AEN1251 Hope that helps... Anas Aaron McSorley wrote: > Is there a method for incorporating a service pack into an > auto install of SLES8. > > I tried putting the service pack in its own directory in my auto install > repository > and giving it preference in the order and instorder directories. > The install starts ok but, after package install I get alot of package > install failures. > After hitting ok to the fail log it prompts me to insert the service > pack cdrom. > > I thought about just replacing the original packages with the new ones > from the service pack but, > I would like to keep the service pack separate from the original > repository so I can > install without it if I want. > > thanks > -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

3 2

linuxrc - netdevice=<hwaddress>
by John Willis 18 Dec '12

18 Dec '12

Does anyone know if any of the SLES releases 9 or 10 support passing the linuxrc option netdevice=<hardware mac address> ? I noticed Red Hat has had this for sometime and it seems totally missing in SuSE which seems really odd. I'm still scratching my head if we really are still passing only by kernel interface name. I read in the change log for linuxrc-1.8.6-3 a change that "sounds" like this feature. * Mon Mar 14 2005 - snwint(a)suse.de - s390: fix segfault in net_list_s390_devs() - extra root image was sometimes not used - allow netdevices to be specified by hwaddress But it looks like linuxrc-1.8.6-3 is only available in SuSE Professional 9.3. "any" commentary would be sincerely appreciated the feature also seems to be fairly minor since any delimiter seperating the octets in the hwaddr string could be used to identify the difference between an interface name and interface hw address if i could figure out a generic method of overriding the linuxrc with a custom script and daisy chain it back into linuxrc after setting up the interface name, I would.. and have a slight idea on how to do that.. but i'd rather find out i'm just missing something and the feature is already there Thanks!

3 2

[opensuse-autoinstall] Repository Priority
by Tim Kirby 28 Sep '11

28 Sep '11

Repository Priority is obviously a useful thing to be able to manipulate. Yast lets me set it and zypper lets me set it. Yet, if I have multiple repositories defined at the beginning of my autoyast (including update repos so I get an up to date system built out of the box), I don't seem to have any control over the respective repository priorities - they're all defaulted. Or did I miss a subtle option somewhere? Tim -- Tim Kirby 651-605-9074 trk(a)cray.com Cray Inc. Information Systems -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

3 2

[opensuse-autoinstall] OT: Centralized patch management for OpenSuse 11.x
by Ivan De Masi 14 Jan '11

14 Jan '11

Hello, someone may start to laugh now for my (OT) question, but I can't find a satisfying solution :-/ How do you manage patches, updates, etc. for your running opensuse clients (not enterprise linux, just the "regular" opensuse distribution)? Is there a way like known from M$-World (WSUS)? As I know "Zend Management Server" is not open source (and not supported any more?!). Or can the complete management only be handled with self written scripts? Thanks! Regards, Ivan -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

3 3

[opensuse-autoinstall] Adding packages to profile triggers error message
by Isaac Hailperin 07 Nov '10

07 Nov '10

Hi, I try to install sles 11 via autoyast. I did an installation from dvd, and pulled an autoyast profile. This profile works, and can be installed via pxe. Now I want to add the following packages: findutils-locate, dhcp-server, bind, apache2, vsftpd, nfs-kernel-server I do this via the gui. I have also tried to do it with an editor, as the gui messed up profiles in sles10sp2. In both cases, after the first reboot, I get the errormessage: "The package resolver run failed. Please check your software section in the aut" [oyast profile] (last part invisible, I guess it should be the software section in my autoyast profile :-)) This a real problem, as I have to confirm this message, thus it stops the autoinstall process. After confirming, the autoinstall process continues. Right bevor I can log in, I get "Could not update ICEauthority file /var/lib/gdm/.ICEauthority" I confirm, and get: "There is a problem with the configuration server. (/usr/lib/GConf/2/gconf-sanity-check-2 exited with status 256)" I confirm, and can log in. Theses messages are presistend after reboot. Its annoying, but not a stopper like the first problem. Why is this? Can I avoid this? Isaac -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

3 2

[opensuse-autoinstall] general rules question
by dutchguy69 26 Jul '10

26 Jul '10

I have a working autoyast install for 11.1 without using rules. Right now I would like to introduce rules but I do not seem to understand exactly how to make this work. The current install is done by supplying information for a linuxrc info file on the kernel command line info=nfs://<ip-address>/<path>/1055_init.linuxrc The info file has several parameters defined for network access, the install and the autoyast variable autoyast: nfs://<ip-address>/<path>/1055_init.autoyast <- this is my autoinst profile below the path I have created the rules directory which includes a rules .xml file with following content <?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> # CPU_TYPE on vm's is giving same result for CPU as on real hardware we have to extend to video to understand the difference between virtual and real CPU_TYPE=`cat /proc/cpuinfo|grep 'model name'|uniq|awk 'BEGIN {FS=":"};{print $2}'` VIDEO_TYPE=`/sbin/lspci | grep "VGA compatible controller"|awk 'BEGIN {FS=":"};{print $3}'` if [ "$CPU_TYPE" == " AMD Athlon(tm) 64 X2 Dual Core Processor 4400+" ]; then if [ "$VIDEO_TYPE" == " nVidia Corporation G70 [GeForce 7300 GT] (rev a1)" ]; then echo -n "host1.xml" elif [ "$VIDEO_TYPE" == " InnoTek Systemberatung GmbH VirtualBox Graphics Adapter" ]; then echo -n "host1-virtualbox.xml" fi # information for scan64-3200 elif [ "$CPU_TYPE" == " AMD Athlon(tm) 64 Processor 3200+" ]; then if [ "$VIDEO_TYPE" == " nVidia Corporation G70 [GeForce 7300 GT] (rev a1)" ]; then echo -n "host2.xml" elif [ "$VIDEO_TYPE" == " InnoTek Systemberatung GmbH VirtualBox Graphics Adapter" ]; then echo -n "host2-virtualbox.xml" fi fi </script> <match>*</match> <match_type>exact</match_type> </custom1> <result> <profile>@custom1@</profile> <continue config:type="boolean">true</continue> </result> </rule> <rule> <custom> <script> </script> <match>*</match> <match_type>exact</match_type> </custom> <result> <profile>1055_init.autoyast</profile> <continue config:type="boolean">false</continue> </result> </rule> </rules> </autoinstall> I have tried to change the autoyast parameter in the info file with the following values autoyast: nfs://<ip-address>/<path>/ <-- question about profile location autoyast: nfs://<ip-address>/<path>/rules/ <-- question about profile location autoyast: nfs://<ip-address>/<path>/rules/rules.xml Above direct reference to rules file seems to work but not as expected. When I check the box I can see that in /tmp/profile/autoinst.xml I find a copy of my rules.xml file where I'm expecting a merged profile from my 1055_init.autoyast and host2.xml information I'm not sure exactly what I'm doing wrong and even after extensive check via google haven't found the right references. I've used http://forgeftp.novell.com/yast/doc/SL11.1/autoinstall/ for documentation but it is not giving me enough detail to solve above issue. Any input would be welcomed. -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

3 5

[opensuse-autoinstall] /etc/sysconfig/network/dhcp der Parameter WRITE_HOSTNAME_TO_HOSTS von "yes" auf "no" SLES11
by Dirk.Lohmann＠Bertelsmann.de 26 Mar '10

26 Mar '10

Hello, we want to set in /etc/sysconfig/network/dhcp WRITE_HOSTNAME_TO_HOSTS from "yes" to "no" in SLES11 How can wie do that with xml ? Dirk Lohmann

7 14

[opensuse-autoinstall] NIC disappears on PXE booted suse client after TFTP.
by Simon Loewenthal/NL/Tele2 01 Feb '10

01 Feb '10

Dear all, I am trying to solve a strange networking problem with PXE boot and SUSE. Here follows a description with the strange ARP broadcast noted at the end: 1) PXE boot the 10.205.8.253 (new server to install) 2) DHCPOFFER to 10.205.8.253 and this then sends a DHCPACK. 3) 10.205.8.253 then TFTP downloads the linux and initrd and executes it successfully. 4) Afterwards 10.205.8.253 looses all the network information. 5) The final messages (Xensourc) shown in Ethereal are ARP requests that come from 10.205.8.253. This is the autoyast server ARPing for the MAC of 10.205.8.253 because it has disappeared from the network. No. Time Source Destination Protocol Info 15120 22.480085 Xensourc_33:3f:cc d8:d3:85:5a:00:b0 ARP Who has 10.205.8.253? Tell 10.205.8.145 At this point the PXE booted system 10.205.8.253 then reverts to the screen for starting a manual set-up programme. "Could not find ... the Installation Source. Activating manual setup program." When I use this to display the network interfaces then it only displays the loopback. This problem is not specific to one server. It happens on all servers. The servers consist of existing HP c-class blades, and some newer G6 blades. I tried a CD installation on the former blades and this works, but Suse does not see the NIC on the newer G6 blades. I do know that the firmware for the OA on the HP c7000 was upgraded this week, it all worked last week, but this is process of elimination because, as ever, one has to prove to others that this is or is not a cause because otherwise the firmware won't be rolled back. Does anyone know where I would start? Perhaps, I could load modules during the PXE boot for the server NIC? Unsure how or whether this is the right path to start down. Yours sincerely, s. -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

4 6

[opensuse-autoinstall] Is there a Package Resolver pre-flight check
by Simon Loewenthal/NL/Tele2 27 Jan '10

27 Jan '10

Dear folks, Is there a programme I can run that will verify that the packages in a customised autoinst.xml file are correct and won't fail the package resolver? Best wishes, S. -- Simon Loewenthal/Tele2 GSM: +31 6 2000 5427 ******** IMPORTANT NOTICE ******** Please repect the X-Reply to klunky.co.uk. PGP available 0xD86A5A17. S/MIME PKCS12 key available for Lotus Notes: Please ask me for it. This e-mail (including any attachments) may contain information that is confidential or otherwise protected from disclosure and it is intended only for the addressees. If you are not the intended recipient, please note that any copying, distribution or other use of information contained in this e-mail (and its attachments) is not allowed. If you have received this e-mail in error, kindly notify us immediately by telephone or e-mail and delete the message (including any attachments) from your system. Please note that e-mail messages may contain computer viruses or other defects, may not be accurately replicated on other systems, or may be subject of unauthorized interception or other interference without the knowledge of sender or recipient. Tele2 only send and receive e-mails on the basis that Tele2 is not responsible for any such computer viruses, corruption or other interference or any consequences thereof. It ought to be obvious that my views do not represent my employer's views. -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

4 5

Re: [opensuse-autoinstall] Config question about autoinst.xml: Automatically generating the MAC address in net-udev
by Simon Loewenthal/NL/Tele2 25 Jan '10

25 Jan '10

There are usually two NICs on each server, but only one NIC [eth0] is required when jumpstarting it from autoyast. If I remove the entry, and there are two NICs, will it default to the first NIC it finds, which hopefully with be eth0. S Uwe Gansert wrote: > on Monday 25 January 2010 Simon Loewenthal/NL/Tele2 wrote: > > >> <net-udev config:type="list"> >> <rule> >> <name>eth0</name> >> <rule>ATTR{address}</rule> >> <value>00:1c:c4:a8:27:42</value> >> </rule> >> </net-udev> >> >> i) Can I remove the lines referencing n-etudev and let autoyast use the >> first interface it happens upon or, >> > > if you only have one interface, then you can remove the complete net-udev part > from the profile. > > -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 0

[opensuse-autoinstall] Config question about autoinst.xml: Automatically generating the MAC address in net-udev
by Simon Loewenthal/NL/Tele2 25 Jan '10

25 Jan '10

Dear all, The autoinst.xml has this line in it and this is normal. <net-udev config:type="list"> <rule> <name>eth0</name> <rule>ATTR{address}</rule> <value>00:1c:c4:a8:27:42</value> </rule> </net-udev> This profile is being modified so that it can be used as a genericone for many systems, but all systems have different MAC addresses, so the line would not be useful in a generic profile. i) Can I remove the lines referencing n-etudev and let autoyast use the first interface it happens upon or, ii) have the newly build machine automatically add the MAC address with a line similar to: <value>auto</value> ? I have searched a little this morning and could not come up with a lot of ideas. Yours faithfully, SL -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 1

[opensuse-autoinstall] <match_type>regex</match_type> -- regex support?
by Stephen Dowdy 25 Jan '10

25 Jan '10

I'm wondering *which* regex system is used here and what the constraints on its use are. Google: [ autoyast "<match_type>regex</match_type>" ] And there's precious few examples to work from. The only official example shows: <rule> <board_vendor> <match>ntel</match> <match_type>regex</match_type> </board_vendor> <result> <profile>classes/largeswap.xml</profile> <continue config:type="boolean">true</continue> <dont_merge config:type="list"> <element>partition</element> </dont_merge> </result> </rule> and the value in the <match> element doesn't even have any regex pattern, wildcard, classes, etc. >From this example, all i can infer is that a <match> element value is used as a non-anchored match string. ("match anywhere") I have seen another example showing the use of the "^" begin-of-line anchor symbol e.g. "<match>^SUSE Linux Enterprise Server</match>". But what is the full-extent of what i can use here? for my needs right now, i'd like to use <product>PowerEdge [12]850</product> to match the Dell PE 1850 and PE 2850 systems. Will this work? (i imagine i may have to escape some patterns to fit XML specification, which i'm not very familiar with, but that's just a detail) thanks, --stephen -- Stephen Dowdy - Systems Administrator - NCAR/RAL 303.497.2869 - sdowdy(a)ucar.edu - http://www.ral.ucar.edu/~sdowdy/ -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 5

[opensuse-autoinstall] SLES10sp3 Autoyast Network configs being processed but lost later.
by Stephen Dowdy 23 Jan '10

23 Jan '10

in SLES 10sp3.. My autoyast profile network configuration is being processed, but forgotten. It does not end up in the "installedSystem.xml", but is clearly being considered in 'y2log' (with no apparent reason for discarding it) Network Interfaces section contains: ------------------------------------------------------------- <interfaces config:type="list"> <interface> <bootproto>static</bootproto> <device>eth0</device> <ipaddr>192.168.50.33</ipaddr> <network>192.168.50.0</network> <broadcast>192.168.50.255</broadcast> <netmask>255.255.255.0</netmask> <startmode>onboot</startmode> <usercontrol>no</usercontrol> </interface> </interfaces> ------------------------------------------------------------- Looks like, at least at SOME point along the way, AutoYast is finding the interface, setting up configuration data for a /etc/sysconfig/network/if file, but then later on seems to completely forget to write the file, or it gets removed. This worked in SLES9. - Should the above autoyast profile configuration work? - If so, what's going wrong? - If not, am i relegated to creating post install scripts to manually configure the sysconfig/network files and udev rules? thanks, --stephen y2log output (reformatted to be more readable) ------------------------------------------------------------- in3(11181) [YCP] network/complex.ycp:65 Devs=$["eth":$["id-00:26:b9:39:18:21":$["BOOTPROTO":"static" "BROADCAST":"" "ETHTOOL_OPTIONS":"" "IPADDR":"192.168.50.33" "MTU":"" "NAME":"Broadcom NetXtreme II BCM5709 Gigabit Ethernet" "NETMASK":"255.255.255.0" "NETWORK":"" "REMOTE_IPADDR":"" "STARTMODE":"auto" "UNIQUE":"rBUF.yy10jcgJwT2" "USERCONTROL":"no" "_aliases":$[] "_nm_name":"bus-pci-0000:01:00.0"]]] in3(11181) [YCP] NetworkDevices.ycp:609 << exact same output as above >> in3(12869) [YCP] Detection.ycp:235 IFCONFIG1: $["exit":0 "stderr":"" "stdout":"eth0 Link encap:Ethernet HWaddr 00:26:B9:39:18:21 \n inet addr:192.168.50.33 Bcast:192.168.50.255 Mask:255.255.255.0\n inet6 addr: fe80::226:b9ff:fe39:1821/64 Scope:Link\n UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1\n RX packets:32410 errors:0 dropped:0 overruns:0 frame:0\n TX packets:1483 errors:0 dropped:0 overruns:0 carrier:0\n collisions:0 txqueuelen:1000 \n RX bytes:5966883 (5.6 Mb) TX bytes:603226 (589.0 Kb)\n Interrupt:58 Memory:d6000000-d6012800 \n\nlo Link encap:Local Loopback \n inet addr:127.0.0.1 Mask:255.0.0.0\n inet6 addr: ::1/128 Scope:Host\n UP LOOPBACK RUNNING MTU:16436 Metric:1\n RX packets:22 errors:0 dropped:0 overruns:0 frame:0\n TX packets:22 errors:0 dropped:0 overruns:0 carrier:0\n collisions:0 txqueuelen:0 \n RX bytes:1424 (1.3 Kb) TX bytes:1424 (1.3 Kb)\n\n"] in3(12869) [YCP] Detection.ycp:242 IFCONFIG2: $["exit":0 << exact same output as under IFCONFIG1 >> in3(12869) [YCP] NetworkDevices.ycp:505 config=$["BOOTPROTO":"static" "BROADCAST":"" "ETHTOOL_OPTIONS":"" "IPADDR":"192.168.50.33/24" "MTU":"" "NAME":"Broadcom NetXtreme II BCM5709 Gigabit Ethernet" "NETWORK":"" "REMOTE_IPADDR":"" "STARTMODE":"auto" "UNIQUE":"rBUF.yy10jcgJwT2" "USERCONTROL":"no" "_nm_name":"bus-pci-0000:01:00.0"] And Finally, last place i see it referenced: [wfm] Y2CCWFM.cc(createInLevel):149 Parsing finished [Interpreter] network/services/proxy.ycp:338 Calling YaST client lan_auto (arguments: ["Export"]) [YCP] clients/lan_auto.ycp:14 ---------------------------------------- [YCP] clients/lan_auto.ycp:15 Lan autoinst client started [YCP] clients/lan_auto.ycp:188 Adding: BOOTPROTO=static [YCP] clients/lan_auto.ycp:188 Adding: BROADCAST= [YCP] clients/lan_auto.ycp:188 Adding: ETHTOOL_OPTIONS= [YCP] clients/lan_auto.ycp:188 Adding: IPADDR=192.168.50.33 [YCP] clients/lan_auto.ycp:188 Adding: MTU= [YCP] clients/lan_auto.ycp:188 Adding: NAME=Broadcom NetXtreme II BCM5709 Gigabit Ethernet [YCP] clients/lan_auto.ycp:188 Adding: NETMASK=255.255.255.0 [YCP] clients/lan_auto.ycp:188 Adding: NETWORK= [YCP] clients/lan_auto.ycp:188 Adding: PREFIXLEN=24 [YCP] clients/lan_auto.ycp:188 Adding: REMOTE_IPADDR= [YCP] clients/lan_auto.ycp:188 Adding: STARTMODE=auto [YCP] clients/lan_auto.ycp:188 Adding: UNIQUE=rBUF.yy10jcgJwT2 [YCP] clients/lan_auto.ycp:188 Adding: USERCONTROL=no [YCP] clients/lan_auto.ycp:188 Adding: _nm_name=bus-pci-0000:01:00.0 [YCP] clients/lan_auto.ycp:337 Lan auto finished [YCP] clients/lan_auto.ycp:338 ---------------------------------------- [Interpreter] network/services/proxy.ycp:338 Called YaST client returned. [wfm] Y2WFMComponent.cc(import):735 Y2WFMComponent::import (Ldap) [wfm] Y2WFMComponent.cc(import):735 Y2WFMComponent::import (Autologin) [wfm] Y2WFMComponent.cc(import):735 Y2WFMComponent::import (Nsswitch) [wfm] Y2WFMComponent.cc(import):735 Y2WFMComponent::import (Pam) [wfm] Y2WFMComponent.cc(import):735 Y2WFMComponent::import (LdapPopup) [wfm] Y2CCWFM.cc(createInLevel):149 Parsing finished [Interpreter] clients/ldap_auto.ycp:104 Calling YaST client ldap_auto (arguments: ["GetModified"]) ------------------------------------------------------------- -- Stephen Dowdy - Systems Administrator - NCAR/RAL 303.497.2869 - sdowdy(a)ucar.edu - http://www.ral.ucar.edu/~sdowdy/ -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

3 5

[opensuse-autoinstall] AutoYaST on USB key and in XEN setup (SLES 10sp3)
by Stephen Dowdy 22 Jan '10

22 Jan '10

Howdy, I am trying to build a rules based deployment that will ultimately be on a custom DVD My intent is that the autoyast configuration be in /cf/... on the deployment media. I want to use a simple rules file in '/cf/rules/rules.xml' to parse the kernel command line to determine other files to pull in. The first rule is an unconditional match on product (could be anything) to fake the equivalent of "#include <FOO.xml>" (i'm not sure if i can, or it's advisable to use a "<class>" here instead?) The other two are custom rules that parse the kernel command line looking for a site designation and a node-type designation to include those specific profile files. I am initially testing this on a USB Key i built using 'mksusebootdisk'. My understanding is that if i placed this rules file on the USB key's VFAT filesystem as '/cf/rules/rules.xml' and boot with: linux autoyast=usb:///cf/ ZORKsite=site1 ZORKnode=ingest That the autoyast system should detect that "/cf" is a directory, it should then look for /cf/rules/rules.xml, it should find it, load and process it and should then include my "base" profile and the two files that match the site and node type. (i.e. it shouldn't require anything other than /cf/rules/rules.xml and the files i ultimately include, which would be in /cf/) I am, however, getting an error that the profile couldn't be loaded. I want to verify that i am using the proper autoyast pathing syntax above and that i understand the loading and parsing process as stated in the previous paragraph. I.E. is what i'm trying to do a correct and/or advisable way to use a rules file to parse the command line as the primary means of pulling the rest of the configurations into play? Secondarily, i wanted to test this stuff out using a virtual machine, but the virtual machine manager wants to be TOO helpful. Apparently, it will accept an "AutoYast" statement that can ONLY be a single profile file. (autoinst.xml), not a directory, therefore no rules can be run. What i tried, instead, was to create an ext2 disk image containing my autoyast setup, and put "autoyast=device:xvdc/cf" into the kernel line. Only the VM creation wizard sees the "autoyast" directive, pulls it from the kernel line, and then tries to handle it itself in the same way, and fails. Is there a method of doing what i want using the standard SLES10 XEN virtual machine management functions so i can test this setup without having to venture down to the machine room with USB key in hand to find that something's still wrong? My rules.xml file is included below: Thanks, --stephen P.S. If i put 'autoyast=usb:///cf/rules/rules.xml' autoyast DOES find the file, but it doesn't work. Initially i noticed a failure, because i was using "PATH=/sbin:/usr/sbin:$(getconf PATH)" and surprisingly 'getconf' isn't on the boot media install environment :-( Also, does the install "shell" support POSIX 'printf' instead of 'echo -n'? ------------------------------------------------------------------------------------------------- <?xml version="1.0"?> <!DOCTYPE autoinstall> <autoinstall xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns">  <rules config:type="list">   <rule> <product> <match>*</match> <match_type>exact</match_type> </product> <result> <profile>ZORK_base.xml</profile> <continue config:type="boolean">true</continue> </result> </rule>  <rule> <custom1> <script> <![CDATA[ #!/bin/sh # Determine which SITE we are being installed at PATH="/bin:/sbin:/usr/bin:/usr/sbin" # Get a Kernel Command Line option. return value (after =) # or the command line option if it takes no arguments getkernopt() { sed -e 's/^.*$'$1'=\?[^[:space:]]*$.*$/\1/;s/^[^=]*=//' /proc/cmdline } zorksite="$(getkernopt ZORKsite)" if [ -z "${zorksite}" ]; then echo "ERROR_SITE_NOT_SPECIFIED (kernel command line=[$(cat /proc/cmdline)])" 1>&2 else echo -n "${zorksite}" fi ]]> </script> <match>*</match> <match_type>exact</match_type> </custom1> <result> <profile>ZORKsite-@custom1@.xml</profile> <continue config:type="boolean">true</continue> </result> </rule>  <rule> <custom2> <script> <![CDATA[ #!/bin/sh # Determine which NODE we are being installing as PATH="/bin:/sbin:/usr/bin:/usr/sbin" # Get a Kernel Command Line option. return value (after =) # or the command line option if it takes no arguments getkernopt() { sed -e 's/^.*$'$1'=\?[^[:space:]]*$.*$/\1/;s/^[^=]*=//' /proc/cmdline } PATH=/bin:/sbin:/usr/bin:/usr/sbin zorknode="$(getkernopt ZORKnode)" if [ -z "${zorknode}" ]; then echo "ERROR_NODE_NOT_SPECIFIED (kernel command line=[$(cat /proc/cmdline)])" 1>&2 else echo -n "${zorknode}" fi ]]> </script> <match>*</match> <match_type>exact</match_type> </custom2> <result> <profile>ZORKnode-@custom2@.xml</profile> <continue config:type="boolean">true</continue> </result> </rule> </rules> </autoinstall> ------------------------------------------------------------------------------------------------- -- Stephen Dowdy - Systems Administrator - NCAR/RAL 303.497.2869 - sdowdy(a)ucar.edu - http://www.ral.ucar.edu/~sdowdy/ -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

3 6

[opensuse-autoinstall] NFS installation fails
by Ivan De Masi 21 Jan '10

21 Jan '10

Hello, I'm trying to install from a nfs repository. The client is booting over the network with tftp and has this arguments submitted: label install openSUSE 11.1 kernel linux append initrd=initrd splash=silent vga=0x314 showopts autoyast=http://192.168.0.111/autoyast/test1.xml hostip=192.168.0.14/24 gateway=192.168.0.254 nameserver=130.83.22.60 install=nfs://192.168.0.250/install/openSUSE_11.1_i568/ I always get the error that the openSUSE repository could not be found. That's some kind of strange because on my "normal" machine I can mount the directory "install". For tftp-boot I'm using linuxrc V.3.4.7 with Kernel 2.6.31.4-3-default. Is installation via nfs still broken like in 11.0? Regards, Ivan -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 3

[opensuse-autoinstall] withiSCSI=1 install 2nd stage network shutdown ?
by D. Bahi 21 Jan '10

21 Jan '10

Hello folks, Installing to a network disk works well with 1st stage - but the 2nd stage restarts networking... and this doesn't seem like a good thing when running over a network disk.... Shutting down (localfs) network interfaces: eth0 device : .... No configuration found for eth0 Nevertheless the interface will be shut down. eth0 done Shutting down service (localfs) network . . . done Ideas for a workaround please ? Thank you db -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

3 6

[opensuse-autoinstall]
by Stefan.Dursch＠gmx.de 19 Jan '10

19 Jan '10

hm i can´t belive that the this part is not relevant in stage1. <net-udev config:type="list"> <rule> <rule>ATTR{address}</rule> <value>customermac</value> <name>eth2</name> </rule> <rule> <rule>ATTR{address}</rule> <value>dhcpmac</value> <name>eth0</name> </rule> </net-udev> so i did an installation with and without this part. With this part after stage1 and the reboot the system came up and would begin with stage2, but the error "cannot access installation media" occurs. I could access console and could see the following in boot.msg: eth1 renamed to eth2 by udev eth0 renamed to eth3 by udev with ifconfig i saw the following: eth0 HWaddr dhcpmac eth1 HWaddr othermac eth2 HWaddr dhcpmac eth3 HWaddr othermac So eth0 and eth2 had the same mac? and the interface with my customermac was not present, but it should be eth2. with dhcp-test eth0 i got an ip for eth0 from my dhcpserver, over eth2 not. The /etc/udev/rules.d/70-persistant-net.rules file looked like this: # Generated by autoyast # program run by the persistent-net-generator.rules rules file. # # You can modify it, as long as you keep each rule on a single line. SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="customermac", NAME="eth2" SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="dhcpmac", NAME="eth0" # PCI device 0x8086:0x105e (e1000e) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="ohtermac", ATTR{type}=="1", KERNEL=="eth*", NAME="eth3" # PCI device 0x14e4:0x164c (bnx2) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="ohtermac", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1" Without the net-udev part everything worked, but i had no persistant eth0 and eth2. any ideas? on Monday 18 January 2010 Stefan.Dursch(a)gmx.de wrote: > These are the relevant parts of my networking section: this is not relevant in your case. The <networking> configuration happens later. Yast2 ist configuring the network with the data of the XML file in stage2. You don't reach that point currently. > When i boot up via dhcp i get the dhcprequest over eth2, Installation > starts, everything looks good, but after first reboot it goes: so you get a networking config in stage1 but the same config does not work in stage2? > So for second stage i get no network and yast fails with "cannot access > installation media" In the logfile i can see save_network.ycp writes befor > the reboot a file ifcfg-eth2 like this: BOOTPROTO='dhcp4' > LLADDR=dhcpmac > STARTMODE='oneboot' the <networking> section is read from the XML file and configured in the second stage. In your case the installation network can not be started for some reason (it worked in stage1) because the eth2 interface gets no IP address from the dhcp server. Can you see something in the log of the dhcp server? -- ciao, Uwe Gansert Uwe Gansert SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Business: http://www.suse.de/~ug -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org -- GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

3 2

[opensuse-autoinstall] sles11 and net persistent names
by Stefan.Dursch＠gmx.de 19 Jan '10

19 Jan '10

Hi List, i am trying to rename ethdevicesnames with AY while installing over pxe/dhcp/http. Sles11 on a HP DL380 G5 with to internal NIC´s and one additional PCI dual-port NIC. I have 2 cables pluged in, one for dhcplan and one for customerlan. I would have after boot of second stage the dhcplan on eth0 and the customerlan on eth2, because of some initscripts, routes and so on. These are the relevant parts of my networking section: <networking> <interfaces config:type="list"> <interface> <bootproto>static</bootproto> <startmode>auto</startmode> <device>eth2</device> <usercontrol>no</usercontrol> <ipaddr>ipcustom</ipaddr> <netmask>255.255.255.0</netmask> <ethtool_options>autoneg off speed 100 duplex full</ethtool_options> </interface> <interface> <bootproto>static</bootproto> <startmode>auto</startmode> <device>eth0</device> <usercontrol>no</usercontrol> <ipaddr>ipdhcp</ipaddr> <netmask>255.255.255.0</netmask> <ethtool_options>autoneg off speed 100 duplex full</ethtool_options> </interface> </interfaces> <net-udev config:type="list"> <rule> <rule>ATTR{address}</rule> <value>customermac</value> <name>eth2</name> </rule> <rule> <rule>ATTR{address}</rule> <value>dhcpmac</value> <name>eth0</name> </rule> </net-udev> </networking> When i boot up via dhcp i get the dhcprequest over eth2, Installation starts, everything looks good, but after first reboot it goes: Setting up (localfs) network interfaces: lo lo IP address: 127.0.0.1/8 IP address: 127.0.0.2/8 done eth0 device: Broadcom Corporation NetXtreme II BCM5708 Gigabit Ethernet (rev 12) No configuration found for eth0 unused eth1 device: Broadcom Corporation NetXtreme II BCM5708 Gigabit Ethernet (rev 12) No configuration found for eth1 unused eth2 device: Broadcom Corporation NetXtreme II BCM5706 Gigabit Ethernet (rev 02) eth2 Starting DHCP4 client. . . . . . . . eth2 DHCP4 continues in background waiting eth3 device: Broadcom Corporation NetXtreme II BCM5706 Gigabit Ethernet (rev 02) No configuration found for eth3 unused Waiting for mandatory devices: eth2 __NSC__ 11 10 8 7 6 5 3 2 1 eth2 device: Broadcom Corporation NetXtreme II BCM5706 Gigabit Ethernet (rev 02) eth2 DHCP4 client (dhcpcd) is running eth2 . . . but is still waiting for data waiting eth2 interface could not be set up until now failed Setting up service (localfs) network . . . . . . . . . . failed *** Starting YaST2 *** So for second stage i get no network and yast fails with "cannot access installation media" In the logfile i can see save_network.ycp writes befor the reboot a file ifcfg-eth2 like this: BOOTPROTO='dhcp4' LLADDR=dhcpmac STARTMODE='oneboot' /etc/udev/rules.d/70-persistent-net.rules is configured right by AY. Iam doing something wrong? Or is it not possible to set persistent names with AT? Thanks for help, Stefan -- Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla Firefox 3.5 - sicherer, schneller und einfacher! http://portal.gmx.net/de/go/chbrowser -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 1

[opensuse-autoinstall] Installing RPMs with missing dependencies
by Enamul Haque 15 Jan '10

15 Jan '10

I am trying to integrate Dell OpenManage 6.2 storage component to my PXE image. Storage RPMs don't have dependencies setup properly. Therefore, AutoYast installs the RPMs in a random order, and OpenManage setup fails. Is there a way to make AutoYast to install a group of RPMs in a certain order during PXE image? TIA, Enamul -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

3 2

[opensuse-autoinstall] Generic boot and installation environment
by Hans-Joachim Ehlers 14 Jan '10

14 Jan '10

SGkNCmkgd291bGQgbGlrZSB0byBlbmhhbmNlIG91ciBsaW51eCBpbnN0YWxsYXRpb24gZW52aXJvbm1lbnQgdG8gc3VwcG9ydCBtb3JlIHRhcmdldCBjb25maWd1cmF0aW9uIHN0YXJ0aW5nIGZyb20gbmV0d29yayB0byBpbnN0YWxsZWQgc29mdHdhcmUuDQpBbHNvIHdlIGhhdmUgYW4gb2ZmbGluZSBlbnZpcm9ubWVudCB3aGljaCB3aWxsIGhhdmUgdGhlIHNhbWUgaW5zdGFsbGF0aW9uIGVudmlyb25tZW50IGJ1dCBkaWZmZXJlbnQgSVAgYWRkcmVzc2VzLg0KDQpUbyBzb2x2ZSB0aGUgbmV3IHJlcXVpcmVtZW50IEkgdGhvdWdodCBvZiB1c2luZyBESENQIHRvIHByb3ZpZGUgSW5mb3JtYXRpb24gYWJvdXQgdGhlIGZpbmFsIHRhcmdldC4gVGhpcyBpbmZvcm1hdGlvbiBpcyB1c2VkIGluIGFuIGluaXQtc2NyaXB0IHRvIGZpbmFsemUgdGhlIGluc3RhbGxhdGlvbg0KDQpFeGFtcGxlOg0KZGhjcHNkLmNvbmYNCg0KY2xpZW50IDEgMTAuMC4wLjENCiB7DQogLSBvcHRpb24gMjI0IE1hcmtldGluZw0KIH0NCmNsaWVudCAxIDEwLjAuMC4yDQogew0KIC0gb3B0aW9uIDIyNCBEZXZlbG9wbWVudA0KIH0NCg0KVGhpcyBpbmZvcm1hdGlvbiB3b3VsZCBiZSBwYXJzZWQgZnJvbSBhIHNjcmlwdCBhbmQgY29waWVkIHRvIHRoZSB0YXJnZXQgZHVyaW5nIGluc3RhbGxhdGlvbi4gT2YgY291cnNlIGFuIGV4dGVuZGVkIHJ1bGUueG1sIGNvdWxkIGJlIHVzZWQgYXMgd2VsbC4NCg0KQnV0IHRoZSBtYWluIHByb2JsZW0gaXMgd2l0aCB0aGUgb2ZmbGluZSBmYWNpbGl0eSB3aGljaCBoYXMgZGlmZmVyZW50IElQIG51bWJlcnMgYnV0IHRoZSBzYW1lIGluc3RhbGxhdGlvbiBzZXJ2ZXIgc3RydWN0dXJlOg0KDQpDdXJyZW50bHkgSSBoYXZlIGFuIGluZm8tZmlsZSBpbiB0aGUgaW5pdHJkIHRvIHByb3ZpZGUgYWxsIGF1dG95YXN0IGluZm9ybWF0aW9uLiBCdXQgdGhpcyBmaWxlIGNvbnRhaW5zIHRoZSBJUCBudW1iZXIgb2YgdGhlIEluc3RhbGxhdGlvbiBzZXJ2ZXINCg0KRXhhbXBsZToNCmNhdCBpbmZvLnNsMTExLng4Ng0KLi4uDQpuZXRkZXZpY2U6IGV0aDANCm5ldG1hc2s6IDI1NS4yNTUuMC4wDQpicm9hZGNhc3Q6IDEwLjAuMjU1LjI1NQ0KZ2F0ZXdheTogMTAuMC4wLjENCnNlcnZlcjogMTAuMC4wLjUNCiNBdXRveWFzdCBjb25maWd1cmF0aW9uDQphdXRveWFzdDogaHR0cDovLzEwLjAuMC41L2V4cG9ydC9zdXNlL3NsMTExL2F1dG9pbnN0YWxsLw0KDQpCVFc6IElzIHRoZSBzZXJ2ZXIgcGFyYW1ldGVyIHN0aWxsIG5lZWRlZCA/DQoNCk9uZSBzb2x1dGlvbiB3b3VsZCBiZSB0byBhIGhhdmUgc2VwYXJhdGUgcHhlIGNvbmYgZmlsZSBhbmQgcHJvdmlkaW5nIHRoZSBpbmZvcm1hdGlvbiBvbiB0aGUga2VybmVsIGNvbW1hbmQgbGluZS4NCg0KRXhhbXBsZToNCmNhdCAvdGZ0cGJvb3QvcHhlbGludXguY2ZnL0RFVi5zbDExMS14ODYuZ3JhcGhpYy5hdXRvDQouLi4NCkFQUEVORCBpbml0cmQ9c2wxMTEvaW5pdHJkLng4Ni5hdXRvIGF1dG95YXN0PTEwLjAuMC41Lw0KLi4uDQoNCmNhdCAvdGZ0cGJvb3QvcHhlbGludXguY2ZnL01BUktFVElORy5zbDExMS14ODYuZ3JhcGhpYy5hdXRvDQouLi4NCkFQUEVORCBpbml0cmQ9c2wxMTEvaW5pdHJkLng4Ni5hdXRvIGF1dG95YXN0PTE5Mi4xNjguMC4xLw0KDQpCdXQgSSB3b3VsZCBsaWtlIHRvIHByb3ZpZGUgdGhlIGluZm9ybWF0aW9uIHZpYSBESENQIHRodXMgZ2l2aW5nIGF1dG95YXN0IHRoZSBpbmZvcm1hdGlvbiBkeW5hbWljYWxseS4gVGh1cyBJIHdvdWxkIGhhdmUgYSBnZW5lcmljIGluc3RhbGxhdGlvbiBlbnZpcm9ubWVudC4NCg0KQW55IGlkZWFzID8NCg0KdGlhDQpIYWpvDQoNCg0KDQoNCi0tDQogSGFucy1Kb2FjaGltIEVobGVycw0KIFVOSVggU3lzdGVtcyBFbmdpbmVlcg0KIEVVTUVUU0FUDQogRXVtZXRzYXQtQWxsZWUgMQ0KIDY0Mjk1LCBEYXJtc3RhZHQsIEdlcm1hbnkNCiBUZWwgOiArNDkgNjE1MSA4MDctNzMwNw0KIG1haWx0bzpoYW5zam9hY2hpbS5laGxlcnNAZXVtZXRzYXQuaW50DQogaHR0cDovL3d3dy5ldW1ldHNhdC5pbnQNCg0K-- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.orgFor additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 3

[opensuse-autoinstall] Problems with MBR/bootloader & GRUB
by Stephen Dowdy 12 Jan '10

12 Jan '10

Summary: Getting GRUB into the MBR properly Structure of bootloader general attributes? Best layout for linux only filesystem? (let autoinstall put all partitions into extended partition or is there any benefit to Primary swap and/or boot these days?) After my autoinstall completes, the system reboots and reports "No operating system". I'm guessing this most likely means that the MBR has no usable boot code or perhaps the MBR can't get to a secondary loader. My *intent* is to install GRUB to the MBR, but i don't think that's happening. (i'm using plain disk device on PERC H/W RAID) Here's what i see on my Debian Lenny desktop system: # file -s /dev/sdd /dev/sdd: x86 boot sector; GRand Unified Bootloader, stage1 version 0x3, stage2 address 0x2000, stage2 segment 0x200; partition 1: ID=0x83, active, starthead 1, startsector 63, 8401932 sectors; partition 2: ID=0x82, starthead 0, startsector 8401995, 16787925 sectors; partition 3: ID=0x5, starthead 254, startsector 25189920, 260269065 sectors Okay, obviously, a GRUB MBR Here's what i see on the SLES device: # file -s dev-sda.64-secs dev-sda.64-secs: x86 boot sector; partition 1: ID=0xf, active, starthead 1, startsector 63, 163830807 sectors (i copied the first 64 sectors to my USB key with 'dd if=/dev/sda bs=512 count=64', so i can deal with at my desktop, rather than the noisy-cold machine room) zia:sdowdy3# strings - dev-sda.64-secs | grep -i grub /grub/stage2 /grub/menu.lst GRUB loading, please wait... GRUB Hmm, so at least *some* grub bits are there. (i was surprised to see no 'strings' binary in the SLES10 mini-root environment :-( ) zia:sdowdy3# grep -ab --only-matching GRUB dev-sda.64-secs 8388:GRUB 32641:GRUB zia:sdowdy3# dd if=/dev/sdd bs=512 count=64 | strings | grep -i grub GRUB /boot/grub/stage2 /boot/grub/menu.lst GRUB loading, please wait... # dd if=/dev/sdd bs=512 count=64 2>/dev/null | grep -ab --only-matching GRUB 383:GRUB 9034:GRUB >From the above, the GRUB strings show that it doesn't occur in the first sector for the SLES installed disk, but does on my desktop system. So, i suspect that the "generic_mbr" option is being applied? If it matters, here's what gets laid down in /boot on the target install system: ----------------------------------------------------------- [device.map] (hd2) /dev/disk/by-id/usb-SanDisk_SanDisk_Cruzer_452601117552995B (hd1) /dev/disk/by-id/scsi-360026b90491c7800129987450f5e5165 (hd0) /dev/disk/by-id/scsi-360026b90491c7800129987100c335daf ----------------------------------------------------------- [menu.lst] # Modified by YaST2. Last modification on Mon Jan 11 13:35:00 UTC 2010 default 0 timeout 10 ##YaST - generic_mbr gfxmenu (hd0,4)/message ##YaST - activate ###Don't change this comment - YaST2 identifier: Original name: linux### title SUSE Linux Enterprise Server 10 SP3 root (hd0,4) kernel /vmlinuz-2.6.16.60-0.54.5-smp root=/dev/disk/by-label/root ZORKsite=zork0 ZORKnode=in3 y2confirm resume=/dev/disk/by-id/scsi-360026b90491c7800129987100c335daf-part7 splash=silent showopts initrd /initrd-2.6.16.60-0.54.5-smp ###Don't change this comment - YaST2 identifier: Original name: failsafe### title Failsafe -- SUSE Linux Enterprise Server 10 SP3 root (hd0,4) kernel /vmlinuz-2.6.16.60-0.54.5-smp root=/dev/disk/by-label/root showopts ide=nodma apm=off acpi=off noresume edd=off 3 initrd /initrd-2.6.16.60-0.54.5-smp ----------------------------------------------------------- The comment in there referencing "generic_mbr" seems to defy what's listed in my bootloader section (below) <loader_type>grub</loader_type> <location>mbr</location> (at least i *think* i'm telling autoyast to put a grub bootloader into the MBR with that) The /var/adm/cache/autoinstall/installedSystem.xml says: <bootloader> <activate config:type="boolean">true</activate> <global config:type="list"> <global_entry> <key>timeout</key> <value config:type="integer">10</value> </global_entry> <global_entry config:type="boolean">true</global_entry> <global_entry config:type="boolean">true</global_entry>  </global> <initrd_modules config:type="list"> ... </initrd_modules> <loader_type>grub</loader_type> <location>mbr</location> <repl_mbr config:type="boolean">true</repl_mbr>  </bootloader> Here's my bootloader section: ----------------------------------------------------------- <bootloader> <global config:type="list"> <global_entry> <key>timeout</key> <value config:type="integer">10</value> </global_entry> <activate config:type="boolean">true</activate> <boot_mbr config:type="boolean">true</boot_mbr> </global> <activate config:type="boolean">true</activate> <loader_type>grub</loader_type> <location>mbr</location> <repl_mbr config:type="boolean">true</repl_mbr>  <initrd_modules config:type="list"> ... includes processor thermal fan jbd ext3 edd ... </initrd_modules> </bootloader> ----------------------------------------------------------- [Aside: while i see a few random examples showing a structure for the bootloader section like: <global_entry> <key>serial</key> <value>--unit=0 --speed=57600 --word=8 --parity=no --stop=1</value> </global_entry> The 'yast2 autoyast' GUI generates lines like: <serial>--unit=0 --speed=57600 --word=8 --parity=no --stop=1</serial> Which is correct, or are both? (and if so, which is preferred?) ] And here's my partitioning info: ----------------------------------------------------------- <partitioning config:type="list"> <drive> <device>/dev/sda</device> <initialize config:type="boolean">true</initialize> <use>all</use> <type config:type="symbol">CT_DISK</type> <partitions config:type="list"> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <mount>/boot</mount> <label>boot</label> <mountby config:type="symbol">label</mountby> <partition_id config:type="integer">131</partition_id> <fstopt>acl,user_xattr</fstopt> <size>256mb</size> <create config:type="boolean">true</create> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <mount>/</mount> <label>root</label> <mountby config:type="symbol">label</mountby> <partition_id config:type="integer">131</partition_id> <fstopt>acl,user_xattr</fstopt> <size>3gb</size> <create config:type="boolean">true</create> </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> <size>16gb</size> <create config:type="boolean">true</create> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <mount>/usr</mount> <label>usr</label> <mountby config:type="symbol">label</mountby> <partition_id config:type="integer">131</partition_id> <fstopt>acl,user_xattr</fstopt> <size>6gb</size> <create config:type="boolean">true</create> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <mount>/var</mount> <label>var</label> <mountby config:type="symbol">label</mountby> <partition_id config:type="integer">131</partition_id> <fstopt>nosuid,acl,user_xattr</fstopt> <size>8gb</size> <create config:type="boolean">true</create> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <mount>/opt</mount> <label>opt</label> <mountby config:type="symbol">label</mountby> <partition_id config:type="integer">131</partition_id> <fstopt>nosuid,acl,user_xattr</fstopt> <size>4gb</size> <create config:type="boolean">true</create> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <mount>/home</mount> <label>home</label> <mountby config:type="symbol">label</mountby> <partition_id config:type="integer">131</partition_id> <fstopt>nosuid,acl,user_xattr</fstopt> <size>8gb</size> <create config:type="boolean">true</create> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <mount>/tmp</mount> <label>tmp</label> <mountby config:type="symbol">label</mountby> <partition_id config:type="integer">131</partition_id> <fstopt>noexec,nosuid,acl,user_xattr</fstopt> <size>4gb</size> <create config:type="boolean">true</create> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <mount>/d2</mount> <label>d2</label> <mountby config:type="symbol">label</mountby> <partition_id config:type="integer">131</partition_id> <fstopt>noexec,nosuid,acl,user_xattr</fstopt> <size>max</size> <create config:type="boolean">true</create> </partition> </partitions> </drive> </partitioning> Thanks for any pointers, --stephen -- Stephen Dowdy - Systems Administrator - NCAR/RAL 303.497.2869 - sdowdy(a)ucar.edu - http://www.ral.ucar.edu/~sdowdy/ -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 2