April 2005 - openSUSE Autoinstall - openSUSE Mailing Lists

RE: [suse-autoinstall] SLES9 Installation Tree
by Radzai, Bridgette A. 04 Apr '05

04 Apr '05

Frank, Thank you for the information. One major issue is my source installation server is a Windows server, so I am unable to use the great tools that yast supplies to do this. One thought I had has to create a Sles9 server and use yast to create my Sles9 SP1 directory tree. Then copy it all to my Windows server. Any thoughts? What will Windows do with the symbolic links? Any other suggestions? I am even seeing issues with my boot CD since I changed the "Linux" and "initrd" files to the SP1 versions. I am so close, but yet so far with this whole project. It seems so straight forward, but I can't get it to work. Thanks for the help! Bridgette -----Original Message----- From: Frank Steiner [mailto:fsteiner-mail@bio.ifi.lmu.de] Sent: Friday, April 01, 2005 7:12 AM To: Radzai, Bridgette A. Cc: suse-autoinstall(a)suse.com Subject: Re: [suse-autoinstall] SLES9 Installation Tree I had the same problem as you can see in the archives. It seems that things can go wrong if you set up your installation directory manually and then try to integrate the SP1 stuff. Rename you current directory, and setup the installation sources again with yast. Then also add the SP1 sources with yast. Then it should work, and will still continue working if you rename the directories (fixing their names in the yast (inst)order, too) afterwards. I could even remove the CD? subdirectories and put all the stuff in the same directory, i.e., just having sles9/ and sles9-SP1/ directories with no further CD? subdirectories. SDK sources could not be added with yast, I added them manually after renaming the subdirs. And that worked fine. 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. *

3 2

RE: [suse-autoinstall] Network Ports and /etc/sysconfig/network
by Schumacher, Gordon 04 Apr '05

04 Apr '05

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(a)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(a)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(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

2 1

RE: [suse-autoinstall] autoyast missing packages when creating iso
by Schumacher, Gordon 04 Apr '05

04 Apr '05

If I'm not mistaken, this is because you've upgraded packages (with something like YOU). I did this, and I had to remove part of the revision number. For instance, in your example below, you'd want: ./suse/i586/3ddiag-0.703.i586.rpm ./suse/i586/BASS-20030801.i586.rpm You should be able to do that with a regex search-and-replace. -----Original Message----- From: Martyn Iles [mailto:martyn@kryten.org] Sent: Friday, March 25, 2005 4:19 AM To: suse-autoinstall(a)suse.com Subject: [suse-autoinstall] autoyast missing packages when creating iso I'm having a problem when trying to create an automatic install of SuSE to put on CDROM. This is SuSE 9.0, if that makes any difference. I go through AutoYaST, tell it to clone my config and then select the Create ISO option, but then I get: Missing Packages ./suse/i586/3ddiag-0.703-172.i586.rpm ./suse/i586/BASS-20030801-55.i586.rpm Plus loads of others Now, I've got the entire SuSE 9.0 (all 7Gb) on an FTP server of mine and if I go into YaST and install extra packages, they install fine. Note that this was NOT where I installed from - I used a remote ftp mirror for the install as my local copy hadn't finished downloading so I've been into Yast and changed the installation source (could autoyast be picking up the path to the original RPMS from somewhere?). If I ftp to the machine and cd to the directories listed above its fine: ftp> cd ./suse 250 CWD command successful. ftp> ls 200 PORT command successful. 150 Opening ASCII mode data connection for file list. i586 i686 noarch nosrc setup src 226 Transfer complete. ftp: 39 bytes received in 0.00Seconds 39000.00Kbytes/sec. ftp> cd i586 250 CWD command successful. ftp> ls 3dd* 200 PORT command successful. 150 Opening ASCII mode data connection for file list. 3ddiag-0.703-172.i586.rpm 226 Transfer complete. ftp: 27 bytes received in 2.12Seconds 0.01Kbytes/sec. ftp> So, any suggestions for what I've done wrong? I've spent over a day on this, had the SuSE available on multiptle FTP/HTTP sites and I just cannot get it to work! Does AutoYaST actually work (I've tried this on two different SuSE 9.0 machines)? If not, how else can I clone a SuSE 9.0 install so that it can be installed (without much user intervention) on multiple machines from a CDROM? -- 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] Network Ports and /etc/sysconfig/network
by Suffin, Charles 01 Apr '05

01 Apr '05

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(a)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(a)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(a)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(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

SLES9 Installation Tree
by Radzai, Bridgette A. 01 Apr '05

01 Apr '05

I have integrated SP1 into my current sles9 MS directory structure as outlined in Anas' 2/05/05 posting to Egan. I have updated my boot cd with the "linux" and "initrd" from the sp1 CD1. Modified the linuxrc.config. I believe something is incorrect with my directory structure, the installation server is found, loads the SUSE SLES CD1 successfully, but when it tries to find SUSE CORE CD1 I get: Insert 'SUSE LINUX Enterprise Server 9 CD2' URL http://...../sles9_x86/SUSE-SLES-Version-9/CD1 SuSE Linux = SuSE Linux AG 2000040702202411 ! = 20040702201519 Did my media.1 folders not get copied correctly? Thanks in advance for the assistance! Bridgette

2 1

Re: [suse-autoinstall] SLES9 Installation Tree
by Alfred Isele 01 Apr '05

01 Apr '05

Hi Bridgette, We run a remote autoyast installation started via pxeboot. See below out directory structure, media files ... Hope this will help you. Regards Alfred autoyast yast SLES/CD1 SP1/CD1 SP1/CD2 SP1/SP3 CORE/CD1 CORE/CD2 CORE/CD3 CORE/CD4 CORE/CD5 boot -> SLES/CD1/boot content -> SLES/CD1/content control.xml -> SLES/CD1/control.xml driverupdate -> SP1/CD1/driverupdate linux -> SP1/CD1/linux media.1 -> SLES/CD1/media.1 # cat SLES/CD1/media.?/media SuSE Linux AG 20040702202411 1 MEDIA1 SUSE LINUX Enterprise Server 9 CD1 # cat SP1/CD?/media.?/media SuSE Linux AG 20050117203108 3 SuSE Linux AG 20050117203108 SuSE Linux AG 20050117203108 # cat CORE9/CD?/media.?/media SuSE Linux AG 20040702201519 5 SuSE Linux AG 20040702201519 SuSE Linux AG 20040702201519 SuSE Linux AG 20040702201519 SuSE Linux AG 20040702201519 # cat yast/order # entries here are tab delimited! /SP1/CD1 /SP1/CD1 /SLES/CD1 /SLES/CD1 /CORE9/CD1 /CORE9/CD1 # cat yast/instorder /SP1/CD1 /SLES/CD1 /CORE9/CD1 At 23:33 31.03.2005, Radzai, Bridgette A. wrote: >I have integrated SP1 into my current sles9 MS directory structure as >outlined in Anas' 2/05/05 posting to Egan. > >I have updated my boot cd with the "linux" and "initrd" from the sp1 >CD1. Modified the linuxrc.config. > >I believe something is incorrect with my directory structure, the >installation server is found, loads the SUSE SLES CD1 successfully, > >but when it tries to find SUSE CORE CD1 I get: > > > >Insert 'SUSE LINUX Enterprise Server 9 CD2' > >URL http://...../sles9_x86/SUSE-SLES-Version-9/CD1 > >SuSE Linux = SuSE Linux AG > >2000040702202411 ! = 20040702201519 > > > >Did my media.1 folders not get copied correctly? > > > >Thanks in advance for the assistance! > > > >Bridgette > >

1 0