September 2006 - openSUSE Autoinstall - openSUSE Mailing Lists

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