April 2005 - openSUSE Autoinstall - openSUSE Mailing Lists

Re: Re: [suse-autoinstall] Re: How to set up PXE server?
by Magnus Gedda 08 Apr '05

08 Apr '05

Hello! Im trying to follow the PXE HOW-TO for installing SuSE 9.2 on my brand new IBM Thinkpad X40. I have set up the tftp-server, copied pxegrub to the tftpboot directory, added the suggested lines to the dhcp server configuration (Im pretty sure the bootp client gets an ID, dhcp server allows IPs 192.168.0.200-204), copied the kernel and the initrd to to the tftp directory and created the sample menu.lst in the tftp boot directory. The first suggested change of the menu.lst is not done yet, since I havent found out the module name of the network card yet, but I still think that the actions above would present me with a grub bootloader screen on my X40 when booting over LAN. As connection between my X40 and my server I use a cross-connected TP cable. Now to the problem. When I boot my X40 over LAN I get the following messages: _____messages_start___________________________________________ Intel(R) Boot Agent GE v1.2.17 Copyright (C) 1997-2003, Intel Corporation Intel(R) Boot Agent PXE Base Code (BA1217BC) Copyright (C) 1997-2003, Intel Corporation CLIENT MAC ADDR: <macaddr> GUID: <guid> CLIENT IP: 192.168.0.203 MASK: 255.255.255.0 DHCP IP: 192.168.0.2 GATEWAY IP: 192.168.0.2 Probing...[RTL8139] - The PCI BIOS has not enabled this service! Updating PCI command 0106->0107. pci_bus 00 pci_device_fn 00 PCI latency timer (CFLT) is unreasonably low at 0. Setting to 32 clocks. ioaddr 0X0000, addr AA:AA:00:00:AA:AA 10Mbps full-duplex _____messages_end_____________________________________________ It seems that the dhcp service works since the client gets an IP of 192.168.0.203, but after that Im completely at a loss. Can anyone please help me figure out what is wrong and why I dont get the menu screen? What is the client probing for, and what is RTL8139? I cannot find anything about it in the BIOS, so haw do I enable it? Any help at all would be greatfully appreciated! Sincerely, Magnus Gedda

2 1

partitioning problem.
by Chuck Clark 07 Apr '05

07 Apr '05

I'm getting an error during the partitioning process of the autoyast install. I have the following partition definitions and it complains that it could not do the partitioning plan and to check the control file. SuSE 8.2. <drive> <device>/dev/sda</device> <use>all</use> <partitions config:type="list"> <partition> <size>1gb</size> <mount>swap</mount> </partition> <partition> <size>5gb</size> <mount>/</mount> </partition> <partition> <size>max</size> <mount>/other</mount> </partition> </partitions> </drive> Any help will be greatly appreciated. Thanks in advance, Chuck

1 0

Problems donwloading driverupdate-SLES8
by Ivor Terret 07 Apr '05

07 Apr '05

Hello list I am trying to install SLES8 for x86 SP 3or SP4 over network using http. Autoyast starts ok, but when i reach the "software configuration" stage, it exits with "error with your software selection" My setup is according to the SuSE documentation, both in the HOWTO and on the WWW. It seems that the client os not requesting the driverupdate file at all. What determines if the client requests the driverupdate file or not? The last error entry in the /var/log/Yast2/y2log complains about /media.1/product but wget retrieves this ok. Thanks Ivor

1 1

UpdateDir:
by Radzai, Bridgette A. 06 Apr '05

06 Apr '05

Can someone tell me what the UpdateDir: parameter in used for in the linuxrc.config file? It is a default parameter and is set to /linux/suse/i386-sles9 I could not find it documented anywhere. Thanks, Bridgette

1 0

RE: [suse-autoinstall] Yast, autoyast, LDAP and home/small company networking
by Schumacher, Gordon 06 Apr '05

06 Apr '05

I don't know if this is a good solution for you... but if your requirement is mainly to get the package selection the same, a simpler thing that using AutoYaST would be to configure your package selection, and then save the list out to a floppy (YaST can do that). -----Original Message----- From: Birger Kollstrand [mailto:birger.kollstrand@losmail.no] Sent: Monday, March 28, 2005 5:08 AM To: suse-autoinstall(a)suse.com Subject: [suse-autoinstall] Yast, autoyast, LDAP and home/small company networking Hi, I have looked around on the SuSE web nad searched the lists to find information on Yast and home/small company network setup. I have com up short on a couple of areas and would very much appreciate som help and guidance. Please redirect me to other mailing lists if this is not the right place. Here is what I want to accomplish on my 8 machine home network first. 1. Authenticate users towards OpenLDAP (or eDirectory) 2. Automount the home directories 3. Add roming possibility so the users can log on while not beeing able to contact the LDAP server. For this I have been thinking of using the http://www.padl.com/OSS/nss_updatedb.html . 4. I want to do this to new machines via autoyast. All machines are different so generating an immage is not good. 5. I want to be able to add necesary SW/Config already configured machines automagically. Now I have accomplished to set up the OpenLDAP server ( although there was no YAST module for that) and I have via YAST set up a client to successfully authenticate towards the OpenLDAP server. In the YAST module I have ticked of the "Start Automounter", but the home directory is not mounted upon login. I can mount the home directory manually without any problems. So the questions are : 1. What does the "Start Automounter" setting actually mean? 2. Is the nss_updatedb the right way to go to achieve the possibility for local login? 3. Can autoyast be used to achieve point 4 and 5 above? (What is the best documentation for autoyast? http://www.novell.com/documentation/nld/index.html?page=/documentation/nld/… ?) 4. There is no mailinglist for Yast. Is it possible to get in contact with the maintainer to discuss enhancements? I'm willing to test and (with my limited c++/qt skills) develop aditions in this area. regards Birger Kollstrand -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

Too long append-line for pxe-installation
by Ragnar Kjørstad 06 Apr '05

06 Apr '05

Hi We have encountered a problem where the append-line for kernel-arguments for the install-kernel (PXE-boot) exceeds 255 characters. Is there any way we can shorten the commandline by moving some of the arguments into the autoyast-file? We currently use the following options: - load_ramdisk - initrd - autoyast - install - netdevice - gateway - nofb - textmode In particular, the "install"-option takes up a lot of characters (with a long nfs-url). -- Ragnar Kjørstad Software Engineer Scali - http://www.scali.com High Performance Clustering

3 4

RE: [suse-autoinstall] Too long append-line for pxe-installation
by Ness, Todd 05 Apr '05

05 Apr '05

There should be plenty of mail on this in the archive, but, look at using the info file in the initrd. -----Original Message----- From: Ragnar Kjørstad [mailto:suse@ragnark.vestdata.no] Sent: Tuesday, April 05, 2005 7:29 AM To: suse-autoinstall(a)suse.com Subject: [suse-autoinstall] Too long append-line for pxe-installation Hi We have encountered a problem where the append-line for kernel-arguments for the install-kernel (PXE-boot) exceeds 255 characters. Is there any way we can shorten the commandline by moving some of the arguments into the autoyast-file? We currently use the following options: - load_ramdisk - initrd - autoyast - install - netdevice - gateway - nofb - textmode In particular, the "install"-option takes up a lot of characters (with a long nfs-url). -- Ragnar Kjørstad Software Engineer Scali - http://www.scali.com High Performance Clustering -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

OES for Linux - network autoinstall problem
by John Line 05 Apr '05

05 Apr '05

I've been doing some preparation for (PXE+HTTP) network installation of a group of new servers (soon to be ordered, don't have them yet) using VMware (V5 beta, with host system running SuSE 9.2 Professional). I was originally installing SLES9 but switched to an evaluation download of OES for Linux (i.e. SLES9 + extras) when that became available. This is using PXE boot and HTTP access to the installation source. [I suspect those details aren't relevant to the problem, but mentioned "just in case".] The fairly basic (so far!) autoinstallation configuration that worked fine with SLES9 also mostly worked with OES, but one significant detail (that I've noticed so far, there may be others) fails consistently without any explanation or comment that I've seen. [Side-issue: is there any documentation of changes and additions to the available XML configuration settings, for OES as compared to SLES9? The DTDs show what differs at the syntactic level, but that's only half the story.] The problem is with nameserver configuration - with SLES9, that "just worked" but with OES it simply fails to create /etc/resolv.conf with the obvious effects on network access. Other aspects of the network configuration (e.g. setting up static IP addresses and default router, and enabling the network) *did* work in OES, the effect is as though something simply forgot to install the nameserver configuration. The namserver-related part of the configuration that's currently getting ignored is <dns> <dhcp_hostname config:type="boolean">false</dhcp_hostname> <dhcp_resolv config:type="boolean">false</dhcp_resolv> <domain>mynet</domain> <hostname>oestest</hostname> <nameservers config:type="list"> <nameserver>131.111.8.32</nameserver> <nameserver>131.111.12.20</nameserver> </nameservers> <searchlist config:type="list"> <search>mynet</search> <search>cam.ac.uk</search> </searchlist> </dns> Has anyone else seen this problem? Is there any better solutio than creating the missing file by using a postinstall script? I tried recreating the network configuration definitions for autoinstallation, using yast after manually installing OES, but I don't think it was any different from what I'd been trying and it made no difference anyway, resolv.conf still not created - so the obvious possibility, that the required XML definitions had changed incompatibly for OES - seems to be ruled out as an explanation. John Line -- John Line - web & news development, University of Cambridge Computing Service

1 0

Autoyast
by Chuck Clark 04 Apr '05

04 Apr '05

Greetings- I have attempted many times to set up the auto install and it continues to give me a problem. I've modified the initrd, I've modified the isolinux.cfg, I've created a simple info file and have the autoinst.xml. Yet it still continues to look for the first disk ??? I've created a directory structure as follows: Boot/ Bootdisk Loader/ Autoinst.xml Initrd Isolinux.bin Isolinux.cfg Linux message Infofile Suse/ I586/ I686/ Noarch/ Setup/ My goal is to create my own distro. With the rpms that I need, is this possible? Thanks ahead of time for the help. Chuck

1 0

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