March 2006 - openSUSE Autoinstall - openSUSE Mailing Lists

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

AutoYaST Reinstalls After First Boot
by Yuval Yaari 14 Mar '06

14 Mar '06

Hey, I'm experiencing some weird problems with AutoYaST and SuSE 9.3. My installation medium is CDs, and after autoyast reboots for the first time (i.e., after it finishes installing packages from CD1), it automatically reboots. The problem is, that it boots from the first CD again, which installs everything from scratch, and generally enters an infinite loop... Is there a way around this...? Possibly relevant is this line from isolinux.cfg: append initrd=initrd ramdisk_size=65536 autoyast=default instmode=cd usedhcp=0 Thanks, --Yuval

2 1

Autoyast and elilo.
by COMBERNOUS Fabien 14 Mar '06

14 Mar '06

Hello, I'm looking for documents about using elilo with autoyast. For me, the latest Autoyast Documentation put at http://www.suse.com/~ug/autoyast_doc/ looks not clear about autoyast and elilo specifics aspects. I have a "bootloader" section using grub working fine on i386 arch. I would like to have something near with elilo on ia64 arch. Does exist some informations about this point somewhere ? Google is not very helpfull this time. :/ BR, -- Fabien Combernous UNEDIC DPI - Soutien Infrastructure Lan 231, rue Clement Ader, 34173 Castelnau-le-lez Tél. 04 67 02 33 89

1 0

@SUSE: Improvement for /etc/init.d/autoyast
by Bernd Nies 14 Mar '06

14 Mar '06

Hi, An Autoyast improvement for future SUSE releases that would make setting up a host using Autoyast with post install scripts easier. Sort the scripts in /var/adm/autoinstall/init.d alphabetically before they are executed. So the order can be defined according to the runlevel scripts in /etc/init.d/rc?.d. ==CUT== start) # Remember status and be verbose for script in `find $INITSCRIPT_DIR -type f |sort`; do echo -n "Executing AutoYaST script: $script" BASENAME=`basename $script` sh -x $script 2&> $LOG_DIR/$BASENAME.log mv $script $SCRIPT_DIR rc_status -v done chkconfig autoyast off ;; ==CUT== Currently the execution order is undefined. Regards, Bernd

2 2

Autoinstallation from CD
by Hans 13 Mar '06

13 Mar '06

Hello all, I am trying to compile a CD to do an unattended setup using autoyast. I took CD1 from the Suse 10.0 cd's and added the following section to the boot/loader/isolinux.cfg file # Automatic Installer label autoyast kernel linux append initrd=initrd splash=silent showopts autoyast=file:///autoinst.xml textmode=1 The file autoinst.xml is ofcourse in the root of the CD When I select this option and press ENTER, then after a short while the following message appears: "Could not find the SUSE Linux Installation Source Activating manual setup program" When I boot from the CD and select this option, and then after pressing F3, I remove 'autoyast=file:///autoinst.xml', then the setup program can use this CD for installation, it won't complain about missing Installation Source. What am I doing wrong? Any hints appreciated, Hans

2 2

FYI - SLES10 incompatibility
by Uwe Gansert 13 Mar '06

13 Mar '06

Hi, I want to inform you, that we are going to have an incompatibility in the autoyast profile for SLES10 to older autoyast profiles like those for SLES9. SLES10 no longer supports "selections" but uses "patterns" now. Autoyast will not be able to convert selections into patterns and so you have to do that on your own. So if you want to use a SLES9 autoyast profile to install a SLES10 server, you have to change the <software> section from selections to patterns. That means, you have to remove all <addon> entries and the <base> entry. Patterns are configured like this: <software> <patterns config:type="list"> <pattern>directory_server</pattern> <pattern>...</pattern> </patterns> </software> SLES10 will always install a minumum set of software, so even with an empty <software> section in the autoyast profile, you'll be able to install a SLES10. It's recommended to use the autoyast UI that comes with SLES10 to configure your profile with patterns. From the autoyast point of view, patterns are quite similar to selections but not every selection has an equivalent pattern - that's why autoyast will not convert between those values. The <packages> section is still the same and will work. SUSE Linux 10.1 still supports selections. If you want to use the same profile for SLES and for SUSE Linux, you must use rules to deal with two separate <software> sections, depending on the product you install at the moment. If you have questions, feel free to ask here on the mailinglist. Here is the list of patterns that exist for SLES10 Beta7. That list might change but I hope you get an impression what patterns are: Basis-Devel WBEM apparmor base ccb default dhcp_dns_server directory_server file_server gateway_server gnome ha_sles kde lamp_server mail_server oracle_server print_server sap_server x11 xen_server -- 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

Where are instorder and order in SLES 10?
by ? 13 Mar '06

13 Mar '06

In SLES previous release, there always is a 'yast' directory under the CD root directory, and there are instorder and order in this directory. But in SLES10, I cannot find them. Are they obsolete? If so, how can SLES10 install future SP via NFS. Where can I get those documents that introduce the new feature of autoyast in SLES10? Many thanks. _________________________________________________________________ 免费下载 MSN Explorer: http://explorer.msn.com/lccn/

2 1

Re: [suse-autoinstall] Problem with Nvidia and Dell Display
by Hans-Joachim Ehlers 13 Mar '06

13 Mar '06

With an IBM graphic card we had an similar issue that with DVI the maximum resolution was lower then as with analog (VGA) So you might check the handbook fom your Graphic card to insure that it really able to to use certain resolution using the DVI. hth Hajo >>> "mailing list" <fzmailinglist(a)googlemail.com> 13/03/2006 09:36 >>> hi, i have a problem with a few workstations over here. The workstations have Nvidia Quadro FX 540 graphix cards, and Dell 1905FP LCD Displays. I setup everything in my autoyast installation. Here is how: <color_depth config:type="integer">16</color_depth> <configure_x11 config:type="boolean">true</configure_x11> <display_manager>kdm</display_manager> <enable_3d config:type="boolean">true</enable_3d> <monitor> <display> <frequency config:type="integer">60</frequency> <height config:type="integer">1024</height> <max_hsync config:type="integer">82</max_hsync> <max_vsync config:type="integer">62</max_vsync> <min_hsync config:type="integer">31</min_hsync> <min_vsync config:type="integer">58</min_vsync> <width config:type="integer">1280</width> </display> <monitor_device>1280X1024@60HZ</monitor_device> <monitor_vendor>--> LCD</monitor_vendor> </monitor> <resolution>1280x1024</resolution> <window_manager>kde</window_manager> </x11> If i use a Analog Cable VGA Cable everything works ok. The workstation comes up with 1280x1024, but if i use a Digital DVI Cable, it comes up with 1024x768. I can do what i want it doesnt work. Any suggestions or tips? mfg Florian Zuegner Junior Network Assistance Honda Research Institute Europe GmbH

2 1

Autoinstallation from CD
by Hans 13 Mar '06

13 Mar '06

Hello all, I am trying to compile a CD to do an unattended setup useing autoyast. I took CD1 from the Suse 10.0 cd'a and changed the boot/loader/isolinux.cfg file so that the following options are added to the boot-options: autoyast=file:///autoinst.xml The file autoyast.xml is ofcourse in the root of the CD Now, when the PC boots from this CD, the following message appears: Could not find the SUSE Linux Installation Source Groeten, Hans Bouwers

1 0

Problem with Nvidia and Dell Display
by mailing list 13 Mar '06

13 Mar '06

hi, i have a problem with a few workstations over here. The workstations have Nvidia Quadro FX 540 graphix cards, and Dell 1905FP LCD Displays. I setup everything in my autoyast installation. Here is how: <color_depth config:type="integer">16</color_depth> <configure_x11 config:type="boolean">true</configure_x11> <display_manager>kdm</display_manager> <enable_3d config:type="boolean">true</enable_3d> <monitor> <display> <frequency config:type="integer">60</frequency> <height config:type="integer">1024</height> <max_hsync config:type="integer">82</max_hsync> <max_vsync config:type="integer">62</max_vsync> <min_hsync config:type="integer">31</min_hsync> <min_vsync config:type="integer">58</min_vsync> <width config:type="integer">1280</width> </display> <monitor_device>1280X1024@60HZ</monitor_device> <monitor_vendor>--> LCD</monitor_vendor> </monitor> <resolution>1280x1024</resolution> <window_manager>kde</window_manager> </x11> If i use a Analog Cable VGA Cable everything works ok. The workstation comes up with 1280x1024, but if i use a Digital DVI Cable, it comes up with 1024x768. I can do what i want it doesnt work. Any suggestions or tips? mfg Florian Zuegner Junior Network Assistance Honda Research Institute Europe GmbH

1 0