March 2006 - openSUSE Autoinstall - openSUSE Mailing Lists

Scripting dirinstall?
by Teun 25 Feb '07

25 Feb '07

Does anyone know if it is possible to use the 'dirinstall' from the command line? For instance i would like to be able to do something like: # yast dirinstall -d /someroot -s mypackages.sel If i do yast -h it says: "Usage: /sbin/yast [OPTIONS] [MODULE] [module specific parameters]" But is there a way to find out what 'module specific parameters' are available for a specific module? Thanks, Teun

3 2

Re: [suse-autoinstall] Where are instorder and order in SLES 10?
by Uwe Gansert 06 Apr '06

06 Apr '06

On Monday 13 March 2006 16:25, Klaus Kaempf wrote: > > you are right, yast/order and yast/instorder will not work for SLES10 > > I'll try to find out how the new resolver wants that now. > > This will be defined by jsrain(a)suse.cz > He's already working on the new specification. I'll announce the solution here on the mailinglist as soon as the specification is ready. -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nuernberg, Germany e-mail: uwe.gansert(a)suse.de, Tel: +49-(0)911-74053-0, Fax: +49-(0)911-74053-476, Web: http://www.suse.de

2 1

autoyast network interfaces won't come online
by Zywusko, Matt 31 Mar '06

31 Mar '06

Hi, I'm trying to move deployments from SLES9 SP1 to SP3 using the same control file. Here's a snippet of xml I'm having trouble getting to work with SP3: <interfaces config:type="list"> <interface> <bootproto>static</bootproto> <broadcast>172.30.192.255</broadcast> <device>eth0</device> <ipaddr>172.30.192.12</ipaddr> <netmask>255.255.255.0</netmask> <network>172.30.192.0</network> <startmode>onboot</startmode> </interface> </interfaces> With SP1, after the install, my network comes up fine whether I'm using a static IP or DHCP assigned. Installing with SP3, the interfaces never get configured and the ifcfg-ethX files aren't written out to disk. I have a workaround that I'm applying right now where I write the ifcfg-ethX files out via a post install script embedded in the xml but I would much rather not hack it in. Any help is appreciated. -Matt

1 0

X11 default is german
by dbellis＠mmm.com 31 Mar '06

31 Mar '06

What is the best way to set the default keyboard layout to english-us in an AutoYaST installation? (SLES9) It appears my keyboard map is correct, but my X11 setup isn't. Thanks, David Bellis

1 0

Update of driverupdate makes that IBM x346 doesn't want to reboot anymore
by Johan Kielbaey 31 Mar '06

31 Mar '06

Hello, This issue occured both with SLES 9 SP2 and SLES 9 SP3 on an IBM x346. We have different hardwaremodels (IBM x306m, IBM x346, ...). To install SLES9 SP2 on an IBM x306m we needed to provide a diskette with the driverupdate for the raid controller. I added this driver in the driverupdate from SLES 9 SP2 (used scripts on site of Uwe Gansert to do this). Installation of my testserver (which is an IBM x346) goes fine. However the server hangs when i reboot the server after logging in. (install uses the default sp2 kernel. reboot is needed to activate the bigsmp kernel). During reboot the server hangs after the message "Please stand by while rebooting the system...". Since nothing happens I press CTRL-ALT-DEL in order to try to reboot and then the message "shutdown: warning: cannot open /var/run/shutdown.pid" appears and the server doesn't continue. I actually have to hold the power button for 4 sec to shutdown the server. I've reinstalled the server, logged in, then removed the unused kernelmodule of the x306m raidcontroller and then rebooted the server. Reboot works fine after this. I would assume that a loaded kernelmodule that is not in use, wouldn't cause such a problem. Anybody who has an idea of what's going wrong? Rgds, Johan

1 0

Cannot disable DHCP
by dbellis＠mmm.com 30 Mar '06

30 Mar '06

Hello, I am trying to build a custom boot cd that will use a static IP address to connect to a HTTP installation source. I can get the boot cd to work with a DHCP configuration, but no matter what I do I cannot get it to use a static IP address. Has anyone done this successfully? Any help or examples would be greatly appreciated. Thanks, David Bellis

3 5

initrd_module TAG on suse 10.1beta8
by Martin Vogt 30 Mar '06

30 Mar '06

Hello list, does autoyast support the initrd_module TAG? This is in my xml file: <initrd_modules config:type="list"> <initrd_module> <module>ext3</module> </initrd_module> <initrd_module> <module>forcedeth</module> </initrd_module> </initrd_modules> But : > cat /etc/sysconfig/kernel | grep INITRD INITRD_MODULES="sis5513 sata_sis processor thermal fan reiserfs dm_mod" does not contain them. Testet on SuSE 10.1 beta8 regards, Martin

2 1

RE: [suse-autoinstall] init scripts
by discip＠pjm.com 30 Mar '06

30 Mar '06

Sorry, sp3, you're right. As for the init-script. I added the debug line like you suggested and it's not hitting that file. I'm also teeing the output of my script to a file, and it's not getting created either. ~Paul -----Original Message----- From: Uwe Gansert [mailto:ug@suse.de] Sent: Thursday, March 30, 2006 7:07 AM To: suse-autoinstall(a)suse.com Subject: Re: [suse-autoinstall] init scripts On Thursday 30 March 2006 01:17, discip(a)pjm.com wrote: > I am using SLES9 sp5, SP5 does not exist. SP3 is the latest one. > my autoinstall.xml looks like this: looks good. > Has anyone else had any luck with this? I'm sure init-scripts on SP3 are working without any problems. Add a line like "touch /tmp/init_was_here" as first line to your init-script to check if it has started. > Do I need a different > profile.dtd (can I get a newer one somewhere?)? a new profile.dtd would not change anything. -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nuernberg, Germany e-mail: uwe.gansert(a)suse.de, Tel: +49-(0)911-74053-0, Fax: +49-(0)911-74053-476, Web: http://www.suse.de -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

2 1

init scripts
by discip＠pjm.com 30 Mar '06

30 Mar '06

The documentation on Novell's website states that starting with SLES9, the init-scripts tag is available. http://forgeftp.novell.com/yast/doc/SL10.0/autoinstall/createprofile.script… l#init.scripts I am using SLES9 sp5, however, xmllint is not happy about the init-scripts tag (surprise surprise) and the installer ignores it. my autoinstall.xml looks like this: <?xml version="1.0"?> <!DOCTYPE profile SYSTEM "/usr/share/autoinstall/dtd/profile.dtd"> <profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <configure> <scripts> <init-scripts config:type="list"> <script> <source><![CDATA[ /root/fixSuSE 2>&1 | tee /root/fixSuSE.out echo "SuSE Patched for US..." sleep 5 ]]> </source> </script> </init-scripts> </scripts> ... Has anyone else had any luck with this? Do I need a different profile.dtd (can I get a newer one somewhere?)? Thanks, Paul

2 1

Defining printers for configuration during printing
by Peter Schwenk 29 Mar '06

29 Mar '06

I ran into a snag with using autoyast to get printers preconfigured during installation. I took an already-configured SuSE 10 machine, set up the printers as desired, and ran the Autoinstallation portion of YaST to get a reference configuration file. I chopped out the part where the printers were defined and grafted it into an already existing autoyast file. Xmllint showed no problems with the syntax, but no printers were defined on the computer that I autoinstalled. Is there a problem with my methods? I can supply the chunk of the autoyast file that had to do with printing, if that helps. Thanks in advance! -- - Peter Schwenk - CITA-3, Systems Administrator - Mathematical Sciences - University of Delaware - (302) 831-0437 - schwenk _at_ udel _dot_ edu - http://www.math.udel.edu/~schwenk

3 2

showopts/info file
by dbellis＠mmm.com 28 Mar '06

28 Mar '06

Hello everyone. I am trying to create a custom boot cd that will be used to build many servers. Our network admins do not allow DHCP in our datacenters, so I need to use a static IP address. I would like to be able to do the following: 1. Use a network installation source 2. Use a control file on a network installation source 3. Use a static IP to connect to the installation source 4. Allow the person using the custom boot cd to change the name of the control file at run time. Can I use a combination of the showopts boot options and a control file to do this? Or are they mutually exclusive of each other? Any help would be greatly appreciated. Thanks, David Bellis

1 0

RE: [suse-autoinstall] lvm volume group problem
by discip＠pjm.com 28 Mar '06

28 Mar '06

Thanks! That worked. Just one problem. If I do a reinstall on this one. It complains about not being able to remove the existing LVs. Is there an option for the volume group to force it to recreate it so I don't have this problem? Thanks, Paul -----Original Message----- From: Uwe Gansert [mailto:ug@suse.de] Sent: Wednesday, March 22, 2006 1:08 PM To: suse-autoinstall(a)suse.com Subject: Re: [suse-autoinstall] lvm volume group problem On Wednesday 22 March 2006 19:05, discip(a)pjm.com wrote: it's like I told you in my last mail. Add the line to your profile that I have added below. > Sorry, here it is: > > <partitioning config:type="list"> ... > <drive> > <device>/dev/vg0</device> > <is_lvm_vg config:type="boolean">true</is_lvm_vg> > <partitions config:type="list"> > <partition> > <filesystem config:type="symbol">reiser</filesystem> > <format config:type="boolean">true</format> > <lv_name>USR</lv_name> > <mount>/usr</mount> > <size>2GB</size> > </partition> > </partitions> <use>all</use> > </drive> > </partitioning> -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nuernberg, Germany e-mail: uwe.gansert(a)suse.de, Tel: +49-(0)911-74053-0, Fax: +49-(0)911-74053-476, Web: http://www.suse.de -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

2 1

problem with an xinclude
by mailing list 27 Mar '06

27 Mar '06

hi, i have a problem with an xinclude here. All of my xincludes work fine (normally) but im having a problem with the include of sysconfig. heres my configuration: default.xml: <?xml version="1.0"?> <!DOCTYPE profile SYSTEM "/usr/share/autoinstall/dtd/profile.dtd"> <profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config=" http://www.suse.com/1.0/configns" xmlns:xinclude=" http://www.w3.org/2001/XInclude"> <xinclude:include href=" http://192.168.100.19/autoyast/includes/bootloader.xml"/> <xinclude:include href="http://192.168.100.19/autoyast/includes/users.xml"/> <xinclude:include href="http://192.168.100.19/autoyast/includes/groups"/> <xinclude:include href=" http://192.168.100.19/autoyast/includes/sysconfig.xml"/> <xinclude:include href=" http://192.168.100.19/autoyast/includes/files-ldap.xml"/> <xinclude:include href="http://192.168.100.19/autoyast/includes/firewall.xml "/> <xinclude:include href="http://192.168.100.19/autoyast/includes/local.xml"/> <xinclude:include href="http://192.168.100.19/autoyast/includes/inetd.xml"/> ...... and so on. everything worked fine .. i just wanted to integrate a sysconfig. Heres my sysconfig.xml: <sysconfig config:type="list" xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1. 0/configns" xmlns:xinclude="http://www.w3.org/2001/XInclude"> <sysconfig_entry> <sysconfig_key>RUN_PARALLEL</sysconfig_key> <sysconfig_path>/etc/sysconfig/boot</sysconfig_path> <sysconfig_value>no</sysconfig_value> </sysconfig_entry> </sysconfig> For me everything looks ok. But i cant really find the mistake im making. checked everything about 10 times allready. any help would be nice. mfg Florian.

1 1

Problems with using XInclude tag:
by Alexander Dubinin 27 Mar '06

27 Mar '06

Hi all, Does anybody know, which format of XML file should be to make it acceptable for XInclude? AutoYaST complains that "Premature end of data in tag profile line 3 " "could not load /partinfo.xml" But same time, xmllint parsing both files fine... I'm using following construct in autoyast.xml to get automatically generated partition layout: - Cut - <?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" xmlns:xinclude="http://www.w3.org/2001/XInclude">  <xinclude:include href="/partinfo.xml" />  </profile> - Cut - And layout, generated by script, is: - Cut - <?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" xmlns:xinclude="http://www.w3.org/2001/XInclude"> <partitioning config:type="list"> <drive> <device>/dev/hda</device> <initialize config:type="boolean">false</initialize> <partitions config:type="list"> <partition> <partition_nr config:type="integer">1</partition_nr> <create config:type="boolean">false</create> <format config:type="boolean">true</format> <filesystem config:type="symbol">ext2</filesystem> <mount>/boot</mount> </partition> <partition> <partition_nr config:type="integer">2</partition_nr> <create config:type="boolean">false</create> <format config:type="boolean">true</format> <filesystem config:type="symbol">swap</filesystem> <mount>swap</mount> </partition> <partition> <partition_nr config:type="integer">3</partition_nr> <create config:type="boolean">false</create> <format config:type="boolean">true</format> <filesystem config:type="symbol">reiser</filesystem> <mount>/</mount> </partition> <partition> <partition_nr config:type="integer">5</partition_nr> <create config:type="boolean">false</create> <format config:type="boolean">true</format> <filesystem config:type="symbol">ext3</filesystem> <mount>/localdisk</mount> </partition> </partitions> </drive> </partitioning> </profile> - Cut - Where is error? Please, do not propose to use rules - these are useless if NFS is not accessible, unfortunately. And I not ready to make whole structure in initrd yet. -- Regards, Alexander Dubinin

2 2

Does AutoYast support smbfs?
by Jonathan Meller 24 Mar '06

24 Mar '06

Hi! Does AutoYast support smbfs? -- Jonathan Meller jonathan.meller(a)tteng.com.br ======================================================= Tools & Technologies - T&T Engenheiros Associados Ltda. Projetos de SW - Desenvolvendo soluções. Rua Riachuelo, 1098 Conj. 1204 Centro - Porto Alegre - CEP 90010-272 Fone DDR: (51)3220-3234 Fone/Fax: (51)3220-3220 / 3220-3206 http://www.tteng.com.br/ tet(a)tteng.com.br =======================================================

2 2

RE: [suse-autoinstall] iscsi install/boot questions/issues for SLES10-beta8
by Lee, Richard 22 Mar '06

22 Mar '06

Hi Yall: How do you get hold of sles10 x86_64 , I have only the 32bit version , I need to compile a cross compiler for it and need a copy of the OS to endorse my cross compiler. Richard Lee , (408)957-1590 richard_lee(a)adaptec.com Software Engineer , HostRAID Driver Adaptec Inc. Milpitas, CA (408)957-1590 http://richnote01.corp.adaptec.com/ -----Original Message----- From: Aggarwal, VikasX [mailto:vikasx.aggarwal@intel.com] Sent: Wednesday, March 22, 2006 1:51 PM To: suse-sles-e(a)suse.com; suse-linux-e(a)suse.com; suse-autoinstall(a)suse.com; alice(a)suse.com Cc: open-iscsi(a)googlegroups.com; Kumar, Dinesh Subject: [suse-autoinstall] iscsi install/boot questions/issues for SLES10-beta8 Hi all I am trying SLES10-beta8 installation to iscsi-target. When booted from SLES-10-beta8 installation Disk1, I could not goto some iscsi-GUI to give iscsi-target IP and initiatorname. Is there a iscsi-configuration-GUI/Menu available for the user during the install time? To be able to try installation to iscsi-target, I went to command-prompt(ctrl+alt+f2) and loaded drivers(iscsi_tcp, e1000), assigned static IP address, start iscsid, run iscsiadm -discovery + iscsiadm -login. I could connect to the iscsi-target and had the remote disk in the installation-partition menu. Main issue appears after the installation is started and is in the middle. The machine will freeze, can't do anything. I tried several times , and it always will freeze before being able to finish the installation. Is it the open-iscsi driver issue(version 0.5.473-11)? Or is there something I need to configure properly to be able to install to iscsi-target? I am just doing a minimal base system install. Also I noticed through local-install that there is an open-iscsi support in /sbin/mkinitrd of SLES10-beta8. Will installer automatically create iscsi enabled initrd image, once it knows installation was made to iscsi target? Thanks in advance -vikas aggarwal

1 0

iscsi install/boot questions/issues for SLES10-beta8
by Aggarwal, VikasX 22 Mar '06

22 Mar '06

Hi all I am trying SLES10-beta8 installation to iscsi-target. When booted from SLES-10-beta8 installation Disk1, I could not goto some iscsi-GUI to give iscsi-target IP and initiatorname. Is there a iscsi-configuration-GUI/Menu available for the user during the install time? To be able to try installation to iscsi-target, I went to command-prompt(ctrl+alt+f2) and loaded drivers(iscsi_tcp, e1000), assigned static IP address, start iscsid, run iscsiadm -discovery + iscsiadm -login. I could connect to the iscsi-target and had the remote disk in the installation-partition menu. Main issue appears after the installation is started and is in the middle. The machine will freeze, can't do anything. I tried several times , and it always will freeze before being able to finish the installation. Is it the open-iscsi driver issue(version 0.5.473-11)? Or is there something I need to configure properly to be able to install to iscsi-target? I am just doing a minimal base system install. Also I noticed through local-install that there is an open-iscsi support in /sbin/mkinitrd of SLES10-beta8. Will installer automatically create iscsi enabled initrd image, once it knows installation was made to iscsi target? Thanks in advance -vikas aggarwal

1 0

RE: [suse-autoinstall] lvm volume group problem
by discip＠pjm.com 22 Mar '06

22 Mar '06

Sorry, here it is: <partitioning config:type="list"> <drive> <initialize config:type="boolean">true</initialize> <partitions config:type="list"> <partition> <mount>/</mount> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <partition_id config:type="integer">131</partition_id> <partition_type>primary</partition_type> <size>5000M</size> </partition> <partition> <mount>/boot</mount> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <loop_fs config:type="boolean">false</loop_fs> <partition_id config:type="integer">131</partition_id> <partition_type>primary</partition_type> <size>500M</size> </partition> <partition> <mount>swap</mount> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <partition_id config:type="integer">130</partition_id> <partition_type>primary</partition_type> <size>auto</size> </partition> <partition> <lvm_group>vg0</lvm_group> <partition_type>primary</partition_type> <size>max</size> </partition> </partitions> <use>all</use> </drive> <drive> <device>/dev/vg0</device> <is_lvm_vg config:type="boolean">true</is_lvm_vg> <partitions config:type="list"> <partition> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <lv_name>USR</lv_name> <mount>/usr</mount> <size>2GB</size> </partition> </partitions> </drive> </partitioning> -----Original Message----- From: Uwe Gansert [mailto:ug@suse.de] Sent: Wednesday, March 22, 2006 12:22 PM To: suse-autoinstall(a)suse.com Subject: Re: [suse-autoinstall] lvm volume group problem On Wednesday 22 March 2006 16:31, discip(a)pjm.com wrote: > Yes, that's what I was trying. The problem is that /dev/vg0 doesn't > exist because the volume group isn't being successfully created in the > previous section. As such, the install fails terribly. you have to create logical volumes in the vg. If you don't do that and just configure the VG but no volumes, then the VG is not created. Unfortunately you did not provide me the information I asked you for. I wanted to see your partitioning part of the profile with the logical volumes. Even if that "fails terribly" I want to see it and I don't want to see a version that does not work either but does not fail that terrible. That the VG is not created might just be an error, triggered by the profile part you did not show us. The logical volume configuration. So, to speed things up, I start to guess. Did you forget the <use>all</use> in the logical volume drive configuration? If not, again, please poste your complete partitioning section. Even if it fails terribly. I can stand it. Just show it. :) -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nuernberg, Germany e-mail: uwe.gansert(a)suse.de, Tel: +49-(0)911-74053-0, Fax: +49-(0)911-74053-476, Web: http://www.suse.de -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

2 1

RE: [suse-autoinstall] lvm volume group problem
by discip＠pjm.com 22 Mar '06

22 Mar '06

Yes, that's what I was trying. The problem is that /dev/vg0 doesn't exist because the volume group isn't being successfully created in the previous section. As such, the install fails terribly. Thanks, Paul -----Original Message----- From: Uwe Gansert [mailto:ug@suse.de] Sent: Wednesday, March 22, 2006 10:17 AM To: suse-autoinstall(a)suse.com Subject: Re: [suse-autoinstall] lvm volume group problem On Wednesday 22 March 2006 15:55, discip(a)pjm.com wrote: > SLES9 SP5 Interesting. Here at SUSE the latest SP we have is SP3. > <partitioning config:type="list"> > <drive> ... > </drive> > </partitioning> I don't know how this will be solved with SP5 but with SP3 you have to configure a second <drive> with <device>/dev/vg0</device> if you have a volume group with the name vg0. Put all partitions into that drive that shall be in the LVM. example 4.16 on page: http://www.suse.de/~ug/autoyast_doc/CreateProfile.Partitioning.html#id25298… explains it. -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nuernberg, Germany e-mail: uwe.gansert(a)suse.de, Tel: +49-(0)911-74053-0, Fax: +49-(0)911-74053-476, Web: http://www.suse.de -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

2 2

RE: [suse-autoinstall] lvm volume group problem
by discip＠pjm.com 22 Mar '06

22 Mar '06

SLES9 SP5 <partitioning config:type="list"> <drive> <initialize config:type="boolean">true</initialize> <partitions config:type="list"> <partition> <mount>/</mount> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <partition_id config:type="integer">131</partition_id> <partition_type>primary</partition_type> <size>5000M</size> </partition> <partition> <mount>/boot</mount> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <loop_fs config:type="boolean">false</loop_fs> <partition_id config:type="integer">131</partition_id> <partition_type>primary</partition_type> <size>500M</size> </partition> <partition> <mount>swap</mount> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <partition_id config:type="integer">130</partition_id> <partition_type>primary</partition_type> <size>auto</size> </partition> <partition> <lvm_group>vg0</lvm_group> <partition_type>primary</partition_type> <size>max</size> </partition> </partitions> <use>all</use> </drive> </partitioning> This obviously isn't going to be my final config since everything is in / right now, but I was planning on slicing up the rest of the filesystems out of the LVM. Thanks, Paul -----Original Message----- From: Uwe Gansert [mailto:ug@suse.de] Sent: Wednesday, March 22, 2006 9:38 AM To: suse-autoinstall(a)suse.com Subject: Re: [suse-autoinstall] lvm volume group problem On Wednesday 22 March 2006 15:21, discip(a)pjm.com wrote: > I have a stanza in my autoinstall.xml file that looks like this, and > the partition is getting created and flagged as an LVM partition, but > the volume group is not being created. Additionally, I still have to > run pvcreate on the partition before I can do a vgcreate with it. Am > I missing something? > > <partition> > <lvm_group>vg0</lvm_group> > <partition_type>primary</partition_type> > <size>max</size> > </partition> poste your SUSE Linux version and your complete partitioning section please. -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nuernberg, Germany e-mail: uwe.gansert(a)suse.de, Tel: +49-(0)911-74053-0, Fax: +49-(0)911-74053-476, Web: http://www.suse.de -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

2 1

Merging of 7 classes each with different sysconfig entries.
by Cameron Seader 22 Mar '06

22 Mar '06

I am trying to do a merge of 7 different classes with each one having different sysconfig entries and it is not working. is there something i need to be doing on the initial control file? Where do i put the classes in the initial control file?, do i put it in the <install> section or the <configure> section? Could someone give me some help on this? Thanks, Cameron

2 7

zSeries Autoyast Differences?
by M. Payne 22 Mar '06

22 Mar '06

Trying to Autoyast install a z990 linux guest with SLES9 SP3. Depending on whether I use a vnc vs a ssh install screen, I get different results. When the parmfile specifies INST_SCREEN=VNC, the installation appears to start, and when I vnc into the installing guest, I see the install progressing. When I specify SSH however, I receive the: *** run 'yast' to start the installation *** message on my 3270 screen, and when I ssh into the installing system, I need to invoke yast to start the autoinstall. Shouldn't the "autoinstall" be kicked of regardless of the install screen option?

2 1

lvm volume group problem
by discip＠pjm.com 22 Mar '06

22 Mar '06

I have a stanza in my autoinstall.xml file that looks like this, and the partition is getting created and flagged as an LVM partition, but the volume group is not being created. Additionally, I still have to run pvcreate on the partition before I can do a vgcreate with it. Am I missing something? <partition> <lvm_group>vg0</lvm_group> <partition_type>primary</partition_type> <size>max</size> </partition>

2 1

root password
by discip＠pjm.com 22 Mar '06

22 Mar '06

is there a way to set root's password throught autoinstall.xml? I put a stanza in for root, but it doesnt seem to take. If I try to do it with the gui, it tells me the user-defs conflict with an already existing user. ~Paul

3 2

sendmail options
by discip＠pjm.com 22 Mar '06

22 Mar '06

I'm trying to get a little more specific with my sendmail config in autoinstall.xml. Is there somewhere that I can look for all of the valid attributes for the mail configuration section. ~Paul

3 2

Re: [suse-autoinstall] root password
by Alfred Isele 22 Mar '06

22 Mar '06

Hallo Paul, For example password "Disciple" within <user> <encrypted config:type="boolean">false</encrypted> <user_password>Disciple</user_password> <username>root</username> </user> ... You can also use encrypted (set to true) passwords from /etc/shadow. Regards Alfred At 15:22 22.03.2006, discip(a)pjm.com wrote: >is there a way to set root's password throught autoinstall.xml? >I put a stanza in for root, but it doesnt seem to take. >If I try to do it with the gui, it tells me the user-defs conflict with an >already existing user. > >~Paul

1 0

seriell console installation suse 10.1b6?
by Martin Vogt 21 Mar '06

21 Mar '06

Hello autoyast list, I'm currently testing an automated installation over pxe. Currently I found two things, which do not seem to work: https://bugzilla.novell.com/show_bug.cgi?id=157024 https://bugzilla.novell.com/show_bug.cgi?id=157027 Now I checked a machine with linuxbios on it, which only can use a serial line. This is the last entry after the .ebi is loaded: Loading 10.136.16.201:netinst/ebi/install-suse101b6-i386.ebi ...(ELF)... .........done Then nothing. cmdline: console=ttyS0,115200 Insmod=e1000,bcm5700,e100,aic7xxx_old install=http://10.136.16.223/itwm101/inst/CD1 autoyast=tftp://10.136.16.221/netinst/suse/autoyast-suse101-lvm.xml" How do I find out if the kernel (The kernel from the installcds beta6) and the initrd supports the serial console? Is this tested? Installation beta6 over serial line? regards, Martin

1 2

SLES9 SP3 autoyast failures
by Roger L. Smith 20 Mar '06

20 Mar '06

Hi, I have recently upgraded my autoyast configuration for SLES9 to incorporate SP3. I followed the README for adding the additional source. Now, when I try to install a new system, I get the following error while it attempts to install many (but not all) of the packages: /bin/sh: error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory. I am using the new kernel and initrd to boot the install system. The install server is already running SP3. I can still install out of the old SLES9 install directory, even using the new kernel and initrd. I've tried using the base package install instead of my own configuration, and get the same results. Does anyone have any suggestions? My install directory now looks like this: drwxr-xr-x SUSE-CORE-Version-9 drwxr-xr-x SUSE-SLES-9-Service-Pack-Version-3 drwxr-xr-x SUSE-SLES-Version-9 drwxr-xr-x boot lrwxrwxrwx content -> SUSE-SLES-Version-9/CD1/content lrwxrwxrwx control.xml -> SUSE-SLES-Version-9/CD1/control.xml lrwxrwxrwx driverupdate -> SUSE-SLES-9-Service-Pack-Version-3/CD1/driverupdate lrwxrwxrwx linux -> SUSE-SLES-9-Service-Pack-Version-3/CD1/linux lrwxrwxrwx media.1 -> SUSE-SLES-Version-9/CD1/media.1 drwxr-xr-x 2 root root 104 Mar 15 16:25 yast I think my /yast/order and instorder files are ok: $ cat order /SUSE-SLES-9-Service-Pack-Version-3/CD1 /SUSE-SLES-9-Service-Pack-Version-3/CD1 /SUSE-SLES-Version-9/CD1 /SUSE-SLES-Version-9/CD1 /SUSE-CORE-Version-9/CD1 /SUSE-CORE-Version-9/CD1 $ cat instorder /SUSE-SLES-9-Service-Pack-Version-3/CD1 /SUSE-SLES-Version-9/CD1 /SUSE-CORE-Version-9/CD1 _\|/_\|/_\|/_\|/_\|/_\|/_\|/_\|/_\|/_\|/_\|/_\|/_\|/_\|/_\|/_\|/_\|/_\|/_ \ Roger L. Smith - roger(a)ERC.MsState.Edu - 662-325-3625 / \ Senior Systems Administrator / \ Mississippi State University / \_____________High Performance Computing Collaboratory____________/

1 1

How to install additional files
by Hans 20 Mar '06

20 Mar '06

Hello all, Is it possible to install additional files (binaries, config files, etc) that are not in an rpm, during auto-install? And if so, how can I do that? (Using OSS 10.0) Gr, Hans

3 2

Custom CD asks for Disc 2
by discip＠pjm.com 17 Mar '06

17 Mar '06

I haven't been able to find the answer to this in the archives; I hope I'm not repeating anyone: I rolled my own custom CD for SLES9 (service pack 5) using the yast autoinstallation gui, generated a control file, and used that with the CD Creator GUI. I've checked to make sure that all the packages I need are on the .iso that I generated, but the installer still asks me to insert the next CD. I even manually edited the descr/packages file and changed the Loc from 2 to 1 for the offending packages, but that didnt help either. Two of the packages giving me this trouble are lkcdutils and TraceToolkit. The software portion of my control file looks like this: <software> <base>Minimal</base> <packages config:type="list"> <package>3ddiag</package> <package>CheckHardware</package> <package>TraceToolkit</package> <package>XFree86</package> <package>XFree86-Mesa</package> <package>XFree86-fonts-75dpi</package> <package>XFree86-fonts-scalable</package> <package>XFree86-libs</package> <package>XFree86-man</package> <package>XFree86-server</package> <package>XFree86-server-glx</package> <package>bitstream-vera</package> <package>desktop-data-SLES</package> <package>dos2unix</package> <package>expat</package> <package>fontconfig</package> <package>freeglut</package> <package>freetype2</package> <package>fribidi</package> <package>fvwm2</package> <package>gdb</package> <package>ghostscript-fonts-std</package> <package>glib</package> <package>gnome-filesystem</package> <package>gtk</package> <package>ifnteuro</package> <package>imlib</package> <package>imwheel</package> <package>intlfnts</package> <package>libjpeg</package> <package>liblcms</package> <package>libmng</package> <package>libpng</package> <package>libstroke</package> <package>libtiff</package> <package>libungif</package> <package>libusb</package> <package>lkcdutils</package> <package>make</package> <package>man-pages</package> <package>nss_ldap</package> <package>openssh-askpass</package> <package>pam_ldap</package> <package>patch</package> <package>perl-XML-Parser</package> <package>qt3</package> <package>sax2</package> <package>saxident</package> <package>saxtools</package> <package>sudo</package> <package>tcl</package> <package>tightvnc</package> <package>tk</package> <package>unclutter</package> <package>unzip</package> <package>wget</package> <package>xaw3d</package> <package>xbanner</package> <package>xdg-menu</package> <package>xdmbgrd</package> <package>xf86tools</package> <package>xlockmore</package> <package>xtermset</package> <package>yast2-control-center</package> <package>yast2-qt</package> <package>zsh</package> </packages> </software> Any help would be greatly appreciated. Thanks, Paul

1 0

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

16 Mar '06

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

4 6

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

14 Mar '06

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

2 1

Autoyast and elilo.
by COMBERNOUS Fabien 14 Mar '06

14 Mar '06

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

1 0

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

14 Mar '06

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

2 2

Autoinstallation from CD
by Hans 13 Mar '06

13 Mar '06

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

2 2

FYI - SLES10 incompatibility
by Uwe Gansert 13 Mar '06

13 Mar '06

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

1 0

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

13 Mar '06

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

2 1

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

13 Mar '06

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

2 1

Autoinstallation from CD
by Hans 13 Mar '06

13 Mar '06

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

1 0

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

13 Mar '06

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

1 0

Mutliple Installsources
by Martin Vogt 10 Mar '06

10 Mar '06

Hello list, OpenSuSE does not contain many multimedia applications. But there ist an addition Multimediadirectory for SUSE 10.x. ftp://packman.inode.at/suse/10.0/ Currently Im using this /proc/cmdline for autoyast: initrd=initrd_suse101b6_i386 vga=0x314 Insmod=e1000,bcm5700,e100,aic7xxx_old install=http://10.136.16.223/mysuse101/inst/CD1 autoyast=tftp://10.136.16.221/suse/autoyast-suse101-lvm.xml Is it possible to add a second installation resource during an autoyast installation? SLES9 for example had something like this: cat yast/order /SUSE-SLES-Version-9/CD1 /SUSE-SLES-Version-9/CD1 /SUSE-CORE-Version-9/CD1 /SUSE-CORE-Version-9/CD1 Which tells yast to use more resources. Is a similiar mechanism supported with OpenSuSE? regards, Martin

2 1

Installation media in SLES9 SP3
by Radoslaw Sypianski XX (LI/EAB) 10 Mar '06

10 Mar '06

Hi During autoinstallation process (in chroot script) I would like to know from where (which device) the installation is going on. How to find out about it ? Regards, Radek

2 1

LSI Logic Megaraid and SLES 9 SP2 --- Uwe Gansert Help me Please :-)
by Rob Thompson 10 Mar '06

10 Mar '06

Hi, I am attempting to use autoyast to install SLES 9 SP2 on a new Dell 2850. I am using a .xml file for the partitioning and package selection and everything works fine until the first reboot. Upon rebooting, the server cannot find its' hard disks. The raid controller it is attempting to use is a megaraid. If I build this server by-hand using the SP2 cd's the install works and during boot it shows it is using the megaraid_mbox module. This is what is also listed in /etc/sysconfig/kernel. If I build using autoyast, then use a rescue cd to see the drives and mount / no megaraid module is present in /etc/sysconfig/kernel. My question is this: Can I force the autoyast installation to use the megaraid_mbox module? I have tried putting the following line in /tftp/pxelinux.cfg/default file label linux kernel linux append pci=noacpi ide=nodma barrier=off initrd=initrd ramdisk_size=65536 insmod=megaraid_mbox along with pointers to my NFS share and the xml file. Is this the correct way to add a module, or am I missing something else? Thanks, Rob Thompson

2 1

AutoYast LVM problem
by dbellis＠mmm.com 08 Mar '06

08 Mar '06

Hello, I am getting the following error during the partition phase of autoyast. LVM error lvremove -f -A n /dev/vg00/home /dev/sda1: open failed: No such device or address Here is my xml file. <?xml version="1.0"?> <!DOCTYPE profile SYSTEM "/usr/share/autoinstall/dtd/profile.dtd"> <profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <configure> <networking> <dhcp_options> <dhclient_additional_options></dhclient_additional_options> <dhclient_client_id></dhclient_client_id> <dhclient_hostname_option>AUTO</dhclient_hostname_option> </dhcp_options> <dns> <dhcp_hostname config:type="boolean">false</dhcp_hostname> <dhcp_resolv config:type="boolean">false</dhcp_resolv> <domain>mmm.com</domain> <hostname>servername</hostname> <nameservers config:type="list"> <nameserver>0.0.0.0</nameserver> <nameserver>0.0.0.0</nameserver> </nameservers> <searchlist config:type="list"> <search>mmm.com</search> </searchlist> </dns> <interfaces config:type="list"> <interface> <bootproto>static</bootproto> <broadcast>0.0.0.0</broadcast> <device>eth-id-00:14:22:0e:7b:d0</device> <ipaddr>0.0.0.0</ipaddr> <netmask>255.255.255.0</netmask> <network>0.0.0.0</network> <startmode>onboot</startmode> </interface> </interfaces> <modules config:type="list"> <module_entry> <device>bus-pci-0000:06:07.0</device> <module>e1000</module> <options>Speed=100 Duplex=2</options> </module_entry> </modules> <routing> <ip_forward config:type="boolean">false</ip_forward> <routes config:type="list"> <route> <destination>default</destination> <device>-</device> <gateway>0.0.0.0</gateway> <netmask>-</netmask> </route> </routes> </routing> </networking> </configure> <install> <general> <clock> <hwclock>UTC</hwclock> <timezone>US/Central</timezone> </clock> <keyboard> <keymap>english-us</keymap> </keyboard> <language>en_US</language> <mode> <confirm config:type="boolean">false</confirm> </mode> <mouse> <id>22_exps2</id> </mouse> </general> <partitioning config:type="list"> <drive> <device>/dev/sda</device> <initialize config:type="boolean">true</initialize> <partitions config:type="list"> <partition> <filesystem config:type="symbol">ext3</filesystem> <create config:type="boolean">true</create> <format config:type="boolean">true</format> <loop_fs config:type="boolean">false</loop_fs> <partition_type>primary</partition_type> <mount>/boot</mount> <size>1GB</size> </partition> <partition> <filesystem config:type="symbol">swap</filesystem> <create config:type="boolean">true</create> <format config:type="boolean">true</format> <loop_fs config:type="boolean">false</loop_fs> <partition_type>primary</partition_type> <mount>swap</mount> <size>2GB</size> </partition> <partition> <create config:type="boolean">true</create> <lvm_group>vg00</lvm_group> <partition_type>primary</partition_type> <size>max</size> </partition> </partitions> <use>all</use> </drive> <drive> <device>/dev/sdb</device> <initialize config:type="boolean">true</initialize> <partitions config:type="list"/> </drive> <drive> <device>/dev/vg00</device> <is_lvm_vg config:type="boolean">true</is_lvm_vg> <create config:type="boolean">true</create> <partitions config:type="list"> <partition> <filesystem config:type="symbol">ext3</filesystem> <lv_name>home</lv_name> <mount>/home</mount> <size>2000mb</size> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <lv_name>opt</lv_name> <mount>/opt</mount> <size>4000mb</size> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <lv_name>root</lv_name> <mount>/</mount> <size>6000mb</size> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <lv_name>tmp</lv_name> <mount>/tmp</mount> <size>2000mb</size> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <lv_name>usr</lv_name> <mount>/usr</mount> <size>4000mb</size> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <lv_name>var</lv_name> <mount>/var</mount> <size>4000mb</size> </partition> </partitions> <pesize>4M</pesize> <use>all</use> </drive> </partitioning> <report> <errors> <log config:type="boolean">true</log> <show config:type="boolean">true</show> <timeout config:type="integer">0</timeout> </errors> <messages> <log config:type="boolean">true</log> <show config:type="boolean">true</show> <timeout config:type="integer">0</timeout> </messages> <warnings> <log config:type="boolean">true</log> <show config:type="boolean">true</show> <timeout config:type="integer">0</timeout> </warnings> <yesno_messages> <log config:type="boolean">true</log> <show config:type="boolean">true</show> <timeout config:type="integer">0</timeout> </yesno_messages> </report> <software> <addons config:type="list"> <addon>Linux-Tools</addon> <addon>Basis-Sound</addon> <addon>X11</addon> <addon>Base-System</addon> <addon>Kde-Desktop</addon> <addon>YaST2</addon> <addon>auth</addon> <addon>Print-Server</addon> <addon>SuSE-Documentation</addon> </addons> <base>default</base> <packages config:type="list"> <package>clamav</package> <package>gmp</package> <package>ltrace</package> <package>sharutils</package> </packages> </software> </install> </profile> Any ideas or help would be greatly apprcieated! David Bellis

2 1

dynamic partition size
by Jochen Mueller 08 Mar '06

08 Mar '06

Hello, i am using autoyast (SLES9 SP3 and Suse 10, both using NFS) Installation on a lot of different systems. How could i size the partitions depending on disk-size and on memory size of the target System? For example: * the swap partition should be 1.5 times the size of the memory, but at least 1 gig and max. 8 gig. * the /home partition should be 20% of the disk drive but at least 50Gig Any ideas about this nice features ? Regads Jochen

2 1

Online updates offline
by Roger Oberholtzer 08 Mar '06

08 Mar '06

I have some SUSE 10 systems that are not able to access the internet. However, I would like them be kept up to date. Previously, I had an on-line system that I did updates on, keeping the downloaded files. Overall, this worked. The problem is that the kept files just grows and grows as there is no mechanism for getting rid of obsolete updates. It also requires that I keep an office computer in sync do this. Is there an easy way to maintain a local copy of the online update database? I guess I could mirror it. But then I get lots of things we never install. Any other interesting option? -- Roger Oberholtzer OPQ Systems AB Ramböll Sverige AB Kapellgränd 7 P.O. Box 4205 SE-102 65 Stockholm, Sweden Tel: Int +46 8-615 60 20 Fax: Int +46 8-31 42 23

1 0

installing SP2 using autoyast
by jaiber john 07 Mar '06

07 Mar '06

Hello, I'm working on a software that lets user install SLES9 and the drivers required on a machine automatically. It does this by collecting essential user inputs and creating the autoyast.xml. This xml file is copied to a hard-disk location along with the vmlinux and initrd from CD1 to the hard-disk which is then made bootable by installing LILO (with kernel and initrd lines pointing to the files copied above). The linuxrc.config is modified within the initrd to set installation source as CD, etc. The following lines were added to linuxrc.config before re-creating the initrd: ------------------------------------------------------- AutoYast: file:///autoyast.xml Exec: modprobe ext3 InstMode: cd ------------------------------------------------------- On re-boot from hard-disk, it'd request SLES9 CD1,2,3,... and the OS would get installed. The drivers would get installed through post-install scripts. This techinique worked well for SLES9 but not with SP2. If I do the same with SP2 (i.e, copying the kernel, initrd from SP2 CD1 to hard-disk), on reboot, it requests for core SLES9 CD1 and then on, only SLES9 installation proceeds, the SP2 cds were not asked and hence they dont get installed. Are there any provision in linuxrc.config or info file to direct autoyast to install SP2 and hence request specifically for SP2 CD1 on reboot? -- Thanks <Jaiber John>

1 0

SLES9 SP2 autoyast installation
by jaiber john 07 Mar '06

07 Mar '06

Hello, Is there any specific entry I need to add to autoyast.xml to install SLES9 SP2? I ask this because when I install SP2 using the autoyast.xml I used for installing SLES9, the installer does not ask for CD2 and CD3 of SP2. Instead it completes using base SLES9 CDs itself. I need the updated kernel drivers in SP2 to get SATA controller detected. Thanks, Jaiber John

1 1

Chroot script: mounting dvdrom
by Radoslaw Sypianski XX (LI/EAB) 02 Mar '06

02 Mar '06

Hi I have to copy some files from installation media (dvd-rom in my case) after installation process, in chroot script. In SuSE Linux Prof. 9.3 there is no problem cause in that script I'm albe to find mounted iso9660 device and copy necessary files from there. But in SLES9 SP3 this method doesn't work - mount command in chroot script returns that there is no mounted iso9660 devices. Of course I can try to mount /dev/cdrom by default but it is not enough in case when there are 2 and more dvd drives - I don't know in which the installation media is. How to find out from which device the installation has been done ? Or maybe there is another way to solve that in SLES9 ? Regards, Radek

1 0

Changing Kernel in pxe install
by Reeves, Matthew J. 01 Mar '06

01 Mar '06

Classification: UNCLASSIFIED I'm trying to set up a pxe environment to install SuSE 9.0 on some Dell Poweredge 1850s. The kernel that comes with 9.0 doesn't support the raid controllers. I want to change the installing kernel to 2.4.32 so that the raid works. I can get the systems booting and linuxrc runs but it asks for a module disk then goes into manual mode. In the manual mode I can kick off a ftp install but after root is downloaded the system just goes back to the linuxrc menu. Is there an easy way to change the kernel? Thanks, Matt

3 2