August 2004 - openSUSE Autoinstall - openSUSE Mailing Lists

[Fwd: Re: [suse-autoinstall] Additional rpm packages are not found on media? (error 11283)]
by Stephan A. Rickauer 03 Sep '04

03 Sep '04

Hard to believe, but it works! Thanks Jan. However, it would be really helpful to know, why it has to be i586 and not "noarch". Furthermore, I'd like to specify my own subdirs, like "uni" or something similar ... isn't that possible? Stephan A. Rickauer ---------------------------- Institut für Neuroinformatik IT-Koordinator Universität / ETH Zürich Winterthurerstr. 190 CH-8057 Zürich Tel: +41 1 635 30 50 Sek: +41 1 635 30 52 Fax: +41 1 635 30 53 http://www.ini.unizh.ch ------------------------ Jan-Marc Pilawa wrote: > Schon probiert die rpms in i586 abzulegen? Meine habe ich dort angelegt und > genau das getan, was in der Mail beschrieben stand. > > Mit freundlichen Gruessen / Sincerely > > Jan Pilawa > -------- Original Message -------- Subject: Re: [suse-autoinstall] Additional rpm packages are not found on media? (error 11283) Date: Thu, 8 Jul 2004 14:22:12 +0200 From: Jan-Marc Pilawa <j.pilawa(a)tu-bs.de> Organization: Rechenzentrum To: Stephan A. Rickauer References: <40ED38D7.7020101(a)ini.phys.ethz.ch> Schon probiert die rpms in i586 abzulegen? Meine habe ich dort angelegt und genau das getan, was in der Mail beschrieben stand. Mit freundlichen Gruessen / Sincerely Jan Pilawa -- + Kontakt ----------------------------------------------------+ + Systembetreuung Rechenzentrum TU Braunschweig + + Hans-Sommer-Str. 65, D-38092 Braunschweig + + Tel: +49 531 391-5548 E-Mail: j.pilawa(a)tu-bs.de ____________+

3 6

X11 configuration, SLES8
by Oliver Schwabedissen 02 Sep '04

02 Sep '04

Hello, I have a problem with configuring X11 when installing SLES8. I want to configure X11, but don't want KDE to start when the server comes up. So I configured runlevel 3 and X11 like this: [...] <runlevels> <default>3</default> </runlevels> <x11> <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">false</enable_3d> <monitor> <display> <max_hsync config:type="integer">60</max_hsync> <max_vsync config:type="integer">60</max_vsync> <min_hsync config:type="integer">31</min_hsync> <min_vsync config:type="integer">30</min_vsync> </display> <monitor_device>1024X768@60HZ</monitor_device> <monitor_vendor>LCD</monitor_vendor> </monitor> <resolution>1024x768</resolution> <start_x11 config:type="boolean">false</start_x11> </x11> </configure> However, when autoinstall finishes the system boots to runlevel 5, which is now also the default runlevel in /etc/inittab. Why does autoyast ignore my configured runlevel? Doesn't <start_x11 config:type="boolean">false</start_x11> mean that X11 should not be started automatically? I'm starting installation by booting from SP3 CD1 with an info file on floppy. It then connects to the installation server through NFS. Oliver -- Superg�nstige DSL-Tarife + WLAN-Router f�r 0,- EUR* Jetzt zu GMX wechseln und sparen http://www.gmx.net/de/go/dsl

1 1

SLES9 bootloader for PPC iSeries
by Carl Pecinovsky 31 Aug '04

31 Aug '04

Hi. I'd just like to post notice of a difference between SLES8 and SLES9 autoyast that needs to be configured for iSeries PPC (power4) logical partitions. For installing SLES8, I can get away with a simple bootloader section: <bootloader> <activate config:type="boolean">false</activate> <location>/dev/hda1</location> </bootloader> The booting is actually controlled by an i5/OS instance running that is hosting the disk. But without any hardware change, if I try to install SLES9, the above doesn't work. I get a message within i5/OS stating: "--0007: IPL source not valid." I used YaST to output a CHRP bootloader section which works fine after a little tweaking, but it is quite long: <bootloader> <activate config:type="boolean">true</activate> <board_type>chrp</board_type> <default>linux</default> <global config:type="list"> <global_entry> <key>timeout</key> <value config:type="integer">100</value> </global_entry> <global_entry> <key>boot</key> <value>/dev/iseries/vda1</value> </global_entry> <global_entry> <key>activate</key> <value config:type="boolean">true</value> </global_entry> <global_entry> <key>default</key> <value>linux</value> </global_entry> </global> <initrd_modules config:type="list"> <initrd_module> <module>ipr</module> </initrd_module> <initrd_module> <module>iseries_veth</module> </initrd_module> </initrd_modules> <loader_device>/dev/iseries/vda1</loader_device> <loader_type>ppc</loader_type> <location>boot</location> <of_defaultdevice config:type="boolean">false</of_defaultdevice> <prep_boot_partition>/dev/iseries/vda1</prep_boot_partition> <sections config:type="list"> <section config:type="list"> <section_entry> <key>image</key> <value>/boot/vmlinux</value> </section_entry> <section_entry> <key>label</key> <value>linux</value> </section_entry> <section_entry> <key>root</key> <value>/dev/iseries/vda3</value> </section_entry> <section_entry> <key>initrd</key> <value>/boot/initrd</value> </section_entry> <section_entry> <key>append</key> <value>selinux=0 elevator=cfq</value> </section_entry> </section> </sections> </bootloader> I wonder if this section can be cut down, or what all the options mean (like <of_defaultdevice>)? Carl Pecinovsky (507) 253-3861, TL: 553-3861, email: csky(a)us.ibm.com "It is never safe to look into the future with eyes of fear." --E.H Harriman

2 1

autoyast=defualt not working
by Schwartz, Matthew (MED) 30 Aug '04

30 Aug '04

In the isolinux.cfg file I added the following lines: #auto yast label Autoinstall kernel linux append initrd=initrd ramdisk_size=65536 autoyast=default netsetup=0 instmode=cd I then added my autoinst.xml file to the root partition on the DVD (Suse9.1), however I get a error message saying it can't find the control file?? However if I change autoyast=default to autoyast=device://hdc/autoinst.xml it works, however the on some system the DVD-ROM is not hdc.. Matthew

1 0

Variables in control file
by Martijn Dekkers 29 Aug '04

29 Aug '04

Hi all, I would like to know how to use (system) variables in the control file - I need to use the asset tag of the systems as the system hostname, and it is not immediatly obvious from the docs and examples how to do this. I have a one-line shell script that uses hwinfo to get the asset tag, but I am not sure how to get this into the control file. I am using suse9.1 on the clients and sles9 on the server. I tried searching on google, and the archives, but no luck. Any help would be appreciated. Cheers, Martijn

1 0

Post Install script and the Location element
by leonard.jacobsen＠usbank.com 29 Aug '04

29 Aug '04

I'm having some problems getting the "location" element to work in my control file. It appears that the post-scripts section is unable to retrieve the shell script, however, if I use the URL listed in the control file and pass it to 'curl', I am able to retrieve the contents just fine. I have tried using NFS and HTTP, but they both have the same issue. The following is what is defined in my control file <scripts> <post-scripts config:type="list"> <script> <interpreter>shell</interpreter> <location>http://192.168.2.2/post-install.sh</location> </script> </post-scripts> </scripts> Here is a snippit from /var/log/YaST2/y2log 2004-08-27 12:08:37 <1> slestest(1316) [YCP] AutoinstScripts.ycp:440 Writing script into /var/adm/autoinstall/scripts/post-scripts 2004-08-27 12:08:37 <1> slestest(1316) [agent-curl] CurlAgent.cc(Execute):209 Data: 2004-08-27 12:08:37 <1> slestest(1316) [agent-curl] CurlAgent.cc(Execute):210 Output: /var/adm/autoinstall/scripts/post-scripts 2004-08-27 12:08:37 <3> slestest(1316) [agent-curl] CurlAgent.cc(Get):70 curl told us 7 2004-08-27 12:08:37 <3> slestest(1316) [YCP] autoinstall/io.ycp:69 Can't find URL: http://192.168.2.2/post-install.sh 2004-08-27 12:08:37 <3> slestest(1316) [YCP] AutoinstScripts.ycp:445 script http://192.168.2.2/post-install.sh could not be retrieved 2004-08-27 12:08:37 <1> slestest(1316) [YCP] AutoinstScripts.ycp:475 Script Execution command: /bin/sh -x /var/adm/autoinstall/scripts/post-scripts 2&> /var/adm/autoinstall/logs/post-scripts.log Does anyone have any ideas? This is driving me crazy that I cant get something this simple working :) Thanks. Len. ------------------------------------------------------------------------------ Electronic Privacy Notice. This e-mail, and any attachments, contains information that is, or may be, covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, and is also confidential and proprietary in nature. If you are not the intended recipient, please be advised that you are legally prohibited from retaining, using, copying, distributing, or otherwise disclosing this information in any manner. Instead, please reply to the sender that you have received this communication in error, and then immediately delete it. Thank you in advance for your cooperation. ==============================================================================

1 0

Post & chroot scripts
by Penney, Christopher (C.) 25 Aug '04

25 Aug '04

I've looked at the documentation at http://www.suse.de/~nashif/autoinstall/ as well as a few examples and I still can't quite figure out the right way to get these scripts to work. They appear to simply not be running. For example, I have the following xml in a SuSE 9.0 build script: <configure> <scripts> <chroot-scripts config:type="list"> <script> <filename>chroot.sh</filename> <interpreter>shell</interpreter> <source> <![CDATA[#!/bin/sh df > /test df > /mnt/test df | rsh 10.6.1.1 dd of=/tmp/test ]]> </source> </script> </chroot-scripts> </scripts> ... I don't think it ever runs. I don't see the file in / or /mnt nor does the rsh work. I've tried it both chroot and post. I also have a question about the chroot script. Am I right to assume that the system is all contained under /mnt when it's executed? The documentation wasn't completely clear to me. Thanks Chris

2 1

Re: [suse-autoinstall] AutoInstall and Western Digital HDD issues.
by Anthony Staples 25 Aug '04

25 Aug '04

Anas, I will check on the email situation... sorry for the inconvenience... Humana has some sort of filtering, so who knows what it is blocking... And I will see about getting the logs from 3rd console or by redirection Cheers, Tony Anas Nashif <nashif(a)planux.c To: Anthony Staples <astaples(a)humana.com> om> cc: dvosburg(a)novell.com, lmarks(a)novell.com, Mike Robinson <mrobinson(a)humana.com>, pgriffen(a)novell.com, suse-autoinstall(a)suse.com, 08/25/2004 03:12 swilson(a)novell.com PM Subject: Re: [suse-autoinstall] AutoInstall and Western Digital HDD issues. Anthony, For some reason, my direct emails to you do not reach you. Can you please check whats going on. Problem cant be on my side, cause everybody else seems to receive my emails. I am sending this email using a different account hoping it will reach you. I need logs from the setup which is not working. You can always get the logs during installation by switching to 3rd console. An alternative is to boot with logserver=<log server ip> and have a remote machine with syslog capture the messages from the installed client. Regards, Anas Anthony Staples wrote: > > > > Anas, > > When the install fails, /dev/hda2 is not formatted and so nothing is really > written to it. > I forgot to mention in my previous post that the SWAP is created (8GB for > some reason), but / is not. That is where the format step fails. > Is there a facility to redirect logging to the NFS repository? > > Cheers, > Tony > > > > > Anas Nashif > <nashif(a)suse.de> To: Anthony Staples <astaples(a)humana.com> > cc: suse-autoinstall(a)suse.com, lmarks(a)novell.com, pgriffen(a)novell.com, > 08/25/2004 12:42 swilson(a)novell.com, dvosburg(a)novell.com, Mike Robinson <mrobinson(a)humana.com> > PM Subject: Re: [suse-autoinstall] AutoInstall and Western Digital HDD issues. > > > > > > > > Anthony, > Can you please provide the log files for a failed installation? > > Thanks, > Anas > > Anthony Staples wrote: > >> >> >>Anas, >> >>RE: Strange behavior regarding Autoinstall and some Western Digital HDDs: >> >>I am trying to develop an autoinstall for NLD 1.6 using a boot cd and an >>NFS repository. >>I have three machines that I am using for testing of autoinstall >>deployments. All are Dell GX60s with 40GB WD HDD, 512 MB RAM and Cereron >>2.2Ghz CPUs. All have been updated to the latest DELL GX60 Bios (A08). >> >>As I have posted previously, I have not been able to get any control > > files > >>built on my primary test PC to work correctly on the other two units. >>Autoinstall always fails during the format phase on these other two > > units, > >>and so the install does not complete. Here is the text of the error. >> >>"Could not format /dev/hda2. you can continue if you know what you are >>doing, but, to prevent damage to your filesystems, it is safer to cancel >>and reboot" >> >>I have tried many different approaches from explicitly setting the >>partition scheme to using the most generic scheme outlined in the >>documentation. >>Each time, the control file works as planned on my primary machine, but >>fails on the other two test units. >> >>Yesterday, Tuesday, 8/24/2004, I had Steve Wilson and Don Vosburg from >>Novell in to help me troubleshoot and possibly solve this conundrum. >>Together we went thru all the different iterations of control files I had >>tried and some that Don came up with on the spot to try and make >>partitioning work on the secondary test machines. We rec'd the same >>results I had encountered over and over. Finally, as a last effort, we >>switched the hard drive in the "good" primary unit with the hard drive in >>one of the "bad" secondary units. This switch cause the two machines to >>exchange behavior. On closer inspection of the HDD we switched out, they >>were not exactly identical. Though both are Western Digital 40GB HDD, > > the > >>model numbers differed slightly and they were manufactured in different >>countries... >> >>The "good" drive details from visual inspection and WD diagnostics: >>Completely black outer shell. >>Manufactured in Thailand >>M/N: WDC WD400BB-75FJA1 >>S/N: WD-WCAJC2052229 >>Firmware: 14.03G14 >>C H S : 77504 16 63 >>Drive 0, port 0x01F0 >>Build Date unknown >> >>The "bad" drive details from visual inspection and WD diagnostics: >>Black and silver outer shell >>Manufactured in Malaysia >>M/N: WDC WD400BB-75FRA0 >>S/N: WD-WMAJF1089739 >>Firmware: 77.07W77 >>C H S: 77504 16 63 >>Drive 0, port 0x01F0 >>Build Date: 8-JAN-04 >> >>The other failing test machine's drive was manufactured in Singapore... > > and > >>also has the black and silver outer shell. >> >>During the testing we also were able to recreate the issue using SLES 9.0 >>while performing a cdrom autoinstall to the "bad" secondary test unit. >> >>Manual installs do not seem encounter the issue. >> >>Autoinstalls seemed to ignore the partitioning info in the control files > > on > >>the secondary test machines. >> >>I have attached many of the autoinstall control files I have used during > > my > >>testing and the testing done with Steve and Don from Novell. >> >> >>(See attached file: ay_006.xml)(See attached file: > > autoyast2_gx60.xml)(See > >>attached file: autoyast3_gx60.xml)(See attached file: >>autoyast_generic_gx60.xml)(See attached file: > > autoyast_refpro_gx60.xml)(See > >>attached file: ay_003.xml)(See attached file: ay_004.xml)(See attached >>file: ay_005.xml) >> >>Anyone's insights appreciated!!! >>If other info is needed please let me know, I will be happy to provide >>whatever I can . >> >>Cheers, >>Tony >> >> >> >>The information transmitted is intended only for the person or entity to > > which it is addressed and may contain CONFIDENTIAL material. If you > receive this material/information in error, please contact the sender and > delete or destroy the material/information. > > -- > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > For additional commands, e-mail: suse-autoinstall-help(a)suse.com > > > > > > > The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information. The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.

1 0

Re: [suse-autoinstall] AutoInstall and Western Digital HDD issues.
by Anthony Staples 25 Aug '04

25 Aug '04

Anas, When the install fails, /dev/hda2 is not formatted and so nothing is really written to it. I forgot to mention in my previous post that the SWAP is created (8GB for some reason), but / is not. That is where the format step fails. Is there a facility to redirect logging to the NFS repository? Cheers, Tony Anas Nashif <nashif(a)suse.de> To: Anthony Staples <astaples(a)humana.com> cc: suse-autoinstall(a)suse.com, lmarks(a)novell.com, pgriffen(a)novell.com, 08/25/2004 12:42 swilson(a)novell.com, dvosburg(a)novell.com, Mike Robinson <mrobinson(a)humana.com> PM Subject: Re: [suse-autoinstall] AutoInstall and Western Digital HDD issues. Anthony, Can you please provide the log files for a failed installation? Thanks, Anas Anthony Staples wrote: > > > > Anas, > > RE: Strange behavior regarding Autoinstall and some Western Digital HDDs: > > I am trying to develop an autoinstall for NLD 1.6 using a boot cd and an > NFS repository. > I have three machines that I am using for testing of autoinstall > deployments. All are Dell GX60s with 40GB WD HDD, 512 MB RAM and Cereron > 2.2Ghz CPUs. All have been updated to the latest DELL GX60 Bios (A08). > > As I have posted previously, I have not been able to get any control files > built on my primary test PC to work correctly on the other two units. > Autoinstall always fails during the format phase on these other two units, > and so the install does not complete. Here is the text of the error. > > "Could not format /dev/hda2. you can continue if you know what you are > doing, but, to prevent damage to your filesystems, it is safer to cancel > and reboot" > > I have tried many different approaches from explicitly setting the > partition scheme to using the most generic scheme outlined in the > documentation. > Each time, the control file works as planned on my primary machine, but > fails on the other two test units. > > Yesterday, Tuesday, 8/24/2004, I had Steve Wilson and Don Vosburg from > Novell in to help me troubleshoot and possibly solve this conundrum. > Together we went thru all the different iterations of control files I had > tried and some that Don came up with on the spot to try and make > partitioning work on the secondary test machines. We rec'd the same > results I had encountered over and over. Finally, as a last effort, we > switched the hard drive in the "good" primary unit with the hard drive in > one of the "bad" secondary units. This switch cause the two machines to > exchange behavior. On closer inspection of the HDD we switched out, they > were not exactly identical. Though both are Western Digital 40GB HDD, the > model numbers differed slightly and they were manufactured in different > countries... > > The "good" drive details from visual inspection and WD diagnostics: > Completely black outer shell. > Manufactured in Thailand > M/N: WDC WD400BB-75FJA1 > S/N: WD-WCAJC2052229 > Firmware: 14.03G14 > C H S : 77504 16 63 > Drive 0, port 0x01F0 > Build Date unknown > > The "bad" drive details from visual inspection and WD diagnostics: > Black and silver outer shell > Manufactured in Malaysia > M/N: WDC WD400BB-75FRA0 > S/N: WD-WMAJF1089739 > Firmware: 77.07W77 > C H S: 77504 16 63 > Drive 0, port 0x01F0 > Build Date: 8-JAN-04 > > The other failing test machine's drive was manufactured in Singapore... and > also has the black and silver outer shell. > > During the testing we also were able to recreate the issue using SLES 9.0 > while performing a cdrom autoinstall to the "bad" secondary test unit. > > Manual installs do not seem encounter the issue. > > Autoinstalls seemed to ignore the partitioning info in the control files on > the secondary test machines. > > I have attached many of the autoinstall control files I have used during my > testing and the testing done with Steve and Don from Novell. > > > (See attached file: ay_006.xml)(See attached file: autoyast2_gx60.xml)(See > attached file: autoyast3_gx60.xml)(See attached file: > autoyast_generic_gx60.xml)(See attached file: autoyast_refpro_gx60.xml)(See > attached file: ay_003.xml)(See attached file: ay_004.xml)(See attached > file: ay_005.xml) > > Anyone's insights appreciated!!! > If other info is needed please let me know, I will be happy to provide > whatever I can . > > Cheers, > Tony > > > > The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information. -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.

2 1

Re: [suse-autoinstall] AutoInstall and Western Digital HDD issues.
by Anas Nashif 25 Aug '04

25 Aug '04

Anthony, Can you please provide the log files for a failed installation? Thanks, Anas Anthony Staples wrote: > > > > Anas, > > RE: Strange behavior regarding Autoinstall and some Western Digital HDDs: > > I am trying to develop an autoinstall for NLD 1.6 using a boot cd and an > NFS repository. > I have three machines that I am using for testing of autoinstall > deployments. All are Dell GX60s with 40GB WD HDD, 512 MB RAM and Cereron > 2.2Ghz CPUs. All have been updated to the latest DELL GX60 Bios (A08). > > As I have posted previously, I have not been able to get any control files > built on my primary test PC to work correctly on the other two units. > Autoinstall always fails during the format phase on these other two units, > and so the install does not complete. Here is the text of the error. > > "Could not format /dev/hda2. you can continue if you know what you are > doing, but, to prevent damage to your filesystems, it is safer to cancel > and reboot" > > I have tried many different approaches from explicitly setting the > partition scheme to using the most generic scheme outlined in the > documentation. > Each time, the control file works as planned on my primary machine, but > fails on the other two test units. > > Yesterday, Tuesday, 8/24/2004, I had Steve Wilson and Don Vosburg from > Novell in to help me troubleshoot and possibly solve this conundrum. > Together we went thru all the different iterations of control files I had > tried and some that Don came up with on the spot to try and make > partitioning work on the secondary test machines. We rec'd the same > results I had encountered over and over. Finally, as a last effort, we > switched the hard drive in the "good" primary unit with the hard drive in > one of the "bad" secondary units. This switch cause the two machines to > exchange behavior. On closer inspection of the HDD we switched out, they > were not exactly identical. Though both are Western Digital 40GB HDD, the > model numbers differed slightly and they were manufactured in different > countries... > > The "good" drive details from visual inspection and WD diagnostics: > Completely black outer shell. > Manufactured in Thailand > M/N: WDC WD400BB-75FJA1 > S/N: WD-WCAJC2052229 > Firmware: 14.03G14 > C H S : 77504 16 63 > Drive 0, port 0x01F0 > Build Date unknown > > The "bad" drive details from visual inspection and WD diagnostics: > Black and silver outer shell > Manufactured in Malaysia > M/N: WDC WD400BB-75FRA0 > S/N: WD-WMAJF1089739 > Firmware: 77.07W77 > C H S: 77504 16 63 > Drive 0, port 0x01F0 > Build Date: 8-JAN-04 > > The other failing test machine's drive was manufactured in Singapore... and > also has the black and silver outer shell. > > During the testing we also were able to recreate the issue using SLES 9.0 > while performing a cdrom autoinstall to the "bad" secondary test unit. > > Manual installs do not seem encounter the issue. > > Autoinstalls seemed to ignore the partitioning info in the control files on > the secondary test machines. > > I have attached many of the autoinstall control files I have used during my > testing and the testing done with Steve and Don from Novell. > > > (See attached file: ay_006.xml)(See attached file: autoyast2_gx60.xml)(See > attached file: autoyast3_gx60.xml)(See attached file: > autoyast_generic_gx60.xml)(See attached file: autoyast_refpro_gx60.xml)(See > attached file: ay_003.xml)(See attached file: ay_004.xml)(See attached > file: ay_005.xml) > > Anyone's insights appreciated!!! > If other info is needed please let me know, I will be happy to provide > whatever I can . > > Cheers, > Tony > > > > The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.

2 1

sles9: distribution-release not available
by Cosmo King 25 Aug '04

25 Aug '04

When configuring Autoyast for SLES9, and selecting "Software Selection" -> "Detailed Selection", I see the dependency conflict "aaa_base requires distribution-release" "distribution-release not available". I have not seen any packages named "distribution-release". Am I missing something? Thanks! Cosmo

1 0

More control...
by Anas Nashif 25 Aug '04

25 Aug '04

Hi, Some people in the past have been asking about how to have more control of the workflow and what is going on during manual and auto installations. Since 9.1, we have something new controling the whole installation phase. Some of you might have noticed a file named control.xml on the first CD. This file basically takes care of what dialogs should be shown and what the installation proposals should look like. It can either be customized for manual or automated installations. It also has some advanced features for manual installation which in most cases influence the initial installation proposal, i.e. partitioning and other global settings. Take a look at http://www.suse.de/~nashif/autoinstall/control.pdf. (Work in progress) The syntax is similar to this used for autoinstallation. Warning: Any change in this file will change the standard installation and might have unwanted results. So you should know exactly what you are doing. Anas

1 0

"No keyboard detected" when installing SuSE9.1 with textmode=1
by Voss Stefan 24 Aug '04

24 Aug '04

Hi folks, Whenever I (auto)install a Dell Optiplex GX60 using SuSE9.1 with the boot parameter 'textmode=1' the boot process stops shortly after Yast is started with the message: "starting yast... No keyboard detected. Trying to connect via serial interface /dev/ttyS0. On your terminal computer start the user interface with y2base "serial(115200):/dev/ttyS0" qt --fullscreen --noborder --auto-fonts ... " The behaviour is the same whether starting the installation process manually from cdrom or netbooting the machine using pxe. Of course, there is a keyboard connected to the machine and the boot messages show that it is detected correctly. It does not happen with SuSE 9.0. It does also not happen without textmode=1, i.e. during a normal manual installation which uses X11. It seems that yast cannot determine the keyboard and/or the console in this configuration. Does somebody know this error? I know this is a little OT, but textmode=1 is probably most often used in combination with autoinstall. Regards, Stefan Voss

1 0

Re: [suse-autoinstall] Could not format /dev/hda2
by Anthony Staples 23 Aug '04

23 Aug '04

Hello, I am encountering the following problem with autoinstall process. 1) I manually install NLD 1.6 on a reference machine, Dell GX60. 2) I create a reference profile on the DELL GX60 using YAST and autoinstall module. 3) I reboot the _reference_ machine from bootable CD for autoyast and autoinstall runs and installs NLD on the machine. 4) At this point all _seems_ well. 5) I boot a different GX60 with identical hardware and specs from the same CD for autoinstallation. 6) Yast fails during format of /dev/hda2 with the following error: "Could not format /dev/hda2. you can continue if you know what you are doing, but, to prevent damage to your filesystems, it is safer to cancel and reboot" However, if the error is ignored, since I want to re-install the target machine, files seem to copy and then the install fails later with lots of missing files. Seems as tho' my reference profile is only good for the original reference machine, which doesn't make much sense... Any insights or help appreciated!!! Regards, Tony The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.

2 1

YOU problem with SuSE 8.1
by Axel Wagner 23 Aug '04

23 Aug '04

Hello, The YaST2 online update stopped working on one of my systems. Here is what happened: I tried to update an older SuSE 8.1 system, which was offline most of the time. I started the YaST2 online update. The update first loaded some updates on YOU itself. I had to restart the online update 2 times. Then it started to download a large number of packages. Unfortunately, there was not much space left on the system, and during the download the system ran out of disk space. The update aborted. I removed some files and have enough space now (about 900MB). But the online update does not work any more. After starting it, it says "Initialisierung für FTP/HTTP-Update... Einen Moment bitte..." and after some seconds "Keine Verbindung zu www.suse.de möglich. Bitte überprüfen Sie die Verbindung." (Note: I'm using the text version of YasT2 on a german system) I checked on our firewall, but I could not find any package going out to www.suse.de. However, ping and ftp to that server work well, so I don't think it's a problem with the connection. I found a note on SuSE's web site that behind firewall, it could help to set wget to passive ftp downloads. I did that by changing /etc/wgetrc, as recommended. Did not help. And, BTW, the first update (before the disk was full) worked through the firewall without that change. Then I looked a little bit into the YaST modules, and found a setting in /usr/share/YaST2/modules/OnlineUpdate.ycp. There is an entry global string you_url = ""; in it. I inserted the text "ftp:://ftp.suse.com/pub/suse" and tried again. That helped a little, as the first initialization step was working now. Actually, YasT2 seems to download some URL if none is given in that variable. But now, when I start the update, I got other similar error messages. However, now I found the line "[mediaaccess] MediaWget.cc(getFile):125 wget error: connection failed" in the y2log file. Seems like wget has some problem. Again, the firewall did not show any packet going out. I also checked DNS and network setups. No clue. And, as I said, I can download packages manually using ftp. This is where I'm stuck. I suspect that during the failed update process, the system has been left in an incomplete state, and there's no way getting out with YaST2. Does anyone have an idea how I can get out of this? I'm currently thinking of removing the YaST packages via rpm, and restore the original ones from the CDs. But before doing that, and maybe causing other trouble, I thought I should ask for help here. I didn't use YOU before. A collegue told me (later) that he had bad experience with it. Is YOU known to have such problems? Should I better do the updates manually? BTW, the rest of the system seems to run fine. Thanks in advance, Axel ************************************************************** Axel Wagner raytest Isotopenmessgeraete GmbH Benzstr. 4 D-75334 Straubenhardt Tel: (07082) 9255 16 Fax: (07082) 20813 Email: wagner(a)raytest.de

1 0

YAST2 Online Update (When is a subscription required?)
by JazzPup 23 Aug '04

23 Aug '04

Hi I recently received and installed the Linux Technical Resource Kit from Novell. I installed SLES 8 (/w United Linux 1.0) My question is, am I able to take advantage of SuSe's YAST2 Online Update services to install patches, software, or system upgrades? I have read what I could find and I believe that I am not able to update SLES 8 components because I am using an evaluation version of the software, but what about United Linux 1.0 or the SuSe client software that is not part of SLES. Can these be updated online or do I have to purchase some kind of support license? I want to install Oracle 10g and want to make sure my system is up-to-date. Thanks and take care, JazzPup

2 1

SLES 9: Errors in the XML DTD
by Hans Kamm 23 Aug '04

23 Aug '04

Hello, I' ve just tested SLES 9 and autoyast, I' ve created a XML file with the yast tool from scratch. Bugs 1. Tools -> Create Reference Profile seems not to work, e.g. no software collection will be created. 2. Tools -> Check Validity of Profile: I don't know the error in the DTD: /tmp/YaST2-02661-GARgtP/valid.xml:70: element security: validity error : No declaration for element security </security> The following errors occur as the bootloader.dtd is incorrect, the mentioned elements 'activate' and 'repl_mbr' are missing: /tmp/YaST2-02661-GARgtP/valid.xml:91: element activate: validity error : No declaration for attribute type of element activate <activate config:type="boolean">false</activate> ^ /tmp/YaST2-02661-GARgtP/valid.xml:91: element activate: validity error : No declaration for element activate <activate config:type="boolean">false</activate> ^ /tmp/YaST2-02661-GARgtP/valid.xml:95: element repl_mbr: validity error : No declaration for attribute type of element repl_mbr <repl_mbr config:type="boolean">false</repl_mbr> ^ /tmp/YaST2-02661-GARgtP/valid.xml:95: element repl_mbr: validity error : No declaration for element repl_mbr <repl_mbr config:type="boolean">false</repl_mbr> ^ /tmp/YaST2-02661-GARgtP/valid.xml:96: element bootloader: validity error : Element bootloader content does not follow the DTD, expecting (global? , initrd_modules? , loader_device? , loader_type , location , sections?), got (activate loader_device loader_type location repl_mbr ) </bootloader> ^ Have anybody tested this piece of software before releasing it? I'm afraid of installing a system with autoyast, is it possible? _________________________________________________________________ Schluß mit Spam! http://www.msn.de/antispam/prevention/junkmailfilter Wir helfen Ihnen, unerwünschte E-Mails zu reduzieren.

2 1

A profile for this machine could not be found
by Joseph V Moss 21 Aug '04

21 Aug '04

I'm experiencing a problem similar to what Luca Lafranchi reported in his message to the list on 22-Apr-2004 where autoyast claims it can't retrieve the needed control file. In my case, I am using SLES9 to retrieve the file via ftp. The log shows: 2004-08-20 16:04:01 <1> linux(875) [YCP] AutoinstConfig.ycp:214 urltok = $["frag ment":"", "host":"10.7.51.226", "pass":"", "path":"/control-files/test.xml", "po rt":"", "query":"", "scheme":"ftp", "user":""] 2004-08-20 16:04:01 <1> linux(875) [YCP] ProfileLocation.ycp:46 Path to remote c ontrol file: /control-files/test.xml 2004-08-20 16:04:01 <1> linux(875) [YCP] ProfileLocation.ycp:57 File=test.xml 2004-08-20 16:04:01 <1> linux(875) [agent-curl] CurlAgent.cc(Execute):209 Data: 2004-08-20 16:04:01 <1> linux(875) [agent-curl] CurlAgent.cc(Execute):210 Output : /tmp/YaST2-00875-tHiu4i/autoinst.xml 2004-08-20 16:04:01 <3> linux(875) [YCP] autoinstall/io.ycp:83 Can't find URL: f tp://10.7.51.226/control-files/test.xml so it claims that it can't find the file, but the log on the ftp server shows that the file was downloaded and in fact the output file .../autoinst.xml has the correct contents. So why is it claiming that it can't find it?

1 0

Manual autoinstall...?
by Miro 20 Aug '04

20 Aug '04

Hi. I am trying to figure out a way to prompt for everything (manual package sel , rootpass, users..etc.). during a vnc autoinstall, except for the network configuration.! aka. install everything manually, but skip the network config (preconfigure= d). Does anybody know a solution to this..? Thanks in advance. Miro.

1 0

post install script oddity
by Dax Kelson 19 Aug '04

19 Aug '04

On SLES9 I have a AutoYaST post install script that runs: useradd -m -p '$1$J1n.X/QK$hj1vaqARqf.O/RWisMGRn1' visitor (this is a test account, on isolated, non-production test systems that are reinstalled daily with a variety of operating systems) The home directory /home/vistor is created and populated, BUT the very odd thing is there is no entry in the /etc/passwd file. All the files in the home directory have their ownership set to UID 1000. No error messages show up in the /var/adm/autoinstall/* log files. Things work fine on SUSE Linux 9.1 and SLES8. Suggestions welcome. Dax Kelson

1 0

RE: [suse-autoinstall] Tips on how to get started with auto install from boot floppy/CD
by Villalovos, John L 19 Aug '04

19 Aug '04

Mike Rose wrote: > It took me a while to work out how to create grub boot floppies and > how to hack the standard Suse boot CD for an autoyast net install, so > maybe some of you will find this useful: > > http://www.tcm.phy.cam.ac.uk/~mr349/suse/boot.html Thanks a lot for the info! I've been wanting to get more information on this but haven't yet had the time to go searching. John

1 0

Tips on how to get started with auto install from boot floppy/CD
by Mike Rose 19 Aug '04

19 Aug '04

It took me a while to work out how to create grub boot floppies and how to hack the standard Suse boot CD for an autoyast net install, so maybe some of you will find this useful: http://www.tcm.phy.cam.ac.uk/~mr349/suse/boot.html Mike Rose TCM & Biological Physics Computer Officer University of Cambridge http://www.bio.phy.cam.ac.uk/ http://www.tcm.phy.cam.ac.uk/

1 0

Several files in wrong place
by Cornelius Koelbel 19 Aug '04

19 Aug '04

Hello, I composed a install CD. I took my package selection and copied all the rpms to one CD. I generated the MD5SUMS and the INDEX.gz and the ls-lR.gz anew. I also generated a autoinst.xml, which I copied to the initrd on this CD. The CD boots fine, and it starts to install all packages. Finally, when all packages are installed, I get the message: "These packages returned an Error" The packages are: XFree86-server-glx, kernel-default, devs, yast2-theme-SuSELinux, libnetpbm, libogg, libidn, libselinux, audiofile .... On tty4 I get a few messages: hdc (which is my cdrom) media error (bad sector): error=0x30 hdc: media error (bad sector): status=0x51 { DriveReady SeekCompleteError } ??? Where or how can I get more information about the 'Errors' the packages returned??? When I go on (the installation is ready at 100%) he does the 'Finish Basic Installation' and will bail out at the point 'Install Boot Manager' and say /sbin/mkinitrd: line 1629: /dev/fd/62: No such file or directory No '/' mountpoint specified in /etc/fstab And indeed, there is no /etc/fstab The fstab, that would be the correct one for this system is still at /mnt/etc/fstab. Seems he missed something like a chroot? The same thing, when installing the bootloader: The files /boot/grub/stage2 and so on do not exist. They exist under /mnt/boot/grub ... So what have I missed in my configuration, so that the files are not in place? How can I take a deeper look or activate excessive logging? Regards Cornelius

1 0

Re: [suse-autoinstall] network configuration
by Marcin Kurc 18 Aug '04

18 Aug '04

the better solution would be probably to keep autoyast.xml on a server and point to it from grub i.e. autoyast=nfs://192.168.0.1/suse/autoyast_box1.xml another option would be to include a piece of code in the post-install script to set the IP based on the address used for installation. This way you would have one autoyast.xml and you would boot with the 'hostip=' option in this case your boot command would look something like this autoyast=nfs://192.168.0.1/suse/autoyast.xml hostip=192.168.0.133 netmask=255.255.255.0 gateway=192.168.0.254 thanks, Marcin Kurc Linux Impact Team Novell, Inc (973) 493-6235 >>>Vladimir Nikolic <vlado(a)agenda.si> 08/18/04 9:14 am >>> Hello! I have to install 40+ workstations with autoyast procedure. I've prepared self-made CD with autoyast.xml control file, try it and it works fine. But there is trouble with network card configuration. Because each worskstation has it's own IP, does it mean that I have to make CD for each workstation? I've tried with control file on floppy, but it doesn't work at all. Regards, Vlado -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

2 1

tty when post script
by jan terje tønnessen 18 Aug '04

18 Aug '04

Hi ! I have an autoyast where my post-script takes 10 minutes (compiling+++). The problem is that it looks as if the machine hangs in the "Desktop Settings" screen. Is it possible to display what is really going on ? /JT

2 1

network configuration
by Vladimir Nikolic 18 Aug '04

18 Aug '04

Hello! I have to install 40+ workstations with autoyast procedure. I've prepared self-made CD with autoyast.xml control file, try it and it works fine. But there is trouble with network card configuration. Because each worskstation has it's own IP, does it mean that I have to make CD for each workstation? I've tried with control file on floppy, but it doesn't work at all. Regards, Vlado

1 0

suse 9.1: Problem when installing the bootloader
by Cornelius Koelbel 18 Aug '04

18 Aug '04

Hello list, I am trying to autoinstall a suse 9.1. I also collected all needed rpms on one CD, so that I will only need this single one. Everything works fine, all software packages are installed until he tries to install to bootloader. He then complains about /dev/fd/62 and tells me there is not entry / in the /etc/fstab. I do not know, where he is looking for the fstab!? I attach my autoinst.xml, which I have placed in my boot/loader/initrd Any Ideas, how I can get the bootloader installed? Regards Cornelius --snip-- <?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> <general> <clock> <hwclock>localtime</hwclock> <timezone>Europe/Berlin</timezone> </clock> </general> <report> <messages> <show config:type="boolean">true</show> <timeout config:type="integer">10</timeout> <log config:type="boolean">true</log> </messages> <errors> <show config:type="boolean">true</show> <timeout config:type="integer">10</timeout> <log config:type="boolean">true</log> </errors> <warnings> <show config:type="boolean">true</show> <timeout config:type="integer">10</timeout> <log config:type="boolean">true</log> </warnings> </report> <partitioning config:type="list"> <drive> <device>/dev/hda</device> <use>all</use> </drive> </partitioning> <bootloader> <global config:type="list"> <global_entry> <key>prompt</key> <value config:type="boolean">true</value> </global_entry> </global> <loader_device></loader_device> <loader_type>grub</loader_type> <location>mbr</location> <sections config:type="list"/> </bootloader> <software> <addons config:type="list"> <addon>Basis-Sound</addon> <addon>Kde-Desktop</addon> <addon>MINIMAL</addon> <addon>Office</addon> <addon>SuSE-Documentation</addon> <addon>X11</addon> </addons> <base>default</base> <packages config:type="list"> <package>MozillaFirefox</package> <package>ImageMagick</package> <package>apache2</package> <package>apache2-devel</package> <package>apache2-mod_php4</package> <package>apache2-prefork</package> <package>apache2-worker</package> <package>capi4hylafax</package> <package>cvs</package> <package>findutils-locate</package> <package>g3utils</package> <package>hylafax</package> <package>kernel-default</package> <package>libapr0</package> <package>mgetty</package> <package>mm</package> <package>php4</package> <package>php4-gettext</package> <package>php4-pear</package> <package>php4-pgsql</package> <package>php4-session</package> <package>postgresql</package> <package>postgresql-contrib</package> <package>postgresql-libs</package> <package>postgresql-server</package> <package>sfftobmp</package> <package>sffview</package> <package>sox</package> <package>tiff</package> <package>uucp</package> <package>wxGTK</package> <package>yast2-trans-en_US</package> </packages> </software> </install> </profile>

1 0

Is it normal to not see created partitions during install?
by Villalovos, John L 18 Aug '04

18 Aug '04

Is it normal to not see created partitions during install? I have my install running and it claims that the partitions have been created and it is chugging away installing packages. When I do an CTRL-ALT F2 and then do an: # fdisk /dev/sda And I only see the /boot/efi partition on my Itanium system. It should have three partitions created. /boot/efi, /, and a swap. When looking at the log file in /var/log/YaST2/ I can see where it says it is formatting the partition. I was just wondering if maybe I messed up and that there is some special value that most be set to make sure the partitions are created in the partition table. John

2 1

autoyast does not find additional self defined installation source SLES9
by Marco Hoehle 17 Aug '04

17 Aug '04

Hi, we want to include a self defined installation Source into our autoyast network installation. Our own Yast Source is defined , all the files (content, media, directory.yast, product) are configurated and in my opinion the looks fine. When the autoyast installation is launched, we can see during the installation, that our selfdefined source is available (the content file is read) but when our own source should be used, yast defaults to the / location. There is no way to make autoyast use our own source tree (like for the /CORE tree) which lays in f.e.: /MYOWN The result is that the installation stops and asks for our "self defined" media. I just have to append the source name (/MYOWN) to the source location autoyast is proposing and then it works. After now spending 3 days in reading all the different dokuments and hints and tipps and tricks I can't see any solution for this problem, even there is no logfile in which i can have a look what kind of source autoyast is looking for or why it does not want to accept the self defined source. (maybe hardcoded stuff ) So if someone (A.N :)) ) can help , this would be great THX in advance marco

2 1

Sample autoinst.xml file for Itantium (IA64)?
by Villalovos, John L 17 Aug '04

17 Aug '04

Does anyone have some sample autoinst.xml files for using on an Itanium (IA64). My big problem seems to be setting up the partitioning and then getting the boot loader to work. If anyone has some helpful advice it would be appreciated. Thanks! John

1 0

Not able to create users from control file.
by Kevin Stallard 17 Aug '04

17 Aug '04

The relevant portion of my autoinst.xml file <configure> <security> <encryption>md5</encryption> <cwd_in_root_path>no</cwd_in_root_path> <passwd_use_cracklib>yes</passwd_use_cracklib> </security> <users config:type="list"> <user> <username>root</username> <user_password>**password in clear text**</user_password> <encrypted config:type="boolean">true</encrypted> <forename/> <surname/> </user> <user> <username>admin</username> <user_password>**password in clear text**</user_password> <encrypted config:type="boolean">true</encrypted> <forename/> <surname/> </user> </users> </configure> When the installation completes, there is no password assigned to root. The user "admin" doesn't get created either. I can use useradd after the install to create users, however, the home directory does not get created. In a possibly related problem. sshd fails to start because the user "sshd" is not created when the RPM installs. I'm using the sshd package from the 9.1 professional CD. Am I missing some yast packages? I'm at a loss. -K -- Kevin Stallard <kstallard(a)lancope.com>

2 1

RE: [suse-autoinstall] autoyast does not find additional self def ined installation source SLES9
by Ness, Todd 17 Aug '04

17 Aug '04

Try reading the following page... http://www.suse.de/~nashif/autoinstall/8.1/html/advanced.html I followed this and have my own CD that installs and works from network install as well. -----Original Message----- From: Marco Hoehle [mailto:MHO@zurich.ibm.com] Sent: Tuesday, August 17, 2004 5:16 AM To: suse-autoinstall(a)suse.com Subject: [suse-autoinstall] autoyast does not find additional self defined installation source SLES9 Hi, we want to include a self defined installation Source into our autoyast network installation. Our own Yast Source is defined , all the files (content, media, directory.yast, product) are configurated and in my opinion the looks fine. When the autoyast installation is launched, we can see during the installation, that our selfdefined source is available (the content file is read) but when our own source should be used, yast defaults to the / location. There is no way to make autoyast use our own source tree (like for the /CORE tree) which lays in f.e.: /MYOWN The result is that the installation stops and asks for our "self defined" media. I just have to append the source name (/MYOWN) to the source location autoyast is proposing and then it works. After now spending 3 days in reading all the different dokuments and hints and tipps and tricks I can't see any solution for this problem, even there is no logfile in which i can have a look what kind of source autoyast is looking for or why it does not want to accept the self defined source. (maybe hardcoded stuff ) So if someone (A.N :)) ) can help , this would be great THX in advance marco -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

Tips on how to get started with auto install from boot disks
by Shane A Broomhall (AUST) 17 Aug '04

17 Aug '04

Hi All, This is my first post to this group, and I apologise if I am asking something that is a common thread. I have the need to using a boot floppy, have a minimal network version of linux start, load a non standard broadcom driver and run a standard install from a network server, actually a laptop. I will need to do this with SUSE 9.1, SLES 8& 9. Whilst I do not expect anyone to provide me with a complete solution, some guidance on where to look for the tools to do this, would be greatly appreciated. Thanks in advance Shane Broomhall Brisbane Australia

2 1

Re: [suse-autoinstall] Default keyboard layout is German after install
by Anthony Staples 16 Aug '04

16 Aug '04

Anas, Sorry, I zipped up the wrong autoyast profile with the logs... I sent the correct one to your email. Here is the line from the y2log file that shows the name of the profile used... 2004-10-10 09:57:31 <1> linux(2374) [YCP] AutoinstConfig.ycp:214 urltok = $["fragment":"", "host":"193.91.6.69", "pass":"", "path":"/nld_install/autoyast2_gx270.xml", "port":"", "query":"", "scheme":"nfs", "user":""] Notice, I sent you "autoyast_gx270.xml originally last week... the correct file was autoyast2_gx270.xml. Anas Nashif <nashif(a)suse.de> To: suse-autoinstall(a)suse.com cc: 08/16/2004 03:53 Subject: Re: [suse-autoinstall] Default keyboard layout is German after install PM Anthony Staples wrote: > > > > Anas, > > Where does autoyast get the default X config file (XF85Config)? Is it > somewhere that it might be edited to change the default keymap to english!? > Any responses appreciated! > If x11 is not configured in autoyast, autoyast does not touch the files. The default config file is installed in some different way, I dont know exactly where is it copied from and which package copies it. You profiles are missing the X11 configuration and thats why you get the default file. Anas > Regards, > > Anthony Staples > Technical Analyst > Humana Inc. > 502.580.2870 > > > > > > Anas Nashif > <nashif(a)suse.de> To: Anthony Staples <astaples(a)humana.com> > cc: Lee Mayes <autoinst(a)mayeses.com>, lmarks(a)novell.com, pgriffen(a)novell.com, > 08/12/2004 01:41 suse-autoinstall(a)suse.com > PM Subject: Re: [suse-autoinstall] Default keyboard layout is German after install > > > > > > > > > > Anthony Staples wrote: > >> >> >>Anas, >> >>Thanks for your quick response. >>The header of the the XF86Config on the autoinstalled machine is: >> >># Generic XFree86 configuration file >> > > > This is the generic x11 file which is german. > > >>If, as you said below, there is no need for locale in x11 config, then > > how > >>can configuring it in AutoYast effect the keymap on my installed systems. >>Since the header is as above, it doesn't seem to make any difference. > > > When you set the language and keyboard as shown below in <general> those > values are used when creating the X11 config. > > >>I checked and then rechecked that my locale settings in "General" were >>correct. >>here is a snip from the profile... ( it won't let me paste the full > > profile > >>due to size limitations...) >> >> <general> >> <clock> >> <hwclock>UTC</hwclock> >> <timezone>US/Eastern</timezone> >> </clock> >> <keyboard> >> <keymap>english-us</keymap> >> </keyboard> >> <language>en_US</language> >> <mode> >> <confirm config:type="boolean">false</confirm> >> <forceboot config:type="boolean">false</forceboot> >> </mode> >> <mouse> >> <id>22_exps2</id> >> </mouse> >> </general> >> >>Why shouldn't the general setting be propagated throughout the installed >>machine? > > > > They are. But not in the X11 config which is the generic one. This > happens if you dont configure x11 at all using autoyast. If you did have > x11 configured in autoyast, then something else happend. Can you send me > the control file you are using and if possible the y2log files from > /var/log/YaST2/y2log? > >>I checked the setting in YAST and keyboard configuration was correctly > > set > >>to English(US). >> > > > Anas > > >>Cheers, >>Tony >> >> >> >> >> >> > > >> Anas Nashif > > >> <nashif(a)suse.de> To: Anthony Staples > > <astaples(a)humana.com> > >> cc: > > lmarks(a)novell.com, pgriffen(a)novell.com, Lee Mayes <autoinst(a)mayeses.com>, > >> 08/12/2004 11:19 suse-autoinstall(a)suse.com > > >> AM Subject: Re: > > [suse-autoinstall] Default keyboard layout is German after install > > > > >> >> >> >>Anthony, >>There is no need for locale in the x11 config, the system settings are >>taken. >>After using the configuration below, what does the header in the >>/etc/X11/XF86Config file say? >> >>Anas >> >>Anthony Staples wrote: >> >> >>> >>>Anas, >>>Just to clarify, I am running NLD beta not SuSE 9.1 pro. >>>When I rec'd Lee's response this morning (Thanks!) I tried just what you >>>suggested, Anas. >>>I thought that the issue may be in the X11 default config so I created >>>(using autoyast) a new reference profile from my original and included >> >>an >> >> >>>X11 configuration: >>>Here is the X11 section of my reference profile, though I don't see >>>anyplace where the keymap is actually set... >>> >>><x11> >>> <color_depth config:type="integer">16</color_depth> >>> <configure_x11 config:type="boolean">true</configure_x11> >>> <display_manager>gdm</display_manager> >>> <enable_3d config:type="boolean">false</enable_3d> >>> <monitor> >>> <display> >>> <frequency config:type="integer">60</frequency> >>> <height config:type="integer">768</height> >>> <width config:type="integer">1024</width> >>> </display> >>> <monitor_device>1024X768@60HZ</monitor_device> >>> <monitor_vendor> LCD</monitor_vendor> >>> </monitor> >>> <resolution>1024x768</resolution> >>> <window_manager>gnome</window_manager> >>> </x11> >>> >>> >>>I then proceeded to install a machine with the updated profile, but still >>>get the German default keymap rather than US keymap. >>>Is there anyway for us to change the default keymap in the XF86Config >> >>that >> >> >>>Autoyast uses? Before profile generation rather than after... >>> >>>Regards, >>> >>>Anthony Staples >>>Technical Analyst >>>Humana Inc. >>>502.580.2870 >>> >>> >>> >>> >>> >> >> >>> Anas Nashif >> >> >>> <nashif(a)suse.de> To: Lee Mayes >> >><autoinst(a)mayeses.com> >> >>> cc: Anthony Staples >> >><astaples(a)humana.com>, suse-autoinstall(a)suse.com >> >> >>> 08/12/2004 09:03 Subject: Re: >> >>[suse-autoinstall] Default keyboard layout is German after install >> >> >>> AM >> >> >> >> >> >>> >>> >>>Hi, >>> >>>This is because you dont configure X using autoyast and the default >>>/etc/X11/XF86Config happens to be in german ;( >>> >>>Anas >>> >>> >>>Lee Mayes wrote: >>> >>> >>> >>>>Hi Tony, >>>> >>>>I noticed that on my SuSE 9.1 AutoYaST installs, the keyboard is set >>>>correctly in everything but X11. I added the following 2 lines in my >>>>post install user script to fix it: >>>> >>>>print KS qq[ >>>>/bin/cp /etc/X11/XF86Config /tmp/XF86Config.back >>>>/usr/bin/sed -e 's/XkbLayout"\\t"de/XkbLayout"\\t"$x_kbd/' \ >>>> </tmp/XF86Config.back >/etc/X11/XF86Config >>>>]; >>>> >>>> >>>>In my case $x_kbd is a variable passed to the perl script creating >>>>autoyast.xml. I made a simple 'table' that cross references linux >>>>keyboard environment variables to the X11 ones. I can provide it if >>>>needed, it's mostly complete but has a few languages I wasn't sure how >>>>to cross reference. >>>> >>>>I think if I had fully qualified X's config (vs. letting it default) I >>>>wouldn't have seen the problem. There are probably other ways to fix it >>>>as well, but I was in a hurry and this works for us. >>>> >>>>Best Regards, >>>> >>>>Lee >>>> >>>>On Wed, 2004-08-11 at 14:24, Anthony Staples wrote: >>>> >>>> >>>> >>>> >>>>>When i do an autoyast install I always get a german default keyboard >>> >>>rather >>> >>> >>> >>>>>than US-English. >>>>>I explicitly set the layout to US-English in the reference profile. > > All > >>>>>other settings seem to be ok. >>>>> >>>>>Any insight on how to fix this would be appreciated!! >>>>> >>>>>Cheers, >>>>>Tony Staples >>>>>astaples(a)humana.com >>>>> >>>>>Here is a snip from my autoyast reference profile... >>>>> >>>>> <general> >>>>> <clock> >>>>> <hwclock>UTC</hwclock> >>>>> <timezone>US/Eastern</timezone> >>>>> </clock> >>>>> <keyboard> >>>>> <keymap>english-us</keymap> >>>>> </keyboard> >>>>> <language>en_US</language> >>>>> <mode> >>>>> <confirm config:type="boolean">false</confirm> >>>>> <forceboot config:type="boolean">false</forceboot> >>>>> </mode> >>>>> <mouse> >>>>> <id>22_exps2</id> >>>>> </mouse> >>>>> </general> >>>>> >>>>> >>>>> >>>>>The information transmitted is intended only for the person or entity > > to > >>>which it is addressed and may contain CONFIDENTIAL material. If you >>>receive this material/information in error, please contact the sender and >>>delete or destroy the material/information. >>> >>> >>> >>>-- >>>To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com >>>For additional commands, e-mail: suse-autoinstall-help(a)suse.com >>> >>> >>> >>> >>> >>> >>>The information transmitted is intended only for the person or entity to >> >>which it is addressed and may contain CONFIDENTIAL material. If you >>receive this material/information in error, please contact the sender and >>delete or destroy the material/information. >> >>-- >>To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com >>For additional commands, e-mail: suse-autoinstall-help(a)suse.com >> >> >> >> >> >> >>The information transmitted is intended only for the person or entity to > > which it is addressed and may contain CONFIDENTIAL material. If you > receive this material/information in error, please contact the sender and > delete or destroy the material/information. > > > -- > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > For additional commands, e-mail: suse-autoinstall-help(a)suse.com > > > > > > > The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information. > -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.

2 1

Re: [suse-autoinstall] Default keyboard layout is German after install
by Anthony Staples 16 Aug '04

16 Aug '04

Anas, Where does autoyast get the default X config file (XF85Config)? Is it somewhere that it might be edited to change the default keymap to english!? Any responses appreciated! Regards, Anthony Staples Technical Analyst Humana Inc. 502.580.2870 Anas Nashif <nashif(a)suse.de> To: Anthony Staples <astaples(a)humana.com> cc: Lee Mayes <autoinst(a)mayeses.com>, lmarks(a)novell.com, pgriffen(a)novell.com, 08/12/2004 01:41 suse-autoinstall(a)suse.com PM Subject: Re: [suse-autoinstall] Default keyboard layout is German after install Anthony Staples wrote: > > > > Anas, > > Thanks for your quick response. > The header of the the XF86Config on the autoinstalled machine is: > > # Generic XFree86 configuration file > This is the generic x11 file which is german. > If, as you said below, there is no need for locale in x11 config, then how > can configuring it in AutoYast effect the keymap on my installed systems. > Since the header is as above, it doesn't seem to make any difference. When you set the language and keyboard as shown below in <general> those values are used when creating the X11 config. > > I checked and then rechecked that my locale settings in "General" were > correct. > here is a snip from the profile... ( it won't let me paste the full profile > due to size limitations...) > > <general> > <clock> > <hwclock>UTC</hwclock> > <timezone>US/Eastern</timezone> > </clock> > <keyboard> > <keymap>english-us</keymap> > </keyboard> > <language>en_US</language> > <mode> > <confirm config:type="boolean">false</confirm> > <forceboot config:type="boolean">false</forceboot> > </mode> > <mouse> > <id>22_exps2</id> > </mouse> > </general> > > Why shouldn't the general setting be propagated throughout the installed > machine? They are. But not in the X11 config which is the generic one. This happens if you dont configure x11 at all using autoyast. If you did have x11 configured in autoyast, then something else happend. Can you send me the control file you are using and if possible the y2log files from /var/log/YaST2/y2log? > I checked the setting in YAST and keyboard configuration was correctly set > to English(US). > Anas > Cheers, > Tony > > > > > > > Anas Nashif > <nashif(a)suse.de> To: Anthony Staples <astaples(a)humana.com> > cc: lmarks(a)novell.com, pgriffen(a)novell.com, Lee Mayes <autoinst(a)mayeses.com>, > 08/12/2004 11:19 suse-autoinstall(a)suse.com > AM Subject: Re: [suse-autoinstall] Default keyboard layout is German after install > > > > > > > > Anthony, > There is no need for locale in the x11 config, the system settings are > taken. > After using the configuration below, what does the header in the > /etc/X11/XF86Config file say? > > Anas > > Anthony Staples wrote: > >> >> >>Anas, >>Just to clarify, I am running NLD beta not SuSE 9.1 pro. >>When I rec'd Lee's response this morning (Thanks!) I tried just what you >>suggested, Anas. >>I thought that the issue may be in the X11 default config so I created >>(using autoyast) a new reference profile from my original and included > > an > >>X11 configuration: >>Here is the X11 section of my reference profile, though I don't see >>anyplace where the keymap is actually set... >> >><x11> >> <color_depth config:type="integer">16</color_depth> >> <configure_x11 config:type="boolean">true</configure_x11> >> <display_manager>gdm</display_manager> >> <enable_3d config:type="boolean">false</enable_3d> >> <monitor> >> <display> >> <frequency config:type="integer">60</frequency> >> <height config:type="integer">768</height> >> <width config:type="integer">1024</width> >> </display> >> <monitor_device>1024X768@60HZ</monitor_device> >> <monitor_vendor> LCD</monitor_vendor> >> </monitor> >> <resolution>1024x768</resolution> >> <window_manager>gnome</window_manager> >> </x11> >> >> >>I then proceeded to install a machine with the updated profile, but still >>get the German default keymap rather than US keymap. >>Is there anyway for us to change the default keymap in the XF86Config > > that > >>Autoyast uses? Before profile generation rather than after... >> >>Regards, >> >>Anthony Staples >>Technical Analyst >>Humana Inc. >>502.580.2870 >> >> >> >> >> > > >> Anas Nashif > > >> <nashif(a)suse.de> To: Lee Mayes > > <autoinst(a)mayeses.com> > >> cc: Anthony Staples > > <astaples(a)humana.com>, suse-autoinstall(a)suse.com > >> 08/12/2004 09:03 Subject: Re: > > [suse-autoinstall] Default keyboard layout is German after install > >> AM > > > > > >> >> >> >>Hi, >> >>This is because you dont configure X using autoyast and the default >>/etc/X11/XF86Config happens to be in german ;( >> >>Anas >> >> >>Lee Mayes wrote: >> >> >>>Hi Tony, >>> >>> I noticed that on my SuSE 9.1 AutoYaST installs, the keyboard is set >>>correctly in everything but X11. I added the following 2 lines in my >>>post install user script to fix it: >>> >>>print KS qq[ >>>/bin/cp /etc/X11/XF86Config /tmp/XF86Config.back >>>/usr/bin/sed -e 's/XkbLayout"\\t"de/XkbLayout"\\t"$x_kbd/' \ >>> </tmp/XF86Config.back >/etc/X11/XF86Config >>>]; >>> >>> >>>In my case $x_kbd is a variable passed to the perl script creating >>>autoyast.xml. I made a simple 'table' that cross references linux >>>keyboard environment variables to the X11 ones. I can provide it if >>>needed, it's mostly complete but has a few languages I wasn't sure how >>>to cross reference. >>> >>> I think if I had fully qualified X's config (vs. letting it default) I >>>wouldn't have seen the problem. There are probably other ways to fix it >>>as well, but I was in a hurry and this works for us. >>> >>>Best Regards, >>> >>>Lee >>> >>>On Wed, 2004-08-11 at 14:24, Anthony Staples wrote: >>> >>> >>> >>>>When i do an autoyast install I always get a german default keyboard >> >>rather >> >> >>>>than US-English. >>>>I explicitly set the layout to US-English in the reference profile. All >>>>other settings seem to be ok. >>>> >>>>Any insight on how to fix this would be appreciated!! >>>> >>>>Cheers, >>>>Tony Staples >>>>astaples(a)humana.com >>>> >>>>Here is a snip from my autoyast reference profile... >>>> >>>> <general> >>>> <clock> >>>> <hwclock>UTC</hwclock> >>>> <timezone>US/Eastern</timezone> >>>> </clock> >>>> <keyboard> >>>> <keymap>english-us</keymap> >>>> </keyboard> >>>> <language>en_US</language> >>>> <mode> >>>> <confirm config:type="boolean">false</confirm> >>>> <forceboot config:type="boolean">false</forceboot> >>>> </mode> >>>> <mouse> >>>> <id>22_exps2</id> >>>> </mouse> >>>> </general> >>>> >>>> >>>> >>>>The information transmitted is intended only for the person or entity to >> >>which it is addressed and may contain CONFIDENTIAL material. If you >>receive this material/information in error, please contact the sender and >>delete or destroy the material/information. >> >> >>> >>-- >>To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com >>For additional commands, e-mail: suse-autoinstall-help(a)suse.com >> >> >> >> >> >> >>The information transmitted is intended only for the person or entity to > > which it is addressed and may contain CONFIDENTIAL material. If you > receive this material/information in error, please contact the sender and > delete or destroy the material/information. > > -- > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > For additional commands, e-mail: suse-autoinstall-help(a)suse.com > > > > > > > The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information. > -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.

2 1

Re: [suse-autoinstall] Default keyboard layout is German after install
by Anthony Staples 16 Aug '04

16 Aug '04

Anas, Did you receive the files I sent? Where they any help? Here is something else I have tried. I included a post install script to change the "de" in the XF86Config to "us" as outlined by Lee Marks in another post to this list. here is the script code I included in the autoyast.xml file. <scripts> <post-scripts config:type="list"> <script> <filename>keymapfix.sh</filename> <interpreter>shell</interpreter> <location></location> <source><![CDATA[ #!/bin/sh echo "Copying files" `/bin/cp /etc/X11/XF86Config /tmp/XF86Config.back ` echo "Copying complete..." echo "Begin Sed Stmnt" `/bin/sed -e 's/XkbLayout"\\t"de/XkbLayout"\\t"us/' /etc/X11/XF86Config > /tmp/XF86Config.back ` echo "End Sed" echo "Moving..." /bin/mv /tmp/XF86Config.back /etc/X11/XF86Config echo "Move Complete..." echo "Done" ]]> </source> </script> </post-scripts> </scripts> I tested the code separately and it seemed to work ok. However, during one of my many test autoinstalls, as I watch one of the final yast output windows I distinctly see it print "Skipping Scripts..." And of course the keymap is still german when the install is finished. So I can only surmise that "Skipping scripts" means it is skipping MY script... but I don't know why. Any help appreciated. Cheers. "Anthony Staples" To: <skarsch(a)s1.karsch-net.de> <astaples@humana cc: "Anthony Staples" <astaples(a)humana.com>, "Lee Mayes" .com> <autoinst(a)mayeses.com>, <lmarks(a)novell.com>, <pgriffen(a)novell.com>, <suse-autoinstall(a)suse.com> 08/16/2004 09:45 Subject: Re: [suse-autoinstall] Default keyboard layout is German after install AM Anas, Where does autoyast get the default X config file (XF85Config)? Is it somewhere that it might be edited to change the default keymap to english!? Any responses appreciated! Regards, Anthony Staples Technical Analyst Humana Inc. 502.580.2870 Anas Nashif <nashif(a)suse.de> To: Anthony Staples <astaples(a)humana.com> cc: Lee Mayes <autoinst(a)mayeses.com>, lmarks(a)novell.com, pgriffen(a)novell.com, 08/12/2004 01:41 suse-autoinstall(a)suse.com PM Subject: Re: [suse-autoinstall] Default keyboard layout is German after install Anthony Staples wrote: > > > > Anas, > > Thanks for your quick response. > The header of the the XF86Config on the autoinstalled machine is: > > # Generic XFree86 configuration file > This is the generic x11 file which is german. > If, as you said below, there is no need for locale in x11 config, then how > can configuring it in AutoYast effect the keymap on my installed systems. > Since the header is as above, it doesn't seem to make any difference. When you set the language and keyboard as shown below in <general> those values are used when creating the X11 config. > > I checked and then rechecked that my locale settings in "General" were > correct. > here is a snip from the profile... ( it won't let me paste the full profile > due to size limitations...) > > <general> > <clock> > <hwclock>UTC</hwclock> > <timezone>US/Eastern</timezone> > </clock> > <keyboard> > <keymap>english-us</keymap> > </keyboard> > <language>en_US</language> > <mode> > <confirm config:type="boolean">false</confirm> > <forceboot config:type="boolean">false</forceboot> > </mode> > <mouse> > <id>22_exps2</id> > </mouse> > </general> > > Why shouldn't the general setting be propagated throughout the installed > machine? They are. But not in the X11 config which is the generic one. This happens if you dont configure x11 at all using autoyast. If you did have x11 configured in autoyast, then something else happend. Can you send me the control file you are using and if possible the y2log files from /var/log/YaST2/y2log? > I checked the setting in YAST and keyboard configuration was correctly set > to English(US). > Anas > Cheers, > Tony > > > > > > > Anas Nashif > <nashif(a)suse.de> To: Anthony Staples <astaples(a)humana.com> > cc: lmarks(a)novell.com, pgriffen(a)novell.com, Lee Mayes <autoinst(a)mayeses.com>, > 08/12/2004 11:19 suse-autoinstall(a)suse.com > AM Subject: Re: [suse-autoinstall] Default keyboard layout is German after install > > > > > > > > Anthony, > There is no need for locale in the x11 config, the system settings are > taken. > After using the configuration below, what does the header in the > /etc/X11/XF86Config file say? > > Anas > > Anthony Staples wrote: > >> >> >>Anas, >>Just to clarify, I am running NLD beta not SuSE 9.1 pro. >>When I rec'd Lee's response this morning (Thanks!) I tried just what you >>suggested, Anas. >>I thought that the issue may be in the X11 default config so I created >>(using autoyast) a new reference profile from my original and included > > an > >>X11 configuration: >>Here is the X11 section of my reference profile, though I don't see >>anyplace where the keymap is actually set... >> >><x11> >> <color_depth config:type="integer">16</color_depth> >> <configure_x11 config:type="boolean">true</configure_x11> >> <display_manager>gdm</display_manager> >> <enable_3d config:type="boolean">false</enable_3d> >> <monitor> >> <display> >> <frequency config:type="integer">60</frequency> >> <height config:type="integer">768</height> >> <width config:type="integer">1024</width> >> </display> >> <monitor_device>1024X768@60HZ</monitor_device> >> <monitor_vendor> LCD</monitor_vendor> >> </monitor> >> <resolution>1024x768</resolution> >> <window_manager>gnome</window_manager> >> </x11> >> >> >>I then proceeded to install a machine with the updated profile, but still >>get the German default keymap rather than US keymap. >>Is there anyway for us to change the default keymap in the XF86Config > > that > >>Autoyast uses? Before profile generation rather than after... >> >>Regards, >> >>Anthony Staples >>Technical Analyst >>Humana Inc. >>502.580.2870 >> >> >> >> >> > > >> Anas Nashif > > >> <nashif(a)suse.de> To: Lee Mayes > > <autoinst(a)mayeses.com> > >> cc: Anthony Staples > > <astaples(a)humana.com>, suse-autoinstall(a)suse.com > >> 08/12/2004 09:03 Subject: Re: > > [suse-autoinstall] Default keyboard layout is German after install > >> AM > > > > > >> >> >> >>Hi, >> >>This is because you dont configure X using autoyast and the default >>/etc/X11/XF86Config happens to be in german ;( >> >>Anas >> >> >>Lee Mayes wrote: >> >> >>>Hi Tony, >>> >>> I noticed that on my SuSE 9.1 AutoYaST installs, the keyboard is set >>>correctly in everything but X11. I added the following 2 lines in my >>>post install user script to fix it: >>> >>>print KS qq[ >>>/bin/cp /etc/X11/XF86Config /tmp/XF86Config.back >>>/usr/bin/sed -e 's/XkbLayout"\\t"de/XkbLayout"\\t"$x_kbd/' \ >>> </tmp/XF86Config.back >/etc/X11/XF86Config >>>]; >>> >>> >>>In my case $x_kbd is a variable passed to the perl script creating >>>autoyast.xml. I made a simple 'table' that cross references linux >>>keyboard environment variables to the X11 ones. I can provide it if >>>needed, it's mostly complete but has a few languages I wasn't sure how >>>to cross reference. >>> >>> I think if I had fully qualified X's config (vs. letting it default) I >>>wouldn't have seen the problem. There are probably other ways to fix it >>>as well, but I was in a hurry and this works for us. >>> >>>Best Regards, >>> >>>Lee >>> >>>On Wed, 2004-08-11 at 14:24, Anthony Staples wrote: >>> >>> >>> >>>>When i do an autoyast install I always get a german default keyboard >> >>rather >> >> >>>>than US-English. >>>>I explicitly set the layout to US-English in the reference profile. All >>>>other settings seem to be ok. >>>> >>>>Any insight on how to fix this would be appreciated!! >>>> >>>>Cheers, >>>>Tony Staples >>>>astaples(a)humana.com >>>> >>>>Here is a snip from my autoyast reference profile... >>>> >>>> <general> >>>> <clock> >>>> <hwclock>UTC</hwclock> >>>> <timezone>US/Eastern</timezone> >>>> </clock> >>>> <keyboard> >>>> <keymap>english-us</keymap> >>>> </keyboard> >>>> <language>en_US</language> >>>> <mode> >>>> <confirm config:type="boolean">false</confirm> >>>> <forceboot config:type="boolean">false</forceboot> >>>> </mode> >>>> <mouse> >>>> <id>22_exps2</id> >>>> </mouse> >>>> </general> >>>> >>>> >>>> >>>>The information transmitted is intended only for the person or entity to >> >>which it is addressed and may contain CONFIDENTIAL material. If you >>receive this material/information in error, please contact the sender and >>delete or destroy the material/information. >> >> >>> >>-- >>To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com >>For additional commands, e-mail: suse-autoinstall-help(a)suse.com >> >> >> >> >> >> >>The information transmitted is intended only for the person or entity to > > which it is addressed and may contain CONFIDENTIAL material. If you > receive this material/information in error, please contact the sender and > delete or destroy the material/information. > > -- > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > For additional commands, e-mail: suse-autoinstall-help(a)suse.com > > > > > > > The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information. > -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information. -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.

1 0

SLES9 single directory network install
by Dax Kelson 16 Aug '04

16 Aug '04

The network-install.pdf states: "In the source directory, copy all SLES and CORE into separate directories (CDs can also be copied into one single directory, but to keep a clean structure, CDs can be copied into separate directories, i.e. using the following scheme: CORE9/CD1, CORE9/CD2, CORE9/CD3 . CORE9/CD4, CORE9/CD5 and SLES/CD1.)" It goes on to illustrate the separate directory approach. For testing, I would like to do the single directory approach. I tried copying all the CDs starting the CORE9-CD5 and working down into the same directory, then (based on SLES8 experience) I ran: cp media.2/media media.1/media When I tried to install however, it installed a few packages and then stopped prompting to insert CD2. Any guidance greatly appreciated. Dax Kelson

2 1

Re: [suse-autoinstall] SLES 8 + SP3(i386) autoinstall failed when writing LILO boot sector
by Krieger-Juhnke, Kai 16 Aug '04

16 Aug '04

Hi Frank, You wrote, you solved the the problem. What was the reason? I have the same problem, I think. The log says ..unable to stat //boot/vmlinuz.. which seems to me, that some env-variable is not set correctly. cu Kai > Kai Krieger-Juhnke > > VOLKSWAGEN BANK GMBH > Postfach I-SBS > Schmalbachstr. 1 > > D-38112 Braunschweig > > Tel.: +49 531 212-2098 > FAX: +49 531 212-72098 > email: K.KRIEGER-JUHNKE(a)VWFSAG.DE > >

3 2

xfs root-partition under suse9.1 with autoyast
by Martin Schmiderer 13 Aug '04

13 Aug '04

Hello *, i try to find a way to install suse9.1 with autoyast in a xfs root partition. I know the hotfix, but how can i involved this fix in the autoinstallation prozedure? A little howto, readme or description would be great :) Thanks in advance, and sorry about my bad english. Greetz, Martin

1 0

SLES9 PPC LVM Errors running second time on same client
by Tomas Baublys 13 Aug '04

13 Aug '04

Hello, I am using SLES9 for PPC on JS20 blade server. Running autoyast with LVM on already installed client I am getting following error: "LVM Error lvremove -f -A n /dev/system/homelv /dev/hda1: open failed: No such device or address" If I reboot the machine and run autoyast installation again without any changes anything works ok and no errors occur. So I always need to start installation twice if the client already had LVM. I do not really understand the error message above, /dev/hda1 is a prepboot partition on the pseries client and is not used for LVM. I guess, there is a way to avoid starting installation twice in order to get it running. Any help would be highly appreciated... Here is my partitioning section in the autoyast.xml file: <partitioning config:type="list"> <drive> <device>/dev/hda</device> <initialize config:type="boolean">true</initialize> <partitions config:type="list"> <partition> <crypt_fs config:type="boolean">false</crypt_fs> <crypt_key></crypt_key> <partition_nr config:type="integer">1</partition_nr> <partition_type>primary</partition_type> <format config:type="boolean">false</format> <loop_fs config:type="boolean">false</loop_fs> <mount></mount> <partition_id config:type="integer">65</partition_id> <size>16M</size> </partition> <partition> <crypt_fs config:type="boolean">false</crypt_fs> <crypt_key></crypt_key> <partition_nr config:type="integer">2</partition_nr> <partition_type>primary</partition_type> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <fstopt>noatime,acl</fstopt> <label></label> <loop_fs config:type="boolean">false</loop_fs> <mount>/</mount> <mountby config:type="symbol">device</mountby> <noauto config:type="boolean">false</noauto> <partition_id config:type="integer">131</partition_id> <size>2000M</size> </partition> <partition> <lvm_group>system</lvm_group> <crypt_fs config:type="boolean">false</crypt_fs> <crypt_key></crypt_key> <partition_nr config:type="integer">3</partition_nr> <partition_type>primary</partition_type> <format config:type="boolean">false</format> <loop_fs config:type="boolean">false</loop_fs> <mount></mount> <partition_id config:type="integer">142</partition_id> <partition_type>primary</partition_type> <size>max</size> </partition> </partitions> <use>all</use> </drive> <drive> <use>all</use> <device>/dev/system</device> <is_lvm_vg config:type="boolean">true</is_lvm_vg> <partitions config:type="list"> <partition> <filesystem config:type="symbol">ext3</filesystem> <lv_name>usrlv</lv_name> <mount>/usr</mount> <size>1200mb</size> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <lv_name>varlv</lv_name> <mount>/var</mount> <size>400mb</size> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <lv_name>homelv</lv_name> <mount>/home</mount> <size>1000mb</size> </partition> </partitions> <pesize>4M</pesize> </drive> </partitioning> Mit freundlichen Gruessen / Best regards, Tomas Baublys IBM Certified Advanced Technical Expert (CATE) pSeries and AIX pSeries Technical Sales Support JS20 Technical Focus Group Systems Sales, Central Region IBM Germany, Godesberger Allee 115, 53175 Bonn

1 0

dynamic partitioning
by Lars Stavholm 13 Aug '04

13 Aug '04

Does anyone know how to create dynamic on-the-fly partitioning? (on SuSE Linux Professional 9.1) I have a heterogenous machine park with disk layout ranging from 1 to 4 disks and various requirements, i.e. raid on some, LVM on some, raid and LVM on some. I would like to create the partitioning scheme as part of the (lovely) automated installation process using autoyast. However, I've played around with the rules mechanism and as far as I can see, there's gonna be a lot of extra coding to cover every possible scenario as opposed to creating the partitioning on-the-fly. Also, does anyone have the XML XInclude feature working on SuSE Pro 9.1? I've tried and I just can't get it to work for me. Any hints? R -- stava(a)jonitec.se

3 2

errors while trying to re-install printer with YaST (SuSE 9.1)
by Thomas Caldwell 13 Aug '04

13 Aug '04

I have been using SuSE 9.1 for about a month. Everything was working well until a printing error came about while I was trying to get my HP LJ 6MP to recognize my manual feed tray. I tried re-configuring and then re-installing the printer with YaST, but it refuses to print out a test page. Now I'm getting the following error messages: cups(File)DoRequest error: client-error-not-authorized lpr: unable to print file: client-error-request-value-too-long I'm not a newcomer to Linux, but am a newcomer to SuSE 9.1 and CUPS. Can anyone tell me what specifically these error messages mean and what might be causing them? Thanks!

1 0

Re: [suse-autoinstall] Default keyboard layout is German after install
by Anthony Staples 12 Aug '04

12 Aug '04

Anas, Thanks for your quick response. The header of the the XF86Config on the autoinstalled machine is: # Generic XFree86 configuration file If, as you said below, there is no need for locale in x11 config, then how can configuring it in AutoYast effect the keymap on my installed systems. Since the header is as above, it doesn't seem to make any difference. I checked and then rechecked that my locale settings in "General" were correct. here is a snip from the profile... ( it won't let me paste the full profile due to size limitations...) <general> <clock> <hwclock>UTC</hwclock> <timezone>US/Eastern</timezone> </clock> <keyboard> <keymap>english-us</keymap> </keyboard> <language>en_US</language> <mode> <confirm config:type="boolean">false</confirm> <forceboot config:type="boolean">false</forceboot> </mode> <mouse> <id>22_exps2</id> </mouse> </general> Why shouldn't the general setting be propagated throughout the installed machine? I checked the setting in YAST and keyboard configuration was correctly set to English(US). Cheers, Tony Anas Nashif <nashif(a)suse.de> To: Anthony Staples <astaples(a)humana.com> cc: lmarks(a)novell.com, pgriffen(a)novell.com, Lee Mayes <autoinst(a)mayeses.com>, 08/12/2004 11:19 suse-autoinstall(a)suse.com AM Subject: Re: [suse-autoinstall] Default keyboard layout is German after install Anthony, There is no need for locale in the x11 config, the system settings are taken. After using the configuration below, what does the header in the /etc/X11/XF86Config file say? Anas Anthony Staples wrote: > > > > Anas, > Just to clarify, I am running NLD beta not SuSE 9.1 pro. > When I rec'd Lee's response this morning (Thanks!) I tried just what you > suggested, Anas. > I thought that the issue may be in the X11 default config so I created > (using autoyast) a new reference profile from my original and included an > X11 configuration: > Here is the X11 section of my reference profile, though I don't see > anyplace where the keymap is actually set... > > <x11> > <color_depth config:type="integer">16</color_depth> > <configure_x11 config:type="boolean">true</configure_x11> > <display_manager>gdm</display_manager> > <enable_3d config:type="boolean">false</enable_3d> > <monitor> > <display> > <frequency config:type="integer">60</frequency> > <height config:type="integer">768</height> > <width config:type="integer">1024</width> > </display> > <monitor_device>1024X768@60HZ</monitor_device> > <monitor_vendor> LCD</monitor_vendor> > </monitor> > <resolution>1024x768</resolution> > <window_manager>gnome</window_manager> > </x11> > > > I then proceeded to install a machine with the updated profile, but still > get the German default keymap rather than US keymap. > Is there anyway for us to change the default keymap in the XF86Config that > Autoyast uses? Before profile generation rather than after... > > Regards, > > Anthony Staples > Technical Analyst > Humana Inc. > 502.580.2870 > > > > > > Anas Nashif > <nashif(a)suse.de> To: Lee Mayes <autoinst(a)mayeses.com> > cc: Anthony Staples <astaples(a)humana.com>, suse-autoinstall(a)suse.com > 08/12/2004 09:03 Subject: Re: [suse-autoinstall] Default keyboard layout is German after install > AM > > > > > > > > Hi, > > This is because you dont configure X using autoyast and the default > /etc/X11/XF86Config happens to be in german ;( > > Anas > > > Lee Mayes wrote: > >>Hi Tony, >> >> I noticed that on my SuSE 9.1 AutoYaST installs, the keyboard is set >>correctly in everything but X11. I added the following 2 lines in my >>post install user script to fix it: >> >> print KS qq[ >>/bin/cp /etc/X11/XF86Config /tmp/XF86Config.back >>/usr/bin/sed -e 's/XkbLayout"\\t"de/XkbLayout"\\t"$x_kbd/' \ >> </tmp/XF86Config.back >/etc/X11/XF86Config >>]; >> >> >>In my case $x_kbd is a variable passed to the perl script creating >>autoyast.xml. I made a simple 'table' that cross references linux >>keyboard environment variables to the X11 ones. I can provide it if >>needed, it's mostly complete but has a few languages I wasn't sure how >>to cross reference. >> >> I think if I had fully qualified X's config (vs. letting it default) I >>wouldn't have seen the problem. There are probably other ways to fix it >>as well, but I was in a hurry and this works for us. >> >>Best Regards, >> >>Lee >> >>On Wed, 2004-08-11 at 14:24, Anthony Staples wrote: >> >> >>>When i do an autoyast install I always get a german default keyboard > > rather > >>>than US-English. >>>I explicitly set the layout to US-English in the reference profile. All >>>other settings seem to be ok. >>> >>>Any insight on how to fix this would be appreciated!! >>> >>>Cheers, >>>Tony Staples >>>astaples(a)humana.com >>> >>>Here is a snip from my autoyast reference profile... >>> >>> <general> >>> <clock> >>> <hwclock>UTC</hwclock> >>> <timezone>US/Eastern</timezone> >>> </clock> >>> <keyboard> >>> <keymap>english-us</keymap> >>> </keyboard> >>> <language>en_US</language> >>> <mode> >>> <confirm config:type="boolean">false</confirm> >>> <forceboot config:type="boolean">false</forceboot> >>> </mode> >>> <mouse> >>> <id>22_exps2</id> >>> </mouse> >>> </general> >>> >>> >>> >>>The information transmitted is intended only for the person or entity to > > which it is addressed and may contain CONFIDENTIAL material. If you > receive this material/information in error, please contact the sender and > delete or destroy the material/information. > >> >> > > -- > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > For additional commands, e-mail: suse-autoinstall-help(a)suse.com > > > > > > > The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information. -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.

2 1

modifying cramfs?
by Harald Finnås 12 Aug '04

12 Aug '04

I've just fixed the dtd files so that I can get autoyast to recognize all my options just fine, but now the problem is how to get the source updated. If I understand this correctly, the /usr filesystem used during installation is a mount of the "root" file, which seems to be cramfs. AFAIK, cramfs has to be recreated since it's a RO fs, but how can I do this? Another problem I've run into btw. :) I've configured only one nic in the xml file, eth0, although this is a dualnic box. Problem is that the config file is named ifcfg-eth-id:<mac addr> and the nic is actually using dhcp after the first boot. If I rename the file to ifcfg-eth0 and restart network, everything works as expected. Any suggestions? Regards, Harald

2 1

Partitioning question........No Free Space Availiable...Error
by Aaron Amauba 12 Aug '04

12 Aug '04

I am Installing SLES8 using autoyast via NFS. I wanted to create a autoyast file that would install on either hd or sd devices. I assumed I could just remove the <device> tag from the control file and yast would use the first disk device found. When yast beginds to configure the partition table an error window appears that says "No Free Space on /dev/sda/". Must I specify a <device> tag or is there another tag I must use to force Yast to blow away the old partition table on the device. Below is my partion section, maybe it is incorrect. Thanks for your help in advance. <partitioning config:type="list"> <drive> <use>all</use> <partitions config:type="list"> <partition> <crypt_fs config:type="boolean">false</crypt_fs> <crypt_key></crypt_key> <format config:type="boolean">false</format> <mount>swap</mount> <partition_id config:type="integer">130</partition_id> <partition_nr config:type="integer">1</partition_nr> <partition_type>primary</partition_type> <size>2GB</size> </partition> <partition> <crypt_fs config:type="boolean">false</crypt_fs> <crypt_key></crypt_key> <format config:type="boolean">false</format> <mount>/</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">2</partition_nr> <partition_type>primary</partition_type> <size>10GB</size> </partition> <partition> <crypt_fs config:type="boolean">false</crypt_fs> <crypt_key></crypt_key> <format config:type="boolean">false</format> <mount></mount> <partition_id config:type="integer">5</partition_id> <partition_nr config:type="integer">3</partition_nr> <partition_type>primary</partition_type> <size>7GB</size> </partition> <partition> <crypt_fs config:type="boolean">false</crypt_fs> <crypt_key></crypt_key> <format config:type="boolean">false</format> <mount></mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">5</partition_nr> <size>1GB</size> </partition> <partition> <crypt_fs config:type="boolean">false</crypt_fs> <crypt_key></crypt_key> <format config:type="boolean">false</format> <mount></mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">6</partition_nr> <size>1GB</size> </partition> <partition> <crypt_fs config:type="boolean">false</crypt_fs> <crypt_key></crypt_key> <format config:type="boolean">false</format> <mount></mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">7</partition_nr> <size>1GB</size> </partition> <partition> <crypt_fs config:type="boolean">false</crypt_fs> <crypt_key></crypt_key> <format config:type="boolean">false</format> <mount></mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">8</partition_nr> <size>1GB</size> </partition> <partition> <crypt_fs config:type="boolean">false</crypt_fs> <crypt_key></crypt_key> <format config:type="boolean">false</format> <mount></mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">9</partition_nr> <size>1GB</size> </partition> <partition> <crypt_fs config:type="boolean">false</crypt_fs> <crypt_key></crypt_key> <format config:type="boolean">false</format> <mount></mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">10</partition_nr> <size>2GB</size> </partition> <partition> <crypt_fs config:type="boolean">false</crypt_fs> <crypt_key></crypt_key> <format config:type="boolean">false</format> <mount>/home</mount> <partition_id config:type="integer">131</partition_id> <partition_type>primary</partition_type> <size>max</size> </partition> </partitions> </drive> </partitioning> --------------------------------- Do you Yahoo!? New and Improved Yahoo! Mail - Send 10MB messages!

2 1

Re: [suse-autoinstall] Default keyboard layout is German after install
by Anthony Staples 12 Aug '04

12 Aug '04

Anas, Just to clarify, I am running NLD beta not SuSE 9.1 pro. When I rec'd Lee's response this morning (Thanks!) I tried just what you suggested, Anas. I thought that the issue may be in the X11 default config so I created (using autoyast) a new reference profile from my original and included an X11 configuration: Here is the X11 section of my reference profile, though I don't see anyplace where the keymap is actually set... <x11> <color_depth config:type="integer">16</color_depth> <configure_x11 config:type="boolean">true</configure_x11> <display_manager>gdm</display_manager> <enable_3d config:type="boolean">false</enable_3d> <monitor> <display> <frequency config:type="integer">60</frequency> <height config:type="integer">768</height> <width config:type="integer">1024</width> </display> <monitor_device>1024X768@60HZ</monitor_device> <monitor_vendor> LCD</monitor_vendor> </monitor> <resolution>1024x768</resolution> <window_manager>gnome</window_manager> </x11> I then proceeded to install a machine with the updated profile, but still get the German default keymap rather than US keymap. Is there anyway for us to change the default keymap in the XF86Config that Autoyast uses? Before profile generation rather than after... Regards, Anthony Staples Technical Analyst Humana Inc. 502.580.2870 Anas Nashif <nashif(a)suse.de> To: Lee Mayes <autoinst(a)mayeses.com> cc: Anthony Staples <astaples(a)humana.com>, suse-autoinstall(a)suse.com 08/12/2004 09:03 Subject: Re: [suse-autoinstall] Default keyboard layout is German after install AM Hi, This is because you dont configure X using autoyast and the default /etc/X11/XF86Config happens to be in german ;( Anas Lee Mayes wrote: > Hi Tony, > > I noticed that on my SuSE 9.1 AutoYaST installs, the keyboard is set > correctly in everything but X11. I added the following 2 lines in my > post install user script to fix it: > > print KS qq[ > /bin/cp /etc/X11/XF86Config /tmp/XF86Config.back > /usr/bin/sed -e 's/XkbLayout"\\t"de/XkbLayout"\\t"$x_kbd/' \ > </tmp/XF86Config.back >/etc/X11/XF86Config > ]; > > > In my case $x_kbd is a variable passed to the perl script creating > autoyast.xml. I made a simple 'table' that cross references linux > keyboard environment variables to the X11 ones. I can provide it if > needed, it's mostly complete but has a few languages I wasn't sure how > to cross reference. > > I think if I had fully qualified X's config (vs. letting it default) I > wouldn't have seen the problem. There are probably other ways to fix it > as well, but I was in a hurry and this works for us. > > Best Regards, > > Lee > > On Wed, 2004-08-11 at 14:24, Anthony Staples wrote: > >> >>When i do an autoyast install I always get a german default keyboard rather >>than US-English. >>I explicitly set the layout to US-English in the reference profile. All >>other settings seem to be ok. >> >>Any insight on how to fix this would be appreciated!! >> >>Cheers, >>Tony Staples >>astaples(a)humana.com >> >>Here is a snip from my autoyast reference profile... >> >> <general> >> <clock> >> <hwclock>UTC</hwclock> >> <timezone>US/Eastern</timezone> >> </clock> >> <keyboard> >> <keymap>english-us</keymap> >> </keyboard> >> <language>en_US</language> >> <mode> >> <confirm config:type="boolean">false</confirm> >> <forceboot config:type="boolean">false</forceboot> >> </mode> >> <mouse> >> <id>22_exps2</id> >> </mouse> >> </general> >> >> >> >>The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information. > > > -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.

2 1

Default keyboard layout is German after install
by Anthony Staples 12 Aug '04

12 Aug '04

When i do an autoyast install I always get a german default keyboard rather than US-English. I explicitly set the layout to US-English in the reference profile. All other settings seem to be ok. Any insight on how to fix this would be appreciated!! Cheers, Tony Staples astaples(a)humana.com Here is a snip from my autoyast reference profile... <general> <clock> <hwclock>UTC</hwclock> <timezone>US/Eastern</timezone> </clock> <keyboard> <keymap>english-us</keymap> </keyboard> <language>en_US</language> <mode> <confirm config:type="boolean">false</confirm> <forceboot config:type="boolean">false</forceboot> </mode> <mouse> <id>22_exps2</id> </mouse> </general> The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.

3 2

autoyast & SCPM
by Steve Potter 11 Aug '04

11 Aug '04

I'm trying to set up a number of laptops with multiple SCPM configuration profiles (one for standalone, one for the office network, etc). Does autoyast have any provision for SCPM? From a quick look at the documentation and the dtd's, it doesn't look like it. I guess my best option is to use autoyast to create the configuration with the most turned on (nis, nfs mounts, etc) and then manually create the other configurations with things turned off. Thanks! Steve Potter __________________________________ Do you Yahoo!? New and Improved Yahoo! Mail - Send 10MB messages! http://promotions.yahoo.com/new_mail

1 0

AW: [suse-autoinstall] Conflicting package
by Krieger-Juhnke, Kai 11 Aug '04

11 Aug '04

Hi Anas, that's it. Many thanks Kai Kai Krieger-Juhnke -----Ursprüngliche Nachricht----- Von: Anas Nashif [mailto:nashif@suse.de] Gesendet: Dienstag, 10. August 2004 01:38 An: Krieger-Juhnke, Kai Cc: 'suse-autoinstall(a)suse.com' Betreff: Re: [suse-autoinstall] Conflicting package What about installing the file without using RPM using the chroot scripts? Anas Krieger-Juhnke, Kai wrote: > Hello list, > does anyone knows how to install a conflicting package (i.e. a > device-driver, which is included in an older version in the > kernel-package) using autoyast? > > Manually, this job would be done using rpm -i --force <package-file>. > Unfortunately, as I want to update the device-driver for the nic, I > cannot use a post-installation-script, because at that time the system > as allready rebooted. > > Thanks for any hints, > > > */Kai Krieger-Juhnke/*// > > VOLKSWAGEN BANK GMBH > Postfach I-SBS > Schmalbachstr. 1 > > D-38112 Braunschweig > > Tel.: +49 531 212-2098 > FAX: +49 531 212-72098 > email: K.KRIEGER-JUHNKE(a)VWFSAG.DE > >

1 0

Updating rpms on source
by Harald Finnås 10 Aug '04

10 Aug '04

Just wondering if there's an easy procedure to update the source media with the lastest rpms from the updates branch? I've got a feeling there are several package lists that needs to be updated making it alot of work... :) Regards, Harald

1 0

Updating installation
by Harald Finnås 10 Aug '04

10 Aug '04

I've been trying to autoinstall from the 9.1 DVD for a while now, but I've given up on this due to all the bugs I've run into. In an attempt to have more control over the source, I've decided to set up and installation server instead so that I may update all the stuff that's missing in the .dtd files etc. My question is if someone out there has updated .dtd files that works with most of the xml code yast2 generates, or do I have to figure out what's missing myself? Regards, Harald

1 0

Conflicting package
by Krieger-Juhnke, Kai 09 Aug '04

09 Aug '04

Hello list, does anyone knows how to install a conflicting package (i.e. a device-driver, which is included in an older version in the kernel-package) using autoyast? Manually, this job would be done using rpm -i --force <package-file>. Unfortunately, as I want to update the device-driver for the nic, I cannot use a post-installation-script, because at that time the system as allready rebooted. Thanks for any hints, > Kai Krieger-Juhnke > > VOLKSWAGEN BANK GMBH > Postfach I-SBS > Schmalbachstr. 1 > > D-38112 Braunschweig > > Tel.: +49 531 212-2098 > FAX: +49 531 212-72098 > email: K.KRIEGER-JUHNKE(a)VWFSAG.DE > >

2 1

autoyast with suse 9.1
by Todd Merritt 09 Aug '04

09 Aug '04

I've read the documentation at http://www.suse.de/~nashif/autoinstall/9.1/html/, and several other sites I found explaining how to create an autoyast.xml file from a complete installation. The instructions for 9.1 don't specify what rpms need to be installed and when I run yast2 autoyast I get: No such client module autoyast I tried installing the modules I found referenced from documents on 8.x (yast-config-autoinst), but I still get the same message. Can somebody point me in the right direction ? Thanks, Todd

5 5

LVM on Raid-1 using same disks problem
by Tomas Baublys 06 Aug '04

06 Aug '04

Hello, I have the same problem mentioned some times since 2002 in the list, unfortunately I did not found an answer which works for me. I am installing SLES8 through autoyast with software raid and LVM on it. Software Raid contains two partitions (sda3 and sdb3) as I can not use whole disks. The machine is a pSeries p690 LPAR so a PrepBoot partition is required on each disk. The installation worked fine for the first time, repeating the installation on the same disks produced an error: can not create md0 device and can not create system volume group- volume group already exists. I am using <initialize config:type="boolean">true</initialize> in each drive section And <destroy_old config:type="boolean">true</destroy_old> in lvmgroup. I guess the problem is related to the persistent superblock used by software raid and VGDA on the disk used by LVM. I also tried using a prescript: dd if=/dev/zero of=/dev/sda bs=1MB count=3 dd if=/dev/zero of=/dev/sdb bs=1MB count=3 # this does not works: blockdev --rereadpt /dev/sda blockdev --rereadpt /dev/sdb For network boot on pSeries I am using SUSE SLES8 SP3 Kernel with the builtin commandline: ./mkzimage_cmdline -a -1 -c -s "insmod=e100 insmod=e1000 hostip=9.156.175.22 netmask=255.255.255.0 install=nfs://9.156.175.8/software/Linux/PPC/SLES8/unpacked/CD1 autoyast=tftp://9.156.175.8/tftpboot/autoyast_tb.xml" install.tb Unfortunately I can overwrite the begining of the disk, but rereading the partition table fails (disc is in use message in the log). Is there any trick how to reread the partition table or to get rid of the persistent Superblock and VGDA before the installation starts? Now, I need to start installation, read the error messages about raid and lvm, restart installation and it works fine running second time. It also works fine on a new LPAR. Any help is welcome.. Mit freundlichen Gruessen / Best regards, Tomas Baublys IBM Certified Advanced Technical Expert (CATE) pSeries and AIX pSeries Technical Sales Support JS20 Technical Focus Group Systems Sales, Central Region here is my autoyast control file: root@csm:/tftpboot> cat autoyast_tb.xml <?xml version="1.0"?> <!DOCTYPE profile SYSTEM "/usr/share/YaST2/include/autoinstall/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">false</dhcp_hostname> <dhcp_resolv config:type="boolean">false</dhcp_resolv> <domain>munich.de.ibm.com</domain> <hostname>p690-lpar2</hostname> <nameservers config:type="list"> </nameservers> <searchlist config:type="list"> <search>ibm.com</search> </searchlist> </dns> <interfaces config:type="list"> <interface> <bootproto>static</bootproto> <broadcast></broadcast> <device>eth0</device> <ipaddr>9.156.175.22</ipaddr> <module>e100</module> <netmask>255.255.255.0</netmask> <network>9.156.175.0</network> <options></options> <remote_ipaddr></remote_ipaddr> <startmode>onboot</startmode> <wireless>no</wireless> </interface> </interfaces> <routing> <ip_forward config:type="boolean">false</ip_forward> <routes config:type="list"> <route> <destination>default</destination> <device>-</device> <gateway>9.156.175.1</gateway> <netmask>-</netmask> </route> </routes> </routing> </networking> <scripts> <chroot-scripts config:type="list"/> <post-scripts config:type="list"> <script> <filename>postinstalltasks.sh</filename> <interpreter>shell</interpreter> <source> <![CDATA[ /sbin/lilo dd if=/dev/sda1 of=/dev/sdb1 mkdir /mnt/sp3 mount 9.156.175.8:/software/Linux/PPC/SLES8/unpacked/Fixpack3-CD1 /mnt/sp3 rpm -Fvh /mnt/sp3/ppc/update/SuSE-SLES/8/rpm/ppc/kernel-ppc64-2.4.21-111.ppc.rpm /usr/bin/installation_sources -e -a nfs://9.156.175.8:/software/Linux/PPC/SLES8/unpacked/Fixpack3-CD1 ]]> </source> </script> </post-scripts> <pre-scripts config:type="list"> <script> <filename>eliminator.sh</filename> <interpreter>shell</interpreter> <source> <![CDATA[ vgchange -an vgremove system pvchange -ax mount -t nfs 9.156.175.8:/software/Linux/PPC /mnt /mnt/mdadm --zero-superblock /dev/sda /mnt/mdadm --zero-superblock /dev/sdb /mnt/mdadm -S /dev/md0 umount /mnt vgscan vgchange -an vgreduce system -a -v vgchange -a y system lvremove -f /dev/system/usrlv lvremove -f /dev/system/swaplv lvremove -f /dev/system/usrlv lvremove -f /dev/system/homelv lvremove -f /dev/system/* vgchange -a n system vgremove system dd if=/dev/zero of=/dev/sda bs=1MB count=3 dd if=/dev/zero of=/dev/sdb bs=1MB count=3 # klappt erst nach reboot blockdev --rereadpt /dev/sda blockdev --rereadpt /dev/sdb ]]> </source> </script> </pre-scripts> </scripts> <files config:type="list"> <config_file> <file_path>/etc/lilo.conf</file_path> <file_contents> <![CDATA[ # lilo von autoyast default=linux timeout=100 boot=/dev/sda1 activate image = /boot/vmlinuz label = linux root = /dev/sda2 # initrd = /boot/initrd append = "" ]]> </file_contents> </config_file> <config_file> <file_path>/root2/etc/lilo.conf</file_path> <file_contents> <![CDATA[ # sdb lilo von autoyast default=linux timeout=100 boot=/dev/sdb1 activate image = /boot/vmlinuz label = linux root = /dev/sdb2 # initrd = /boot/initrd append = "" ]]> </file_contents> </config_file> <config_file> <file_path>/etc/ntp.conf</file_path> <file_contents> <![CDATA[ # ntp config von autoyast server 192.53.103.103 server 192.53.103.104 ]]> </file_contents> </config_file> </files> <users config:type="list"> <user> <encrypted config:type="boolean">true</encrypted> <user_password>XGULujbJ2KVmI</user_password> <username>root</username> </user> </users> </configure> <install> <bootloader> <location>ppc_chrp</location> <prep_boot_partition>/dev/sda1</prep_boot_partition> </bootloader> <general> <clock> <hwclock>localtime</hwclock> <timezone>Europe/Berlin</timezone> </clock> <keyboard> <keymap>german</keymap> </keyboard> <language>de_DE</language> <mode> <confirm config:type="boolean">false</confirm> <forceboot config:type="boolean">false</forceboot> <interactive_boot config:type="boolean">false</interactive_boot> <reboot config:type="boolean">false</reboot> </mode> <mouse> <id>none</id> </mouse> </general> <partitioning config:type="list"> <drive> <device>/dev/sda</device> <use>all</use> <initialize config:type="boolean">true</initialize> <partitions config:type="list"> <partition> <partition_nr config:type="integer">1</partition_nr> <partition_type>primary</partition_type> <crypt_fs config:type="boolean">false</crypt_fs> <crypt_key></crypt_key> <format config:type="boolean">false</format> <mount></mount> <partition_id config:type="integer">65</partition_id> <size>7.8MB</size> </partition> <partition> <partition_nr config:type="integer">2</partition_nr> <partition_type>primary</partition_type> <crypt_fs config:type="boolean">false</crypt_fs> <crypt_key></crypt_key> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <fstopt>noatime,data=ordered</fstopt> <label>ROOT</label> <mount>/</mount> <mountby config:type="symbol">device</mountby> <partition_id config:type="integer">131</partition_id> <size>2GB</size> </partition> <partition> <crypt_fs config:type="boolean">false</crypt_fs> <crypt_key></crypt_key> <format config:type="boolean">false</format> <raid_name>/dev/md0</raid_name> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">3</partition_nr> <size>max</size> </partition> </partitions> </drive> <drive> <device>/dev/sdb</device> <use>all</use> <initialize config:type="boolean">true</initialize> <partitions config:type="list"> <partition> <partition_nr config:type="integer">1</partition_nr> <partition_type>primary</partition_type> <crypt_fs config:type="boolean">false</crypt_fs> <crypt_key></crypt_key> <format config:type="boolean">false</format> <mount></mount> <partition_id config:type="integer">65</partition_id> <size>7.8MB</size> </partition> <partition> <partition_nr config:type="integer">2</partition_nr> <partition_type>primary</partition_type> <crypt_fs config:type="boolean">false</crypt_fs> <crypt_key></crypt_key> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <fstopt>noatime,data=ordered</fstopt> <size>2GB</size> <label>ROOT2</label> <mount>/root2</mount> </partition> <partition> <crypt_fs config:type="boolean">false</crypt_fs> <crypt_key></crypt_key> <format config:type="boolean">false</format> <raid_name>/dev/md0</raid_name> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">3</partition_nr> <size>max</size> </partition> </partitions> </drive> </partitioning> <raid config:type="list"> <raid_device> <device_name>/dev/md0</device_name> <parity_algorithm>left-asymmetric</parity_algorithm> <persistent_superblock config:type="boolean">true</persistent_superblock> <raid_type>raid1</raid_type> <lvm_group>system</lvm_group> <mount /> <format config:type="boolean">false</format> </raid_device> </raid> <lvm config:type="list"> <lvm_group> <destroy_old config:type="boolean">true</destroy_old> <lvm_name>system</lvm_name> <pesize>16M</pesize> <logical_volumes config:type="list"> <lv> <lv_name>usrlv</lv_name> <lv_size>1GB</lv_size> <lv_fs>ext3</lv_fs> <lv_mount>/usr</lv_mount> </lv> <lv> <lv_name>swaplv</lv_name> <lv_size>512MB</lv_size> <lv_mount></lv_mount> </lv> <lv> <lv_name>varlv</lv_name> <lv_size>512MB</lv_size> <lv_fs>ext3</lv_fs> <lv_mount>/var</lv_mount> </lv> <lv> <lv_name>varloglv</lv_name> <lv_size>512MB</lv_size> <lv_fs>ext3</lv_fs> <lv_mount>/var/log</lv_mount> </lv> <lv> <lv_name>optlv</lv_name> <lv_size>512MB</lv_size> <lv_fs>ext3</lv_fs> <lv_mount>/opt</lv_mount> </lv> <lv> <lv_name>homelv</lv_name> <lv_size>512MB</lv_size> <lv_fs>ext3</lv_fs> <lv_mount>/home</lv_mount> </lv> </logical_volumes> </lvm_group> </lvm> <software> <base>Minimal</base> <packages config:type="list"> <package>tripwire</package> <package>rsync</package> <package>xntp</package> <package>raidtools</package> <package>vim</package> <package>autoyast2-installation</package> </packages> </software> </install> </profile>

1 0

Problems with autoinstall sles9
by Sohst, Martin 05 Aug '04

05 Aug '04

Hi all, I'm trying to autoinstall SLES9 via NFS My problem is, that after all packages have been loaded, and the first reboot starts the system does not configure itself. Especially network settings are not done which prevents any post install script to run. How can this be fixed ? Also I'm trying to autoinstall a HP ProLiant DL360 with SLES9 but the kernel and initrd in boot/loader (CD1) do not work. I guess the cciss driver is missing. (i'm using a suse9.1 kernel to install) Martin

1 0

[suse-autoinstall] problem with resolv.conf
by m.frerichs 05 Aug '04

05 Aug '04

Hallo, I 'm trying to install the file /etc/resolv.conf on a linux 9.1 client with autoinstallation. My xml-file looks like this: 1) <configure> <networking> <dns> <dhcp_hostname config:type="boolean">true</dhcp_hostname> <domain>zam.kfa-juelich.de</domain> <hostname>zam724</hostname> <nameservers config:type="list"> <nameserver>134.94.80.2</nameserver> <nameserver>134.94.80.3</nameserver> <nameserver>134.94.100.7</nameserver> </nameservers> <searchlist config:type="list"> <search>zam.kfa-juelich.de</search> <search>kfa-juelich.de</search> <search>fz-juelich.de</search> </searchlist> </dns> <scripts> <post-scripts config:type="list"> <script> <filename>post.sh</filename> <interpreter>shell</interpreter> <source> .... During executing post.sh-script I listed /etc/resolv.conf. It is installed with searchline and nameserver , but without line " domain zam.kfa-juelich.de" 2) to prevent several daemons from changing resolv.conf I inserted: <sysconfig config:type="list"> <sysconfig_entry> <sysconfig_key>XNTPD_INITIAL_NTPDATE</sysconfig_key> <sysconfig_path>xntp</sysconfig_path> <sysconfig_value>134.94.80.2</sysconfig_value> </sysconfig_entry> <sysconfig_entry> <sysconfig_key>MODIFY_RESOLV_CONF_DYNAMICALLY</sysconfig_key> <sysconfig_path>/etc/sysconfig/network/config</sysconfig_path> <sysconfig_value>no</sysconfig_value> </sysconfig_entry> </sysconfig> .... --> /etc/sysconfig/network/config is installed with line MODIFY_RESOLV_CONF_DYNAMICALLY="no" a) /etc/resolv.conf is linked to a file mounted readonly by nfs in post.sh which is valid to all our clients , without 2) --> link is overwritten, resolv.conf is changed by dhcpd , pay attention to length 0 of /etc/resolv.conf.saved.by.dhcpcd zam724:~ # ls -l /etc/reso* -rw-r--r-- 1 root root 1321 Aug 5 12:42 /etc/resolv.conf -rw-r--r-- 1 root root 125 Aug 5 12:20 /etc/resolv.conf.install -rw-r--r-- 1 root root 0 Aug 5 12:42 /etc/resolv.conf.saved.by.dhcpcd b) /etc/resolv.conf is installed as a link to a file mounted ro by nfs in post.sh and with 2) :MODIFY_RESOLV_CONF_DYNAMICALLY="no" --> When system boots for the first time, there are the following errormessages on screen and /etc/resolv.conf becomes an empty file!!!!! grep resolv /var/log/* boot.msg:Cleaning up using /sbin/modify_resolvconf: boot.msg:touch: cannot touch `/etc/resolv.conf': No such file or directory boot.msg:Deleted the following stale backups: removed `/etc/resolv.conf.saved.by.yast2' boot.msg:sed: can't read /etc/resolv.conf: No such file or directory boot.msg:cat: /etc/resolv.conf: No such file or directory messages:Aug 4 11:24:15 linux modify_resolvconf: Service yast2 modified /etc/resolv.conf. See info block in this file messages:Aug 4 11:25:59 linux modify_resolvconf: Service yast2 tried to modify resolver configuration, but it messages:Aug 4 11:25:59 linux modify_resolvconf: was not modified due to MODIFY_RESOLV\NAMED_CONF_DYNAMICALLY=no messages:Aug 4 11:44:50 linux modify_resolvconf: Service dhcpcd tried to modify resolver configuration, but it messages:Aug 4 11:44:50 linux modify_resolvconf: was not modified due to MODIFY_RESOLV\NAMED_CONF_DYNAMICALLY=no Thanks for your answers and improvements +----------------------------------------------------------------------+ | Marianne Frerichs | | Zentralinstitut fuer Angewandte Mathematik | | Forschungszentrum Juelich GmbH | | D-52425 Juelich | | Phone: +49 02461 61-6432 | | Email: M.Frerichsfz-juelich.de Fax: +49 02461 61-6656 | +----------------------------------------------------------------------+

2 1

AutoYaST messages: How do you set the default response and timeout for the yesno_message tag?
by Chris Partridge 03 Aug '04

03 Aug '04

Hi, I am just beginning to use the autoinstall with SLES 9-RC5 and I noticed the reference profile generates a tag for "yesno_messages" with the same defaults as the other message tags. But I don't think it's really doing anything. I have a few windows pop up during installation (confirm a driver installation, continue detecting NIC) and I want those to timeout and continue. How do I do that? Here is the tag I have right now: <yesno_messages> <show config:type="boolean">true</show> <timeout config:type="integer">10</timeout> <log config:type="boolean">true</log> </yesno_messages> Chris

2 1

users
by Todd Merritt 02 Aug '04

02 Aug '04

I'm trying to use autoyast with suse 9.1, I seem to be stuck on creating user accounts. I'm just trying to have the base system accounts created during the install, but I get an group file with only +::: and a password file with +::::, and I'm not configuring nis. I tried just not putting any users in, but then I got no root password, if I have it create root, it creates it like a normal user account. Two questions, what am I doing wrong, and how do I configure autoyast to NOT configure the machine as a nis client ? I'd be happy to sent the config file if needed. Thanks, Todd

1 0

Installing with Fibre attached drive onto local scsi device
by Aaron Amauba 02 Aug '04

02 Aug '04

Sorry if this question has already been addressed here on the lists. I am new to the SAN enviornment and am haveing a difficult time installing SLES8 onto a machine while it is attached to the SAN. At installation time (I use autoyast via NFS) the fibre attached LUN is being seen first and is being assigned /dev/sda. How do I force the local scsi device to be seen as /dev/sda? I looked in linuxrc in initrd, but it wasnt a script. Thanks in advance. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

1 1

autoyast soundcard detection and configuration
by jan terje tønnessen 02 Aug '04

02 Aug '04

Hi ! Trying to set up suse91 autoyast. I can't figure out how to set that the soundcard shall be autodetected and configured. Have tried something like <sound> <autoinstall config:type="boolean">true</autoinstall> </sound> /JT

1 0