September 2006 - openSUSE Autoinstall - openSUSE Mailing Lists

Anyone has experence on x86_64 autoyast installation?
by hp9 19 Sep '06

19 Sep '06

I have very bad experience to install SLES10.0 x86_64 on 64bits machine. Though I can do it manually. But I can not install it by AUTOYAST, because AUTOYAST always install i586 but x86_64! Anyone has experence on x86_64 autoyast installation?

3 2

RE: [suse-autoinstall] SuSE 10.1: Could not find the SUSE Linux Installation Source
by GUNREBEN, PETER (Peter) 19 Sep '06

19 Sep '06

GUNREBEN, PETER wrote: > > I have problems to get the autoyast installation (SuSE 10.1) > up and running with some new computers (K8N-DRE, 2xOpteron > 275). The main error message is "Could not find the SUSE > Linux Installation Source". The onboard NICs are Broadcom > 5721and I'm using the tg3 driver. I can see on console 3 that > there is a problem with the nfs mount. However, I can mount > this directory via nfs (from console 9) without any problems. > Any help or idea is highly appreciated. I'm desperately > searching for a solution. I just got a hint from Lee per E-Mail to add netwait=5 to the kernel command line. This solved the problem. Many thanks to Lee. Peter.

1 0

SuSE 10.1: Could not find the SUSE Linux Installation Source
by GUNREBEN, PETER (Peter) 19 Sep '06

19 Sep '06

Hi, I have problems to get the autoyast installation (SuSE 10.1) up and running with some new computers (K8N-DRE, 2xOpteron 275). The main error message is "Could not find the SUSE Linux Installation Source". The onboard NICs are Broadcom 5721and I'm using the tg3 driver. I can see on console 3 that there is a problem with the nfs mount. However, I can mount this directory via nfs (from console 9) without any problems. Any help or idea is highly appreciated. I'm desperately searching for a solution. ======== Console 3 ======== got info from file:/info hostname: 135.246.30.241 netmask: 255.255.254.0 broadcast: 135.246.31.255 gateway: 135.246.30.1 server: 135.246.75.102 nameserver: 135.246.31.80 Ok, that seems to have worked. :-) Ok, that seems to have worked. :-) Ok, that seems to have worked. :-) Looking for a network server... Trying to activate eth0 setting up localhost...done eth0 activated nfs: trying to mount 135.246.75.102:/raid0/SuSE/10.1 Starting portmap. mount: nfs mount failed, server says: unknown error -1 Ok, that didn't work; see if we can activate another network device... No further network cards found; giving up. Automatic setup not possible. ======== Console 3 ======== Peter.

1 0

RE: [suse-autoinstall] SLES10 Archive Selection: My autoyast alway install i586 but x86_64
by hp9 18 Sep '06

18 Sep '06

My autoyast alway install i586 but x86_64 in its process. Who know the reason about that? Thank you lots. The follow is my scripts: ------------------------------ <?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"> <bootloader> <activate config:type="boolean">true</activate> <global> <embed_stage1.5 config:type="boolean">true</embed_stage1.5> <lines_cache_id>0</lines_cache_id> <prompt>1</prompt> <stage1_dev>/dev/sda1</stage1_dev> <timeout config:type="integer">8</timeout> </global> <initrd_modules config:type="list"> <initrd_module> <module>piix</module> </initrd_module> <initrd_module> <module>ata_piix</module> </initrd_module> <initrd_module> <module>processor</module> </initrd_module> <initrd_module> <module>thermal</module> </initrd_module> <initrd_module> <module>fan</module> </initrd_module> </initrd_modules> <loader_device>/dev/sda1</loader_device> <loader_type>grub</loader_type> <location>boot</location> <repl_mbr config:type="boolean">false</repl_mbr> <sections config:type="list"> <section> <append>showopts</append> <initial>1</initial> <initrd>/boot/initrd</initrd> <kernel>/boot/vmlinuz</kernel> <lines_cache_id>1</lines_cache_id> <name>SUSE Linux 10.0</name> <original_name>linux</original_name> <root>/dev/sda1</root> <type>image</type> <vga>0x31a</vga> </section> <section> <append>showopts ide=nodma apm=off acpi=off noresume edd=off 3</append> <initrd>/boot/initrd</initrd> <kernel>/boot/vmlinuz</kernel> <lines_cache_id>2</lines_cache_id> <name>Failsafe -- SUSE Linux 10.0</name> <original_name>failsafe</original_name> <root>/dev/sda1</root> <type>image</type> <vga>normal</vga> </section> </sections> </bootloader>

1 0

RE: [suse-autoinstall] SLES10 Archive Selection: My autoyast alway install i586 but x86_64
by hp9 18 Sep '06

18 Sep '06

My autoyast alway install i586 but x86_64 in its process. Who know the reason about that? Thank you lots.

1 0

problem including customer packages: add-on product vs multi-product media
by Oliver Schweikert 18 Sep '06

18 Sep '06

Hello, I want to create a single installation DVD, that contains SLES10 and customer packages. The DVD shall also act as network installation source, when it is mounted. When using SLES8 I put the customer packages among the SLES packages and update the package description, and all works fine. Now i try to separate SUSE and customer rpms, but cannot get it to work (all while automatic installation process): add-on product approach: YaST expects an URL in the add_on_product file, but i can only provide a relative path, because if the media is used from a drive the protocol is cd://, but when acting as network source it is ftp://. Is there a way to specify the add-on product path relative to the media root? multi-product approach: When I append my product to /media.1/products (*asc/*key removed and <signature-handling> adjusted to accept it), the meta data are read from YaST myprod/setup/descr/packages,...), but if i define a package from this product YaST messes up the package selection and the installation fails: Instead of the 1.3 Gbyte from SLES sources, YaST claims to have only about 47 Mbyte to install and the first package (grub) fails to install at the %post script. Any idea, why YaST gets confused? Oliver

4 4

SLES10 Package Selection
by Rajeev Mishra 18 Sep '06

18 Sep '06

I would like to setup a network based "Interactive" and "autoyast" install of SLES10. My question is regarding package selection for interactive install. We generally do not install all the packages but make a list of all the packages, In sles9 there is an option of exporting the package list as a .sel file and then you can import the same file in your future installs. We then keep a copy of this file in sles9.0 install repository so if you are doing an interactive install of a machine then you can browse the user.sel and it imports your package selection. I do not see an option of importing/exporting of package selection in SLES10. I manually installed a SLES10 machine with all the packages we want. and then created a autoyast.xml file. Now, What I want is if I do an autoyast install of SLES10 then it should ask me all the install questions but all the packages should be selected from the autoyast.xml file I created . Thanks - Rajeev

2 1

[suse-autoinstall] SLES10 Kernel Selection
by hp9 18 Sep '06

18 Sep '06

I am installing SLES10 by autoyast. It is strange that when I install dual cores machine MANUALLY, the Kernel x86_64 had been installed. WHEN I install macine by using autoyast, the installed Kernel is i586 ! What's wrong? Any one had ecperience like that? Any good point to solve the problem?

1 0

Adding ZYPP repositories at install time
by Ian Grant 15 Sep '06

15 Sep '06

This is a little OT but I don't know where else to ask. In an autoyast script, how can I add a trusted key that rug/yast will use to verify signed ZYPP repositories? I am trying to add ZYPP repositories in an autoinstall script. (I can do it manually using YaST 'Installation Sources' and it asks me if I want to trust the key used to sign the repository. But I don't want to have to do this manually every time I install a machine.) The repository is one I have created myself using createrepo and signed as described here: http://en.opensuse.org/Secure_Installation_Sources#The_.22repomd.22_or_.22Y… To sign the repository I 'cd' to the top-level directory and ran gpg -a -u rpm-packager --detach-sign repodata/repomd.xml gpg -a --export rpm-packager > repodata/repomd.xml.key So I have the key in repodata/repomd.xml.key On the new machine (in an autoyast post-init script) I want to add the key to the rug keyring. I have tried gpg --homedir /root/.gnupg \ --import repodata/repomd.xml.key to add it to root's keyring, and I have tried adding the key to the zmd whitelist using rug ka packager 68C0D40964D6D632 "6E55 E6C6 8A0D 5557 C10D 571B 68C0 D409 64D6 D632" But neither work. When I run rug --quiet sa -t zypp \ nfs://repo.host/path/suse-10.1/extras \ SUSE-10.1-extras I get an error 'parsing metadata: Untrusted key rpm-packager ... (I am paraphrasing, I don't have a copy of the message and can't reproduce it without re-installing.) However, if I delete an installation source added using YaST 'Installation Source' graphical tool and then run the above 'rug sa' command it works, presumably because the key has been kept.

1 0

Problems with bootloader configuration in autoyast SLES10 RC3
by Matt Gillard 13 Sep '06

13 Sep '06

I have logged SR#10273247971 for this but I thought I would get peoples thoughts here as well. Problem is with the <default> global parameter in the <bootloader> section of autoyast. This works fine: <bootloader> <loader_type>lilo</loader_type> <location>mbr</location> </bootloader> Default kernel is SLES_10 as expected. This doesnt work, during boot loader installation an error is given that there is no default value given in lilo.conf. This occurs if I put an entry in the <default> tag or not. <bootloader> <global> <default>SLES_10</default> <gfxmenu></gfxmenu> <prompt>1</prompt> <timeout config:type="integer">5</timeout> </global> <loader_type>lilo</loader_type> <location>mbr</location> </bootloader> ie: This also gives the same error for the default tag. It should default to SLES_10 - I should not have to specify it. <bootloader> <global> <default></default> <gfxmenu></gfxmenu> <prompt>1</prompt> <timeout config:type="integer">5</timeout> </global> <loader_type>lilo</loader_type> <location>mbr</location> </bootloader> And this also the same error: <bootloader> <global> <gfxmenu></gfxmenu> <prompt>1</prompt> <timeout config:type="integer">5</timeout> </global> <loader_type>lilo</loader_type> <location>mbr</location> </bootloader> The reason I am doing this is because I do *not* want a graphical menu so I want to specify nothing for <gfxmenu> which seems to work ok. The text of the error during the bootloader config/installation phase is: "Value expected for 'default' at or above line 11 in file /etc/lilo.conf." And sure enough in /mnt/etc/lilo.conf at that point of the installation default has no value. thanks -- Matt Gillard UNIX Systems Engineer Coles Myer Ltd | Lvl 4 236 Bourke St | +61 3 963 51926 This email and any attachments may contain privileged and confidential information and are intended for the named addressee only. If you have received this e-mail in error, please notify the sender and delete this e-mail immediately. Any confidentiality, privilege or copyright is not waived or lost because this e-mail has been sent to you in error. It is your responsibility to check this e-mail and any attachments for viruses. No warranty is made that this material is free from computer virus or any other defect or error. Any loss/damage incurred by using this material is not the sender's responsibility. The sender's entire liability will be limited to resupplying the material.

4 13

hostname not set during autoinstall
by Hartmut Gottwald 13 Sep '06

13 Sep '06

Hi, I like to get the hostname passed from DHCP to the client during autoinstall. But whatever I do the hostname is set to "linux". However the IP was set correctly. Platform is IA64 and OS version SLES 10 A snippet from dhcpd.conf: ddns-update-style none; ignore unknown-clients; group { use-host-decl-names on; filename "elilo.efi"; subnet 192.168.72.0 netmask 255.255.255.0 { next-server 192.168.72.72; } host client02 { hardware ethernet 08:00:69:14:04:5E; fixed-address client02; } } ------ and from autoinstall.xml: <networking> <dns> <dhcp_hostname config:type="boolean">true</dhcp_hostname> <dhcp_resolv config:type="boolean">true</dhcp_resolv> <domain></domain> <hostname></hostname> </dns> ... ----- Tried several variations with dhcp_hostname/dhcp_resolv also set to false and <hostname></hostname> removed without success. Can't figure out what's wrong... can't even find documentation for dhcp_hostname/dhcp_resolv tags. Any ideas? Hartmut

3 5

How to make login service,rlogin, rsh work?
by hp9 11 Sep '06

11 Sep '06

I am installing SUSE 10.1 for a small cluster with autoyast. How to make login service,rlogin, rsh work without using yast1 manually? Hongbin

1 0

SLES10.1 autoinstall hangs at creating initrd
by hp9 11 Sep '06

11 Sep '06

Hi, I am trying to install SUSE 10.1 by network method and NFS and autoyast2 are fine. But SLES10.1 autoinstall hangs at creating initrd. THere is anyone had experience as that? It will be appreciated if anyone can provide ressolution for it. hongbin

3 2

bootloader configuration
by Karsten Künne 08 Sep '06

08 Sep '06

Hi, I try to configure the bootloader for SUSE 10.1 on a Sunfire X4100 with the following disk configuration: 2 SAS drives combined as a mirror via the SAS controller on SCSI id 0 2 other SAS drives on SCSI ids 2 and 3 In my autoyast profile I have the following section: <bootloader> <activate config:type="boolean">true</activate> <global config:type="list"> .... </global> <initrd_modules config:type="list"> <initrd_module> <module>mptsas</module> </initrd_module> <initrd_module> <module>scsi_mod</module> </initrd_module> .... </initrd_modules> <loader_device>/dev/sdc</loader_device> <loader_type>grub</loader_type> <location>mbr</location> <sections config:type="list"> <section config:type="list"> <section_entry> <key>title</key> <value>Linux</value> </section_entry> <section_entry> <key>kernel</key> <value>(hd2,4)/vmlinuz root=/dev/sdc7 vga=normal console=ttyS0,9600 console=tty0 noresume showopts</value> </section_entry> <section_entry> <key>initrd</key> <value>(hd2,4)/initrd</value> </section_entry> </section> <section config:type="list"> <section_entry> <key>title</key> <value>Failsafe</value> </section_entry> <section_entry> <key>kernel</key> <value>(hd2,4)/vmlinuz root=/dev/sdc7 vga=normal console=ttyS0,9600 console=tty0 noresume showopts ide=nodma apm=off acpi=off edd=off nosmp noapic maxcpus=0 3</value> </section_entry> <section_entry> <key>initrd</key> <value>(hd2,4)/initrd</value> </section_entry> </section> </sections> </bootloader> I want to install everything on the mirror which for whatever reason always appears as the last drive, even if it is SCSI id 0. But this seems to be a driver or controller issue and I can live with that. In my case the mirror is /dev/sdc resp. for grub it's (hd2). In the BIOS I explicitely set it to boot ONLY from the mirror and don't even look on the other drives. Now what happens is that Yast installs everything fine on the mirror but after the reboot the system doesn't come up anymore. The reason is that Yast never puts grub into the MBR on the mirror but instead puts it into the MBR of the first non-mirrored drive (which doesn't even have a valid partition table). This is the y2log_bootloader: GNU GRUB version 0.97 (640K lower / 3072K upper memory) [ Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists the possible completions of a device/filename. ] grub> root (hd2,4) Filesystem type is ext2fs, partition type 0x83 grub> install --stage2=/boot/grub/stage2 /grub/stage1 d (hd2,4) /grub/stage2 0x8000 (hd2,4)/grub/menu.lst grub> install --stage2=/boot/grub/stage2 /grub/stage1 d (hd0) /grub/stage2 0x8000 (hd2,4)/grub/menu.lst grub> quit Is that intentional behaviour and how can I get around it? Or is it just broken, in which case I can file a bug on bugzilla? Karsten. -- "The last time somebody said, `I find I can write much better with a word processor.', I replied, `They used to say the same thing about drugs.' -- Roy Blount, Jr.

1 1

Default installation encoding ISO-8895-1
by Klaus Jaensch 08 Sep '06

08 Sep '06

Hello, I want to set the default encoding of the installation to ISO-8859-1. I tried the following: <language>de_DE.ISO-8859-1</language> and <sysconfig config:type="list"> <sysconfig_entry> <sysconfig_key>RC_LANG</sysconfig_key> <sysconfig_path>/etc/sysconfig/language</sysconfig_path> <sysconfig_value>de_DE.ISO-8859-1</sysconfig_value> </sysconfig_entry> </sysconfig> but the encoding is finally always set to "de_DE.UTF-8". Any suggestions ? Klaus

1 0

WG: [suse-autoinstall] reboot after install
by Maurer, Andreas 08 Sep '06

08 Sep '06

Hello Simon, forceboot only forces the boot :) the reboot is done by: <reboot config:type="boolean">true</reboot> andreas ________________________________ Von: Simon Crute [mailto:scrute@novell.com] Gesendet: Do 07.09.2006 14:12 An: suse-autoinstall(a)suse.com Betreff: [suse-autoinstall] reboot after install Hi, I'm trying to get my autoyast setup to reboot after the install has finished, and then run the initscript scripts after the first boot. I've got the following section. <general> <mode> <confirm config:type="boolean">true</confirm> <forceboot config:type="boolean">true</forceboot> <second_stage config:type="boolean">true</second_stage> </mode> <mouse/> ... </general> but it's still not rebooting after an install. This causes me problems because the install kernel is a -default one, but I'm building -smp systems, so the initscrupt (which configures the sound card, and the display) fails cos there are no -default modules there, only -smp ones -- Simon Crute IS&T Bracknell Novell UK Ltd -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

4 12

Partitioning problem: /boot auto-added
by Frank Steiner 08 Sep '06

08 Sep '06

Hi, I'm trying to install SuSE 10.1 on a system with one SCSI disk. I used a profile to keep all existing partitions: /dev/sda1 / ext3 /dev/sda2 swap swap /dev/sda3 /var ext3 /dev/sda4 /export reiserfs The profile worked with SLES9, now fails with 10.1. While debugging I tried the same profile but toll AY to create all 4 partitions, just to see what comes out of it. Amazingly, AY creates this partitioning scheme: /dev/sda1 / ext3 /dev/sda2 /var ext3 /dev/sda3 extended partition /dev/sda5 swap swap /dev/sda6 /export reiserfs /dev/sda7 /boot ext2 A complete mess, of course (note that also swap and /var are swapped with the partition no.). Looking at y2log I find this: Partitions.ycp: BootCycl lba_support false Partitions.ycp: BootCycl /proc/xen/capabilities $[] Partitions.ycp: BootCycl lba_support false autoinstall/autoaprt.ycp: boot added automagically... So it looks like AY thinks that I need a special boot partition, which is nosense, of course. What can I do? Is this some known bug, or do I need to send the full y2log? The partitioning profile is below... cu, Frank <partitioning config:type="list"> <drive> <device>/dev/sda</device> <partitions config:type="list"> <partition> <create config:type="boolean">true</create> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <fstopt>defaults</fstopt> <mount>/</mount> <partition_nr config:type="integer">1</partition_nr> <size>20gb</size> </partition> <partition> <create config:type="boolean">true</create> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <fstopt>defaults</fstopt> <mount>/var</mount> <partition_nr config:type="integer">3</partition_nr> <size>4gb</size> </partition> <partition> <create config:type="boolean">true</create> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <fstopt>defaults</fstopt> <mount>swap</mount> <partition_nr config:type="integer">2</partition_nr> <size>2gb</size> </partition> <partition> <create config:type="boolean">true</create> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <fstopt>defaults</fstopt> <mount>/export</mount> <partition_nr config:type="integer">4</partition_nr> <size>max</size> </partition> </partitions> <use>all</use> </drive> </partitioning> -- Dipl.-Inform. Frank Steiner Web: http://www.bio.ifi.lmu.de/~steiner/ Lehrstuhl f. Bioinformatik Mail: http://www.bio.ifi.lmu.de/~steiner/m/ LMU, Amalienstr. 17 Phone: +49 89 2180-4049 80333 Muenchen, Germany Fax: +49 89 2180-99-4049 * Rekursion kann man erst verstehen, wenn man Rekursion verstanden hat. *

2 8

reboot after install
by Simon Crute 07 Sep '06

07 Sep '06

Hi, I'm trying to get my autoyast setup to reboot after the install has finished, and then run the initscript scripts after the first boot. I've got the following section. <general> <mode> <confirm config:type="boolean">true</confirm> <forceboot config:type="boolean">true</forceboot> <second_stage config:type="boolean">true</second_stage> </mode> <mouse/> ... </general> but it's still not rebooting after an install. This causes me problems because the install kernel is a -default one, but I'm building -smp systems, so the initscrupt (which configures the sound card, and the display) fails cos there are no -default modules there, only -smp ones -- Simon Crute IS&T Bracknell Novell UK Ltd

1 0

problems with language settings.
by Simon Crute 07 Sep '06

07 Sep '06

HI All, I'm having problems setting the language settings. I'm using this fragment of XML that's being pulled in via a rule. (basically, import a custom file depending on which domain the client is in) This fragment was created by yast2 autoyast. I just added the <general>tags round it. <?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"> <general> <keyboard> <keyboard_values> <capslock config:type="boolean">false</capslock> <delay></delay> <discaps config:type="boolean">false</discaps> <numlock></numlock> <rate></rate> <scrlock config:type="boolean">false</scrlock> <tty>tty1 tty2 tty3 tty4 tty5 tty6 tty8 tty9 tty10 tty11 tty12 tty13 tty14 tty15 tty16 tty17 tty18 tty19 tty20</tty> </keyboard_values> <keymap>english-uk</keymap> </keyboard> <language> <language>en_GB</language> <languages>en_US,en_GB</languages> </language> <timezone> <hwclock>UTC</hwclock> <timezone>Europe/London</timezone> </timezone> </general> </profile> However, the compleated system ends up with a US keyboard.... Interestingly, shortly after loading the xml fragment, the log file has 2006-08-17 17:01:55 <3> 192.168.21.139(3453) [Interpreter] Profile.ycp:118 Can't convert value '$["language":"en_GB", "languag es":"en_US,en_GB"]' to type 'string' in it. so, is it a bug, or user error ? ;-) -- Simon Crute IS&T Bracknell Novell UK Ltd

2 1

AutoYaST IP and partitioning problems
by Peter Ludikovsky 07 Sep '06

07 Sep '06

Good morning! I have some problems using AutoYaST to test the automatic installation I made from within VMware. But first things first. My target is to generate a bootable DVD that should be used to "reset" testing servers. The installation should run as quietly and automatic as possible from inserting the DVD and powering up the system to a complete system with Samba & Oracle. The configuration files can be retrieved at http://www.badongo.com/file/1308770 While the used linuxrc.config & info files should tell AutoYaST to use a static IP address (using VMwares emulated AMD PCnet32 card) it always tries to fetch information from a DHCP server, which is not present, or skips this step all together without BOOTP fallback. This is a major problem since the autoinstall directives should be fetched by HTTP. As soon as the installation proceeds past this it stops short at partitioning. I already tried using fresh disks (remember, still in VMware) and disks that had all required partitions written but to no avail. Is this a general problem with VMware or did I find a glitch? I would really like to be able to continue my test within VMware since I don't want to stress out the hardware now and have it break too soon. Regards, Peter

2 4

RAID1 md-device with "missing"-device
by Tob_Sch＠gmx.de 07 Sep '06

07 Sep '06

Hi, which entries in autoyast.xml do I need to configure a raid1 device with 2 devices, where one of these should be (at the beginning / installation time) a missing device. Sometimes, after the installation, I want to add a second HD and make a "mdadm -a". => so the functionality of "mdadm -C /dev/md0 -l raid1 -n 2 /dev/hda1 missing" and "mdadm -C /dev/md1 -l raid1 -n 2 /dev/hda2 missing" in autoyast is required Because, I didn't find anything about missing devices in the autoyast documentation, I tried to only change "/dev/hdb" to "missing", but that's not working... (see below) : : : <partitioning config:type="list"> <drive> <device>/dev/hda</device> <initialize config:type="boolean">true</initialize> <partitions config:type="list"> <partition> <format config:type="boolean">false</format> <partition_id config:type="integer">253</partition_id> <partition_type>primary</partition_type> <raid_name>/dev/md0</raid_name> <size>256M</size> </partition> <partition> <format config:type="boolean">false</format> <partition_id config:type="integer">253</partition_id> <partition_type>primary</partition_type> <raid_name>/dev/md1</raid_name> <size>max</size> </partition> </partitions> <use>all</use> </drive> <drive> <device>missing</device> <initialize config:type="boolean">true</initialize> <partitions config:type="list"> <partition> <format config:type="boolean">false</format> <partition_id config:type="integer">253</partition_id> <partition_type>primary</partition_type> <raid_name>/dev/md0</raid_name> <size>256M</size> </partition> <partition> <format config:type="boolean">false</format> <partition_id config:type="integer">253</partition_id> <partition_type>primary</partition_type> <raid_name>/dev/md1</raid_name> <size>max</size> </partition> </partitions> <use>all</use> </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> <filesystem_id config:type="integer">131</filesystem_id> <chunk_size>4</chunk_size> <mount>/boot</mount> <format config:type="boolean">true</format> <filesystem config:type="symbol">xfs</filesystem> </raid_device> <raid_device> <device_name>/dev/md1</device_name> <lvm_group>vg00</lvm_group> <parity_algorithm>left-asymmetric</parity_algorithm> <persistent_superblock config:type="boolean">true</persistent_superblock> <raid_type>raid1</raid_type> <filesystem_id config:type="integer">142</filesystem_id> <chunk_size>4</chunk_size> </raid_device> </raid> : : : Thanks in advance. -- Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer

2 1

error in create_update_source.sh + fix
by Stan Novogroudski 06 Sep '06

06 Sep '06

Please fix it: in create_update_source.sh line 101 use if ! [[ "$VALUE" -eq "SHA1" ]]; then instead of if ! [[ "$VALUE" =~ "SHA1" ]]; then Operator =~ is used in Perl, not in shell. After this fix is create_update_source.sh working. Best regards. Stan

3 2

init-scripts without network config
by Paul DiSciascio 06 Sep '06

06 Sep '06

init-scripts don't seem to work if there is no network config in SLES 10. So i added a network section to my autoinst.xml. The problem with this is that the default for eth0 is dhcp, which is not allowed on my network, so i set bootproto to "none", which had absolutely no affect. So I removed the /etc/sysconfig/network/ifcfg-eth0-* file in my init-script and rebooted. The problem with this solution is that /etc/hosts and /etc/resolv.conf are already modified by the installer by this point (i would like that to not happen.) Is there a better way besides setting bootproto to "none" that will make the network subsystem come up, but with no devices configured? Or failing that, is there a way to make init-scripts work without the network dependency? Thanks, Paul

2 1

Preload modules before hardware detection? (wrong scsi order)
by Frank Steiner 05 Sep '06

05 Sep '06

Hi, similar post was sent in July with title "Problem with the order of disks", where Michael Schulz had the same problem we have: SCSI controllers are detected in the wrong order, so that the disk that should be /dev/sda ends up as /dev/sde. This used to work with SuSE 9.0 where we loaded the module for the first controller with "insmod gdth" passed to linuxrc (we are using pxeboot). Now, with 10.1, the init process of YA starts a "Hardware detection" *before* loading the modules defined in the info file or passed to the command line. This makes the insmod option for linuxrc more or less superfluous and removes any control over the order in which modules are loaded during the AY boot. Here, it makes the fc modules load before the scsi modules, thus moving our scsi disk to /dev/sde. Is it possible to disable automatic hardware detection or load the modules before the hardware detection? Or could I try thinks like renaming the init binary in the initrd and install my own script there that's just modprobe gdth exec init.suse Of course, I would prefer a method without changing the initrd if possible... cu, Frank -- Dipl.-Inform. Frank Steiner Web: http://www.bio.ifi.lmu.de/~steiner/ Lehrstuhl f. Bioinformatik Mail: http://www.bio.ifi.lmu.de/~steiner/m/ LMU, Amalienstr. 17 Phone: +49 89 2180-4049 80333 Muenchen, Germany Fax: +49 89 2180-99-4049 * Rekursion kann man erst verstehen, wenn man Rekursion verstanden hat. *

3 8

OpenSUSE 10.1 Online update in autoyast
by Ian Grant 01 Sep '06

01 Sep '06

Does anyone have XML for OpenSUSE 10.1 to cause autoyast to do an online update at install time? I am hoping this is better than the farce we have to go through at the moment to run it after the autoyast install: it has to be run, interactively, four times to get the security/recommended updates done. Failing that, does anyone know how to run it from the command line so it doesn't need somoeone to press keys?

6 7