April 2004 - openSUSE Autoinstall - openSUSE Mailing Lists

IBM HS20 Blade PXE install of SLES 8 w/ SP3 - revised
by Kohrs, Steven 28 Apr '04

28 Apr '04

I'm looking for any pointers on automating the installation of SLES 8 w/ SP3 to IBM HS20 blade servers via PXE booting. First, I have a question about creating my network share. http://portal.suse.com/sdb/en/2003/03/rschmid_slesnfs.html states to copy all 4 CDs, in reverse order, to a common directory. How does the SP3 CD fit into this puzzle? Can I substitute the SP3 CD for CD 1, since you can boot from SP3? Second, I'm going to try and follow the instructions from http://portal.suse.com/sdb/en/2003/06/tsieden_pxe-install.html. This is where any (HS20 | Blade Center Chassis | RDM) specific hints would be great. Thank you. -- Sincerely, Steve Kohrs Distributed Systems 402.633.7058 This email and any files attached with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error delete this message and notify the sender at 402-341-0500. If you are not the named recipient you should not disseminate, distribute or copy this email or any attachment.

1 0

IBM HS20 Blade PXE install of SLES 8 w/ SP3
by Kohrs, Steven 28 Apr '04

28 Apr '04

I'm looking for any pointers on automating the installation of SLES 8 w/ SP3 to IBM HS20 blade servers via PXE booting. First, I have a question about creating my SMB share. http://portal.suse.com/sdb/en/2003/03/rschmid_slesnfs.html states to copy all 4 CDs, in reverse order, to a common directory. How does the SP3 CD fit into this puzzle? Can I substitute the SP3 CD with CD 1, since you can boot from SP3? Second, I'm going to try and follow the instructions from http://portal.suse.com/sdb/en/2003/06/tsieden_pxe-install.html. This is where any (HS20 | Blade Center Chassis | RDM) specific hints would be great. Thank you. -- Sincerely, Steve Kohrs Distributed Systems 402.633.7058 This email and any files attached with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error delete this message and notify the sender at 402-341-0500. If you are not the named recipient you should not disseminate, distribute or copy this email or any attachment.

1 0

SLES8 and keeping partitions / linuxrc and installation media
by Wenk, Moritz 28 Apr '04

28 Apr '04

Hi, I am trying to do a disk-to-disk installation using SLES 8 and autoyast. Now I have two questions: 1) Is it possible to keep disk partitions? And if yes, how? I figured it out for SuSE 9.0 but it does not work this way for SLES 8. 2) I prepared a source repository as described in 6.1.3 in http://www.suse.de/~nashif/autoinstall/sles8/html/advanced.html#AEN1321 on partition /dev/hda7 (the last one on the disk). The info file for linuxrc seems to work but linuxrc always says "/dev/hda7 is not a SuSE Linux installation media". After trying DHCP on the NICs it runs into the textual UI of linuxrc. When I select installation from harddisk and then /dev/hda7 as source, everything works fine. Any ideas? Regards, i. A. Moritz Wenk Software Developer Produkt Management International PLATINUM Server MAXDATA Computer GmbH&Co.KG Elbestraße 12 - 16 D-45768 Marl Telefon: +49 2365 952-2715 Telefax: +49 2365 952-2279 http://www.maxdata.com

2 1

Automatische Größe bei logischen Laufwerken?
by Hartmut.Dunker＠finanzit.com 28 Apr '04

28 Apr '04

Hallo, ich möchte per AutoYast2 unter SLES8 logische Laufwerke anlegen. Das letzte logische Laufwerk soll dabei den restlichen zur Verfügung stehenden Plattenplatz belegen. Ist dieses Möglich und wenn ja wie sieht die Syntax dafür aus? Ich konnte leider keine Referenz finden, in der die Syntax mit möglichen Parametern beschrieben ist. Gibt es eine solche? Folgendes habe ich versucht: <partitioning config:type="list"> <drive> <device>/dev/cciss/c0d0</device> <reuse>all</reuse> <initialize config:type="boolean">true</initialize> <partitions config:type="list"> [...] <partition> <size>max</size> <lvm_group>datavg</lvm_group> </partition> </partitions> </drive> </partitioning> <lvm config:type="list"> <lvm_group> <lvm_name>datavg</lvm_name> <pesize>4M</pesize> <logical_volumes config:type="list"> [...] <lv> <lv_name>datalv</lv_name> <lv_size>max</lv_size> <lv_fs>ext3</lv_fs> <lv_mount>/data</lv_mount> </lv> </logical_volumes> </lvm_group> </lvm> Bei datalv bleibt AutoYast2 mit einer Fehlermeldung stehen - hier scheint es max für lv_size nicht zu mögen... MfG Hartmut Dunker

2 1

WG: [suse-autoinstall] Antwort: Re: [suse-autoinstall] autoinst.xml on self-made cd
by Manuel.Laesser＠telekurs.com 27 Apr '04

27 Apr '04

Hello, is there really no way to have the ethernet adapter detected automatically so that there will be the entry for my ethernet interface in /etc/modules.conf again? Since I create my CD according to Anas instruction it won't be inserted automatically. Thank you for you help. Regards Manuel ----- Weitergeleitet von Manuel Lässer/TK Services/Telekurs am 17.04.2004 13:32 ----- Manuel.Laesser(a)telekurs.com 07.04.2004 21:52 An Anas Nashif <nashif(a)suse.de> Kopie suse-autoinstall(a)suse.com Thema [suse-autoinstall] Antwort: Re: [suse-autoinstall] autoinst.xml on self-made cd Hello Anas Thank you so much for this hint! It really works if you follow all your instruction below step by step. There are a couple of things that changed if I compare it with the installation from my repository-server. 1. at the stage when the license agreement is displayed, there is a 10 second countdown and after this the installation starts. How can I disable this timer so you really have to press enter to continue? 2. no module will be loaded for the network interface(s) because there is no entry in /etc/modules.conf for eth0. If I install the server from my repository-server the ethernet interface eth0 will be discovered automatically and I've got an alias set for my eth0 in /etc/modules.conf. Is there a way, I can detect all ethernet interfaces and insert them all in /etc/modules.conf even I install my server from the cd as described by Anas below? Thank you for your answer. Regards Manuel ----------------------------------------------------------- Telekurs Services Hardturmstrasse 201, 8005 Zürich Phone : +41 1 279 44 24 Fax : +41 1 279 34 44 mailto : manuel.laesser(a)telekurs.com ----------------------------------------------------------- Anas Nashif <nashif(a)suse.de> 03.04.2004 02:59 An Manuel.Laesser(a)telekurs.com Kopie suse-autoinstall(a)suse.com Thema Re: [suse-autoinstall] autoinst.xml on self-made cd Hi, I have just tried reproducing this, and it works for me as expected. - unpack ISO/CD of SLES8 into a directory /tmp/SLES - unpack ISO/CD of SP3 into a directory /tmp/SP3 - cp /tmp/SP3/driverupdate /tmp/SLES - cp /tmp/SP3/boot/loader/linux /tmp/SLES/boot/loader - cp /tmp/SP3/boot/loader/initrd /tmp/SLES/boot/loader - Edit /tmp/SLES/boot/loader/isolinux.cfg and add autoyast=default instmode=cd - Copy autoinst.xml into /tmp/SLES Create ISO image Boot and it works. Anas Manuel.Laesser(a)telekurs.com wrote: > Hello, > sorry to bother you again and again. I'm using SLES8 with > autoyast2-2.6.44-7 and autoyast2-installation-2.6.44-7. I think this is > the latest version for SLES8 (comming with SP3). I copied autoinst.xml to > the root of my self-made CD-ROM and I'm using the following parameter in > isolinux.cfg > > # autoyast > label autoyast > kernel linux > append initrd=initrd ramdisk_size=65536 autoyast=default instmode=cd > usedhcp=0 textmode=1 > > If you use parameter "autoyast=default" YaST2 will look for autoinst.xml > in the following three places (according to Anas Nashif PDF SLES8 - > Automatic Linux Installation and Configuration with YaST2) : > > 1. the root directory of the floppy disk > 2. the root directory of the installation medium (CD-ROM in my case) > 3. the root directory of the initial ram disk used to boot the system > > Cool......unfortunately it doesn't work at all in my environment. I tried > with "autoyast=file:/autoinst.xml", "autoyast=file://autoinst.xml", > "autoyast=default" I always got this bloody control menu where it asks for > the location of the autoinst.xml! From there I could choose http, device, > floppy, nfs....but I didn't manage to access the cdrom. If I insert a > floppy with my autoinst.xml in the root, the installation is proceeding. I > also can edit isolinux.cfg with "autoyast=floppy://autoinst.xml" and it'll > find autoinst.xml. > > Why do I get always very nice and well meant hints from the autoinstall > mailing list telling me that the are using "...autoyast= default > instmode=cd..." and everything is working fine. Does this have a coherence > that I'm using SLES8 with autoyast2-2.6.44-7 and most of people Suse x.x > with the newest autoyast2 autoyast2-2.8.14-20 or so..... > > I'm really stumped.... > > Any comment is welcome. > > Regards Manuel > > p.s. I'll send a box of the finest original swiss chocolate to the one who > can give me the right tip to solve this problem...... ;-)) > > ----------------------------------------------------------- > Telekurs Services > Hardturmstrasse 201, 8005 Zürich > Phone : +41 1 279 44 24 > Fax : +41 1 279 34 44 > mailto : manuel.laesser(a)telekurs.com > -----------------------------------------------------------

2 3

RE: [suse-autoinstall] automatic updates after autoinstall
by Ness, Todd 27 Apr '04

27 Apr '04

You can run "online_update -s" That will update for you assuming that you have all the network access you need. Todd -----Original Message----- From: Cosmo King [mailto:cosmo@pogolinux.com] Sent: Monday, April 26, 2004 5:39 PM To: suse-autoinstall(a)suse.com Subject: [suse-autoinstall] automatic updates after autoinstall How do I force updates to be automatically run after a network autoinstall of susepro 9/ sles8? I have downloaded the update tree, and placed it in the update folder at the root of the suse installation repository. Thanks! -- Cosmo King Systems Engineer Pogo Linux, Inc. 888.828.7646 cosmo(a)pogolinux.com -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

2 1

RE: [suse-autoinstall] Postinstall scripts in a different file
by Ness, Todd 27 Apr '04

27 Apr '04

I have used the method of "wget http://IP/somepath/somefile -O /somedest" in a post install script. -----Original Message----- From: Cosmo King [mailto:cosmo@pogolinux.com] Sent: Monday, April 26, 2004 5:34 PM To: suse-autoinstall(a)suse.com Subject: [suse-autoinstall] Postinstall scripts in a different file Is there a way to have the entire postinstall script reside in a file other than the autoinstall.xml, and circumventing the need for the awkward <![CDATA[#!/bin/bash ]]> syntax? Thanks! -- Cosmo King Systems Engineer Pogo Linux, Inc. 888.828.7646 cosmo(a)pogolinux.com -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

Postinstall scripts in a different file
by Cosmo King 27 Apr '04

27 Apr '04

Is there a way to have the entire postinstall script reside in a file other than the autoinstall.xml, and circumventing the need for the awkward <![CDATA[#!/bin/bash ]]> syntax? Thanks! -- Cosmo King Systems Engineer Pogo Linux, Inc. 888.828.7646 cosmo(a)pogolinux.com

1 0

automatic updates after autoinstall
by Cosmo King 27 Apr '04

27 Apr '04

How do I force updates to be automatically run after a network autoinstall of susepro 9/ sles8? I have downloaded the update tree, and placed it in the update folder at the root of the suse installation repository. Thanks! -- Cosmo King Systems Engineer Pogo Linux, Inc. 888.828.7646 cosmo(a)pogolinux.com

1 0

Keep various installations up to date
by Stefano Zanarini 26 Apr '04

26 Apr '04

Hi, I have several installations done throught autoyast and everithing works fine,but I spend lot of time replicating all configuration variations after installation across different machines,is it possible to use autoyast and generate an autoinst.conf with some variations (for example one more user or something similar ...) and pass it to another autoyast on an other machine and make him write changes on the configuration files (or pass it directly to yast) ? I've read that autoyast use a format compatible with other modules of yast ,so how can I make yast able of reading these configurations from autoyast and use them to change my configuration files ? Is it possible ? even with some hacks .... Thanks in advance regards

1 0

Automatische Größe bei logischen Laufwerken?
by Hartmut.Dunker＠finanzit.com 26 Apr '04

26 Apr '04

Hello, i want to create logical volumes with AutoYast2. The last volume should use the remaining place of the Volume group. Is this possible? How is the Syntax for this? I wasn't able to find a reference including the syntax with possible parameters and values. Is there any one avalable? I tried following: <partitioning config:type="list"> <drive> <device>/dev/cciss/c0d0</device> <reuse>all</reuse> <initialize config:type="boolean">true</initialize> <partitions config:type="list"> [...] <partition> <size>max</size> <lvm_group>datavg</lvm_group> </partition> </partitions> </drive> </partitioning> <lvm config:type="list"> <lvm_group> <lvm_name>datavg</lvm_name> <pesize>4M</pesize> <logical_volumes config:type="list"> [...] <lv> <lv_name>datalv</lv_name> <lv_size>max</lv_size> <lv_fs>ext3</lv_fs> <lv_mount>/data</lv_mount> </lv> </logical_volumes> </lvm_group> </lvm> When reaching datalv AutoYast2 stops with an error message - it seams AutoYast2 don't like the value max for lv_size... Regards Hartmut Dunker

1 0

Antwort: [suse-autoinstall] Automatische=?iso-8859-1?Q?Gr=F6=DFe_bei_logischen_Laufwerken=3F?=
by Hartmut.Dunker＠finanzit.com 26 Apr '04

26 Apr '04

Hello, i didn't remember that this is an english mailinglist. Sorry. I opened a new thread in english. Regards Hartmut Dunker

1 0

Suse 9.0: Help for Autoyast via FTP server
by Support Idea-Net Consulting & Web Solutions 22 Apr '04

22 Apr '04

Hi, I'm begin to describe my network/server configuration: ******************** server configuration ******************** ip: 192.168.2.10 Netmask: 255.255.255.0 Gateway: 192.168.2.1 ftp user: hotspot pass: xxx directory on ftp server: /_ |- profiles/_ | |_ default (autoinst.xml renamed in default for multiple | profiles) |_ suse/_ |- boot/ |- docu/ |- dosutils/ |- media.1/ |- suse/ |_ unsorted/ ************************ linux.config on boot.iso ************************ I wrote in to linuxrc.config on boot.iso this following parameters: KernelPCMCIA: 1 UseUSBSCSI: 1 Product: SuSE Linux Display: Color InstMode: ftp Server: 192.168.2.10 Serverdir: suse Netdevice: eth0 Insmod: 3c59x Username: hotspot Password: xxx HostIp: 192.168.2.254 Netmask: 255.255.255.0 Gateway: 192.168.2.1 AutoYast: ftp://192.168.2.10/profiles/ and after I have burned the cd ********** My problem ********** I boot the client with my cd bootable, yast2 starting, load the network configuration from linuxrc.config and log on the ftp server with my user "hotspot". Read the profile ("default" file), run the yast2 GUI interface and configure the language selection. Via Ethereal I sow that's works fine, but in the second step named "Installation Setting" of yast2 GUI, the autoyast prompt me a windows where are the message: "Profile for this machine could not be founde o retrieved. Please make sure you have specified the correct location on the command line" Any idea? I have renamed the default file in autoinst.xml and changed in the linuxrc.config the parameter, but I receive always the same error. Thank you Luca Lafranchi

1 0

AutoInstall on small memory systems
by Lee Mayes 21 Apr '04

21 Apr '04

I'm using some old hardware (and vmware instances) to verify some SuSE 9.0 autoinstalls. Some only have 128MB of RAM. While I wouldn't attempt to run any production services on these boxes, they're a good test of my final scripts and processes. I've run across a problem in the way the rpm's are installed using a network (http) source. By pushing a virtual console during the actual install, it appears that the rpm command is caching the rpm to be installed in / (the ramfs) vs. the mounted hardrive. So basically, this limits the size of an rpm that can be installed from a network source to roughly Physical Ram - ( kernel + cramfs installer ram footprint), which works out to roughly 52MB on a 128M system. With less than 128M there are other concerns, so that's my bare minimum for testing installs. Is there a switch I can pass AutoYaST2 somewhere to have it use the installing system's mounted /var/tmp vs. the ramfs? There are some pretty big RPM's out there, like OpenOffice (who's integration I need to test :^). Thanks, I realize this is a corner case most people would never hit on modern hardware (HTTP install + 128M RAM). Lee

2 1

RE: [suse-autoinstall] Saving packages...
by Ness, Todd 15 Apr '04

15 Apr '04

Thank you that is a thought, I was hoping that there was a install flag that tells the installer to keep the rpm when installing. Much like redcarpet has for not clearing the cache. -----Original Message----- From: Lenz, Fabian [mailto:Fabian.Lenz@telekom.de] Sent: Thursday, April 15, 2004 6:44 AM To: todd.ness(a)eds.com; suse-autoinstall(a)suse.com Subject: AW: [suse-autoinstall] Saving packages... Hello! You can mount the installmedium an copy the rpm´s on the disk with a preinstall-script. Fabian Lenz Azb Fachinformatiker für Systemintegration Deutsche Telekom AG Telekom Training BBi Koblenz Hausadresse: Blücherstr. 6-8, 56073 Koblenz Postanschrift: Postfach 9100, 56065 Koblenz Telefon (mobil): +49 (160) 3565851 E-Mail: mailto:Fabian.Lenz@telekom.de Intranet: http://ttc.telekom.de/ -----Ursprüngliche Nachricht----- Von: Ness, Todd [mailto:todd.ness@eds.com] Gesendet: Donnerstag, 15. April 2004 14:33 An: suse-autoinstall(a)suse.com Betreff: [suse-autoinstall] Saving packages... Is there a way to save the rpms that are being installed during autoinstall to the local disk? For example: If I save every rpm I install and I save a special initrd and autoinst.xml saved on the machine I could have a re-install option on the boot menu that a user could re-image his machine if he broke it too badly and could not get remote support. Todd -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

AW: [suse-autoinstall] Saving packages...
by Lenz, Fabian 15 Apr '04

15 Apr '04

Hello! You can mount the installmedium an copy the rpm´s on the disk with a preinstall-script. Fabian Lenz Azb Fachinformatiker für Systemintegration Deutsche Telekom AG Telekom Training BBi Koblenz Hausadresse: Blücherstr. 6-8, 56073 Koblenz Postanschrift: Postfach 9100, 56065 Koblenz Telefon (mobil): +49 (160) 3565851 E-Mail: mailto:Fabian.Lenz@telekom.de Intranet: http://ttc.telekom.de/ -----Ursprüngliche Nachricht----- Von: Ness, Todd [mailto:todd.ness@eds.com] Gesendet: Donnerstag, 15. April 2004 14:33 An: suse-autoinstall(a)suse.com Betreff: [suse-autoinstall] Saving packages... Is there a way to save the rpms that are being installed during autoinstall to the local disk? For example: If I save every rpm I install and I save a special initrd and autoinst.xml saved on the machine I could have a re-install option on the boot menu that a user could re-image his machine if he broke it too badly and could not get remote support. Todd -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

Saving packages...
by Ness, Todd 15 Apr '04

15 Apr '04

Is there a way to save the rpms that are being installed during autoinstall to the local disk? For example: If I save every rpm I install and I save a special initrd and autoinst.xml saved on the machine I could have a re-install option on the boot menu that a user could re-image his machine if he broke it too badly and could not get remote support. Todd

1 0

Suse 9.0 on Raid mirror - include external driver module
by Eveline Bernard 15 Apr '04

15 Apr '04

Please help me install Suse 9 on a new Raid system! It is driving me MAD! I noticed several unsolved issues on this newsforum, about Raid, External modules. Please let some more experienced Linux crack dive into it and solve it, I'm a newbe on Linux. The Yast2 should ask for the external driver module, but it does not. Hèèlup! My system is Asus P4C800-E Deluxe motherboard with Promise FasTrak 378 controller. I attached two Maxtor 80 GB SATA disks in Raid mirror configuration. The system has also an Adaptec 2940 SCSi controller, with Plextor CD-Writer and Iomega Zip 100 drive attached. And to the on-board USB 2.0 controller an multimedia card reader is attached. There is an Plextor DVD RW on the EIDE controller. I partitioned the Raid disks in 3 NTFS and 1 Ext3 partition. On one NTFS partition Windows 2000 is succesfully running. I want to install Suse 9.0 on an ext3 partition. I downloaded the file 1_ft3xssb19.zip file, containing the FasTrack S150 TX2plus driver for Suse 9.0 from Promise, since the FasTrak 378 OEM controller is the same, according to Promise. I unpacked it and put it on a floppy disk, as the manual says. I put the Suse 9.0 CD #1 in the CD drive, start the PC. The system boots from the CD, while I press the F3 key (as the manual says to do) The Suse Installation screen appears and I Enter on the option "Installation". @@@>The YASt2 should now ask for the floppy. But it does not!<@@@ It does not matter if I insert the floppy before or afterwards. The diskette is read for a second, when inserted. But the module seems not toe be loaded. I tried again with a diskette where the driver module is in the root - no result either. Yast2 does not find my Raid disks, whatever I try. (Error) So Yast givess no configuration proposal. I also tried left Alt key instead of F3 key. I also tried "Installation - safe settings" - no result I also installed "Installation" with ACPI = Off in the boot options - no result I also tried, after a no result installation effort, to click the button "cancel installation. A smaller Main menu window appears. I choose option "Start Installation / system" Then I push OK, select Installation, and Ok again, a menu appears: choose source medium. But choices are CD-Rom, Network, Hard disk When I choose Harddisk I can fill in several partitions. Not any of my choices had result: "error could not mount the specified partition" When I choose CD-Rom and have the F3 key pressed the same useless round starts, with one difference: there is a window asking "confirm driver activation" "Yast2 has detected the following device: Promise Technology Inc (Asustek Computer Inc) Driver module to load" and then there is a window with "pdcraid" I can click OK or cancel. Both to no result. On OK I get a similar window about usb storage and then another one about sbp2 protocol. What should I do wih these? Do I have to enter something? The whole thing drives me raving mad. Please help.. Eveline Bernard 'Denkster'

3 2

Re: [suse-autoinstall] Suse 9.0 on Raid mirror - include external driver module
by Harald.Milz＠computacenter.com 15 Apr '04

15 Apr '04

Is it just me or is this forum more and more used as a generic SuSE support list? Mit freundlichen Gruessen - Best regards Harald Milz Senior Consultant CC CompuNet AG & Co. oHG A part of Computacenter plc Hoerselbergstrasse 7, 81677 Muenchen, Germany Phone: +49 (0)89 45712-161, Fax: -331, Mobile: +49 (0)173 3866604 E-Mail : Harald.Milz(a)computacenter.com Visit us on the Internet: http://www.computacenter.com Visit our Online-Shop: http://www.compunet.de/connect This email is confidential. If you are not the intended recipient, you must not disclose or use the information contained in it. If you have received this mail in error, please tell us immediately by return email and delete the document. suse-autoinstall-return-1815-harald.milz=computacenter.com(a)suse.com on 14.04.2004 18:27:33 To: <suse-autoinstall(a)suse.com> cc: Subject: [suse-autoinstall] Suse 9.0 on Raid mirror - include external driver module -------------------------------------------------------------------------- Please help me install Suse 9 on a new Raid system! It is driving me MAD! I noticed several unsolved issues on this newsforum, about Raid, External modules. Please let some more experienced Linux crack dive into it and solve it, I'm a newbe on Linux. The Yast2 should ask for the external driver module, but it does not. Hèèlup! My system is Asus P4C800-E Deluxe motherboard with Promise FasTrak 378 controller. I attached two Maxtor 80 GB SATA disks in Raid mirror configuration. The system has also an Adaptec 2940 SCSi controller, with Plextor CD-Writer and Iomega Zip 100 drive attached. And to the on-board USB 2.0 controller an multimedia card reader is attached. There is an Plextor DVD RW on the EIDE controller. I partitioned the Raid disks in 3 NTFS and 1 Ext3 partition. On one NTFS partition Windows 2000 is succesfully running. I want to install Suse 9.0 on an ext3 partition. I downloaded the file 1_ft3xssb19.zip file, containing the FasTrack S150 TX2plus driver for Suse 9.0 from Promise, since the FasTrak 378 OEM controller is the same, according to Promise. I unpacked it and put it on a floppy disk, as the manual says. I put the Suse 9.0 CD #1 in the CD drive, start the PC. The system boots from the CD, while I press the F3 key (as the manual says to do) The Suse Installation screen appears and I Enter on the option "Installation". @@@>The YASt2 should now ask for the floppy. But it does not!<@@@ It does not matter if I insert the floppy before or afterwards. The diskette is read for a second, when inserted. But the module seems not toe be loaded. I tried again with a diskette where the driver module is in the root - no result either. Yast2 does not find my Raid disks, whatever I try. (Error) So Yast givess no configuration proposal. I also tried left Alt key instead of F3 key. I also tried "Installation - safe settings" - no result I also installed "Installation" with ACPI = Off in the boot options - no result I also tried, after a no result installation effort, to click the button "cancel installation. A smaller Main menu window appears. I choose option "Start Installation / system" Then I push OK, select Installation, and Ok again, a menu appears: choose source medium. But choices are CD-Rom, Network, Hard disk When I choose Harddisk I can fill in several partitions. Not any of my choices had result: "error could not mount the specified partition" When I choose CD-Rom and have the F3 key pressed the same useless round starts, with one difference: there is a window asking "confirm driver activation" "Yast2 has detected the following device: Promise Technology Inc (Asustek Computer Inc) Driver module to load" and then there is a window with "pdcraid" I can click OK or cancel. Both to no result. On OK I get a similar window about usb storage and then another one about sbp2 protocol. What should I do wih these? Do I have to enter something? The whole thing drives me raving mad. Please help.. Eveline Bernard 'Denkster'

1 0

Excuse me. I accidentely reported a non-spam
by Eveline Bernard 15 Apr '04

15 Apr '04

I want to apologize. I accidentely reported a message as spam, which is not (see below). Can you correct this and please excuse me. thanks, Eveline Bernard The falsely reported message Return-Path: <suse-autoinstall-return-1817-ebernard=denkster.nl(a)suse.com> Received: from viruscheck1.xs4all.nl (viruscheck1.xs4all.nl [194.109.20.101]) by maildrop10.xs4all.nl (8.12.9/8.12.6) with ESMTP id i3EKUOCi011156 for <popde493(a)xs4all.nl>; Wed, 14 Apr 2004 22:30:24 +0200 (CEST) Received: from mxzilla7.xs4all.nl (mxzilla7.xs4all.nl [194.109.24.207]) by viruscheck1.xs4all.nl (8.12.9/8.12.9) with ESMTP id i3EKUNHR016343 for <popde493(a)viruscheck.xs4all.nl>; Wed, 14 Apr 2004 22:30:23 +0200 (CEST) X-XS4ALL-DNSBL-Checked: mxzilla7.xs4all.nl checked 195.135.221.131 against DNS blacklists X-XS4ALL-Pad: empty Received: from lists.suse.com (lists.suse.com [195.135.221.131]) by mxzilla7.xs4all.nl (8.12.10/8.12.10) with SMTP id i3EKUNAi084029 for <ebernard(a)denkster.nl>; Wed, 14 Apr 2004 22:30:23 +0200 (CEST) Received: (qmail 5643 invoked by alias); 14 Apr 2004 20:30:21 -0000 Mailing-List: contact suse-autoinstall-help(a)suse.com; run by ezmlm Precedence: bulk List-Post: <mailto:suse-autoinstall@suse.com> List-Help: <mailto:suse-autoinstall-help@suse.com> List-Unsubscribe: <mailto:suse-autoinstall-unsubscribe-ebernard=denkster.nl@suse.com> List-Subscribe: <mailto:suse-autoinstall-subscribe@suse.com> X-Mailinglist: suse-autoinstall Delivered-To: mailing list suse-autoinstall(a)suse.com Received: (qmail 5633 invoked from network); 14 Apr 2004 20:30:20 -0000 Message-ID: <20040414202203.99773.qmail(a)web61301.mail.yahoo.com> Date: Wed, 14 Apr 2004 13:22:03 -0700 (PDT) From: anna cheng <anna_cheng11(a)yahoo.com> To: suse-autoinstall(a)suse.com MIME-Version: 1.0

1 0

problem using grub for NFS install
by anna cheng 14 Apr '04

14 Apr '04

I have tried this at home and it worked, but for some reasons I was not able to make it to work in my office. My home machine is a Compaq desktop and the machine at work is Dell PowerEdge 1650. I downloaded the grub floppy from http://www.suse.de/~nashif/autoinstall/ and updated menu.lst to use the following. It works like a charm at home. title autoinstall-ip ifconfig --address=172.20.212.51 --server=172.20.212.41 --mask=255.255.255.0 --gateway=172.20.212.1 root (nd) kernel (nd)/linux install=nfs://172.20.212.41/usr/local/SuSE autoyast=nfs://172.20.212.41/usr/local/SuSE/profiles/autoinst.xml ip=172.20.212.51 netmask=255.255.255.0 initrd (nd)/initrd title floppy root (fd0) chainloader +1 However, I updated the IP and use the **same floppy** to test a PowerEdge server at work, it hangs on kernel (nd)/linux install=nfs://172.20.212.41/usr/local/SuSE autoyast=nfs://172.20.212.41/usr/local/SuSE/profiles/autoinst.xml ip=172.20.212.51 netmask=255.255.255.0 Basically after I picked autoinstall-ip from the grub menu, the messages from the console are Booting autoinst-ip ifconfig --address=172.20.212.51 --server=172.20.212.41 --mask=255.255.255.0 --gateway=172.20.212.1 Probing ..[RTL8139]... The PCI BIOS has not enabled this device Updating PCI command 0000->0005. PC_bus 00 pci_device_fn 00 ioaddr 0x0000, addr 00:00:00:00:00:FF 10mbs full-deplex Filesystem is tftp, using whole disk root (nd) kernel (nd)/linux install=nfs://172.20.212.41/usr/local/SuSE autoyast=nfs://172.20.212.41/usr/local/SuSE/profiles/autoinst.xml ip=172.20.212.51 netmask=255.255.255.0 Then it just hangs.... I was not sure whether it was related to the PC BIOS has not been enabled, even I think the version under http://www.suse.de/~nashif/autoinstall/ may already have those options enabled, but I downloaded grub and recompiled with the options --enable-diskless and --enable-rtl8139 and still have the same problem. Have anyone seen this before? and I appreciate any suggestion in fixing the problem. Thanks anna --------------------------------- Do you Yahoo!? Yahoo! Tax Center - File online by April 15th

1 0

AW: [suse-autoinstall] Dynamic partitioning
by itredl＠freudenberg.de 14 Apr '04

14 Apr '04

>> It all depends on what SuSE Linux release you are using. With recent >> releases this might be possible using rules. >> >> Anas > We use SuSE Linux Enterprise Server release 8. Should be recent enough, > shouldn't it? I've just done some research concerning rules with SLES8 and now I'm almost sure that SLES8 does not support them. My assumption comes from the facts that it ignores my rules/rules.xml file, that I didn't find any rules.dtd file and that rules appear in your documentation for 8.2 at first. (suggestion: It would be nice if you provided a changelog which can be reached through your website easily.) Is my assumption - it is only a assumption because I could not find a changelog - true? As I've already mentioned we use SLES8. Since we would need such a solution (and I'm not really willing to write sfdisk-scripts or something like that) I've had another idea: Is it possible to update AutoYast and continue using SLES8? If so, what has to be done? Thanks in advance! Best regards Matthias Redlich

2 1

AW: [suse-autoinstall] Dynamic partitioning
by itredl＠freudenberg.de 14 Apr '04

14 Apr '04

> It all depends on what SuSE Linux release you are using. With recent > releases this might be possible using rules. > > Anas We use SuSE Linux Enterprise Server release 8. Should be recent enough, shouldn't it? Best regards Matthias Redlich

1 0

Dynamic partitioning
by itredl＠freudenberg.de 14 Apr '04

14 Apr '04

Hello list, we use AutoYast for a lot of different server types. Some of them have 32GB harddrives, others have bigger once with 72GB and so on. Thus the partitioning differs from server to server. Currently our linux system, with all its filesystems (/tmp, /usr ..), is about 2GB. The rest of the disk space is used for 10GB partitions for databases. Since we have different harddrives the number of additional 10GB partitions may vary. (example: 32GB means 3 additional partitions; 72GB => 7 additional partitions) Is there a feature (or a simple solution) which makes AutoYast create as much 10GB partitions as possible until the disk is full automatically? Therefore it should detect the size of the disk and then decide how many partitions it can create. Or do we have to change the control file manually? Or do we have to manage this with self-written scripts? Best regards Matthias Redlich

2 1

unable to see info file
by anna cheng 13 Apr '04

13 Apr '04

I understand this may not be an autoinstall program, but I thought some of you may have seen this. I have read the documentation in http://www.suse.com/~nashif/autoinstall and created a floppy which contains an autoinst.xml and info file. I put the first SLES 8 CD in the CDROM and entered autoyast=floppy when the system came up. I put the floppy in the floppy drive and have no problem setting up the machine at home using NFS. However, I was not able to repeat the same setup at work. For some reasons, the machine kept on reporting cannot see info file and tried to start manual install. I tried different settings on autoinst.xml and even use the same settings I have at home (with the IP address updated to reflect the IP address at work), but without success. My home machine is Compaq but my machine at work is Dell PowerEdge 1650. Will this be a problem? ( I have tested including aacraid aic7xxx usb-storage in the kernel_parameter of the autoinst.xml file and I have also tested removing the CDATA portion from the xml file) It failed after "Searching for the infofile", it returned a manual install screen. When I attemtped to do a manual install, it was obvious that the system already knew the IP of the machine and the server, it even knew the serverdir of the software. <?xml version="1.0"?> <!DOCTYPE profile SYSTEM "/usr/share/YaST2/include/autoinstall/profile.dtd"> <profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <configure> <networking> <dns> <dhcp_hostname config:type="boolean">false</dhcp_hostname> <dhcp_resolv config:type="boolean">false</dhcp_resolv> <domain></domain> <hostname></hostname> <nameservers config:type="list"/> <searchlist config:type="list"/> </dns> <interfaces config:type="list"> <interface> <bootproto>static</bootproto> <broadcast>172.20.212.255</broadcast> <device>eth0</device> <ipaddr>172.20.212.51</ipaddr> <module></module> <netmask>255.255.255.0</netmask> <network>172.20.212.0</network> <options></options> <remote_ipaddr></remote_ipaddr> <startmode>onboot</startmode> <wireless>no</wireless> </interface> </interfaces> <routing> <ip_forward config:type="boolean">false</ip_forward> <routes config:type="list"> <route> <destination>default</destination> <device>-</device> <gateway>172.20.212.1</gateway> <netmask>-</netmask> </route> </routes> </routing> </networking> <users config:type="list"> <user> <encrypted config:type="boolean">true</encrypted> <user_password>3ssF48KCbJon2</user_password> <username>root</username> </user> <user> <encrypted config:type="boolean">true</encrypted> <user_password>wxEGdL44Qe4IY</user_password> <username>acheng</username> </user> </users> </configure> <install> <bootloader> <activate config:type="boolean">false</activate> <kernel_parameters></kernel_parameters> <lba_support config:type="boolean">false</lba_support> <linear config:type="boolean">false</linear> <location>mbr</location> </bootloader> <general> <clock> <hwclock>localtime</hwclock> <timezone>US/Eastern</timezone> </clock> <keyboard> <keymap>english-us</keymap> </keyboard> <language>en_US</language> <mode> <confirm config:type="boolean">false</confirm> <forceboot config:type="boolean">false</forceboot> <interactive_boot config:type="boolean">false</interactive_boot> <reboot config:type="boolean">false</reboot> </mode> <mouse> <id>00_ps2</id> </mouse> </general> <software> <addons config:type="list"> <addon>YaST2_modules</addon> <addon>LSB</addon> <addon>sles_admin</addon> <addon>Basis-Devel</addon> <addon>X11</addon> </addons> <base></base> <packages config:type="list"/> </software> <init> <info_file> <![CDATA[ # #start_linuxrc_conf # install nfs://172.20.212.41/usr/local/SuSE/current ip: 172.20.212.51 netmask: 255.255.255.0 gateway: 172.20.212.1 server: 172.20.212.41 serverdir: /usr/local/SuSE/current netdevice: eth0 # #end_linuxrc_conf ]]> </info_file> </init> </install> </profile> thanks anna --------------------------------- Do you Yahoo!? Yahoo! Tax Center - File online by April 15th

1 0

root passwort, sound
by Dominic Lukwata 13 Apr '04

13 Apr '04

Hi all, we autoinstall Suse 9.0. It work better and better but there still some problems: 1. we have not succeeded to set a root passowrd per autoinstall. 2. The sound module makes post installation after the first log in and the Master volume ist at zero. We use the onboard sound on the motherboard ASUS P4P800 Delux Hier ist the sound section in the controll file <sound> <autoinstall config:type="boolean">true</autoinstall> <modules_conf config:type="list"> <module_conf> <alias>snd-card-0</alias> <model>82801DB-ICH4, Intel</model> <module>snd-intel8x0</module> <options> <snd_ac97_clock>0</snd_ac97_clock> <snd_enable>1</snd_enable> <snd_index>0</snd_index> </options> <unique_key>uniq.virtual</unique_key> </module_conf> </modules_conf> <volume_settings config:type="list"> <listentry> <Master config:type="integer">75</Master> </listentry> </volume_settings> </sound> Does any one has any hint how to fix these? Thanks Dominic

3 3

Helge Koehn/Germany/IBM is out of the office.
by Helge Koehn 09 Apr '04

09 Apr '04

I will be out of the office starting 04/08/2004 and will not return until 04/14/2004. I will respond to your message when I return.

1 0

Re: SuSE - Yast2 Autoinstall CD for SLES8
by Robert Pollak 09 Apr '04

09 Apr '04

On Thu, 2004-04-08 at 09:30, s-steins(a)web.de wrote in private mail: > (refering to: http://lists2.suse.com/archive/suse-autoinstall/2004-Feb/0020.html) > > have you now been successful creating a single SLES8-YaST2-Autoinstall-CD from the > CD-Rom-Sources of the 4 CDs which came with the SLES-box? Hello, I'm afraid no. I only managed to create a version of the SLES8-CD (dependent on hd type: ide or scsi) containing the control file. This makes it possible to install SLES8 without floppy with two cd changes and one click of "OK". (SP3 is not necessary for this.) I did not manage to collect the needed rpms on one cd. According to Anas Nashif, "Create iso image" from autoyast2 cannot be used for this, because it only processes packets of one software source. (Since "Create iso image" started working in SP3, we have got three sources: UnitedLinux, SLES8, SP3.) The following approaches were unsuccesful so far: - Collecting the needed packets in one directory and using this as software source for "Create iso image". - Copying rpms from UnitedLinux-cd1 into the custom version of the sles8 cd; changing the package files entries s.t. the rpms are found at the new location. The next thing I had planned was to try it the other way round: to include rpms from sles8 into the UL cd. This could be easier, since the UL cd only contains one "product". But then the task was assigned to a coworker, and I think nothing has happened since then. Let me (and the list) know about your progress - I wish you good luck. -- Robert Pollak GPG Key ID: 748646AD

1 1

autoinst.xml on self-made cd
by Manuel.Laesser＠telekurs.com 07 Apr '04

07 Apr '04

Hello, sorry to bother you again and again. I'm using SLES8 with autoyast2-2.6.44-7 and autoyast2-installation-2.6.44-7. I think this is the latest version for SLES8 (comming with SP3). I copied autoinst.xml to the root of my self-made CD-ROM and I'm using the following parameter in isolinux.cfg # autoyast label autoyast kernel linux append initrd=initrd ramdisk_size=65536 autoyast=default instmode=cd usedhcp=0 textmode=1 If you use parameter "autoyast=default" YaST2 will look for autoinst.xml in the following three places (according to Anas Nashif PDF SLES8 - Automatic Linux Installation and Configuration with YaST2) : 1. the root directory of the floppy disk 2. the root directory of the installation medium (CD-ROM in my case) 3. the root directory of the initial ram disk used to boot the system Cool......unfortunately it doesn't work at all in my environment. I tried with "autoyast=file:/autoinst.xml", "autoyast=file://autoinst.xml", "autoyast=default" I always got this bloody control menu where it asks for the location of the autoinst.xml! From there I could choose http, device, floppy, nfs....but I didn't manage to access the cdrom. If I insert a floppy with my autoinst.xml in the root, the installation is proceeding. I also can edit isolinux.cfg with "autoyast=floppy://autoinst.xml" and it'll find autoinst.xml. Why do I get always very nice and well meant hints from the autoinstall mailing list telling me that the are using "...autoyast= default instmode=cd..." and everything is working fine. Does this have a coherence that I'm using SLES8 with autoyast2-2.6.44-7 and most of people Suse x.x with the newest autoyast2 autoyast2-2.8.14-20 or so..... I'm really stumped.... Any comment is welcome. Regards Manuel p.s. I'll send a box of the finest original swiss chocolate to the one who can give me the right tip to solve this problem...... ;-)) ----------------------------------------------------------- Telekurs Services Hardturmstrasse 201, 8005 Zürich Phone : +41 1 279 44 24 Fax : +41 1 279 34 44 mailto : manuel.laesser(a)telekurs.com -----------------------------------------------------------

2 4

lvm: autoyast complains about wrong lvcreate parameters
by Mathias Pietsch 07 Apr '04

07 Apr '04

hello. when i run an autoyast profile (for suse 8.2) with this lvm-configuration: <lvm config:type="list"> <lvm_group> <lvm_name>HomeVol</lvm_name> <pesize>4M</pesize> <logical_volumes config:type="list"> <lv> <lv_name>Linux_home_lv</lv_name> <lv_size>21296</lv_size> <lv_fs>ext3</lv_fs> <lv_mount>/export</lv_mount> </lv> </logical_volumes> </lvm_group> </lvm> i get the following errors: 1) yast says that on /export are some megabytes of disk space missing and i should deselect some packages (allthough nothing at all will be installed there during installation). and when i continue ... 2) yast complains about wrong lvcreate parameters. but when i run "lvcreate --name Linux_home_lv --size 21296 HomeVol" (these are exactly the parameters that should be used by autoyast, too) manually, the command succeeds and i can continue and finish the installation successfully. from the last line of /var/log/YaST2/y2log i can read that yast thinks the lv_size parameter is 0. (but i have to admit that i hardly can understand the content of these y2log* files). has anyone a clue about what goes wrong here? thanks in advance mp -- ---------------------------------------------------------------- Mathias Pietsch Network and System Administration - Neuroimage Nord, Bldg S10, 3rd Floor, Room 301 Department of Neurology Universitätsklinikum Hamburg-Eppendorf Martinistr. 52 D-20246 Hamburg Germany - Phone: +49-40-42803-8673 Fax: +49-40-42803-9955 Mail: m.pietsch(a)uke.uni-hamburg.de ---------------------------------------------------------------- GnuPG/PGP (http://www.gnupg.org) key id: 644112F2, fingerprint: E37B 77F4 87C7 6309 758D F507 A93C 207C 6441 12F2 ---------------------------------------------------------------- Please avoid sending me Word, Excel or PowerPoint attachments. (see http://www.fsf.org/philosophy/no-word-attachments.html) ----------------------------------------------------------------

1 0

Wireless and Suse 9.0
by Mike Wilson 05 Apr '04

05 Apr '04

New to Linux. Trying to get my Linksys WUSB V2.5 to work with Suse.I tried linux-wlan.org and others. I have missed something somewhere. It is USB and appears to use the prism drivers. I get all that in the configuration, however it never really connects

1 0

Automated install from hard disk
by Peter Jenkins 05 Apr '04

05 Apr '04

All, I'm trying to automate an install where the install media is on a partition of hard disk. Google has been good to me and I have worked out pretty much how to do this, but for one small part. I'm unsure of the correct syntax for "info" file that I've created and placed in the initrd. I've found this: <http://www.suse.de/~nashif/autoinstall/9.0/html/x1808.html> Which should be all I need, but as yet no combination gives me a full automated install. The best info file I've managed is: instmode: hd partition: sda2 rootimage: device://sda2/boot/root installdir: device://sda2 textmode: 1 autoyast: file:///info This fails initially but I'm able to traverse the menus and point the installer to the correct disk partition etc and then off it goes and finds the autoyast file. You'll notice the "device://" in some of the parameters, I've also tried others including "hd://", "file:///" etc. I'd really like to hear from anyone that knows what I'm talking about who can point me in the right direction. Thanks in advance, Peter. -- Peter Jenkins Design & Engineering Team Professional Services EMEA Sun Microsystems Ltd

1 0

AW: [suse-autoinstall] Antwort: RE: [suse-autoinstall] Antwort: A W: [suse-autoinstall] Antwort: [ suse-autoinstall] autoinst
by Lenz, Fabian 03 Apr '04

03 Apr '04

Hello, That was my second question, but now i see that you have edit the isolinux.cfg! instmode=cd is right, my isolinux.cfg looks so # install label linux kernel linux append initrd=initrd ramdisk_size=65536 splash=silent showopts autoyast=default Language=de_DE UseDHCP=0 InstMode=cd and it works fine! Regards Fabian Lenz Azb Fachinformatiker für Systemintegration Deutsche Telekom AG Telekom Training BBi Koblenz Hausadresse: Blücherstr. 6-8, 56073 Koblenz Postanschrift: Postfach 9100, 56065 Koblenz Telefon (mobil): +49 (160) 3565851 E-Mail: mailto:Fabian.Lenz@telekom.de Intranet: http://ttc.telekom.de/ -----Ursprüngliche Nachricht----- Von: Manuel.Laesser(a)telekurs.com [mailto:Manuel.Laesser@telekurs.com] Gesendet: Donnerstag, 1. April 2004 17:02 An: suse-autoinstall(a)suse.com Betreff: [suse-autoinstall] Antwort: RE: [suse-autoinstall] Antwort: AW: [suse-autoinstall] Antwort: [ suse-autoinstall] autoinst Hello Todd Yes, I think your right. If you create an iso image using autoyast the /boot/loader/isolinux.cfg on the cd looks like this: ***************************** default autoyast # autoyast label autoyast kernel linux append initrd=initrd ramdisk_size=65536 autoyast=default instmode=cd usedhcp=0 textmode=1 ... **************************** The "texmode=1" was added by myself. But in this case "instmode=cd" would be wrong.... :-o??. If you go to the PDF of Anas Nashif on page 38/39 it says you should use "autoyast=file:/autoinst.xml" for CD-ROM as well. I'll test if it works whith this option. Regards Manuel Mit freundlichen Grüssen, Manuel Laesser ----------------------------------------------------------- Telekurs Services Hardturmstrasse 201, 8005 Zürich Phone : +41 1 279 44 24 Fax : +41 1 279 34 44 mailto : manuel.laesser(a)telekurs.com -----------------------------------------------------------

3 2

RE: [suse-autoinstall] autoinst.xml on self-made cd
by Ness, Todd 02 Apr '04

02 Apr '04

We spent yesterday trying to get autoinst.xml file to be recognized in / of the cdrom as well, no luck. With package version autoyast2-installation-2.6.41-62 I have made reading xml files from a /profiles directory of the initrd work, with a autoyast=file:/profiles/filename.xml in the isolinux.cfg file. Todd -----Original Message----- From: Manuel.Laesser(a)telekurs.com [mailto:Manuel.Laesser@telekurs.com] Sent: Friday, April 02, 2004 11:11 AM To: suse-autoinstall(a)suse.com Subject: [suse-autoinstall] autoinst.xml on self-made cd Hello, sorry to bother you again and again. I'm using SLES8 with autoyast2-2.6.44-7 and autoyast2-installation-2.6.44-7. I think this is the latest version for SLES8 (comming with SP3). I copied autoinst.xml to the root of my self-made CD-ROM and I'm using the following parameter in isolinux.cfg # autoyast label autoyast kernel linux append initrd=initrd ramdisk_size=65536 autoyast=default instmode=cd usedhcp=0 textmode=1 If you use parameter "autoyast=default" YaST2 will look for autoinst.xml in the following three places (according to Anas Nashif PDF SLES8 - Automatic Linux Installation and Configuration with YaST2) : 1. the root directory of the floppy disk 2. the root directory of the installation medium (CD-ROM in my case) 3. the root directory of the initial ram disk used to boot the system Cool......unfortunately it doesn't work at all in my environment. I tried with "autoyast=file:/autoinst.xml", "autoyast=file://autoinst.xml", "autoyast=default" I always got this bloody control menu where it asks for the location of the autoinst.xml! From there I could choose http, device, floppy, nfs....but I didn't manage to access the cdrom. If I insert a floppy with my autoinst.xml in the root, the installation is proceeding. I also can edit isolinux.cfg with "autoyast=floppy://autoinst.xml" and it'll find autoinst.xml. Why do I get always very nice and well meant hints from the autoinstall mailing list telling me that the are using "...autoyast= default instmode=cd..." and everything is working fine. Does this have a coherence that I'm using SLES8 with autoyast2-2.6.44-7 and most of people Suse x.x with the newest autoyast2 autoyast2-2.8.14-20 or so..... I'm really stumped.... Any comment is welcome. Regards Manuel p.s. I'll send a box of the finest original swiss chocolate to the one who can give me the right tip to solve this problem...... ;-)) ----------------------------------------------------------- Telekurs Services Hardturmstrasse 201, 8005 Zürich Phone : +41 1 279 44 24 Fax : +41 1 279 34 44 mailto : manuel.laesser(a)telekurs.com -----------------------------------------------------------

1 0

AW: Antwort: [suse-autoinstall] AW: Antwort: AW: [suse-autoinstal l] Antwort: RE: [suse-autoinstal l] Antwort: A W: [suse-autoinstall] Antw ort: [ suse-autoinstall] autoinst
by Lenz, Fabian 02 Apr '04

02 Apr '04

Hello! The packages are on Suse Linux CD1 in /suse/noarch/! Change the old packages with the new from the CD, there is the package autoyast..., autoyast-utilities and autoyast-installation, change all! Fabian Lenz Azb Fachinformatiker für Systemintegration Deutsche Telekom AG Telekom Training BBi Koblenz Hausadresse: Blücherstr. 6-8, 56073 Koblenz Postanschrift: Postfach 9100, 56065 Koblenz Telefon (mobil): +49 (160) 3565851 E-Mail: mailto:Fabian.Lenz@telekom.de <mailto:Fabian.Lenz@telekom.de> Intranet: http://ttc.telekom.de/ <http://ttc.telekom.de/> -----Ursprüngliche Nachricht----- Von: Manuel.Laesser(a)telekurs.com [mailto:Manuel.Laesser@telekurs.com] Gesendet: Freitag, 2. April 2004 11:53 An: autoinstall_suse(a)telekurs.com Cc: Lenz, Fabian Betreff: Antwort: [suse-autoinstall] AW: Antwort: AW: [suse-autoinstall] Antwort: RE: [suse-autoinstal l] Antwort: A W: [suse-autoinstall] Antwort: [ suse-autoinstall] autoinst Hello Is it possible to upgrade autoyast2-2.6.44-7 from SLES8 to Version autoyast2-2.8.14-20 from Suse 9.0? I just found some information about autoyast2 2.7.19 (Suse 8.2) which would fix probably my problem with /boot and ext2 instead of ext3. 23 May 2003 RPM autoyast2 2.7.19 (noarch) 673 kB This update fixes the following: -cloning systems with LVM configuration and -execution of perl post-install scripts. -Now it is possible to create a /boot partition as ext3 Additionaly this package has some corrections for the documentation Would I only have to upgrade this package on my Repository Server or are there any dependencies whith package autoyast2? Unfortunately I can't find package 2.8.14 under Suse Linux 9.0. Where would I get this package and all dependencies if necessary? Thank you for your Answer. Mit freundlichen Grüssen, Manuel Laesser ----------------------------------------------------------- Telekurs Services Hardturmstrasse 201, 8005 Zürich Phone : +41 1 279 44 24 Fax : +41 1 279 34 44 mailto : manuel.laesser(a)telekurs.com -----------------------------------------------------------

1 0

AW: Antwort: AW: [suse-autoinstall] Antwort: RE: [suse-autoinstal l] Antwort: A W: [suse-autoinstall] Antwort: [ suse-autoinstall] autoinst
by Lenz, Fabian 02 Apr '04

02 Apr '04

I use the newest version of Autoyast, autoyast2-2.8.14-20, try it with this version, with older version i had have many problems. ;-) Fabian Lenz Azb Fachinformatiker für Systemintegration Deutsche Telekom AG Telekom Training BBi Koblenz Hausadresse: Blücherstr. 6-8, 56073 Koblenz Postanschrift: Postfach 9100, 56065 Koblenz Telefon (mobil): +49 (160) 3565851 E-Mail: mailto:Fabian.Lenz@telekom.de <mailto:Fabian.Lenz@telekom.de> Intranet: http://ttc.telekom.de/ <http://ttc.telekom.de/> -----Ursprüngliche Nachricht----- Von: Manuel.Laesser(a)telekurs.com [mailto:Manuel.Laesser@telekurs.com] Gesendet: Freitag, 2. April 2004 08:25 An: Lenz, Fabian Cc: autoinstall_suse(a)telekurs.com Betreff: Antwort: AW: [suse-autoinstall] Antwort: RE: [suse-autoinstall] Antwort: A W: [suse-autoinstall] Antwort: [ suse-autoinstall] autoinst Hello Fabian Thanx for you help. That's really strange! Why does your isolinux.cfg with "instmode=cd" work? Which version of autoyast do you use? I'm using autoyast2-2.6.44-7 and after the licence agreement I always got the menu to specify the location of the autoinst.xml......anyway, I'll try with "autoyast=file:/autoinst.xml" in my case, hope this will solve MY problems.... :-( Greetings Manuel Mit freundlichen Grüssen, Manuel Laesser ----------------------------------------------------------- Telekurs Services Hardturmstrasse 201, 8005 Zürich Phone : +41 1 279 44 24 Fax : +41 1 279 34 44 mailto : manuel.laesser(a)telekurs.com -----------------------------------------------------------

2 1

AW: [suse-autoinstall] AW: Antwort: AW: [suse-autoinstall] Antwor t: RE: [suse-autoinstal l] Antwort: A W: [suse-autoinstall] Antwort: [ su se-autoinstall] autoinst
by Lenz, Fabian 02 Apr '04

02 Apr '04

OK, this was the newest version 5 weeks ago, i don´t know if there is a newer version! Fabian Lenz Azb Fachinformatiker für Systemintegration Deutsche Telekom AG Telekom Training BBi Koblenz Hausadresse: Blücherstr. 6-8, 56073 Koblenz Postanschrift: Postfach 9100, 56065 Koblenz Telefon (mobil): +49 (160) 3565851 E-Mail: mailto:Fabian.Lenz@telekom.de Intranet: http://ttc.telekom.de/ -----Ursprüngliche Nachricht----- Von: Lenz, Fabian Gesendet: Freitag, 2. April 2004 08:35 An: Manuel.Laesser(a)telekurs.com; suse-autoinstall(a)suse.com Betreff: [suse-autoinstall] AW: Antwort: AW: [suse-autoinstall] Antwort: RE: [suse-autoinstal l] Antwort: A W: [suse-autoinstall] Antwort: [ suse-autoinstall] autoinst I use the newest version of Autoyast, autoyast2-2.8.14-20, try it with this version, with older version i had have many problems. ;-) Fabian Lenz Azb Fachinformatiker für Systemintegration Deutsche Telekom AG Telekom Training BBi Koblenz Hausadresse: Blücherstr. 6-8, 56073 Koblenz Postanschrift: Postfach 9100, 56065 Koblenz Telefon (mobil): +49 (160) 3565851 E-Mail: mailto:Fabian.Lenz@telekom.de <mailto:Fabian.Lenz@telekom.de> Intranet: http://ttc.telekom.de/ <http://ttc.telekom.de/> -----Ursprüngliche Nachricht----- Von: Manuel.Laesser(a)telekurs.com [mailto:Manuel.Laesser@telekurs.com] Gesendet: Freitag, 2. April 2004 08:25 An: Lenz, Fabian Cc: autoinstall_suse(a)telekurs.com Betreff: Antwort: AW: [suse-autoinstall] Antwort: RE: [suse-autoinstall] Antwort: A W: [suse-autoinstall] Antwort: [ suse-autoinstall] autoinst Hello Fabian Thanx for you help. That's really strange! Why does your isolinux.cfg with "instmode=cd" work? Which version of autoyast do you use? I'm using autoyast2-2.6.44-7 and after the licence agreement I always got the menu to specify the location of the autoinst.xml......anyway, I'll try with "autoyast=file:/autoinst.xml" in my case, hope this will solve MY problems.... :-( Greetings Manuel Mit freundlichen Grüssen, Manuel Laesser ----------------------------------------------------------- Telekurs Services Hardturmstrasse 201, 8005 Zürich Phone : +41 1 279 44 24 Fax : +41 1 279 34 44 mailto : manuel.laesser(a)telekurs.com -----------------------------------------------------------

1 0

RE: [suse-autoinstall] Single Disk Network Install - Not Network Boot
by discip＠pjm.com 01 Apr '04

01 Apr '04

Ok, how might I do this with a CD? Where do I put the info file? Which .iso image should I start with to modify? Thanks, Paul -----Original Message----- From: Anas Nashif [mailto:nashif@suse.de] Sent: Monday, January 26, 2004 8:09 PM To: discip(a)pjm.com Cc: suse-autoinstall(a)suse.com Subject: Re: [suse-autoinstall] Single Disk Network Install - Not Network Boot Hi, single floppy disk network install is not possible. You need at least 2 floppies. You need a CD for this. And by the way, even with rh kickstart you cant do that in recent releases. Anas discip(a)pjm.com wrote: > Hey, > I am trying to do an NFS install and would really like to get > everything I need to get this to work onto a single diskette (or CD if > it's absolutely necessary). I'd like to just pop in a floppy, turn on > the machine and have it boot, restart, and be ready to go. As it > stands now, I have all the config setup (info file and autoinst.xml), > but I need to swap 3 floppies first for modules and stuff. Can I get > these all on a single disk? I can do this with Redhat's kickstart. > Any help would be greatly appreciated as I will eventually need to > hand this process off to some less informed individuals who I don't > want to have to mess with lots of disks,etc. > > Thanks a lot, > Paul > -- 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] Antwort: RE: [suse-autoinstall] Antwort: A W: [suse-autoinstall] Antwort: [ suse-autoinstall] autoinst
by Ness, Todd 01 Apr '04

01 Apr '04

Let me know what you come up with, it would be easier to just add autoinst.xml to the root of the CD instead of imbedding in the initrd. -----Original Message----- From: Manuel.Laesser(a)telekurs.com [mailto:Manuel.Laesser@telekurs.com] Sent: Thursday, April 01, 2004 8:02 AM To: suse-autoinstall(a)suse.com Subject: [suse-autoinstall] Antwort: RE: [suse-autoinstall] Antwort: AW: [suse-autoinstall] Antwort: [ suse-autoinstall] autoinst Hello Todd Yes, I think your right. If you create an iso image using autoyast the /boot/loader/isolinux.cfg on the cd looks like this: ***************************** default autoyast # autoyast label autoyast kernel linux append initrd=initrd ramdisk_size=65536 autoyast=default instmode=cd usedhcp=0 textmode=1 ... **************************** The "texmode=1" was added by myself. But in this case "instmode=cd" would be wrong.... :-o??. If you go to the PDF of Anas Nashif on page 38/39 it says you should use "autoyast=file:/autoinst.xml" for CD-ROM as well. I'll test if it works whith this option. Regards Manuel Mit freundlichen Grüssen, Manuel Laesser ----------------------------------------------------------- Telekurs Services Hardturmstrasse 201, 8005 Zürich Phone : +41 1 279 44 24 Fax : +41 1 279 34 44 mailto : manuel.laesser(a)telekurs.com -----------------------------------------------------------

1 0

Re: Re: [suse-autoinstall] Two type network adapters problem
by george_king 01 Apr '04

01 Apr '04

BTW, do you know how to identify the module name used by a network interface? Replyed From: george_king <george_king(a)ustc.edu> > > Hi Georges, > > I have had some similar issues with several network cards in the server. > And I did not find any autoyast option/function to solve it. > The solution I found was a postscript, as you mentionned. > > Now, if you have only one network card to configure, to can proceed that > way: > > 1- identify the Mac address of the used card > 2- identify the module used by this card > 3- configure "nameif" to create "your_eth" ... (man nameif :p ) > 4- create the ifcfg-your_eth file > 5- update /etc/modules.conf with "alias your_eth module" > > it should bypass your iss r>> other modules loaded. > > In case you are relunctant to use nameif... well.. your post script must be > a bit more complex.. > but it is still possible. :)) > > hope it will help. > > > Regards, > Damien. > > > > > > > "george_king" > <george_king(a)ustc.edu> > ustc.edu > To: > 01/04/2004 13:56 "suse-autoinstall" <suse-autoinstall(a)suse.com> > Please respond to cc: > george_king > > > > Subject: > [suse-autoinstall] Two type network adapters problem > > ------------------------------------------------------------------------------------------------------------------------------------------------- > > > > Hi, > > I encounter a problem when I use autoyast to > install a machine with two type network adapters. > > The target machine have two types of network > adapter. Since the number of network adapters is > not fixed, I can not tell autoyast xml file how > many network interface should be configured. I > write a post-install script to config the network > adapter used for network install. What I do is 1) > add alias to modules.conf 2) add ifcfg-eth? files. > > The way can work in most of cases. But in follow > case, it fail -- > during installation, autoyast find three interface > eth0 3c59x > eth1 3c59x > eth2 e100 -- It is for network install. > > My script will add "alias eth2 e100" to > modules.conf. > > When the system reboot, it can not bring up e100 > network adapter. I can make it work by change > "eth2" to eth0 . It seems that kernel think e100 > is "eth0" because 3c59x was not loaded. > > Since network type and network adapter number is > not fixed, i can not make my script to config all > found network adapters. Does autoyast xml can > probe all found network adapter and make > configuration for all of them? If so, what shall > we do? > > > -- > USTC Alumni Email System > > > > > > > > > -- > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > For additional commands, e-mail: suse-autoinstall-help(a)suse.com > > -- USTC Alumni Email System

2 1

Antwort: RE: [suse-autoinstall] Antwort: AW: [suse-autoinstall] Antwort: [ suse-autoinstall] autoinst
by Manuel.Laesser＠telekurs.com 01 Apr '04

01 Apr '04

Hello Todd Yes, I think your right. If you create an iso image using autoyast the /boot/loader/isolinux.cfg on the cd looks like this: ***************************** default autoyast # autoyast label autoyast kernel linux append initrd=initrd ramdisk_size=65536 autoyast=default instmode=cd usedhcp=0 textmode=1 ... **************************** The "texmode=1" was added by myself. But in this case "instmode=cd" would be wrong.... :-o??. If you go to the PDF of Anas Nashif on page 38/39 it says you should use "autoyast=file:/autoinst.xml" for CD-ROM as well. I'll test if it works whith this option. Regards Manuel Mit freundlichen Grüssen, Manuel Laesser ----------------------------------------------------------- Telekurs Services Hardturmstrasse 201, 8005 Zürich Phone : +41 1 279 44 24 Fax : +41 1 279 34 44 mailto : manuel.laesser(a)telekurs.com -----------------------------------------------------------

1 0

RE: [suse-autoinstall] Antwort: AW: [suse-autoinstall] Antwort: [ suse-autoinstall] autoinst
by Ness, Todd 01 Apr '04

01 Apr '04

I believe you have to add it to your initrd file, there are instructions in the list archives for how to add stuff to initrd. -----Original Message----- From: Manuel.Laesser(a)telekurs.com [mailto:Manuel.Laesser@telekurs.com] Sent: Thursday, April 01, 2004 7:35 AM To: suse-autoinstall(a)suse.com Subject: [suse-autoinstall] Antwort: AW: [suse-autoinstall] Antwort: [suse-autoinstall] autoinst Hello Fabian That's exactly what I did! autoinst.xml is in the root of my cd. sles8:/home/tklsa # ls -l /mnt total 4471 dr-xr-xr-x 6 root root 4096 Mar 26 14:00 . drwxr-xr-x 21 root root 4096 Apr 1 2004 .. -r--r--r-- 1 root root 2185477 Mar 26 13:48 ARCHIVES.gz -r--r--r-- 1 root root 1265 Mar 26 13:48 COPYRIGHT -r--r--r-- 1 root root 27878 Mar 26 13:48 COPYRIGHT.yast -r--r--r-- 1 root root 2254127 Mar 26 13:48 ChangeLog -r--r--r-- 1 root root 17205 Mar 26 13:48 INDEX.gz -r--r--r-- 1 root root 17862 Mar 26 13:48 LICENSE.TXT -r--r--r-- 1 root root 742 Mar 26 13:48 README -r--r--r-- 1 root root 810 Mar 29 11:54 TRANS.TBL dr-xr-xr-x 7 root root 2048 Mar 26 13:48 UnitedLinux -r--r--r-- 1 root root 15077 Mar 26 13:48 autoinst.xml dr-xr-xr-x 3 root root 4096 Mar 26 13:49 boot -r--r--r-- 1 root root 2048 Mar 29 11:54 boot.cat -r--r--r-- 1 root root 587 Mar 26 13:48 content -r--r--r-- 1 root root 31479 Mar 26 13:48 ls-lR.gz dr-xr-xr-x 2 root root 2048 Mar 26 13:58 media.1 -r--r--r-- 1 root root 2474 Mar 26 13:48 pubring.gpg dr-xr-xr-x 3 root root 2048 Mar 26 14:00 tk Greetings Manuel Mit freundlichen Grüssen, Manuel Laesser ----------------------------------------------------------- Telekurs Services Hardturmstrasse 201, 8005 Zürich Phone : +41 1 279 44 24 Fax : +41 1 279 34 44 mailto : manuel.laesser(a)telekurs.com -----------------------------------------------------------

1 0

AW: [suse-autoinstall] Antwort: [suse-autoinstall] autoinst
by Lenz, Fabian 01 Apr '04

01 Apr '04

Hello! The autoinst.xml must be in the root directory of the cd. Autoyast search the file in the root directory. the name of the file must be autoinst.xml! -----Ursprungliche Nachricht----- Von: Manuel.Laesser(a)telekurs.com [mailto:Manuel.Laesser@telekurs.com] Gesendet: Montag, 29. Marz 2004 10:52 An: suse-autoinstall(a)suse.com Betreff: [suse-autoinstall] Antwort: [suse-autoinstall] autoinst Hello, today I burn the original iso image created by autoyast to a cd and tried to boot my test server. Unlike the iso image on which I made some changes (see mail before), the system is able to boot from the cd. Unfortunately the automatic installation stops when it comes to the stage of retrieving the xml file. Then I got the follwing error message: Profile for this machine could not be found or retrieved.... I could also enter a path where the file is located. I specified /dev/hdc (cdrom) and also tried with /dev/cdrom without success. Why does autoyast not find my autoinst.xml on the cd? Has anyone a good idea? Thank you very much! Manuel

2 1

Re: Re: [suse-autoinstall] Two type network adapters problem
by damien.selles＠eu.effem.com 01 Apr '04

01 Apr '04

hi again. I found the info somewhere on the web.. I don't remember where: kernel_version=`hostname` pcimap=/lib/modules/$kernel_version/modules.pcimap alldev=$(lspci -n| sed -e 's/^.*:[[:blank:]]\+$[^[:blank:]]\+$.*$/\1/') if [ -n "$alldev" -a -r $pcimap ] then for i in $alldev do vendor="$(echo $i| cut -d':' -f1)" device="$(echo $i| cut -d':' -f2)" all_modules=`grep "0x0000$vendor[[:blank:]]\+0x0000$device" $pcimap \ |awk '{ print $1 }'|sort -u` for module in $all_modules do find /lib/modules/$kernel_version/kernel/drivers/net/ -name \ "$module.o"|grep $module > /dev/null if [ $? = 0 ] then echo $module fi done done fi This should give you what you are looking for. Regards, Damien. "george_king" <george_king(a)ustc.edu> ustc.edu To: 01/04/2004 15:31 "damien.selles" <damien.selles(a)eu.effem.com>, "george_king" <george_king(a)ustc.edu> Please respond to cc: george_king "suse-autoinstall " <suse-autoinstall(a)suse.com> Subject: Re: Re: [suse-autoinstall] Two type network adapters problem --------------------------------------------------------------------------------------------------------------------------------------------------- BTW, do you know how to identify the module name used by a network interface? Replyed From: george_king <george_king(a)ustc.edu> > > Hi Georges, > > I have had some similar issues with several network cards in the server. > And I did not find any autoyast option/function to solve it. > The solution I found was a postscript, as you mentionned. > > Now, if you have only one network card to configure, to can proceed that > way: > > 1- identify the Mac address of the used card > 2- identify the module used by this card > 3- configure "nameif" to create "your_eth" ... (man nameif :p ) > 4- create the ifcfg-your_eth file > 5- update /etc/modules.conf with "alias your_eth module" > > it should bypass your iss r>> other modules loaded. > > In case you are relunctant to use nameif... well.. your post script must be > a bit more complex.. > but it is still possible. :)) > > hope it will help. > > > Regards, > Damien. > > > > > > > "george_king" > <george_king(a)ustc.edu> > ustc.edu > To: > 01/04/2004 13:56 "suse-autoinstall" <suse-autoinstall(a)suse.com> > Please respond to cc: > george_king > > > > Subject: > [suse-autoinstall] Two type network adapters problem > > ------------------------------------------------------------------------------------------------------------------------------------------------- > > > > Hi, > > I encounter a problem when I use autoyast to > install a machine with two type network adapters. > > The target machine have two types of network > adapter. Since the number of network adapters is > not fixed, I can not tell autoyast xml file how > many network interface should be configured. I > write a post-install script to config the network > adapter used for network install. What I do is 1) > add alias to modules.conf 2) add ifcfg-eth? files. > > The way can work in most of cases. But in follow > case, it fail -- > during installation, autoyast find three interface > eth0 3c59x > eth1 3c59x > eth2 e100 -- It is for network install. > > My script will add "alias eth2 e100" to > modules.conf. > > When the system reboot, it can not bring up e100 > network adapter. I can make it work by change > "eth2" to eth0 . It seems that kernel think e100 > is "eth0" because 3c59x was not loaded. > > Since network type and network adapter number is > not fixed, i can not make my script to config all > found network adapters. Does autoyast xml can > probe all found network adapter and make > configuration for all of them? If so, what shall > we do? > > > -- > USTC Alumni Email System > > > > > > > > > -- > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > For additional commands, e-mail: suse-autoinstall-help(a)suse.com > > -- USTC Alumni Email System

1 0

Re: [suse-autoinstall] Two type network adapters problem
by damien.selles＠eu.effem.com 01 Apr '04

01 Apr '04

Hi Georges, I have had some similar issues with several network cards in the server. And I did not find any autoyast option/function to solve it. The solution I found was a postscript, as you mentionned. Now, if you have only one network card to configure, to can proceed that way: 1- identify the Mac address of the used card 2- identify the module used by this card 3- configure "nameif" to create "your_eth" ... (man nameif :p ) 4- create the ifcfg-your_eth file 5- update /etc/modules.conf with "alias your_eth module" it should bypass your issue with the eth number that can depend on the other modules loaded. In case you are relunctant to use nameif... well.. your post script must be a bit more complex.. but it is still possible. :)) hope it will help. Regards, Damien. "george_king" <george_king(a)ustc.edu> ustc.edu To: 01/04/2004 13:56 "suse-autoinstall" <suse-autoinstall(a)suse.com> Please respond to cc: george_king Subject: [suse-autoinstall] Two type network adapters problem ------------------------------------------------------------------------------------------------------------------------------------------------- Hi, I encounter a problem when I use autoyast to install a machine with two type network adapters. The target machine have two types of network adapter. Since the number of network adapters is not fixed, I can not tell autoyast xml file how many network interface should be configured. I write a post-install script to config the network adapter used for network install. What I do is 1) add alias to modules.conf 2) add ifcfg-eth? files. The way can work in most of cases. But in follow case, it fail -- during installation, autoyast find three interface eth0 3c59x eth1 3c59x eth2 e100 -- It is for network install. My script will add "alias eth2 e100" to modules.conf. When the system reboot, it can not bring up e100 network adapter. I can make it work by change "eth2" to eth0 . It seems that kernel think e100 is "eth0" because 3c59x was not loaded. Since network type and network adapter number is not fixed, i can not make my script to config all found network adapters. Does autoyast xml can probe all found network adapter and make configuration for all of them? If so, what shall we do? -- USTC Alumni Email System

1 0

Two type network adapters problem
by george_king 01 Apr '04

01 Apr '04

Hi, I encounter a problem when I use autoyast to install a machine with two type network adapters. The target machine have two types of network adapter. Since the number of network adapters is not fixed, I can not tell autoyast xml file how many network interface should be configured. I write a post-install script to config the network adapter used for network install. What I do is 1) add alias to modules.conf 2) add ifcfg-eth? files. The way can work in most of cases. But in follow case, it fail -- during installation, autoyast find three interface eth0 3c59x eth1 3c59x eth2 e100 -- It is for network install. My script will add "alias eth2 e100" to modules.conf. When the system reboot, it can not bring up e100 network adapter. I can make it work by change "eth2" to eth0 . It seems that kernel think e100 is "eth0" because 3c59x was not loaded. Since network type and network adapter number is not fixed, i can not make my script to config all found network adapters. Does autoyast xml can probe all found network adapter and make configuration for all of them? If so, what shall we do? -- USTC Alumni Email System

1 0