November 2005 - 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

Partitioning problems doing RAID + LVM on SL 10.0
by Gavin Carr 06 Dec '05

06 Dec '05

Hi, I'm having all kinds of problems trying to get a RAID1 + LVM partitioning scheme working on SL10.0. I'm wanting this: /dev/sda: swap auto raid1a 100MB raid2a 100MB raid3a 100MB raid4a max /dev/sdb: swap auto raid1b 100MB raid2b 100MB raid3b 100MB raid4b max RAID: md0: raid1a + raid1b, /boot md1: raid2a + raid2b, /boot2 md2: raid3a + raid3b, /boot3 md3: raid4a + raid4b, LVM physical volume LVM: volume group /dev/system: /dev/md3 logical volumes: / ext3 5GB /data ext3 200GB i.e. an LVM physical volume on a RAID1 partition. The partitioning fragment of my autoyast config looks like this: <partitioning config:type="list"> <drive> <device>/dev/sda</device> <initialize config:type="boolean">false</initialize> <partitions config:type="list"> <partition> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <mount>swap</mount> <size>auto</size> </partition> <partition> <partition_id config:type="integer">253</partition_id> <raid_name>/dev/md0</raid_name> <size>100mb</size> </partition> <partition> <partition_id config:type="integer">253</partition_id> <raid_name>/dev/md1</raid_name> <size>100mb</size> </partition> <partition> <partition_id config:type="integer">253</partition_id> <raid_name>/dev/md2</raid_name> <size>100mb</size> </partition> <partition> <partition_id config:type="integer">253</partition_id> <raid_name>/dev/md3</raid_name> <size>max</size> </partition> </partitions> <use>all</use> </drive> <drive> <device>/dev/sdb</device> <initialize config:type="boolean">false</initialize> <partitions config:type="list"> <partition> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <mount>swap</mount> <size>auto</size> </partition> <partition> <partition_id config:type="integer">253</partition_id> <raid_name>/dev/md0</raid_name> <size>100mb</size> </partition> <partition> <partition_id config:type="integer">253</partition_id> <raid_name>/dev/md1</raid_name> <size>100mb</size> </partition> <partition> <partition_id config:type="integer">253</partition_id> <raid_name>/dev/md2</raid_name> <size>100mb</size> </partition> <partition> <partition_id config:type="integer">253</partition_id> <raid_name>/dev/md3</raid_name> <size>max</size> </partition> </partitions> <use>all</use> </drive> <drive> <device>/dev/md</device> <partitions config:type="list"> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <partition_id config:type="integer">130</partition_id> <partition_nr config:type="integer">0</partition_nr> <mount>/boot</mount> <raid_options> <chunk_size>4</chunk_size> <parity_algorithm>left-asymmetric</parity_algorithm> <raid_type>raid1</raid_type> </raid_options> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <partition_id config:type="integer">130</partition_id> <partition_nr config:type="integer">1</partition_nr> <mount>/boot2</mount> <raid_options> <chunk_size>4</chunk_size> <parity_algorithm>left-asymmetric</parity_algorithm> <raid_type>raid1</raid_type> </raid_options> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <partition_id config:type="integer">130</partition_id> <partition_nr config:type="integer">2</partition_nr> <mount>/boot3</mount> <raid_options> <chunk_size>4</chunk_size> <parity_algorithm>left-asymmetric</parity_algorithm> <raid_type>raid1</raid_type> </raid_options> </partition> <partition> <lvm_group>system</lvm_group> <partition_id config:type="integer">142</partition_id> <partition_nr config:type="integer">3</partition_nr> <raid_options> <chunk_size>4</chunk_size> <parity_algorithm>left-asymmetric</parity_algorithm> <raid_type>raid1</raid_type> </raid_options> </partition> </partitions> <use>all</use> </drive> <drive> <device>/dev/system</device> <is_lvm_vg config:type="boolean">true</is_lvm_vg> <partitions config:type="list"> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <lv_name>root1</lv_name> <mount>/</mount> <size>5gb</size> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <lv_name>data</lv_name> <mount>/data</mount> <size>200gb</size> </partition> </partitions> <pesize>32M</pesize> <use>all</use> </drive> </partitioning> This validates against the DTDs with xmllint, and it _almost_ works under autoyast. Here's the Partitioning confirmation output: Create extended partition /dev/sda1 (232.8 GB) Create swap partition /dev/sda5 (1.0 GB) Create partition /dev/sda6 (101.9 MB) with id=8E Create partition /dev/sda7 (101.9 MB) with id=8E Create partition /dev/sda8 (101.9 MB) with id=8E Create partition /dev/sda9 (231.5 GB) with id=8E Create extended partition /dev/sdb1 (232.8 GB) Create swap partition /dev/sdb5 (1.0 GB) Create partition /dev/sdb6 (101.9 MB) with id=FD Create partition /dev/sdb7 (101.9 MB) with id=FD Create partition /dev/sdb8 (101.9 MB) with id=FD Create partition /dev/sdb9 (231.5 GB) with id=FD Create software RAID /dev/md0 (101.9 MB) for /boot with ext3 Create software RAID /dev/md1 (101.9 MB) for /boot2 with ext3 Create software RAID /dev/md2 (101.9 MB) for /boot3 with ext3 Create software RAID /dev/md3 (231.5 GB) Create volume group system Create logical volume /dev/system/data (200.0 GB) for /data with ext3 Create logical volume /dev/system/root1 (5.0 GB) for / with ext3 The problem is that somehow it comes up with the wrong partition type /dev/sda[6-9] partitions, making them LVM partitions (8E) instead of RAID partitions (FD), it's added all the /dev/sda partitions to the /dev/system volume group, and the raid partitions only contain the /dev/sdb members, and so raid volume creation fails. Does this look like an error in my config somewhere, or a bug? If I correct these problems by hand, everything works. In addition, if I try and initialise the drives I get even more bizarre problems - the /dev/sda partitions disappear altogther. I've been deleting the partition tables by hand to get it this far. This is x86_64 on sata drives, in case that matters. Thanks a lot for any clues/ideas. Been banging my head against this for a day and a half now ... Cheers, Gavin

3 3

Disabling Suse Watcher
by Thomas Muders 30 Nov '05

30 Nov '05

Hello, I install machines with autoyast, automatic updates via YOU enabled. Therefore, I want to disable the Suse watcher so that it doesn't come up when a new user logs in. Is there any way other than creating the configuration file for susewatcher in /etc/skel/.kde ... which tells it not to run? Unfortunately it's not in a separate package but in kdebase. Maybe I should file a suggestion to Opensuse to move it into a separate package... Thanks, Thomas

1 0

Time for automatic YOU
by Guido Kölsch 30 Nov '05

30 Nov '05

Hi, i have installed many machines with the automatic update via YOU configured. Every monday and the time is set to random. But on every machines there is the same time configured: 21:28. Don't know why? Any ideas? -- ------------------------------------------------------------------------ Guido Kölsch Max-Planck-Institut fuer Radioastronomie Phone: +49 (0)228 525 164 Auf dem Huegel 69, D-53121 Bonn, Germany FAX : +49 (0)228 525 229 email: gkoelsch(a)mpifr-bonn.mpg.de ------------------------------------------------------------------------

1 0

What is a _working_ minimal install?
by Christian Goetze 29 Nov '05

29 Nov '05

If I set up my profile like so: <software> <addons config:type="list"> <addon>Base-System</addon> </addons> <base>Minimal</base> </software> The autoinstall stops when attempting to create the bootloader and requests me to insert CD1. If I hit "skip", I then see it complaining about a missing rpm. I've been through 4 iterations now, and added: <package>libpcap</package> <package>libcap</package> <package>nfs-utils</package> <package>nss_ldap</package> How many more are there? What is the true self-sustaining minimal install? Thanks in advance -- cg

3 4

Suse watcher
by Thomas Muders 29 Nov '05

29 Nov '05

Hello, I install machines with autoyast, automatic updates via YOU enabled. Therefore, I want to disable the Suse watcher so that it doesn't come up when a new user logs in. Is there any way other than creating the configuration file for susewatcher in /etc/skel/.kde ... which tells it not to run? Unfortunately it's not in a separate package but in kdebase. Maybe I should file a suggestion to Opensuse to move it into a separate package... Thomas

1 0

iscsi_boot in /sbin/mkinitrd of SLES9
by Aggarwal, VikasX 28 Nov '05

28 Nov '05

Hello All, I am working on for SLES9 installation to iSCSI disk and then booting from it. It is already working for RHEL4 linux. My procedure(for iscsi installation and boot-from iscsi-disk) required changes to "mkinitrd" for RHEL4 linux. While going through "/sbin/mkinitrd" of SLES9, i found "iscsi_boot" variable inside it. Now i wonder if i can find a doucment to teach myself to use this already-existing feature of SLES9 to enable iscsi boot. I installed on iSCSi disk. As i added the iscsi.ko and iscsid-daemon and related configuration files via driver-update-diskettes prepared using "dkms mkdriverdisk ....". But so far i had not been able to understand how to enable the iscsi boot for SLES9 in initrd. My NIC already has some iscsi expansion ROM which can get the iscsi_boot drive from DHCP server and it will scsi-read the grub-loader and initrd+vmlinuz. After that the iscsi-stack inside the initrd will take-over. From SUSE gurus i am trying to find out "how can I enable the alread-existing feature of iscsi_boot in SLES9 mkinitrd ?". regards -vikas aggarwal

1 0

help with labels in partition
by jaiber john 28 Nov '05

28 Nov '05

hi, I'm using autoyast to install SLES9 on a set of systems where the disk order may change (It may be /dev/sda sometimes, /dev/sdb, etc..) but I've made proper labels on partitions I want to install. I want to use them in my autoyast.xml instead of device names. I'll create/format paritions before installation. I want to autoyast to re-use those partitions. Labels are set by e2label program. eg: I want to use the partition with label /1 as root. ---------------------------------------------------------------------------- <partitions config:type="list> <partition> <creat config:type="boolean">false</format> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">false</format> <mount>/</mount> <label>/1</label> <mountby config:type="symbol">label</mountby> </partition> </partitions> ------------------------------------------------------------------------------ I've tried this approach, but it doesnt seem to work! The documentation says if mountby symbol label is used, then the partition specified in label attribute will be used. Any help would be appreciated. Thanks Jaiber John

2 1

YOU with SP2
by Michael T. Halligan 26 Nov '05

26 Nov '05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm having a bit of trouble syncing up my YOU server to you.novell.com/update .. Can anybody give me an idea on how to sync for SP2? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Darwin) iD8DBQFDh/ABwjCqooJyNAMRAjXcAJ47S66naDGI/MiPQxK6jWzKMbAh2ACdFpsp GkCXHrnXn3DvyXGAY5z5h7E= =1kyr -----END PGP SIGNATURE-----

1 0

passing boot ( interactively) options to grub combined with with using the menu.lst
by Hans-Joachim Ehlers 25 Nov '05

25 Nov '05

Hi folks, i am trying to move a Suse Installation CD to a USB-Stick so i can use the USB Stick for installation. The suse installation has the wonderfull option that you can add on a command line additional parameters to the kernel . Like: -> Select Installation -> On the command line add: hostname=myws At the moment i am able to boot from the USB-Stick with grub and can select 'Installation' from the grub menu. But how do i add additional parameter to grub without the need to modify the menu.lst ? Like the isolinux.cfg when booting from cd/dvd Extract from the menu.lst .. title Installation root (hd0,0) kernel /boot/loader/linux root=dev/sda1 vga=791 initrd /boot/loader/initrd tia Hajo ============================ Hans-Joachim Ehlers UNIX Systems Engineer EUMETSAT Am Kavalleriesand, 31 64295, Darmstadt, Germany Tel : +49 6151 807-7307 mailto:hansjoachim.ehlers@eumetsat.int http://www.eumetsat.int

2 1