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

bootloader for RAID1
by Lars Stavholm 24 Nov '05

24 Nov '05

Hi all, having problems with the bootloader for RAID1 boot. I've specified the bootloader section explicitly in my autoinst.xml (since the one suggested by autoyast doesn't work). Despite this, the first boot doesn't use my specified bootloader, it still uses the autoyast one. After the first boot, however, my specific one is used, but only if I implement it as a post-script. The bootloader specifications from the bootloader section is still not used. How do I get my bootloader specification to be used at all, especially at first boot? Is there a workaround? R /LarS PS. Here's my autoinst.xml: --- Begin Included Message --- <?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">false</activate> <global config:type="list"> <global_entry> <key>color</key><value>white/blue black/light-gray</value> </global_entry> <global_entry> <key>default</key><value>0</value> </global_entry> <global_entry> <key>timeout</key><value config:type="integer">5</value> </global_entry> </global> <loader_device>/dev/md0</loader_device> <loader_type>grub</loader_type> <repl_mbr config:type="boolean">false</repl_mbr> <sections config:type="list"> <section> <section_entry> <key>title</key><value>SuSE Linux 10.0</value> </section_entry> <section_entry> <key>root</key><value>(hd0,0)</value> </section_entry> <section_entry> <key>kernel</key> <value>/vmlinuz root=/dev/md2 vga=791 selinux=0 noresume acpi=off splash=silent showopts</value> </section_entry> <section_entry> <key>initrd</key> <value>/initrd</value> </section_entry> </section> <section> <section_entry> <key>title</key><value>SuSE Linux 10.0 - failsafe</value> </section_entry> <section_entry> <key>root</key><value>(hd0,0)</value> </section_entry> <section_entry> <key>kernel</key> <value>/vmlinuz root=/dev/md2 vga=normal showopts ide=nodma apm=off acpi=off noresume selinux=0 nosmp noapic maxcpus=0 edd=off 3</value> </section_entry> <section_entry> <key>initrd</key> <value>/initrd</value> </section_entry> </section> </sections> </bootloader> <scripts>  <pre-scripts config:type="list"> <script> <filename>pre.sh</filename> <interpreter>shell</interpreter> <source> <![CDATA[ hds=`fdisk -l | grep Disk | grep '/dev/hd' | cut -d\ -f2 | cut -d: -f1` for hd in $hds; do ps=`parted $hd print | grep '^[1-9]' | cut -d\ -f1` for p in $ps; do mdadm --force --zero-superblock $hd$p parted $hd rm $p done #dd if=/dev/zero of=$hd bs=1k count=1 done ]]> </source> </script> </pre-scripts> </scripts> <users config:type="list"> <user> <encrypted config:type="boolean">true</encrypted> <gid config:type="integer">0</gid> <grouplist></grouplist> <home>/root</home> <password_settings> <expire></expire> <flag></flag> <inact></inact> <last_change>12418</last_change> <max>10000</max> <min>0</min> <warn></warn> </password_settings> <shell>/bin/tcsh</shell> <user_password>$2a$10$hqI8xRFGn1Wo26WF4V1qqeqDVYOEF5eiFeQo2WpdQTwrbIVOb2U0e</user_password> <username>root</username> </user> </users> <general> <clock> <hwclock>UTC</hwclock> <timezone>Europe/Stockholm</timezone> </clock> <keyboard> <keymap>swedish</keymap> </keyboard> <language>en_US</language> <mode> <confirm config:type="boolean">false</confirm> <forceboot config:type="boolean">false</forceboot> <reboot config:type="boolean">false</reboot> </mode> <mouse> <id>probe</id> </mouse> </general> <bootloader> <activate config:type="boolean">true</activate> <loader_device>/dev/md0</loader_device> <loader_type>grub</loader_type> </bootloader> <partitioning config:type="list"> <drive> <device>/dev/hda</device> <initialize config:type="boolean">false</initialize> <partitions config:type="list"> <partition> <create config:type="boolean">true</create> <format config:type="boolean">false</format> <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> <raid_type>raid</raid_type> <size>100MB</size> </partition> <partition> <create config:type="boolean">true</create> <format config:type="boolean">false</format> <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> <raid_type>raid</raid_type> <size>900MB</size> </partition> <partition> <create config:type="boolean">true</create> <format config:type="boolean">false</format> <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> <raid_type>raid</raid_type> <size>max</size> </partition> </partitions> <use>all</use> </drive> <drive> <device>/dev/hdc</device> <initialize config:type="boolean">false</initialize> <partitions config:type="list"> <partition> <create config:type="boolean">true</create> <format config:type="boolean">false</format> <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> <raid_type>raid</raid_type> <size>100MB</size> </partition> <partition> <create config:type="boolean">true</create> <format config:type="boolean">false</format> <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> <raid_type>raid</raid_type> <size>900MB</size> </partition> <partition> <create config:type="boolean">true</create> <format config:type="boolean">false</format> <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> <raid_type>raid</raid_type> <size>max</size> </partition> </partitions> <use>all</use> </drive> <drive> <device>/dev/md</device> <initialize config:type="boolean">false</initialize> <partitions config:type="list"> <partition> <filesystem config:type="symbol">ext2</filesystem> <format config:type="boolean">true</format> <mount>/boot</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">0</partition_nr> </partition> <partition> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <mount>swap</mount> <partition_id config:type="integer">130</partition_id> <partition_nr config:type="integer">1</partition_nr> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <mount>/</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">2</partition_nr> </partition> </partitions> <use>all</use> </drive> </partitioning> <software> <addons> <addon>Min</addon> <addon>X11</addon> <addon>Jonix-Addons</addon> </addons> <base>Minimal+X11</base> <packages config:type="list"> <package>lvm2</package> </packages> <remove-packages config:type="list"> <package>imap</package> <package>lukemftp</package> <package>tftp</package> </remove-packages> </software> </profile> --- End Included Message ---

2 2

SLES 9 install source for i386 and x86_64
by Andreas Vetter 24 Nov '05

24 Nov '05

Hi Is it possible to setup a combined install repository for i386 and x86_64? I also want to include SP2. I know how to do that for i386 alone. How do I do it for both? What made me ask is the difference in the file content and media.1/product on the first CDs. TIA, Andreas -- Andreas Vetter Universitaet Wuerzburg

2 2

Custom packages
by Ness, Todd 23 Nov '05

23 Nov '05

I have added an extra source for packages, which has patches, and other RPMS that I have added to my build. When I build from this source, I get all the updated kernel packages etc that I expect to get. But, I have a problem in that the installer does not reboot after Disk 1's contents have been installed like when I build off the initial source. Which causes problems with large RPMS not installing due to lack of disk space during the memory version of the install OS. How do I get the installer to reboot as soon as possible? Todd

1 0

RAID problem
by Lars Stavholm 22 Nov '05

22 Nov '05

Hi all, I'm using SuSE 10.0 Professional and I'm trying to get an autoinstall with RAID going. Everything looks fine, but the installation stops with the following message: Error Storage modification failed. System error code was -6002. Failure occured during following action: Creating software RAID /dev/md0. Has anyone else run in to this? Does anyone know what it means? R /stava PS, here's my full autoinst.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"> <general> <clock> <hwclock>UTC</hwclock> <timezone>Europe/Stockholm</timezone> </clock> <keyboard> <keymap>swedish</keymap> </keyboard> <language>en_US</language> <mode> <confirm config:type="boolean">true</confirm> <forceboot config:type="boolean">false</forceboot> <reboot config:type="boolean">false</reboot> </mode> <mouse> <id>probe</id> </mouse> </general> <bootloader> <activate config:type="boolean">true</activate> <loader_device>/dev/md0</loader_device> <loader_type>grub</loader_type> </bootloader> <partitioning config:type="list"> <drive> <device>/dev/hda</device> <initialize config:type="boolean">true</initialize> <partitions config:type="list"> <partition> <create config:type="boolean">true</create> <format config:type="boolean">false</format> <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> <raid_type>raid</raid_type> <size>1GB</size> </partition> <partition> <create config:type="boolean">true</create> <format config:type="boolean">false</format> <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> <raid_type>raid</raid_type> <size>1GB</size> </partition> <partition> <create config:type="boolean">true</create> <format config:type="boolean">false</format> <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> <raid_type>raid</raid_type> <size>max</size> </partition> </partitions> <use>all</use> </drive> <drive> <device>/dev/hdc</device> <initialize config:type="boolean">true</initialize> <partitions config:type="list"> <partition> <create config:type="boolean">true</create> <format config:type="boolean">false</format> <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> <raid_type>raid</raid_type> <size>1GB</size> </partition> <partition> <create config:type="boolean">true</create> <format config:type="boolean">false</format> <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> <raid_type>raid</raid_type> <size>1GB</size> </partition> <partition> <create config:type="boolean">true</create> <format config:type="boolean">false</format> <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> <raid_type>raid</raid_type> <size>max</size> </partition> </partitions> <use>all</use> </drive> <drive> <device>/dev/md</device> <initialize config:type="boolean">true</initialize> <partitions config:type="list"> <partition> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <mount>/</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">0</partition_nr> </partition> <partition> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <mount>swap</mount> <partition_id config:type="integer">130</partition_id> <partition_nr config:type="integer">1</partition_nr> </partition> <partition> <format config:type="boolean">false</format> <partition_id config:type="integer">142</partition_id> <partition_nr config:type="integer">2</partition_nr> <lvm_group>sys</lvm_group> </partition> </partitions> <use>all</use> </drive> <drive> <device>/dev/sys</device> <initialize config:type="boolean">true</initialize> <is_lvm_vg config:type="boolean">true</is_lvm_vg> <partitions config:type="list"> <partition> <partition_id config:type="integer">142</partition_id> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <lv_name>usr</lv_name> <mount>/usr</mount> <size>8GB</size> </partition> <partition> <partition_id config:type="integer">142</partition_id> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <lv_name>opt</lv_name> <mount>/opt</mount> <size>5GB</size> </partition> <partition> <partition_id config:type="integer">142</partition_id> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <lv_name>var</lv_name> <mount>/var</mount> <size>4GB</size> </partition> <partition> <partition_id config:type="integer">142</partition_id> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <lv_name>srv</lv_name> <mount>/srv</mount> <size>1GB</size> </partition> <partition> <partition_id config:type="integer">142</partition_id> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <lv_name>tmp</lv_name> <mount>/tmp</mount> <size>1GB</size> </partition> <partition> <partition_id config:type="integer">142</partition_id> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <lv_name>home</lv_name> <mount>/home</mount> <size>1GB</size> </partition> </partitions> <pesize>4M</pesize> <use>all</use> </drive> </partitioning> </profile>

2 2

DTD issue
by Frédéric Brin 22 Nov '05

22 Nov '05

2 1

Re: [suse-autoinstall] LDAP error during autoyast
by Nick Tzaperas 21 Nov '05

21 Nov '05

I tried that and it actually game me an extra popup =P Something about a network device needing to be configured. Howerver, after that popup, the same LDAP error message appears and I still got the exact same log entries. Thanks for your suggestion though. What I'm confused about is that the error message appears in DhcpServer.pm, yet in the logs the error message is sandwiched between 2005-09-21 16:28:44 <1> linux(2691) [YCP] clients/dns-server_auto.ycp:26 ---------------------------------------- 2005-09-21 16:28:44 <1> linux(2691) [YCP] clients/dns-server_auto.ycp:27 DnsServer auto started and 2005-09-21 16:42:33 <1> linux(2691) [YCP] clients/dns-server_auto.ycp:92 DnsServer auto finished 2005-09-21 16:42:33 <1> linux(2691) [YCP] clients/dns-server_auto.ycp:93 ---------------------------------------- So it looks like the DNS server is configured to use DHCP and DHCP is configured to use LDAP? Here's my DNS section: <dns-server> <chroot>1</chroot> <logging config:type="list"> <listentry> <key>category</key> <value>default { default_syslog; }</value> </listentry> </logging> <start_service>1</start_service> <zones config:type="list"> </zones> </dns-server> Any ideas? Thanks, Nick Lukas Ocilka wrote: > Hi, > > Adding this into your profile might help: > --- cut --- > <dhcp-server> > ... > <use_ldap>0</use_ldap> > </dhcp-server> > --- cut --- > > Lukas > > Nick Tzaperas wrote: > >> Quick FYI, I tried commenting out the whole ldap section like I said >> in a previous e-mail and it didn't work either. Same dialog box and >> log entries. Is there anything else I can try? >> >> Jiří Suchomel wrote: >> >>> Hi Nick! >>> >>> >>> I'm not sure, but from the quick look to the sources it looks like >>> that you can prevent this popup to show when you _exclude_ >>> ldap_address and base_config_dn keys from the xml file (assuming you >>> really don't want tu use LDAP at all). >>> >>> Jiri >>> >>> On Monday 14 of November 2005 16:29, Nick Tzaperas wrote: >>> >>> >>>> Greetings, >>>> >>>> I cannot seem to avoid getting an LDAP error when doing an AutoYast >>>> install. A dialog box pops up saying "Invalid LDAP configuration. >>>> Cannot >>>> use LDAP." and you have to press OK to continue. Here's the y2log >>>> snip: >>>> >>>> ... >>>> ---------------------------------------- >>>> >>>> I was looking around at some of the YaST2 modules and it seems the >>>> error >>>> is coming from the DhcpServer.pm module, is this correct? If so, this >>>> error message is produced when $ldap_config_dn is not set. >>>> $ldap_config_dn gets set by Ldap->GetMainConfigDN () which appears to >>>> return base_config_dn which seems to be grabbed from the autoyast >>>> file. >>>> Here's the relevant snippet from the autoyast xml file I'm using: >>>> >>>> <?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> >>>> <ldap> >>>> <start_ldap>false</start_ldap> >>>> <ldap_domain>dc=foo,dc=bar,dc=com</ldap_domain> >>>> <ldap_address>10.1.128.1</ldap_address> >>>> <base_config_dn>cn=test,ou=test,dc=test,dc=com</base_config_dn> >>>> </ldap> >>>> >>>> So, it appears I have base_config_dn set yet it's still not >>>> grabbing it. >>>> Any ideas? I'm not trying to use LDAP at all. I'm just trying to >>>> get it >>>> to where we don't have to intervene. Our entire build process is >>>> pretty >>>> much automated except for this LDAP error. Let me know if you need >>>> more >>>> info. >>>> >>>> Thanks, >>> >

2 1

suse 9 network failing on boot
by Kevin McGarry 16 Nov '05

16 Nov '05

hi, I have installed Suse 9.0 on a Dell GX520. The installer picked up my onboard NIC (Broadcom NetXTreme 57xx Gigabit Controller) and I can see it and check the values in the YaST control centre. The problem is I can´t connect to the internet. I can ping 127.0.0.1<http://127.0.0.1/>, but no other machines. I get "network is unreachable" errors. I get the same message if I use DHCP or static IP address. I turned on the debug value in the network/config file and it gave me some extra debug info on boot up. The following is a copy (typed) of the boot.msg eth0 ifup DEBUG eth0 -o onboot rc ifup HWDESC=eth0 CONFIG=eth0 INTERFACE=nointerface ifup could not get a valid interface name -> skipped (returned 7) failed To make matters worse, I´m a newbie. Any ideas?

2 2

RE: [suse-autoinstall] LDAP error during autoyast
by Marlier, Ian 16 Nov '05

16 Nov '05

> -----Original Message----- > From: Nick Tzaperas [mailto:njt@thecatalis.com] > Sent: Tuesday, November 15, 2005 4:44 PM > To: Jiří Suchomel > Cc: suse-autoinstall(a)suse.com; locilka(a)suse.cz > Subject: Re: [suse-autoinstall] LDAP error during autoyast > > Quick FYI, I tried commenting out the whole ldap section like I said in > a previous e-mail and it didn't work either. Same dialog box and log > entries. Is there anything else I can try? If you're not using LDAP at all, you need to take out every reference to LDAP everywhere, throughout the control file, if you don't want that popup. Make sure that the <ldap> section is gone, along with pam_ldap and nss_ldap from the packages section. I'll agree, happily, that this shouldn't be the case, but my experience shows that it is. Not sure if it's been fixed in builds beyond the one included in Pro 9.3. On the other hand, if you _do_ have an LDAP server available and want it to work, then I think you may be short a couple of elements in the config section. Your LDAP section doesn't have nearly as many elements as mine, and I do remember getting errors if I didn't have _all_ of these defined -- or at least present. My config is for SuSE Pro 9.3, though, which may have some effect on your results. In any case, my ldap config section looks like this (and works just fine and dandy): <ldap> <base_config_dn>ou=ldapconfig,DC=sub,dc=domain,dc=com</base_config_dn> <bind_dn></bind_dn> <create_ldap config:type="boolean">false</create_ldap> <file_server config:type="boolean">false</file_server> <ldap_domain>DC=sub,dc=domain,dc=com</ldap_domain> <ldap_server>192.168.X.YYY, 192.168.X.yyy</ldap_server> <ldap_tls config:type="boolean">false</ldap_tls> <ldap_v2 config:type="boolean">false</ldap_v2> <member_attribute>member</member_attribute> <nss_base_group></nss_base_group> <nss_base_passwd></nss_base_passwd> <nss_base_shadow></nss_base_shadow> <pam_password></pam_password> <start_autofs config:type="boolean">false</start_autofs> <start_ldap config:type="boolean">true</start_ldap> </ldap> Again, YMMV... - Ian

4 5

Fwd: Re: [suse-autoinstall] LDAP error during autoyast
by Jiří Suchomel 16 Nov '05

16 Nov '05

I'm not sure if this mail got it to the list, so I'm forwarding it. It's from Lukas Ocilka, yast2-dhcp-server maintainer. Jiri ---------- Forwarded Message ---------- Subject: Re: [suse-autoinstall] LDAP error during autoyast Date: Wednesday 16 of November 2005 08:58 From: Lukas Ocilka <lukas.ocilka(a)suse.cz> To: Nick Tzaperas <njt(a)thecatalis.com> Cc: Jiří Suchomel <jsuchome(a)suse.cz>, suse-autoinstall(a)suse.com, locilka(a)suse.cz Hi, Adding this into your profile might help: --- cut --- <dhcp-server> ... <use_ldap>0</use_ldap> </dhcp-server> --- cut --- Lukas -- Jiri Suchomel SuSE CR, s.r.o. e-mail: jsuchome(a)suse.cz Drahobejlova 27 tel:+420-2-96542385 190 00 Praha 9, Czech Republic http://www.suse.cz

1 0

LDAP error during autoyast
by Nick Tzaperas 15 Nov '05

15 Nov '05

Greetings, I cannot seem to avoid getting an LDAP error when doing an AutoYast install. A dialog box pops up saying "Invalid LDAP configuration. Cannot use LDAP." and you have to press OK to continue. Here's the y2log snip: 2005-09-21 16:28:44 <1> linux(2691) [YCP] clients/dns-server_auto.ycp:26 ---------------------------------------- 2005-09-21 16:28:44 <1> linux(2691) [YCP] clients/dns-server_auto.ycp:27 DnsServer auto started 2005-09-21 16:28:44 <1> linux(2691) [wfm] Y2WFMComponent.cc(import):579 Y2WFMComponent::import (Mode) 2005-09-21 16:28:44 <1> linux(2691) [wfm] Y2WFMComponent.cc(import):579 Y2WFMComponent::import (Mode) 2005-09-21 16:28:44 <1> linux(2691) [-e] Initializing LDAP support 2005-09-21 16:28:44 <1> linux(2691) [wfm] Y2WFMComponent.cc(import):579 Y2WFMComponent::import (Ldap) 2005-09-21 16:28:44 <3> linux(2691) [YCP] Service.ycp:80 Service ypbind does not exist. 2005-09-21 16:28:44 <3> linux(2691) [YCP] Service.ycp:80 Service autofs does not exist. 2005-09-21 16:28:44 <1> linux(2691) [wfm] Y2WFMComponent.cc(import):579 Y2WFMComponent::import (Ldap) 2005-09-21 16:28:44 <1> linux(2691) [wfm] Y2WFMComponent.cc(import):579 Y2WFMComponent::import (Ldap) 2005-09-21 16:28:44 <1> linux(2691) [-e] Main configuration DN: 2005-09-21 16:28:44 <1> linux(2691) [-e] Main config DN not found 2005-09-21 16:28:44 <1> linux(2691) [wfm] Y2WFMComponent.cc(import):579 Y2WFMComponent::import (Report) 2005-09-21 16:42:33 <1> linux(2691) [YCP] clients/dns-server_auto.ycp:92 DnsServer auto finished 2005-09-21 16:42:33 <1> linux(2691) [YCP] clients/dns-server_auto.ycp:93 ---------------------------------------- I was looking around at some of the YaST2 modules and it seems the error is coming from the DhcpServer.pm module, is this correct? If so, this error message is produced when $ldap_config_dn is not set. $ldap_config_dn gets set by Ldap->GetMainConfigDN () which appears to return base_config_dn which seems to be grabbed from the autoyast file. Here's the relevant snippet from the autoyast xml file I'm using: <?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> <ldap> <start_ldap>false</start_ldap> <ldap_domain>dc=foo,dc=bar,dc=com</ldap_domain> <ldap_address>10.1.128.1</ldap_address> <base_config_dn>cn=test,ou=test,dc=test,dc=com</base_config_dn> </ldap> So, it appears I have base_config_dn set yet it's still not grabbing it. Any ideas? I'm not trying to use LDAP at all. I'm just trying to get it to where we don't have to intervene. Our entire build process is pretty much automated except for this LDAP error. Let me know if you need more info. Thanks, Nick

2 3

RE: [suse-autoinstall] Autoyast SLES9 with network and root passw ord at prompt
by Gunreben, Peter (Peter) 15 Nov '05

15 Nov '05

Jean-Paul, > I use autoyast procedure > [...] > my goal is to include the configuration of ethernet interfaces and root > password during the installation process... What's the code > to include in my autoinst.xml file for enabling these purposes please ? I'd prefer "yast2 autoyast" to setup the XML-File, but however this would be an example for a static configuration: <networking> <dns> <dhcp_hostname config:type="boolean">false</dhcp_hostname> <dhcp_resolv config:type="boolean">false</dhcp_resolv> <domain>YOUR_DOMAIN_NAME</domain> <hostname>YOUR_HOST_NAME</hostname> <nameservers config:type="list"> <nameserver>YOUR_NAMESERVER_1</nameserver> <nameserver>YOUR_NAMESERVER_2</nameserver> </nameservers> <searchlist config:type="list"> <search>YOUR_DNS_SEARCH_PREFIX</search> </searchlist> </dns> <interfaces config:type="list"> <interface> <bootproto>static</bootproto> <broadcast>YOUR_BROADCAST_ADDRESS</broadcast> <device>eth0</device> <ipaddr>YOUR_IP_ADDRESS</ipaddr> <name>Ethernet Network Card</name> <netmask>YOUR_NETMASK</netmask> <network>YOUR_NETWORK_IP_ADDRESS</network> <startmode>auto</startmode> <usercontrol>no</usercontrol> </interface> </interfaces> <modules config:type="list"> <module_entry> <device>static-0</device> <module>YOUR_ETH0_KERNEL_MODULE</module> <options>YOUR_OPTIONS_FOR_THE_ETH0_KERNEL_MODULE</options> </module_entry> </modules> <routing> <ip_forward config:type="boolean">false</ip_forward> <routes config:type="list"> <route> <destination>default</destination> <device>-</device> <gateway>YOUR_GATEWAY</gateway> <netmask>-</netmask> </route> </routes> </routing> </networking> ======= <users config:type="list"> <user> <encrypted config:type="boolean">true</encrypted> <fullname>root</fullname> <gid>0</gid> <home>/root</home> <password_settings> <max>10000</max> <min>0</min> </password_settings> <shell>/bin/bash</shell> <uid>0</uid> <user_password>ENCRYPTED_PASSPHRASE_COMES_HERE</user_password> <username>root</username> </user> </users> ===== Regards, Peter.

3 2

Using blowfish encryption in autoyast results in corrupted passwords for logins...
by Jeff Christensen 14 Nov '05

14 Nov '05

Hi, I searched this list and hadn't really seen this addressed already. I am having problems with using blowfish encryption with autoyast on sles9 sp2. When I choose blowfish for the encryption as opposed to md5, my users are not able to login with a default password. If however I do choose md5 encryption, they can login just fine. I wanted to see if anyone had run across this before or if I am doing something wrong. Thank you, Jeff Christensen

1 0

Re: [suse-autoinstall] suse 9 network failing on boot
by Hans-Joachim Ehlers 11 Nov '05

11 Nov '05

Hi Kevin, The problem is that the driver will not be put into the /etc/sysconfig/hardware/hwcfg-bus-pci* file so the Value : MODULE will have no attribut e.a will be empty. Since i was to lazy to find a better approach ( I think the main problem is the time it takes the tg3 module to initialzie the driver ) i use the following post script in the autoyast.xml : echo "INFO: Setting missing module entry in /etc/sysconfig/hardware for broadcom network card" cd /etc/sysconfig/hardware for i in hwcfg-bus-pci* ; do perl -p -i -e s/"MODULE=''"/"MODULE='tg3'"/ $i done cd - HTH Hajo BTW: If you have an working grafic driver please let me know by P.M. Right now i use a version from http://www.fairlite.demon.co.uk/i810_drv.o ============================ 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 >>> Kevin McGarry <kev.mcgarry(a)gmail.com> 09/11/05 19:41:01 >>> hi, I have installed Suse 9.0 on a Dell GX520. The installer picked up my onboard NIC (Broadcom NetXTreme 57xx Gigabit Controller) and I can see it and check the values in the YaST control centre. The problem is I can t connect to the internet. I can ping 127.0.0.1<http://127.0.0.1/>, but no other machines. I get "network is unreachable" errors. I get the same message if I use DHCP or static IP address. I turned on the debug value in the network/config file and it gave me some extra debug info on boot up. The following is a copy (typed) of the boot.msg eth0 ifup DEBUG eth0 -o onboot rc ifup HWDESC=eth0 CONFIG=eth0 INTERFACE=nointerface ifup could not get a valid interface name -> skipped (returned 7) failed To make matters worse, I m a newbie. Any ideas?

1 0

Re: [suse-autoinstall] AutoInstall on SLES8 SP3 s390x - dasd handling in control file
by Yan Fitterer 11 Nov '05

11 Nov '05

Hi Steen Ok - bit of confusion here. I though your install was going through, but with an additional partition being created beyond dsadx1. The devices must be formated and partitioned, as YaST isn't capable (in SLES8) of doing it automatically. 1) I believe that you can do a z/VM format of the DASD devices as ECKD/Linux Disk Layout. In which case you can't have more than one partition, but apparently you can then use it from YaST without partitioning. 2) Alternatively, you should look into the autoyast pre-install script. That's the place you can do things like load the dasd module manually and do the required format and partitioning. The dasd tools should be on the initrd! See the README file on top level of first install media for SLES8. Best, Yan >>> On 10/11/2005 at 11:36:03, in message <200511101236.03777.sjo(a)oncable.dk>, Steen Bank Johnsen <sjo(a)oncable.dk> wrote: > Hi Yan > > It never comes that far. During prepare of harddisks Yast annonces that it > couldn't format /dev/dasda2. Then I abort the installation. Should I always > make a dasdfmt and fdasd -a on my dasd after loading the dasd module ???? If > that the answer I still haven't unattended installation. > > :-) Steen > > Torsdag 10 november 2005 12:08 skrev du: >> Hi Steen >> >> > Have tried the <initialize> didn't change anything. For the size >> >> statement >> >> > didn't you mean max and not all? >> >> I did. Sorry about that! Does it change anything? >> >> > The output from fdisk -l >> >> I meant after autoyast has completed partitioning. I just wanted to see >> what the (wrong) result is. >> >> Yan

3 4

Re: [suse-autoinstall] Network installation - kernel command line limitation
by Alexander Dubinin 11 Nov '05

11 Nov '05

Hi Marion, As I've read in documentation, linuxrc just parsing autoyast.xml content and should get these lines without problems. This doesn't happens - but it can mount NFS and get file, and it can get content from HTTP, FTP, whatever. So, seems like this is one of few things in SLES9, which are "documented" but not exists in reality. IMHO it should be raised as request to Novell... Regards, Alexander Dubinin. 2005/10/18, Michael Marion <mmarion(a)qualcomm.com>: > On 18 Oct, Alexander Dubinin wrote: > > > Example 7.2. Linxurc options in the control file > > .... > > <install> > > .... > > <init> > > <info_file> > > <![CDATA[ > > ## > > Don't remove the following line: > > # start_linuxrc_conf > > # > > install: nfs://192.168.1.1/CDs/full-i386 > > textmode: 1 > > autoyast: file:///info > > # end_linuxrc_conf > > # Do not remove the above comment > > # > > ]]> > > </info_file> > > </init> > > ...... > > </install> > > .... > > Someone can correct me if they've seen differently, but my experience in > actually trying this is that it doesn't work. Why? Because the autoyast > system has to mount the install path and load the secondary bits before > autoyast itself starts and it ever even tries to load the xml profile file. > It does seem to work if the xml file is on the boot media itself, but > not if your autoyast and install variables point to NFS locations. > > > Recreation of initrd is not suitable - as I need to install SLES9 in > > many different locations (As I understand it's "Enterprize" Linux, > > isn't it? ;) and from different NFS servers. > > Even in one office, there are few LABs, located behind firewall, where > > addresses of NFS server are different. > > Same here, which is why we created different info files per location and pass > the info file argument to the kernel. Also use a custom rule with the new > rules system that was added, and have different xml files based on site with > the site specific installation bits. > > -- > Mike Marion-Unix SysAdmin/Staff Engineer-http://www.qualcomm.com > Homer Simpson: "To alcohol! The cause of, and solution to, all of life's > problems." -- Simpsons > > -- Regards, Alexander Dubinin

3 3

Re: [suse-autoinstall] AutoInstall on SLES8 SP3 s390x - dasd handling in control file
by Yan Fitterer 10 Nov '05

10 Nov '05

Hi > Q1: > > I have tried numerous setups for trying to get the right setup in the > control > file for the following setup. Currently trying on SLES8 s390x SP3. > > > /dev/dasda1 mountet on / with reiserfs. It should use all diskspace > available. > > /dev/dasdb1 mountet on /boot with ext2. It should use all diskspace. Have you tried <size>all</size> ? > For some reason it always creates a second partition on each drive. Is it > possible to solve this this? For each <drive>, you could try adding: <initialize config:type="boolean">true</initialize> Not sure if that was available on SLES8, only tried on SLES9 to ensure autoyast consideres the disk to be empty. If still no joy, could you send the output of fdisk -l for the various drives? > > Q2: > > Is it possible to run yast unattended during installation? I currently > always > accepts a few times. Example, after load off dasd module? I am using the SSH On SLES9 the following entities will enable auto-timeout on the various prompts that come up: <report> <errors> <log config:type="boolean">true</log> <show config:type="boolean">true</show> <timeout config:type="integer">5</timeout> </errors> <messages> <log config:type="boolean">true</log> <show config:type="boolean">true</show> <timeout config:type="integer">5</timeout> </messages> <warnings> <log config:type="boolean">true</log> <show config:type="boolean">true</show> <timeout config:type="integer">5</timeout> </warnings> <yesno_messages> <log config:type="boolean">true</log> <show config:type="boolean">true</show> <timeout config:type="integer">5</timeout> </yesno_messages> </report> Yan

1 0

AutoInstall on SLES8 SP3 s390x - dasd handling in control file
by Steen Bank Johnsen 10 Nov '05

10 Nov '05

Hi out there Q1: I have tried numerous setups for trying to get the right setup in the control file for the following setup. Currently trying on SLES8 s390x SP3. /dev/dasda1 mountet on / with reiserfs. It should use all diskspace available. /dev/dasdb1 mountet on /boot with ext2. It should use all diskspace. /dev/dasdc1 swap For some reason it always creates a second partition on each drive. Is it possible to solve this this? The following section from the control file is just the latest example of what I have tried. <partitioning config:type="list"> <drive> <device>/dev/dasdc</device> <partitions config:type="list"> <partition> <mount>swap</mount> <partition_nr config:type="integer">1</partition_nr> <create config:type="boolean">false</create> </partition> </partitions> </drive> <drive> <device>/dev/dasdb</device> <partitions config:type="list"> <partition> <partition_nr config:type="integer">1</partition_nr> <filesystem config:type="symbol">ext2</filesystem> <mount>/boot</mount> <format config:type="boolean">true</format> <size>34mb</size> </partition> </partitions> </drive> <drive> <device>/dev/dasda</device> <partitions config:type="list"> <partition> <partition_nr config:type="integer">1</partition_nr> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <mount>/</mount> <size>6800mb</size> </partition> </partitions> </drive> </partitioning> Q2: Is it possible to run yast unattended during installation? I currently always accepts a few times. Example, after load off dasd module? I am using the SSH network installation method. The part of installation in z/VM now works unattended, so it would be nice that the part in SSH install also was unattended. Regards Steen Bank Johnsen JN DATA A/S

1 0

RE: [suse-autoinstall] SOLVED: AutoYaST SP2 weirdnes...
by Sanchez, Francisco J. 09 Nov '05

09 Nov '05

Thank you! That was the problem exactly... IIS was interpreting packages.cs as a C# file because of the .NET framework integration. We disabled this, and the install works fine now. I had only been looking at packages and packages.en because I thought they were the only ones being used in my installation, since it is all english. I'm still pretty new to SuSE, so I'm still learning what all the installtion files do and the ins and outs of the installation tree. Anyway, thanks again. Cordialmente, --fjs-- > -----Original Message----- > From: Meyers, Holger [mailto:Holger.Meyers@softservice.de] > Sent: Tuesday, 08 November, 2005 01:33 > To: Sanchez, Francisco J. > Cc: suse-autoinstall(a)suse.com > Subject: RE: [suse-autoinstall] AutoYaST SP2 weirdnes... > > Hello, > > I can not remember what I did excactly, but IIS requires > modification of the servers Global MIME Types and (if ASP.NET > is installed) the scripting support of the virtual server. > Check the IIS log to locate the file which is not transfered > (? packages.cs ?) and remove its extension from the IIS MIME > type to stop IIS interpreting this file. > > Mit freundlichen Grüßen / kind regards > SoftService GmbH > > Holger Meyers > Consulting > > Tel 0211 977 09 69 > Fax 0211 977 09 27 > Mobil 0172 2740969 > http://www.softservice.de > > > ________________________________ > > From: Sanchez, Francisco J. [mailto:Francisco.Sanchez@unisys.com] > Sent: Tue 08.11.2005 02:29 > To: suse-autoinstall(a)suse.com > Cc: suse-sles-e(a)suse.com > Subject: RE: [suse-autoinstall] AutoYaST SP2 weirdnes... > > > > ... some more troubleshooting: > > i put my repository into a tarball, managed to get the tar.gz > over to the w2k serve, and verified that the contents were > the same as those on my linux machine, bit-for-bit, using > MD5sum.exe. i unzipped/untarred the file, and put the > contents in <install_dir>, but still was not able to use this > repository. it failed at the same place as before, but with > a slightly more detailed error message: > > "Cannot read media description for /. Packages from this > media cannot be installed." > > and > > "Cannot read media description for /yast/core9. Packages > from this media cannot be installed." > > so, i ran create_package_descr -x ./setup/descr/EXTRA_PROV on > my linux machine, within the windows share where i untarred > the installation tree. it only found 226 packages (as > opposed to 1770 when used within the "golden" repository), > and the installation aborted the same as before. > > i don't have time to troubleshoot this immediately, but am > posting just in case someone has an idea before i get back to > the office on wednesday. Thanks for any help!!! > > --fjs-- > > > > > -----Original Message----- > > From: Sanchez, Francisco J. [mailto:Francisco.Sanchez@unisys.com] > > Sent: Monday, 07 November, 2005 16:25 > > To: suse-autoinstall(a)suse.com > > Cc: suse-sles-e(a)suse.com > > Subject: [suse-autoinstall] AutoYaST SP2 weirdnes... > > > > Hello, > > I have just created a SLES9-SP2 installation source > manually for use > > as an http repository for automated installations. > > In order to create the installation repository, i created an > > installation dir (/install), mounted the necessary ISOs (sles9cd1, > > core9cd{1,2}, and sles9sp2cd{1,2}), and then used > > > > rsync -auvvP /path/to/iso /install > > > > to get all the necessary files into the repository. I then ran > > > > create_package_descr -x ./setup/descr/EXTRA_PROV > > > > from within the /install/suse directory in order to update > the pacakge > > descritptions. Finally, i pointed to this directory within > Yast, and > > used the "Autoinstallation" module to create an autoinst.xml file > > within /install/profiles/. > > > > to test the installation, i made the repository available > via apache, > > booted with a custom SP2-CD1 cd, and pointed the network > installation > > (http) to my repository. i used the following linuxrc.config: > > > > KernelPCMCIA: 1 > > UseUSBSCSI: 1 > > Product: SUSE LINUX Enterprise Server 9 SP2 > > UpdateDir: /linux/suse/i386-sles9 > > MemLoadImage: 163840 > > MinMemory: 256 > > MemYaST: 64000 > > MemYaSTText: 64000 > > Language: english > > Display: Color > > Keytable: us > > Install: http://<ip_addr>/install/ > > DHCP: 1 > > HostIP: > > Netmask: 255.255.255.0 > > Server: <ip_addr> > > Serverdir: /install/ > > Netdevice: eth0 > > insmod: 3c59x > > insmod: mii > > insmod: e100 > > insmod: e1000 > > Textmode: 1 > > AutoYast: http://<ip_addr>/install/ > > > > the installation worked just as i had hoped. > > > > Now, the problem begins... > > I need to have this repository available via IIS from a > windows 2000 > > server machine (not my choice, i am controlled by the > > paycheck-makers). > > So, i mounted the windows directory that is going to host the > > repository with samba, and then used rsync -auvvP to copy the > > repository to this windows share. > > > > when i boot with the same cd (with a modified > linuxrc.config to point > > the network installation to the windows web server), my > installation > > fails. The installation begins fine, finds the control.xml and my > > autoinst.xml, but when it gets to the "Configure Software > selections" > > it fails with the following error message > > > > "Could not set base selection: default" > > > > followed by > > > > "Error while configuring software selections. Try again." > > > > fwiw, i also reran YaST and pointed the installation to the mounted > > windows share, recreated the autoinst.xml, and saved it within > > <windows_share_install>/profiles/, but that did not work either. i > > also tried to using the option from with YaST to see the > repository as > > a windows share, but that also fails. > > > > I have searched high and low regarding these error > messages, but have > > found nothing. Does anyone have any ideas that could help me out? > > THANK YOU!!! > > > > --fjs-- > > > > > > -- > > Francisco J. Sanchez > > UNISYS // ESP: Preload Team > > > > -- > > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > > For additional commands, e-mail: suse-autoinstall-help(a)suse.com > > > > > > -- > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > For additional commands, e-mail: suse-autoinstall-help(a)suse.com > > > >

1 0

Second repository during autoinstall?
by T. Ribbrock 09 Nov '05

09 Nov '05

Hi all, for the autoinstallation of our workstations, I would like to add a second repository to the installation sources. I intend to mirror the complete Packman repo locally, then add some stuff from that repository during the install. I've read through the AutoYAST doc and through quite a few postings on this list, but that left me utterly confused... :-( Did I understand correctly that it is not possible to add a second repository as an install source? Chapter 4.5.3 and the postings I found all talk about modifying the one install repository which is not what I want - I'd much prefer to keep the original SuSE 10.0 install tree untouched, as it's easier to track what has been added. Someone (Michael Marion?) hinted at having a separate repository, but unfortunately not in a way that I was able to make something out of it... :-} Hence: How do I go about this? The Packman repo is a complete repo and the local mirror is already usable by YaST2 as an install source (at least if I mount the directory from the server to the workstation and use "file://" - "nfs://" doesn't work for some strange reason - but that's another problem) - all I want to do is add it as an additional source so I can add the additional packages I want to autoinstall.xml and have them installed as well. Any hints appreciated! Cheerio, Thomas

2 14

AutoYast script location
by Bernd Nies 09 Nov '05

09 Nov '05

Hi, I'm preparing an installation DVD for SLES9 SP and want to use AutoYast with XML control file and customized shell scripts. Because I don't want copy the shell code into every XML control file I want it separately on the DVD. Is the following possible? <post-scripts config:type="list"> <script> <filename>post-install.sh</filename> <location>dvd:///autoyast/post-install.sh</location> </script> </post-scripts> Or does one need to write a wrapper script that mounts the DVD, copies and executes the script manually? How can this be done during chroot installation phase when the name of the CD/DVD device file is not known and the /dev/cdrom link does not yet exist? Regards, Bernd

2 2

Re: [suse-autoinstall] retrieving xml installation profiles with http
by Thomas Mieslinger 08 Nov '05

08 Nov '05

Sorry. Forget to cc the list. Thomas Mieslinger/de02/gls schrieb am 08.11.2005 15:12:35: > SLES 8 SP3 > > Can I use a newer linuxrc to install SLES 8? > > regards Thomas > -- > GLS IT Services > Thomas Mieslinger > GLS Germany Str. 1-7 fon: +49 6677 17 463 > 36286 Neuenstein fax: +49 6677 17 111 > Germany eMail: thomas.mieslinger(a)gls-itservices.com > > Uwe Gansert <ug(a)suse.de> schrieb am 08.11.2005 14:53:31: > > > On Tuesday 08 November 2005 11:34, Thomas Mieslinger wrote: > > > > > my pxelinux.cfg/xyz file contains > > > > > > autoyast=http://adminserv/categories/windows/ui_client/index.php?action=a > > >utoyast_start&client=bla > > > > > > entering this uri into a webbrowser gives back the correct xml file. When > > > autoyast does this it only fetches > > > "http://adminserv/categories/windows/ui_client/index.php" and not the > > > full uri. How can I escape '?' and '&' so that autoyast fetches the full > > > uri? > > > > it works fine here on a 10.0 > > Which SUSE version do you use? > > > > > > -- > > 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 > >

3 6

retrieving xml installation profiles with http
by Thomas Mieslinger 08 Nov '05

08 Nov '05

Hello *, my pxelinux.cfg/xyz file contains autoyast=http://adminserv/categories/windows/ui_client/index.php?action=autoyast_start&client=bla entering this uri into a webbrowser gives back the correct xml file. When autoyast does this it only fetches "http://adminserv/categories/windows/ui_client/index.php" and not the full uri. How can I escape '?' and '&' so that autoyast fetches the full uri? regards Thomas -- GLS IT Services Thomas Mieslinger GLS Germany Str. 1-7 fon: +49 6677 17 463 36286 Neuenstein fax: +49 6677 17 111 Germany eMail: thomas.mieslinger(a)gls-itservices.com

3 3

RE: [suse-autoinstall] AutoYaST SP2 weirdnes...
by Meyers, Holger 08 Nov '05

08 Nov '05

Hello, I can not remember what I did excactly, but IIS requires modification of the servers Global MIME Types and (if ASP.NET is installed) the scripting support of the virtual server. Check the IIS log to locate the file which is not transfered (? packages.cs ?) and remove its extension from the IIS MIME type to stop IIS interpreting this file. Mit freundlichen Grüßen / kind regards SoftService GmbH Holger Meyers Consulting Tel 0211 977 09 69 Fax 0211 977 09 27 Mobil 0172 2740969 http://www.softservice.de ________________________________ From: Sanchez, Francisco J. [mailto:Francisco.Sanchez@unisys.com] Sent: Tue 08.11.2005 02:29 To: suse-autoinstall(a)suse.com Cc: suse-sles-e(a)suse.com Subject: RE: [suse-autoinstall] AutoYaST SP2 weirdnes... ... some more troubleshooting: i put my repository into a tarball, managed to get the tar.gz over to the w2k serve, and verified that the contents were the same as those on my linux machine, bit-for-bit, using MD5sum.exe. i unzipped/untarred the file, and put the contents in <install_dir>, but still was not able to use this repository. it failed at the same place as before, but with a slightly more detailed error message: "Cannot read media description for /. Packages from this media cannot be installed." and "Cannot read media description for /yast/core9. Packages from this media cannot be installed." so, i ran create_package_descr -x ./setup/descr/EXTRA_PROV on my linux machine, within the windows share where i untarred the installation tree. it only found 226 packages (as opposed to 1770 when used within the "golden" repository), and the installation aborted the same as before. i don't have time to troubleshoot this immediately, but am posting just in case someone has an idea before i get back to the office on wednesday. Thanks for any help!!! --fjs-- > -----Original Message----- > From: Sanchez, Francisco J. [mailto:Francisco.Sanchez@unisys.com] > Sent: Monday, 07 November, 2005 16:25 > To: suse-autoinstall(a)suse.com > Cc: suse-sles-e(a)suse.com > Subject: [suse-autoinstall] AutoYaST SP2 weirdnes... > > Hello, > I have just created a SLES9-SP2 installation source manually > for use as an http repository for automated installations. > In order to create the installation repository, i created an > installation dir (/install), mounted the necessary ISOs > (sles9cd1, core9cd{1,2}, and sles9sp2cd{1,2}), and then used > > rsync -auvvP /path/to/iso /install > > to get all the necessary files into the repository. I then ran > > create_package_descr -x ./setup/descr/EXTRA_PROV > > from within the /install/suse directory in order to update > the pacakge descritptions. Finally, i pointed to this > directory within Yast, and used the "Autoinstallation" module > to create an autoinst.xml file within /install/profiles/. > > to test the installation, i made the repository available via > apache, booted with a custom SP2-CD1 cd, and pointed the > network installation > (http) to my repository. i used the following linuxrc.config: > > KernelPCMCIA: 1 > UseUSBSCSI: 1 > Product: SUSE LINUX Enterprise Server 9 SP2 > UpdateDir: /linux/suse/i386-sles9 > MemLoadImage: 163840 > MinMemory: 256 > MemYaST: 64000 > MemYaSTText: 64000 > Language: english > Display: Color > Keytable: us > Install: http://<ip_addr>/install/ > DHCP: 1 > HostIP: > Netmask: 255.255.255.0 > Server: <ip_addr> > Serverdir: /install/ > Netdevice: eth0 > insmod: 3c59x > insmod: mii > insmod: e100 > insmod: e1000 > Textmode: 1 > AutoYast: http://<ip_addr>/install/ > > the installation worked just as i had hoped. > > Now, the problem begins... > I need to have this repository available via IIS from a > windows 2000 server machine (not my choice, i am controlled > by the paycheck-makers). > So, i mounted the windows directory that is going to host the > repository with samba, and then used rsync -auvvP to copy the > repository to this windows share. > > when i boot with the same cd (with a modified linuxrc.config > to point the network installation to the windows web server), > my installation fails. The installation begins fine, finds > the control.xml and my autoinst.xml, but when it gets to the > "Configure Software selections" it fails with the following > error message > > "Could not set base selection: default" > > followed by > > "Error while configuring software selections. Try again." > > fwiw, i also reran YaST and pointed the installation to the > mounted windows share, recreated the autoinst.xml, and saved > it within <windows_share_install>/profiles/, but that did not > work either. i also tried to using the option from with YaST > to see the repository as a windows share, but that also fails. > > I have searched high and low regarding these error messages, > but have found nothing. Does anyone have any ideas that > could help me out? > THANK YOU!!! > > --fjs-- > > > -- > Francisco J. Sanchez > UNISYS // ESP: Preload Team > > -- > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > For additional commands, e-mail: suse-autoinstall-help(a)suse.com > > -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

RE: [suse-autoinstall] AutoYaST SP2 weirdnes...
by Sanchez, Francisco J. 08 Nov '05

08 Nov '05

... some more troubleshooting: i put my repository into a tarball, managed to get the tar.gz over to the w2k serve, and verified that the contents were the same as those on my linux machine, bit-for-bit, using MD5sum.exe. i unzipped/untarred the file, and put the contents in <install_dir>, but still was not able to use this repository. it failed at the same place as before, but with a slightly more detailed error message: "Cannot read media description for /. Packages from this media cannot be installed." and "Cannot read media description for /yast/core9. Packages from this media cannot be installed." so, i ran create_package_descr -x ./setup/descr/EXTRA_PROV on my linux machine, within the windows share where i untarred the installation tree. it only found 226 packages (as opposed to 1770 when used within the "golden" repository), and the installation aborted the same as before. i don't have time to troubleshoot this immediately, but am posting just in case someone has an idea before i get back to the office on wednesday. Thanks for any help!!! --fjs-- > -----Original Message----- > From: Sanchez, Francisco J. [mailto:Francisco.Sanchez@unisys.com] > Sent: Monday, 07 November, 2005 16:25 > To: suse-autoinstall(a)suse.com > Cc: suse-sles-e(a)suse.com > Subject: [suse-autoinstall] AutoYaST SP2 weirdnes... > > Hello, > I have just created a SLES9-SP2 installation source manually > for use as an http repository for automated installations. > In order to create the installation repository, i created an > installation dir (/install), mounted the necessary ISOs > (sles9cd1, core9cd{1,2}, and sles9sp2cd{1,2}), and then used > > rsync -auvvP /path/to/iso /install > > to get all the necessary files into the repository. I then ran > > create_package_descr -x ./setup/descr/EXTRA_PROV > > from within the /install/suse directory in order to update > the pacakge descritptions. Finally, i pointed to this > directory within Yast, and used the "Autoinstallation" module > to create an autoinst.xml file within /install/profiles/. > > to test the installation, i made the repository available via > apache, booted with a custom SP2-CD1 cd, and pointed the > network installation > (http) to my repository. i used the following linuxrc.config: > > KernelPCMCIA: 1 > UseUSBSCSI: 1 > Product: SUSE LINUX Enterprise Server 9 SP2 > UpdateDir: /linux/suse/i386-sles9 > MemLoadImage: 163840 > MinMemory: 256 > MemYaST: 64000 > MemYaSTText: 64000 > Language: english > Display: Color > Keytable: us > Install: http://<ip_addr>/install/ > DHCP: 1 > HostIP: > Netmask: 255.255.255.0 > Server: <ip_addr> > Serverdir: /install/ > Netdevice: eth0 > insmod: 3c59x > insmod: mii > insmod: e100 > insmod: e1000 > Textmode: 1 > AutoYast: http://<ip_addr>/install/ > > the installation worked just as i had hoped. > > Now, the problem begins... > I need to have this repository available via IIS from a > windows 2000 server machine (not my choice, i am controlled > by the paycheck-makers). > So, i mounted the windows directory that is going to host the > repository with samba, and then used rsync -auvvP to copy the > repository to this windows share. > > when i boot with the same cd (with a modified linuxrc.config > to point the network installation to the windows web server), > my installation fails. The installation begins fine, finds > the control.xml and my autoinst.xml, but when it gets to the > "Configure Software selections" it fails with the following > error message > > "Could not set base selection: default" > > followed by > > "Error while configuring software selections. Try again." > > fwiw, i also reran YaST and pointed the installation to the > mounted windows share, recreated the autoinst.xml, and saved > it within <windows_share_install>/profiles/, but that did not > work either. i also tried to using the option from with YaST > to see the repository as a windows share, but that also fails. > > I have searched high and low regarding these error messages, > but have found nothing. Does anyone have any ideas that > could help me out? > THANK YOU!!! > > --fjs-- > > > -- > Francisco J. Sanchez > UNISYS // ESP: Preload Team > > -- > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > For additional commands, e-mail: suse-autoinstall-help(a)suse.com > >

1 0

AutoYaST SP2 weirdnes...
by Sanchez, Francisco J. 08 Nov '05

08 Nov '05

Hello, I have just created a SLES9-SP2 installation source manually for use as an http repository for automated installations. In order to create the installation repository, i created an installation dir (/install), mounted the necessary ISOs (sles9cd1, core9cd{1,2}, and sles9sp2cd{1,2}), and then used rsync -auvvP /path/to/iso /install to get all the necessary files into the repository. I then ran create_package_descr -x ./setup/descr/EXTRA_PROV from within the /install/suse directory in order to update the pacakge descritptions. Finally, i pointed to this directory within Yast, and used the "Autoinstallation" module to create an autoinst.xml file within /install/profiles/. to test the installation, i made the repository available via apache, booted with a custom SP2-CD1 cd, and pointed the network installation (http) to my repository. i used the following linuxrc.config: KernelPCMCIA: 1 UseUSBSCSI: 1 Product: SUSE LINUX Enterprise Server 9 SP2 UpdateDir: /linux/suse/i386-sles9 MemLoadImage: 163840 MinMemory: 256 MemYaST: 64000 MemYaSTText: 64000 Language: english Display: Color Keytable: us Install: http://<ip_addr>/install/ DHCP: 1 HostIP: Netmask: 255.255.255.0 Server: <ip_addr> Serverdir: /install/ Netdevice: eth0 insmod: 3c59x insmod: mii insmod: e100 insmod: e1000 Textmode: 1 AutoYast: http://<ip_addr>/install/ the installation worked just as i had hoped. Now, the problem begins... I need to have this repository available via IIS from a windows 2000 server machine (not my choice, i am controlled by the paycheck-makers). So, i mounted the windows directory that is going to host the repository with samba, and then used rsync -auvvP to copy the repository to this windows share. when i boot with the same cd (with a modified linuxrc.config to point the network installation to the windows web server), my installation fails. The installation begins fine, finds the control.xml and my autoinst.xml, but when it gets to the "Configure Software selections" it fails with the following error message "Could not set base selection: default" followed by "Error while configuring software selections. Try again." fwiw, i also reran YaST and pointed the installation to the mounted windows share, recreated the autoinst.xml, and saved it within <windows_share_install>/profiles/, but that did not work either. i also tried to using the option from with YaST to see the repository as a windows share, but that also fails. I have searched high and low regarding these error messages, but have found nothing. Does anyone have any ideas that could help me out? THANK YOU!!! --fjs-- -- Francisco J. Sanchez UNISYS // ESP: Preload Team

1 0

Still unclear on adding additional packages with SLES9-SP2
by Michael T. Halligan 04 Nov '05

04 Nov '05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 First off, I've read through the list archives, and there are so many conflicting methods for doing this, I'm back to square one. In redhat, all I would do is symlink my packages into my main RPM directory, then run genhdlist. My understanding from Novell's very spares documentation is that I would do something similar, but it does not work, and breaks in a rather ugly way each time. My source tree looks like this : rwxr-xr-x 6 root root 456 Nov 3 17:17 . drwxr-xr-x 5 root root 152 Nov 3 16:20 .. drwxr-xr-x 7 root root 168 Nov 3 10:17 SUSE-CORE-Version-9 drwxr-xr-x 5 root root 120 Nov 3 10:42 SUSE-SLES-9-Service-Pack- Version-2 drwxr-xr-x 3 root root 72 Nov 3 10:11 SUSE-SLES-Version-9 lrwxrwxrwx 1 root root 28 Nov 3 10:58 boot -> SUSE-SLES- Version-9/CD1/boot lrwxrwxrwx 1 root root 31 Nov 3 10:58 content -> SUSE-SLES- Version-9/CD1/content lrwxrwxrwx 1 root root 35 Nov 3 11:07 control.xml -> SUSE-SLES- Version-9/CD1/control.xml lrwxrwxrwx 1 root root 51 Nov 3 11:07 driverupdate -> SUSE- SLES-9-Service-Pack-Version-2/CD1/driverupdate lrwxrwxrwx 1 root root 44 Nov 3 10:58 linux -> SUSE-SLES-9- Service-Pack-Version-2/CD1/linux lrwxrwxrwx 1 root root 31 Nov 3 11:02 media.1 -> SUSE-SLES- Version-9/CD1/media.1 - -rw-r--r-- 1 root root 5081 Nov 3 16:41 part.xml drwxr-xr-x 2 root root 104 Nov 3 10:18 yast I've tried adding packages to: SUSE-CORE-Version-9/CD1/suse/x86_64 SUSE-CORE-Version-9/CD1/suse/addons SUSE-CORE-Version-9/CD1/suse/updates SUSE-SLES-9-Service-Pack-Version-2/CD1/suse/x86_64 SUSE-SLES-9-Service-Pack-Version-2/CD1/suse/addons SUSE-SLES-9-Service-Pack-Version-2/CD1/suse/updates SUSE-SLES-Version-9/CD1/suse/x86_64 SUSE-SLES-Version-9/CD1/suse/addons SUSE-SLES-Version-9/CD1/suse/updates From the "suse" directory all of those above paths, I've tried: create_package_descr -x ./setup/descr/EXTRA_PROV -d . create_package_descr -x ./setup/descr/EXTRA_PROV -d addons create_package_descr -x ./setup/descr/EXTRA_PROV -d updates The effect is the same, either errors during the autoyast, which is unable to find the added rpms, or a newly created depdency hell where autoyast tries installing conflicting versions of packages like lvm, and becomes unusable (only fixable by rebuilding my source-tree). Does anybody have a good answer to a working way, that doesn't involve "please look back through the archives"? I'd be really grateful! -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Darwin) iD8DBQFDaxHZwjCqooJyNAMRAsw2AJ9BkXwIpNdKEKY3KrDJRrlNMZ009QCeOv3T Ma10UO+eSKx1032vvTvEXwA= =nl2K -----END PGP SIGNATURE-----

2 3

Autoyast SLES9 with network and root password at prompt
by Jean-Paul Cheney 04 Nov '05

04 Nov '05

Hello, I want to install some servers x86 with SLES9. I use autoyast procedure for auto-configuring the partionning, packages choice.. etc... but my goal is to include the configuration of ethernet interfaces and root password during the installation process... What's the code to include in my autoinst.xml file for enabling these purposes please ? Sorry for my poor english :( -- Jean-Paul Cheney

2 1

SLES9 SP2, Pentium D & yast/instorder
by kanji linux 04 Nov '05

04 Nov '05

Hi I have been trying to autoinstall SLES9 SP2 ( i have been able to install on other iem64 or amd64 motherboards) on a pentium D motherboard. After the installation, 1. when it reboots to boot from the local disk, the hard disk is not recognized as a boot device. 2. I then used SP2 CD1 to repair the installed system. The s/w detected the bootloader settings and did not find any errors. Anyway i went ahead repaired the bootloader installation and was then able to boot from hard disk during the next reboot. This happens everytime the node is autoinstalled using SLES9 SP2. Any idea what causes the bootloader not to be installed properly during autoinstall?? In yast/inorder & yast/order files, should the order of SLES9/CD1 be first followed by SLES9SP2/CD1 ? or is the order reversed? Does this order affect the installation ?? thanks kanji __________________________________ Yahoo! FareChase: Search multiple travel sites in one click. http://farechase.yahoo.com

1 0

Re: [suse-sles-e] SLES9 + SP2 on DVD
by mm＠gnulinux.de 03 Nov '05

03 Nov '05

Am Dienstag, 1. November 2005 11:57 schrieb Bernd Nies: > Hi, Hi Bernd, > > All documentations I know describe it in another way. The above will > > not allow YOU updates with autoyast2, too. > > It was so explained on Nashif's Autoyast documentation. > > http://www.suse.de/~nashif/autoinstall/ > > Now the pages have been swallowed and digested by Novell. You can still find the "original" pages here: http://forgeftp.novell.com//yast/doc/SL10.0/autoinstall/ > > >>Why doesn't Suse release SP2 as one complete SLES9+SP2 DVD? The SP2 > >>contains almost the same amount of data than the original SLES9. > > > > Which is not true, SLES9 still contains a lot of more data. Much more. > > 6 SLES9 CDs compared to 3 SP2 CDs is not a lot more. > > The install process with 9 CDs that need to be changed every few minutes > is a pain if one cannot have an install server because one has to > install it on a customer site. This is not very customer friendly. > > It would be much better if at least the SLES9 and the SP2 are each on a > DVD but we only got CDs. > > The free burn and fire version of SUSE Linux is available on DVD, why > not the SLES? Normally it should be possible to rebuild a dvd from the cds but it seems to be real hard work. You can take a look at the: http://www.opensuse.org/Making_a_DVD_from_CDs tutorial. But you will need a double layer dvd to fit. I also think that this script is unable to handle SP CDs so you have to replace all the updated packages manually. Best Regards Marcus PS: Meanwhile I prefer Slackware which comes on 4 CDs where only one CD is really necessary :)

1 0

Re: [suse-autoinstall] Best practices for adding external package sources?
by Michael T. Halligan 03 Nov '05

03 Nov '05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Michael, Is there a good searchable site for the archives? Right now, the best I've found is http://lists.suse.com/archive/suse-autoinstall/ and not very useful... Perhaps a FAQ on this topic would be appropriate at this point, if anybody @ Novell is reading this.. Since it comes up so often. Mihcael On Oct 18, 2005, at 4:03 PM, Michael Marion wrote: > On 18 Oct, Michael T. Halligan wrote: > > >> I have two dilemmas with AutoYast I'm sure somebody here will be able >> to help me solve. They're >> really the same issue, and that is adding external rpms. >> > > Both of what you want to do can be easily solved using a custom > path with > custom RPMS. > > Look in the archives for the subject: > > Additional Package & Silent install > > One message of which also talks about 2 other threads with more in- > depth info. > > -- > Mike Marion-Unix SysAdmin/Staff Engineer-http://www.qualcomm.com > Frasier: "...we know for whom the bell tolls." > [A bell dinging is heard, everyone looks around a little confused] > Martin: "Anybody else hear that?" > Daphne: "Oh! The biscuits!" --Fraiser > > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Darwin) iD8DBQFDXx9AwjCqooJyNAMRArHOAJ94RnQFYkwOuurmFUGocMH0CrVKGACdHO2s pEdANrCvZt0Y8lj4Bq8z3OM= =7Az6 -----END PGP SIGNATURE-----

4 6

Server environment variable
by Yan Fitterer 03 Nov '05

03 Nov '05

Does the Server environment variable point to the control source or the installation source? Thanks Yan

3 5

(Auto-)install multiple languages?
by Thomas Ribbrock 03 Nov '05

03 Nov '05

Hi all, after I just finished my first succesful autoinstall (yeah!) :-) I am left with a couple of questions as to how to improve it further. One thing I need to do is to automatically install more than one language - basically like you do under YaST2 in the "language" module with adding "Secondary Languages". I have seached through http://www.suse.de/~ug/autoyast_doc/ as well as through the archive of this list http://marc.theaimsgroup.com/?l=suse-autoinstall&r=1&w=2 but came up empty. Is there an easy way to accomplish this? If not, I can think of only two alternatives: - Manually add all language related packages for the languages I need to the package list (brrrrr...) - Try to do some script-wizardry in post-install or init? I have yet to figure out whether I can convince YaST2 to add the secondary languages from the commandline - if not, I'm down to the first option... Any hints (including docs I might have missed...) are welcome! Cheerio, Thomas

4 7

AutoYast XML and controller-independend disk partitioning
by Bernd Nies 02 Nov '05

02 Nov '05

Hi, Is it possible to define in the AutoYast XML file a generic hard disk (e.g. the boot device) that should be partitioned? We want to use the same XML profile for different types of host wit SCSI, SATA, IDE and RAID drives. Currently the device to be partitioned must be listed with the full device name, for instance: <partitioning config:type="list"> <drive> <device>/dev/hda</device> <initialize config:type="boolean">true</initialize> <partitions config:type="list"> ... </partitions> <use>1,2,3,4</use> </drive> </partitioning> This means that one XML file needs to be there for /dev/hda (IDE), another for /dev/sda (SATA, SCSI) and one for /dev/cciss/c0d0 (HP RAID Controller). The normal SUSE Yast installation can discover the boot device and make a suggestion. Can AutoYast also? Thanks in advance for help. Regards, Bernd

2 3

Strange behaviour of autoinstall
by Bernhard Duebi 02 Nov '05

02 Nov '05

Dear everybody, I have two problems: 1) CD Creator doesn't respect SP2 2) ncompress package is not installed I use a custom CD to install all our servers. I create the CD with SuSE Yast CD Creator. With SLES9 SP1 everything was fine. With SP2 I noticed that not all files on the CD are up to date. The driverupdate file comes from the SP1 CDs. The /boot comes even from the original SLES9 CDs. I fixed this by copying the SP2 files into the directory and regenerating the ISO image by hand, but I think this is the job of CD Creator. I need /usr/bin/uncompress to install one of our enterprise tools. In SP1 this was in the sharutils package. With SP2 it moved to the ncompress package. Though, I added the ncompress package to my XML file and recreated the ISO image. When I install a machine with this new CD, the GUI tells me that the ncompress package is being installed. The Yast logfiles, tell me that the installation of ncompress was successful. But if I do a rpm –q ncompress it tells me that ncompress is not installed and I can't find the /usr/bin/uncompress on disk. If I do rpm –ihv /media/cdrom/suse/*/ncompress*.rpm it installs cleanly. I also installed the machine with an install-server using the same XML files. The result is the same. The logfiles tell me that ncompress was successfully installed, but the files are not on disk. Any idea what's happening here ? Sincerely Bernhard Dübi

2 1

SLES9 + SP2 on DVD
by Bernd Nies 02 Nov '05

02 Nov '05

Hi, Has someone managed to burn all SLES9 CDs plus SP2 CDs on one DVD and made this as installation source so that one doesn't have to play disk jockey during installation? My first approach of taking the source from the installation server failed: - Copy all SLES9 CDs in one directory /export/suse/i386/sles9sp2 - Copy all SLES9 SP2 CDs into the same directory - Remove all src RPMs in the src directory - Change dir to /export/suse/i386/sles9sp2/suse - Run create_package_descr - Create bootable ISO file with mkisofs -A "SUSE LINUX Enterprise Server 9 SP2" \ -l -r -T -J -pad -no-emul-boot -boot-load-size 4 -boot-info-table \ -b boot/loader/isolinux.bin \ -c boot/boot.catalog \ -hide boot/boot.catalog \ -hide-joliet boot/boot.catalog \ -input-charset default \ -V "SLES9SP2" \ -o "/tmp/sles9sp2-i386-dvd.iso" \ /export/suse/i386/sles9sp2 - Burn the ISO file onto DVD cdrecord-dvd dev=ATAPI:0,0,0 speed=8 -eject -sao /tmp/sles9sp2-i386-dvd.iso The DVD was bootable but then it complained that I should insert the first product CD. What am I missing? Thanks in advance for help. Regards, Bernd

2 1