March 2007 - openSUSE Autoinstall - openSUSE Mailing Lists

[opensuse-autoinstall] LDAP server
by Lars Stavholm 28 Mar '07

28 Mar '07

Hi List, does anyone know of a way to use autoyast to install an LDAP server, short of using scripts, i.e. is there anything in the autoyast.xml syntax besides the script sections that could be used? I know there's stuff there for an LDAP client, but I'm looking for an automated setup of an LDAP server. Any ideas appreciated /Lars -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 2

[opensuse-autoinstall] RAID1 problem
by Lars Stavholm 27 Mar '07

27 Mar '07

Hi all, I'm trying to setup a software raid on three SATA disks with autoyast, and it works like a charm, just great, except for one little (but fatal for me:) detail: no matter how I connect the drives to the board, I always get RAID arrays setup with sda, sdc, sdb, i.e. a strange order, as I was expecting the arrays to be built with a, b, c. I.e., when connecting the drives I get: Physical connection: HD1 -> SATA-1 on the board HD2 -> SATA-2 HD3 -> SATA-3 lsscsi shows: /dev/sda /dev/sdb /dev/sdc ...whereas /proc/mdstat shows me sda, sdc, sdb. Another try: HD1 -> SATA-1 /dev/sda HD2 -> SATA-3 /dev/sdb HD3 -> SATA-2 /dev/sdc ...i.e. I swapped 2 and 3, I still get /proc/mdstat: sda, sdc, sdb. I'm at a loss here, does anyone know how this works? I need to know how to identify the disks in order for a hotswap (swap disks) functionality to work properly. Is there anyway I can influence the choices made by autoyast here? Any thoughts appreciated /Lars Stavholm -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 0

[opensuse-autoinstall] Cross-compiling SuSE kernel fails
by Frank Steiner 27 Mar '07

27 Mar '07

Hi, I'm trying to compile a set of i586 kernel rpms on a x86_64 host running SuSE 10.1(x86_64). I'm using the kernel-source-2.6.16.27-0.9.i586.rpm for the sources and compile them with "make ARCH=i386..." Works file for the kernels/modules, but generating the stuff for my kernel-source.rpm I call make ARCH=i386 O=/root/tmp/kernel/usr/src/linux-2.6.16-6suse-bio-obj/i386/default scripts which results in e.g. gcc -Wp,-MD,scripts/basic/.docproc.d -Iscripts/basic -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -o scripts/basic/docproc /root/tmp/kernel/usr/src/linux-2.6.16-6suse-bio/scripts/basic/docproc.c and I end up with "ELF 64-bit LSB executable, AMD x86-64" files: ...i386/default/scripts/basic/docproc: ELF 64-bit LSB executable, AMD x86-64, version 1 (SYSV), for GNU/Linux 2.6.4, dynamically linked (uses shared libs), for GNU/Linux 2.6.4, not stripped So I get a kernel-source.i586.rpm that I can't install on a i586 host due to these binaries. All other stuff like the modules or the kernel are compiled with "gcc -m32", but that -m32 is missing here. When I call make HOSTCC="gcc -m32" scripts ... I get 32bit binaries, but I'm not sure if that's the right way to do it. Is there any reason why "make scripts" ignores the ARCH parameter? Is there a better fix than the "HOSTCC=.." call? cu, Frank -- Dipl.-Inform. Frank Steiner Web: http://www.bio.ifi.lmu.de/~steiner/ Lehrstuhl f. Bioinformatik Mail: http://www.bio.ifi.lmu.de/~steiner/m/ LMU, Amalienstr. 17 Phone: +49 89 2180-4049 80333 Muenchen, Germany Fax: +49 89 2180-99-4049 * Rekursion kann man erst verstehen, wenn man Rekursion verstanden hat. * -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 1

[opensuse-autoinstall] Need swap partition for pxe installation because of too less memory
by Thomas Vogt 26 Mar '07

26 Mar '07

Hello List I try to install OpenSuSe 10.2 via PXE. First I run a Linux unattended image and it boots the OpenSuSe 10.2 kernel and the normal autoyast part starts. It worked perfectly with older SuSe 9.2 and SuSe 9.3 installations but it fails now with OpenSuSe 10.2 because of too less memory for yast. My machines only has 256mb Ram and 8mb of it is shared with AGP. Yast asks for a swap partition. Is there a way to auto create a swap partition during the pxe boot? The boot procedure looks like: dns: mirror.intern setfont linuxrc-16.psfu Setting up lolcahost ... done Going for automatic install Loading image "mirror/opensuse/distribution/10.2/repo/oss/boot/i386/root" ... Cramfs: "root 70540" Image Size: 70540kB mount download image0: we need a loop device mount: using /dev/loop0 Loading image "mirror/opensuse/distribution/10.2/repo/oss/diverupdate" ... /dowload/imag1 removed That's it. Then I got an error about to less memory, please define a swap partition. My autoyast looks like: <?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> <device_map config:type="list"> <device_map_entry> <firmware>hd0</firmware> <linux>/dev/hda</linux> </device_map_entry> </device_map> <global> <boot_mbr>true</boot_mbr> <lines_cache_id>0</lines_cache_id> </global> <initrd_modules config:type="list"> <initrd_module> <module>piix</module> </initrd_module> <initrd_module> <module>processor</module> </initrd_module> <initrd_module> <module>thermal</module> </initrd_module> <initrd_module> <module>fan</module> </initrd_module> <initrd_module> <module>jbd</module> </initrd_module> <initrd_module> <module>ext3</module> </initrd_module> <initrd_module> <module>edd</module> </initrd_module> </initrd_modules> <loader_device>/dev/hda</loader_device> <loader_type>grub</loader_type> <location>mbr</location> <repl_mbr config:type="boolean">false</repl_mbr> <sections config:type="list"> <section> <append>acpi=off resume=/dev/hda5 splash=silent showopts</append> <initial>1</initial> <initrd>/boot/initrd</initrd> <kernel>/boot/vmlinuz</kernel> <lines_cache_id>1</lines_cache_id> <name>openSUSE 10.2</name> <original_name>linux</original_name> <root>/dev/hda6</root> <type>image</type> <vga>0x31a</vga> </section> <section> <chainloader>/dev/hda1</chainloader> <lines_cache_id>2</lines_cache_id> <name>Windows</name> <original_name>windows</original_name> <root></root><sectors>1</sectors> <type>chainloader</type> </section> <section> <append>showopts ide=nodma apm=off acpi=off noresume nosmp noapic maxcpus=0 edd=off 3</append> <initrd>/boot/initrd</initrd> <kernel>/boot/vmlinuz</kernel> <lines_cache_id>3</lines_cache_id> <name>Failsafe -- openSUSE 10.2</name> <original_name>failsafe</original_name> <root>/dev/hda6</root> <type>image</type> <vga>normal</vga> </section> </sections> </bootloader> <firewall> <FW_DEV_DMZ></FW_DEV_DMZ> <FW_DEV_EXT></FW_DEV_EXT> <FW_DEV_INT></FW_DEV_INT> <enable_firewall config:type="boolean">false</enable_firewall> <start_firewall config:type="boolean">false</start_firewall> </firewall> <general> <mode> <confirm config:type="boolean">false</confirm> </mode> <mouse> <id>none</id> </mouse> <signature-handling/> </general> <keyboard> <keyboard_values> <capslock config:type="boolean">false</capslock> <delay></delay> <discaps config:type="boolean">false</discaps> <numlock></numlock> <rate></rate> <scrlock config:type="boolean">false</scrlock> <tty>tty1 tty2 tty3 tty4 tty5 tty6 tty8 tty9 tty10 tty11 tty12 tty13 tty14 tty15 tty16 tty17 tty18 tty19 tty20</tty> </keyboard_values> <keymap>german-ch</keymap> </keyboard> <networking> <dhcp_options> <dhclient_additional_options></dhclient_additional_options> <dhclient_client_id></dhclient_client_id> <dhclient_hostname_option>AUTO</dhclient_hostname_option> </dhcp_options> <dns> <dhcp_hostname config:type="boolean">false</dhcp_hostname> <dhcp_resolv config:type="boolean">true</dhcp_resolv> </dns> <interfaces config:type="list"> <interface> <bootproto>dhcp</bootproto> <device>eth0</device> <ifplugd_priority>20</ifplugd_priority> <startmode>ifplugd</startmode> <usercontrol>no</usercontrol> </interface> </interfaces> <managed config:type="boolean">false</managed> <modules config:type="list"> <module_entry> <device>static-0</device> <module></module> <options></options> </module_entry> </modules> <routing> <ip_forward config:type="boolean">false</ip_forward> </routing> </networking> <partitioning config:type="list"> <drive> <device>/dev/hda</device> <partitions config:type="list"> <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">5</partition_nr> <size>781369344</size> </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">6</partition_nr> <size>18202512384</size> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <mount>/home</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">7</partition_nr> <size>27225644032</size> </partition> </partitions> <use>2,5,6,7</use> </drive> </partitioning><report> <errors> <log config:type="boolean">true</log> <show config:type="boolean">true</show> <timeout config:type="integer">0</timeout> </errors> <messages> <log config:type="boolean">true</log> <show config:type="boolean">true</show> <timeout config:type="integer">0</timeout> </messages> <warnings> <log config:type="boolean">true</log> <show config:type="boolean">true</show> <timeout config:type="integer">0</timeout> </warnings> <yesno_messages> <log config:type="boolean">true</log> <show config:type="boolean">true</show> <timeout config:type="integer">0</timeout> </yesno_messages> </report> etc.... Thanks Thomas -- * Thomas Vogt System Engineer - SolNet ISP (AS 9044) * * phone: +41 32 686 82 22 / PGPKEY-3239B720 *

1 0

[opensuse-autoinstall] GPT disklables?
by Beat Rubischon 22 Mar '07

22 Mar '07

Hello! It looks like all current releases of SuSE and SLES uses MSDOS disklables. As more and more storage systems exceedes 2TB, it would be nice to be able to create GPT disklables during installation or in Yast without using parted manually. Booting from a GPT partition should also be possible in a recent system using EFI - even x86 based systems are more and more equipped with EFI and a BIOS emulator. Did I overlooked such a feature or do I have a feature request for future SuSE versions? Beat -- \|/ Beat Rubischon <beat(a)0x1b.ch> ( 0^0 ) http://www.0x1b.ch/~beat/ oOO--(_)--OOo--------------------------------------------------- Meine Erlebnisse, Gedanken und Traeume: http://www.0x1b.ch/blog/ -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 1

Re: [opensuse-autoinstall] Problem with Pattern Prq verses Prc Packages
by Yan Fitterer 21 Mar '07

21 Mar '07

> Uwe's response to an earlier question suggested removing unwanted > packages using "<remove- packages>". There are 121 packages in the > suggested list (+ what ever dependencies they are pulling in). Would > this mean that these are all installed and then removed? No it doesn't. Autoyast will work out the final list of packages to install (including dependencies) before starting the install. -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

3 3

[opensuse-autoinstall] adding a "Plain Cache" RPM source
by Dave 21 Mar '07

21 Mar '07

Hello, This is not strictly an autoyast question, but is very relevant for us since we are interested in creating an additional YaST installation source (with RPMs not included on the CDs) during the AutoYast install. The "other" RPMs will reside in a dedicated directory on the NFS install server. I followed the instructions outlined here: http://en.opensuse.org/Creating_YaST_Installation_Sources for adding "Plain Cache Sources", but this unfortunately failed. <ipaddr> is the IP address of the nfs server +----------------------+ Media Containing the Software Catalog ¦ Software packages - +-----------------------------------------------------+ ¦can be installed from ¦ ¦Status¦Refresh¦Name ¦URL ¦ ¦the CD, over a ¦ ¦On ¦Off ¦SUSE Linux 10.1¦nfs://<ipaddr>/san¦ ¦network, or from the ¦ ¦ ¦ ¦hard disk. ¦ ¦ ¦ ¦ To in+-------------------------------------------------------------+ ¦ ¦from CD,¦ Unable to create installation source ¦ ¦ ¦SUSE LIN¦ from URL 'nfs://<ipaddr>/sanrep/suse/10.1/RPMS.other'. ¦ ¦ ¦the DVD ¦ Details: ¦ ¦ ¦ The S¦ Cannot create the installation source ¦ ¦ ¦can be c¦ Try again? ¦ ¦ ¦hard dis¦ [Yes] [No ] ¦ ¦ ¦that as +-------------------------------------------------------------+ ¦ ¦installat ¦ ¦Insert the path name ¦ ¦ ¦ ¦where the first CD is ¦ ++---------------------------------------¦------------+ ¦located, for example, ¦ [ Add v] [ Up ][ Down ] ¦/data1/CD1. Only the ¦ [ Edit v] [ Enable or Disable ] ¦base path is required ¦ [ Delete ] [ Refresh On or Off ] +----------------------+ [Abort] [Finish] The full path used to install the server was (nfs://<ipaddr>/sanrep/suse/10.1) which works. I am also able to mount the separate NFS directory nfs://<ipaddr>/sanrep/suse/10.1/RPMS.other succesfully from the command line of this server, seen here: user@slp10-1:~ > sudo mount -t nfs <ipaddr>:/sanrep/suse/10.1/RPMS.other /mnt user@slp10-1:~ > ls /mnt gcc-fortran-4.1.0-25.i586.rpm regina-3.3-14.i586.rpm IS_PLAINcache.gz the-3.1-263.i586.rpm Here are the directory contents seen on the server: user@nfs-server:/sanrep/suse/10.1/RPMS.other > ls -l total 4560 -rw-r--r-- 1 root root 2430198 2007-03-20 15:22 gcc-fortran-4.1.0-25.i586.rpm -rw-r--r-- 1 root root 13908 2007-03-20 15:23 IS_PLAINcache.gz -rw-r--r-- 1 root root 1427053 2007-03-20 15:22 regina-3.3-14.i586.rpm -rw-r--r-- 1 root root 783015 2007-03-20 15:22 the-3.1-263.i586.rpm which were created using the steps mentioned in the web page referenced above: genIS_PLAINcache -f -v . gzip IS_PLAINcache Why YaST can't create the installation source? Thanks, Dave ____________________________________________________________________________________ Now that's room service! Choose from over 150,000 hotels in 45,000 destinations on Yahoo! Travel to find your fit. http://farechase.yahoo.com/promo-generic-14795097 -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 2

[opensuse-autoinstall] About -1012 error while creating LVM partitions.
by gm05a 21 Mar '07

21 Mar '07

Hi, I use opensue10.2 and want to use autoyast to setting LVM partitions. But I got a problem that -1012 error occurs while making simple LVM partitions, below message is at this problem. "Setting hda4 to type F" Othes type of partitions got no error. I got same error only making "LVM" partitions. Is this a BUG?? Any ideas? show below that section; <partitioning config:type="list"> <drive> <device>/dev/hda</device> <partitions config:type="list"> <partition> <filesystem config:type="symbol">ext3</filesystem> <filesystem_id config:type="integer">131</filesystem_id> <format config:type="boolean">true</format> <mount>/boot</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">1</partition_nr> <partition_type>primary</partition_type> <size>73995264</size> </partition> <partition> <filesystem_id config:type="integer">142</filesystem_id> <lvm_group>system</lvm_group> <partition_id config:type="integer">142</partition_id> <partition_nr config:type="integer">2</partition_nr> <partition_type>primary</partition_type> <size>82269250560</size> </partition> </partitions> <type config:type="symbol">CT_DISK</type> <use>all</use> </drive> <drive> <device>/dev/system</device> <lvm2 config:type="boolean">true</lvm2> <partitions config:type="list"> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <lv_name>home</lv_name> <mount>/home</mount> <size>26843545600</size> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <lv_name>root</lv_name> <mount>/</mount> <size>21474836480</size> </partition> <partition> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <lv_name>swap</lv_name> <mount>swap</mount> <size>922746880</size> </partition> </partitions> <pesize>4M</pesize> <type config:type="symbol">CT_LVM</type> <use>all</use> </drive> </partitioning> -- K.F casiopea(a)meg.winknet.ne.jp -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 1

[opensuse-autoinstall] error creating extended partition
by Ian Grant 21 Mar '07

21 Mar '07

Dear List (and Uwe), I am using openSUSE 10.2. When I try to do an autoyast install I get an error dialog when the program tries to set the type of the extended partition: Error: Failure occurred during the following action: Setting type of partition /dev/sda3 to F System error code was: -1012 And the install quits. It leaves the MBR corrupt with an invalid partition type so subsequent autoinstalls don't work (parted says it can't use the format and refuses to create partitions etc.) Does anyone know a way around this? Here is my partitioning XML which I got from 'clone this system for autoyast' on a successful manual install of the same machine. All I have changed is the <use>1,2,3 etc</use> to <use>all</use>: <partitioning config:type="list"> <drive> <device>/dev/md</device> <partitions config:type="list"> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <mount>/</mount> <partition_nr config:type="integer">0</partition_nr> <raid_options> <persistent_superblock config:type="boolean">false</persistent_superblock> <raid_type>raid1</raid_type> </raid_options> </partition> <partition> <lvm_group>system</lvm_group> <partition_nr config:type="integer">1</partition_nr> <raid_options> <persistent_superblock config:type="boolean">false</persistent_superblock> <raid_type>raid1</raid_type> </raid_options> </partition> <partition> <lvm_group>scratch</lvm_group> <partition_nr config:type="integer">2</partition_nr> <raid_options> <persistent_superblock config:type="boolean">false</persistent_superblock> <raid_type>raid1</raid_type> </raid_options> </partition> </partitions> <use>all</use> </drive> <drive> <device>/dev/scratch</device> <lvm2 config:type="boolean">true</lvm2> <partitions config:type="list"> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <lv_name>scratch</lv_name> <mount>/local/scratch</mount> <size>32212254720</size> </partition> </partitions> <pesize>4M</pesize> <type config:type="symbol">CT_LVM</type> <use>all</use> </drive> <drive> <device>/dev/sda</device> <partitions config:type="list"> <partition> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">2</partition_nr> <partition_type>primary</partition_type> <raid_name>/dev/md0</raid_name> <size>21476205568</size> </partition> <partition> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">3</partition_nr> <partition_type>primary</partition_type> <size>21476205568</size> </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">5</partition_nr> <size>2154990592</size> </partition> <partition> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">6</partition_nr> <raid_name>/dev/md1</raid_name> <size>42952379392</size> </partition> <partition> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">7</partition_nr> <raid_name>/dev/md2</raid_name> <size>42952379392</size> </partition> <partition> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">8</partition_nr> <size>42952379392</size> </partition> <partition> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">9</partition_nr> <size>42952379392</size> </partition> <partition> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">10</partition_nr> <size>42952379392</size> </partition> <partition> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">11</partition_nr> <size>38724585472</size> </partition> </partitions> <use>2,3,4,5,6,7,8,9,10,11</use> </drive> <drive> <device>/dev/sdb</device> <partitions config:type="list"> <partition> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">2</partition_nr> <partition_type>primary</partition_type> <raid_name>/dev/md0</raid_name> <size>21476205568</size> </partition> <partition> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">3</partition_nr> <partition_type>primary</partition_type> <size>21476205568</size> </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">5</partition_nr> <size>2154990592</size> </partition> <partition> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">6</partition_nr> <raid_name>/dev/md1</raid_name> <size>42952379392</size> </partition> <partition> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">7</partition_nr> <raid_name>/dev/md2</raid_name> <size>42952379392</size> </partition> <partition> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">8</partition_nr> <size>42952379392</size> </partition> <partition> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">9</partition_nr> <size>42952379392</size> </partition> <partition> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">10</partition_nr> <size>42952379392</size> </partition> <partition> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">11</partition_nr> <size>38724585472</size> </partition> </partitions> <use>2,3,4,5,6,7,8,9,10,11</use> </drive> <drive> <device>/dev/system</device> <lvm2 config:type="boolean">true</lvm2> <partitions config:type="list"> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <lv_name>tmp</lv_name> <mount>/tmp</mount> <size>10737418240</size> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <lv_name>var</lv_name> <mount>/var</mount> <size>8053063680</size> </partition> </partitions> <pesize>4M</pesize> <type config:type="symbol">CT_LVM</type> <use>all</use> </drive> </partitioning> -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

3 6

[opensuse-autoinstall] Problems SLES10 / autoyast / creating initrd during setup proccess
by Achim Schmidt 20 Mar '07

20 Mar '07

Hi all I try to install sles10 systems by using autoyast and pxeboot. It seems thats working fine until the systems tries to create it's initrd. At that point the system hung's and stops working. any idea ?? thx & rgds Achim -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 1