Hello, Am Mittwoch, 20. August 2008 03:43:31 schrieb Alan Keng:

Hi,

I am trying to add some RPMs from the oss repositoiy to the AutoYast installation.

I used the following instructions:

Suppose the source resides in myInstallSource ./create_update_source.sh myInstallSource cp -a myPackage-x86_64.rpm myInstallSource/updates/suse/x86_64 cd myInstallSource/updates/suse create_package_descr -x setup/descr/EXTRA_PROV cd setup/descr ls > directory.yast cd ../../.. create_sha1sums -x -n ./

Try also create_sha1sums -x -n . If it dosn't help, I followed this instruction for my Own Packages: mkdir -p /installation/repository/OpenSuSE110/ownpackages cd /installation/repository/OpenSuSE110/ownpackages mkdir media.1 vi media.1/media (Copy from OpenSuSE repository, changed to my needs) vi content (Copy from OpenSuSE repository, changed to my needs) mkdir suse cd suse mkdir i386 i486 i586 i686 noarch x86_64 tar ls -A1 > directory.yast Copy the relevant packages to it's folders create_package_descr -l german -l english -d suse/ create_sha1sums -x -n ./ (content file unter setup/descr create_sha1sums -x -n . (für das content file im rootdirectory) The nfs share is /installation

And added following lines to the control XML file:

<add-on> <add_on_products config:type="list"> <listentry> <media_url>nfs://"Server IP"/myInstallSource/updates</media_url>

<media_url>nfs://"ServerIP"/installation/repository/OpenSuSE110/ownpackages/</media_url> <product>Own Packages</product> <product_dir>/</product_dir> <ask_on_error config:type="boolean">false</ask_on_error>

<ask_on_error config:type="boolean">true</ask_on_error> <product_dir>/</product_dir> </listentry> </add_on_products> </add-on>

looks OK

I also added the following lines between the <general><signature-handling> … </signature-handling></general> tags:

<signature-handling> <accept_unsigned_file config:type=”boolean”>true</accept_unsigned_file> <accept_file_without_checksum config:type=”boolean”>true</accept_file_without_checksum> <accept_verification_failed config:type=”boolean”>true</accept_verification_failed> <accept_unknown_gpg_key config:type=”boolean”>true</accept_unknown_gpg_key> <import_gpg_key config:type=”boolean”>true</import_gpg_key> </signature-handling>

looks OK

I believe I got the NFS server all setup correctly because the control file is also located on the NFS server.

During the installation, I got the "Add-on is not available via NFS" error:

"Please make the add-on "SuSE-Linux-Updates" available via "nfs://"Server IP"/myInstallSource/updates"

Any one can help? What went wrong?

Thanks, Alan

Georg -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org

Alan, Did you use the "yast2 autoyast" tool to create the control xml? If you can, it'll be pretty easy to see how to do what you want. You can start the tool and then File->Open your existing control.xml and then modify, I think. Root around in the Bootloader section. if ! "$luck" == "good" then write back && I can probably hack together the xml for you fi Best, Mike Mike Diehn Sr. SysAdmin mike.diehn@ansys.com +1-603-727-5492

-----Original Message----- From: Alan Keng [mailto:akeng@aehr.com] Sent: Tuesday, August 26, 2008 3:42 PM To: opensuse-autoinstall@opensuse.org Subject: [opensuse-autoinstall] How to install bootloader on both disks with software RAID 1 (openSUSE 11.0)

Hi,

When I used AutoYast with Software RAID 1 partition, I installed the GRUB bootloader on MBR.

Apparently, the bootloader was only installed on one of the physical hard disk. How can I set it up to install the bootloader on both of the disks, so whenever one of the disk's gone bad and doesn't matter which on it is, I am still able to boot the system?

This is extracted from my control XML file if it helps:

<bootloader> <device_map config:type="list"> <device_map_entry> <firmware>fd0</firmware> <linux>/dev/fd0</linux> </device_map_entry> <device_map_entry> <firmware>hd0</firmware> <linux>/dev/sda</linux> </device_map_entry> <device_map_entry> <firmware>hd1</firmware> <linux>/dev/sdb</linux> </device_map_entry> </device_map> <global> <activate>true</activate> <boot_mbr>true</boot_mbr> <default>openSUSE 11.0 - 2.6.25.5-1.1</default> <gfxmenu>/boot/message</gfxmenu> <lines_cache_id>3</lines_cache_id> <timeout config:type="integer">8</timeout> </global> <initrd_modules config:type="list"> <initrd_module> <module>processor</module> </initrd_module> <initrd_module> <module>thermal</module> </initrd_module> <initrd_module> <module>sata_nv</module> </initrd_module> <initrd_module> <module>pata_amd</module> </initrd_module> <initrd_module> <module>fan</module> </initrd_module> <initrd_module> <module>reiserfs</module> </initrd_module> <initrd_module> <module>raid1</module> </initrd_module> <initrd_module> <module>edd</module> </initrd_module> </initrd_modules> <loader_type>grub</loader_type> <sections config:type="list"> <section> <append>resume=/dev/md1 splash=silent showopts</append> <image>/boot/vmlinuz-2.6.25.5-1.1-default</image> <initial>1</initial> <initrd>/boot/initrd-2.6.25.5-1.1-default</initrd> <lines_cache_id>0</lines_cache_id> <name>openSUSE 11.0 - 2.6.25.5-1.1</name> <original_name>linux</original_name> <root>/dev/md2</root> <type>image</type> <vga>0x317</vga> <vgamode>0x317</vgamode> </section> <section> <append>showopts ide=nodma apm=off acpi=off noresume edd=off x11failsafe</append> <image>/boot/vmlinuz-2.6.25.5-1.1-default</image> <initrd>/boot/initrd-2.6.25.5-1.1-default</initrd> <lines_cache_id>1</lines_cache_id> <name>Failsafe -- openSUSE 11.0 - 2.6.25.5-1.1</name> <original_name>failsafe</original_name> <root>/dev/md2</root> <type>image</type> <vga>0x317</vga> <vgamode>0x317</vgamode> </section> <section> <blockoffset>1</blockoffset> <chainloader>/dev/fd0</chainloader> <lines_cache_id>2</lines_cache_id> <name>Floppy</name> <noverifyroot>true</noverifyroot> <original_name>floppy</original_name> <type>other</type> </section> </sections> </bootloader>

<partitioning config:type="list"> <drive> <device>/dev/md</device> <partitions config:type="list"> <partition> <create config:type="boolean">true</create> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <mount>/boot</mount> <mountby config:type="symbol">device</mountby> <partition_nr config:type="integer">0</partition_nr> <raid_options> <persistent_superblock config:type="boolean">false</persistent_superblock> <raid_type>raid1</raid_type> </raid_options> </partition> <partition> <create config:type="boolean">true</create> <mount>swap</mount> <mountby config:type="symbol">device</mountby> <partition_nr config:type="integer">1</partition_nr> <raid_options> <persistent_superblock config:type="boolean">false</persistent_superblock> <raid_type>raid_unknown</raid_type> </raid_options> </partition> <partition> <create config:type="boolean">true</create> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <mount>/</mount> <mountby config:type="symbol">device</mountby> <partition_nr config:type="integer">2</partition_nr> <raid_options> <persistent_superblock config:type="boolean">false</persistent_superblock> <raid_type>raid1</raid_type> </raid_options> </partition> <partition> <create config:type="boolean">true</create> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <mount>/home</mount> <mountby config:type="symbol">device</mountby> <partition_nr config:type="integer">3</partition_nr> <raid_options> <persistent_superblock config:type="boolean">false</persistent_superblock> <raid_type>raid1</raid_type> </raid_options> </partition> </partitions> <type config:type="symbol">CT_MD</type> <use>all</use> </drive> <drive> <device>/dev/sda</device> <partitions config:type="list"> <partition> <create config:type="boolean">true</create> <filesystem_id config:type="integer">253</filesystem_id> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">1</partition_nr> <partition_type>primary</partition_type> <raid_name>/dev/md0</raid_name> <size>2gb</size> </partition> <partition> <create config:type="boolean">true</create> <filesystem_id config:type="integer">253</filesystem_id> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">2</partition_nr> <partition_type>primary</partition_type> <size>8gb</size> </partition> <partition> <create config:type="boolean">true</create> <filesystem_id config:type="integer">253</filesystem_id> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">3</partition_nr> <partition_type>primary</partition_type> <raid_name>/dev/md2</raid_name> <size>20gb</size> </partition> <partition> <create config:type="boolean">true</create> <filesystem_id config:type="integer">253</filesystem_id> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">4</partition_nr> <partition_type>primary</partition_type> <raid_name>/dev/md3</raid_name> <size>max</size> </partition> </partitions> <type config:type="symbol">CT_DISK</type> <use>all</use> </drive> <drive> <device>/dev/sdb</device> <partitions config:type="list"> <partition> <create config:type="boolean">true</create> <filesystem_id config:type="integer">253</filesystem_id> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">1</partition_nr> <partition_type>primary</partition_type> <raid_name>/dev/md0</raid_name> <size>2gb</size> </partition> <partition> <create config:type="boolean">true</create> <filesystem_id config:type="integer">253</filesystem_id> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">2</partition_nr> <partition_type>primary</partition_type> <raid_name>/dev/md1</raid_name> <size>8gb</size> </partition> <partition> <create config:type="boolean">true</create> <filesystem_id config:type="integer">253</filesystem_id> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">3</partition_nr> <partition_type>primary</partition_type> <raid_name>/dev/md2</raid_name> <size>20gb</size> </partition> <partition> <create config:type="boolean">true</create> <filesystem_id config:type="integer">253</filesystem_id> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">4</partition_nr> <partition_type>primary</partition_type> <raid_name>/dev/md3</raid_name> <size>max</size> </partition> </partitions> <type config:type="symbol">CT_DISK</type> <use>all</use> </drive> </partitioning>

Thanks, Alan

-- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org

On Wednesday 10 September 2008, Alan Keng wrote:

I was wondering if there way to enable the user auto login using AutoYast?

Any XML element can be used for that?

untested! <sysconfig config:type="list" > <sysconfig_entry> <sysconfig_key>DISPLAYMANAGER_AUTOLOGIN</sysconfig_key> <sysconfig_path>/etc/sysconfig/displaymanager</sysconfig_path> <sysconfig_value>uwe</sysconfig_value> </sysconfig_entry> </sysconfig> -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Business: http://www.suse.de/~ug listening to: "Post Blue" by Placebo -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org

Hi, I was trying to use AutoYast to install number of systems with BIOS Raid1. The raid is created by Intel Matrix Storage Manager that comes w/ the system. In my case, when a BIOS Raid1,named Volume0, is created, the name of the device would be like, isw_xxxxx_Volume0. In the autoinst.xml, "/dev/mapper/isw_xxxxx_Volume0", are the values of many parts of the profile. e.g. <bootloader> <device_map> <device_map_entry> <linux>/dev/mapper/isw_bbcihdbdh_Volume0</linux> <sections config:type="list"> <section> <append>resume=/dev/mapper/isw_bbcihdbdh_Volume0_part6 splash=silent showopts</append> <root>/dev/mapper/isw_bbcihdbdh_Volume0_part7</root> <partitioning config:type="list"> <drive> <device>/dev/mapper/isw_bbcihdbdh_Volume0</device> The name of BIOS Raid1 would be different each time it gets created and it will cause problems when using the profile to do the installations with different names. Is there a way to get around with it? Like having it to have the same name always? Or can the installation be more dynamically to set the values? Just like the "Ask". However, instead of asking the user to enter values, can we use pre-defined linux commands or scripts in the profile to set the values based on the system settings? Thank you for your time. Regards, Alan -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org

Can you run a pre-install script to determine which device should be used for the partioning plan (SLES 10)? We have some servers where fiber attached drives are being identified first (SDA) as opposed to locally attached drives. We have other servers where we would like to SAN boot, but the first drive detected is sometimes a 5 mb lun. -----Original Message----- From: Uwe Gansert [mailto:ug@suse.de] Sent: Tuesday, October 28, 2008 5:16 AM To: opensuse-autoinstall@opensuse.org Subject: Re: [opensuse-autoinstall] Autoyast installation with BISO Raid 1 (fake raid) Am Freitag 24 Oktober 2008 01:30:09 schrieb Alan Keng:

In my case, when a BIOS Raid1,named Volume0, is created, the name of the device would be like, isw_xxxxx_Volume0.

Which SUSE Linux version? Since openSUSE 11.0 autoyast should autodetect raid device names if the <device> tags are missing in the profile. If that does not work, you can use a pre-script to detect the device name on your own and modify your profile before the installation starts: http://www.suse.de/~ug/autoyast_doc/createprofile.scripts.html#pre- install.scripts -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Business: http://www.suse.de/~ug -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org

Does anyone have any examples of how to present a list of disks and their sizes to the user at install time to let them choose which disk to install to? -----Original Message----- From: Uwe Gansert [mailto:ug@suse.de] Sent: Tuesday, October 28, 2008 10:11 AM To: opensuse-autoinstall@opensuse.org Subject: Re: [opensuse-autoinstall] Autoyast installation with BISO Raid 1 (fake raid) Am Dienstag 28 Oktober 2008 15:11:42 schrieb Stephens, Bill {PBSG}:

Can you run a pre-install script to determine which device should be used for the partioning plan (SLES 10)? We have some servers where fiber attached drives are being identified first (SDA) as opposed to locally attached drives. We have other servers where we would like to SAN boot, but the first drive detected is sometimes a 5 mb lun.

yes, you can change the partitioning section via pre-script on SLES10 -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Business: http://www.suse.de/~ug listening to: "Phoenix" by Unheilig -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org

Hi, I have 2 NICs on the system and one is used to connect to the NFS server for AutoYast installation. When AutoYast has completed the system configuration and booting the system for the first time, quite oftenly, one of the NICs cannot be detected by the system and causing the LAN setting cannot be set correctly based on the profile later on. It would be even worse If the un-found interface is the one used for connecting to the server. Is this the problem of AutoYast or openSuse itself? Why all the NICs can't be picked up all the time? Thanks -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org