August 2004 - openSUSE Autoinstall - openSUSE Mailing Lists

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