openSUSE Autoinstall June 2004

autoinstall@lists.opensuse.org

46 participants
63 discussions

Fw: autoyast and loadorder of modules
by Helge Koehn 10 Jun '04

10 Jun '04

... any ideas to that problem from march?! till now not one answer :-( helge. ----- Forwarded by Helge Koehn/Germany/IBM on 06/09/2004 11:57 AM ----- Helge Koehn/Germany/IBM To 03/08/2004 03:14 suse-autoinstall(a)suse.com PM cc Subject autoyast and loadorder of modules hi, we face a problem where we have to load kernelmodules in a specific order to get our scsi devices recognized correctly! we are doing an autoyastinstallation via pxe. we send with the append parameter in the pxe-config file the modules to load, that works. our scsi device are recognized in the correct order. in the autoyast.xml we are partitioning the scsi devices and write the bootloader to /dev/sda. the stuff from disk 1 is transfered to the installed system. after the first initial boot, the order we have with the append parameter in the pxe-config file no longer works, autoyast has build its own initrd for the initial boot and with that the devices are changing because of loading the adapterdrivers in the wrong order! how can we arrange that our wanted order of devices also works after the initial boot. so that /dev/sda remains /dev/sda and not switches to /dev/sdb thanks for an answer. helge.

3 4

how is the extra_prov file made
by Richard Bos 10 Jun '04

10 Jun '04

I wonder how the EXTRA_PROV files is being made, that is required by create_package_descr? Another thing I would like to know is why the information is actually needed by create_package_descr or is it YPM that needs this information? How does the information influence the behaviour of YPM? I understand that it could be needed as e.g: # rpm -q --whatprovides /bin/sh bash-2.05b-96 bug the other way around does not work: # rpm -q --provides bash (I would expect /bin/sh here) Is EXTRA_PROV made manually? Also in 9.1 the rpm kdebase3-SuSE provides an EXTRA_PROV too. This one and the one in suse/setup/description are rather different. Is this intended? Why not use the Provides tag in the rpm to store this information and use that?? It would be easy for suse rpm contributors to support this too => Would that make it easier to provide yast enabled rpm repositories? -- Richard Bos Without a home the journey is endless

4 4

RE: [suse-autoinstall] RE: How Do I Get Rid Of DHCP!!?! -- Same P roblem in 9.1
by discip＠pjm.com 09 Jun '04

09 Jun '04

This doesn't seem to help. I tried both netsetup=0 and netsetup=-dhcp. Now pops up a window and tells me "your network has already been configured. Do you want to keep this configuration?". Then when I say yes, it tries to DHCP again. :-( Paul -----Original Message----- From: Anas Nashif [mailto:nashif@suse.de] Sent: Wednesday, June 09, 2004 12:03 PM To: discip(a)pjm.com Cc: suse-autoinstall(a)suse.com Subject: Re: [suse-autoinstall] RE: How Do I Get Rid Of DHCP!!?! -- Same Problem in 9.1 This is something new in 9.1/SLES9. Add netsetup=0 to skip DHCP. 3. Advanced Network Setup The netsetup keyword allows advanced network configurations and enables dialogs to setup the network where required. netsetup=1 the normal network setup questions netsetup=xxx,yyy just xxx and yyy netsetup=+xxx,-yyy default, additionally xxx, but not yyy xxx could have the following values: dhcp, hostip, gateway, netmask, nameserver. nameserverN asks for N nameservers (max. 4). For example, the following can be entered on the command line: netsetup=-dhcp,+nameserver3 discip(a)pjm.com wrote: > No matter what I do to the info file, I still can't get linuxrc to not > try to do dhcp on eth0. I look at console number 2 and I see that it > has even configured eth0 with the right IP parameters, but it tries to > do DHCP anyway. I am trying this with 9.1 now. Same behavior. What > gives? > > Paul > > P.S. If you care, my info file looks like this: > > insmod: 3c59x > netdevice: eth0 > DHCP: 0 > HostIP: 192.168.1.5 > netmask: 255.255.255.0 > gateway: 192.168.1.1 > server: 192.168.1.18 > autoyast: nfs://192.168.1.18/opt/Linux/SUSE-9/profiles/test.xml >

2 1

Patterned installs
by Jesse Pretorius 09 Jun '04

09 Jun '04

Hi to all, Thank you for the help with the previous request - I have come quite a way since then. I'd like to know if it's possible to use the existing patterned installations provided in the distribution. Eg SUSE LINUX Desktop has an 'Enterprise Template' and 'GNOME Desktop' pattern. I'd like to use these as the basis for my software selection and make some minor modifications. Any insight would be appreciated. Jesse

1 0

RE: How Do I Get Rid Of DHCP!!?! -- Same Problem in 9.1
by discip＠pjm.com 09 Jun '04

09 Jun '04

No matter what I do to the info file, I still can't get linuxrc to not try to do dhcp on eth0. I look at console number 2 and I see that it has even configured eth0 with the right IP parameters, but it tries to do DHCP anyway. I am trying this with 9.1 now. Same behavior. What gives? Paul P.S. If you care, my info file looks like this: insmod: 3c59x netdevice: eth0 DHCP: 0 HostIP: 192.168.1.5 netmask: 255.255.255.0 gateway: 192.168.1.1 server: 192.168.1.18 autoyast: nfs://192.168.1.18/opt/Linux/SUSE-9/profiles/test.xml

2 1

PXE-based autoinstallation setup
by Jesse Pretorius 09 Jun '04

09 Jun '04

> Hi to all, > > I'm busy trying to setup a PXE-based auto-installation of SUSE LINUX > Desktop. > > Part of the instructions indicate that I should have 'initrd', > 'pxelinux.0', and 'linux' in the /tftpboot/ directory, and that I should > be able to find 'initrd' and 'linux' in the /suse/images/boot directory of > any of the SLES CD's. > I didn't find them there - I did find them in /boot/loader though. Are > these the same files that I need? > > Also, I don't seem to find 'pxelinux.0' anywhere. can someone point me to > it, or if I need to build it can you please point me to a helpful > resource? > > Thanks, > > Jesse

3 2

AW: [suse-autoinstall] PXE-based autoinstallation setup
by Martin.Linten＠rzf.fin-nrw.de 09 Jun '04

09 Jun '04

Hi Jesse, The file pxelinux.0 is part of the syslinux package. (.rpm) The files linux and initrd can be found in /boot/loader. These are the correct files. I think the Docs http://www.suse.de/~nashif/autoinstall/ quite helpful. Greetings, Martin -----Ursprüngliche Nachricht----- Von: Jesse Pretorius [mailto:preycor@myrealbox.com] Gesendet am: Mittwoch, 9. Juni 2004 17:40 An: SUSE LINUX Auto-installation List Betreff: [suse-autoinstall] PXE-based autoinstallation setup > Hi to all, > > I'm busy trying to setup a PXE-based auto-installation of SUSE LINUX > Desktop. > > Part of the instructions indicate that I should have 'initrd', > 'pxelinux.0', and 'linux' in the /tftpboot/ directory, and that I should > be able to find 'initrd' and 'linux' in the /suse/images/boot directory of > any of the SLES CD's. > I didn't find them there - I did find them in /boot/loader though. Are > these the same files that I need? > > Also, I don't seem to find 'pxelinux.0' anywhere. can someone point me to > it, or if I need to build it can you please point me to a helpful > resource? > > Thanks, > > Jesse

1 0

How Do I Get Rid Of DHCP!!?!
by discip＠pjm.com 09 Jun '04

09 Jun '04

1 0

Re: [suse-autoinstall] nfs timeouts?! client or server specific?!
by Helge Koehn 09 Jun '04

09 Jun '04

this would be technical possible but it's not an answer to my question! (i don't wanted a workaround i wanted a solution!) imagine a situation where ftp or http protocol are not the allowed choice and you have to use nfs ... ;-) helge. Harald.Milz@compu tacenter.com To 06/09/2004 12:54 Helge Koehn/Germany/IBM@IBMDE PM cc Subject Re: [suse-autoinstall] nfs timeouts?! client or server specific?! http? ftp? 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. Helge Koehn <koehn(a)de.ibm.com> on 09.06.2004 11:52:27 To: suse-autoinstall(a)suse.com cc: Subject: [suse-autoinstall] nfs timeouts?! client or server specific?! -------------------------------------------------------------------------- hi mailinglist, we have setup an autoyast environment which serves the installation data via nfs. we are facing the situation that some clients can't connect to the nfs-server (others do), the automatic installation process wents back to the manual installation menu. if we choose there network install and as source nfs the client find its way and can connect to the nfs install server, the installation starts and a "half automatic" installation goes on. how can we be sure that the client also connects to the nfs-server without going through the menu by hand?! are there any possible settings or parameters for the nfs-server or the client to change, may be timeout values or something like that?! thanks for answers. :-) helge. -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com COMPUTACENTER (UK) LTD The contents of this e-mail are intended for the named addressee only. It contains information which may be confidential and which may also be privileged. Unless you are the named addressee (or authorised to receive for the addressee) you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it. Computacenter information is available from http://www.computacenter.com This footnote also confirms that this email message has been swept for the presence of computer viruses. ***************************************************************************************************************************

1 0

Is there any way to refer the "info" file when install the SLES9?
by You, Yongkang 09 Jun '04

09 Jun '04

Hi all, I am now trying to automatically install the SLES9 by NFS with PXE booting or using SLES9 CD1 booting. There is an antoyast control file. It can be rightly used to auto-install the SLES9. But before auto-installation, it always jumped into manually installation. It said that it didn't found the installation source. Then I have to manually set the machine's IP address, IP mask, the network Gateway and NFS server etc. to locate the NFS installation source. I think there is an "info" file can help to locate them. Then the auto-installation process can skip the manual NFS server configuration. I also create a linuxrc configuration file "info" by the reference guide. But I don't know where I can put it, because our machines haven't any floppy. I have put it in the NFS with ramdisk or in the /rftproot. It seems to be useless. :-( Anybody can help me? I need know where to put the "info" file except in the floppy. And how can I refer it to Yast2 when installation. Thank you very much! Regards, You, Yongkang( Kangkang )

1 0

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

openSUSE Autoinstall June 2004