Oooh, I don't know, Gordon. I've only tried them (and they work) with SLES9 SP1, using the "update" directory that's created by Anas' script in the installation source. -----Original Message----- From: Schumacher, Gordon [mailto:gordon_schumacher@maxtor.com] Sent: Friday, April 01, 2005 1:32 PM To: Anas Nashif Cc: suse-autoinstall@suse.com Subject: RE: [suse-autoinstall] Network Ports and /etc/sysconfig/network Out of curiosity - will those RPMs work with SuSE 9.2? -----Original Message----- From: Suffin, Charles [mailto:Charles.Suffin@stratus.com] Sent: Wednesday, March 23, 2005 3:07 PM To: 'Anas Nashif' Cc: suse-autoinstall@suse.com Subject: RE: [suse-autoinstall] Network Ports and /etc/sysconfig/network Anas, Looks good now!!! You've really helped me out. The latest batch of RPMs create the files in /etc/sysconfig/network and they contain all the correct information, including the "UNIQUE=" data. Thank you so much for your assistance in getting this resolved. -- Charlie -----Original Message----- From: Anas Nashif [mailto:nashif@suse.de] Sent: Friday, March 18, 2005 12:28 PM To: Suffin, Charles Cc: suse-autoinstall@suse.com Subject: Re: [suse-autoinstall] Network Ports and /etc/sysconfig/network Hi, There is an update pending you might want to try which fixes some issues with network and autoyast. See http://www.suse.de/~nashif/autoyast2/rpms/sles9/sles9-i386/ You will need all rpms. Create a new source with those updates using the script: http://www.suse.de/~nashif/autoyast2/scripts/create_update_source.sh and put all the above rpms in there. Dont forget to run create_package_descr after you have copied the rpms. then, you will need something like that: <interfaces config:type="list"> <interface> <bootproto>dhcp</bootproto> <device>eth0</device> <startmode>onboot</startmode> </interface> <interface> <bootproto>dhcp</bootproto> <device>eth1</device> <startmode>onboot</startmode> </interface> </interfaces> <modules config:type="list"> <module_entry> <device>eth0</device> <module>e1000</module> </module_entry> <module_entry> <device>eth1</device> <module>e100</module> </module_entry> </modules> Please report if that works for you. Anas Suffin, Charles wrote:

Hi folks,

It seems that the auto-installation of network ports (which are described in the XML control file) doesn't create files in /etc/sysconfig/network. However, if you run YaST2 Network Devices (left) Network Card (right) and add a network port, a file in /etc/sysconfig/network like ifcfg-eth-id-AA:BB:CC:DD:EE:FF is created -- the name corresponds to the MAC address of the card.

Here's a snippet from my XML. Anyone know why auto-install isn't creating the file(s) in /etc/sysconfig/network? Or, do you know what source code I should look at to figure this out? :

<interfaces config:type="list"> <interface> <bootproto>dhcp</bootproto> <device>eth0</device> <startmode>onboot</startmode> </interface> <interface> <bootproto>dhcp</bootproto> <device>eth1</device> <startmode>onboot</startmode> </interface> </interfaces> <modules config:type="list"> <module_entry> <device>bus-pci-0000:01:03.0</device> <module>e1000</module> </module_entry> <module_entry> <device>bus-pci-0000:01:06.0</device> <module>e100</module> </module_entry> </modules>

-- Charlie

p.s./ I'm talking about auto-installation of SLES9 and SLES9-SP1.

----- A. Charles Suffin Senior Software Engineer Stratus Technologies, Inc. (http://www.stratus.com) 111 Powdermill Road Maynard, MA 01754-3409 US (978)461-7590

-- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com