openSUSE Autoinstall June 2004

autoinstall@lists.opensuse.org

46 participants
63 discussions

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

15 Jun '04

Yup, that Did it! I added the "install" keyword to the info file, and now it is fine. The documentation, however, says that if I use the "autoyast" keyword that the "install" keyword is unnecessary. Oh well, I am just happy it works now. I think "overjoyed" is more the word. Thanks Anas! Paul -----Original Message----- From: Anas Nashif [mailto:nashif@suse.de] Sent: Wednesday, June 09, 2004 8:16 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 P roblem in 9.1 Where do you set the installation source? You info file does not have it, do you have it on the command line? I would say yast cant find the installation source and trying DHCP to find it... Anas discip(a)pjm.com wrote: > 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 >> > >

1 0

Re: [suse-autoinstall] Fw: autoyast and loadorder of modules
by Helge Koehn 15 Jun '04

15 Jun '04

du hast recht, fuer sles8 funktionierts, indem man die treiberreihenfolge als append parameter fuer den bootkernel mitgibt (aber wahrscheinlich auch nur, weil sles8 erst alle pakete installiert, dann die postskripte ausfuehrt und danach der initial boot erfolgt, waehrend suse9 halt gleich nach der 1. cd rebooten will und die bis dahin zusammengebaute initrd die einstellungen einfach ignoriert!). wenn sles9 auf basis suse 9 aufgebaut ist, haben wir dann dort wahrscheinlich die mimik von suse9 nach der ersten cd?! waere einen versuch wert ;-) Harald.Milz@compu tacenter.com To 06/09/2004 12:54 Helge Koehn/Germany/IBM@IBMDE PM cc Subject Re: [suse-autoinstall] Fw: autoyast and loadorder of modules Nur halt mit SLES8, da geht's ja. SuSE9 ist insofern kaputt. Mal sehen, was SLES9 macht - wenn sich's mal installieren läßt :-( 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 12:03:42 To: suse-autoinstall(a)suse.com cc: Subject: [suse-autoinstall] Fw: autoyast and loadorder of modules -------------------------------------------------------------------------- ... 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. -- 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. ***************************************************************************************************************************

2 1

Antwort: [suse-autoinstall] Determining file layout [FinanzIT: Viruscheck]
by Hartmut.Dunker＠finanzit.com 15 Jun '04

15 Jun '04

Hi Dustin, when you are creating a new multi CD install with create_package_description from the autoyast package, YaST stores the information of each package where it resides on. You can find this information in the packages file under /suse/setup/descr in each package description (=Loc:). Regards Hartmut "Dustin Nielson" <DUNIELSON@novell An: <suse-autoinstall(a)suse.com> .com> Kopie: Thema: [suse-autoinstall] Determining file layout [FinanzIT: Viruscheck] 14.06.2004 16:47 In a multi CD install, how does YaST know on which CD a given RPM resides on in order to prompt for the correct CD?

1 0

Determining file layout
by Dustin Nielson 14 Jun '04

14 Jun '04

In a multi CD install, how does YaST know on which CD a given RPM resides on in order to prompt for the correct CD?

1 0

Filesystem mount options on SuSE 9.1 LVM installs
by David Carter 14 Jun '04

14 Jun '04

Hello all, The <fstopt> option doesn't appear to work on LVM devices under SuSE 9.1. <install> . . . <partitioning config:type="list"> . . . <drive> <device>/dev/hermes</device> <is_lvm_vg config:type="boolean">true</is_lvm_vg> <use>all</use> <partition> <filesystem config:type="symbol">ext3</filesystem> <fstopt>defaults,usrquota,nosuid</fstopt> <lv_name>homes</lv_name> <mount>/homes</mount> <size>250g</size> </partition> </partitions> </drive> The resulting fstab entry is: /dev/hermes/homes /homes ext3 defaults 1 2 Is this expected behaviour? Checking the list archives, I see someone asking a similar question about SLES 8 a few days back. -- David Carter Email: David.Carter(a)ucs.cam.ac.uk University Computing Service, Phone: (01223) 334502 New Museums Site, Pembroke Street, Fax: (01223) 334679 Cambridge UK. CB2 3QH.

1 0

archives.gz
by Dustin Nielson 10 Jun '04

10 Jun '04

Curious as to how the ARCHIVES.gz file is generated on the first CD. If anyone knows I'd appreciate some information. Dustin

2 1

RE: [suse-autoinstall] Sample autoyast script
by Jesse Pretorius 10 Jun '04

10 Jun '04

Excellent, that works perfectly, thank you. -----Original Message----- From: Lee Mayes [mailto:autoinst@mayeses.com] Sent: 10 June 2004 01:58 PM To: Jesse Pretorius Subject: Re: [suse-autoinstall] Sample autoyast script Hi Jesse, Here's the relevant lines from my autoyast file: <install> <general> <mode> <confirm config:type="boolean">false</confirm> <forceboot config:type="boolean">false</forceboot> <reboot config:type="boolean">true</reboot> </mode> </general> </install> That will remove the need to accept anything (including the reboot before SuSE.config runs. Best Regards, Lee On Thu, 2004-06-10 at 06:54, Jesse Pretorius wrote: > Hi to all, > > Could anyone forward me a working autoinst.xml (autoyast script) file. > I need one from a fully automated installation. > > I'd like to use it for comparison to see where mine has a problem and > is thus requiring me to do two clicks to complete the install. > > Thanks, > > Jesse

1 0

Sample autoyast script
by Jesse Pretorius 10 Jun '04

10 Jun '04

Hi to all, Could anyone forward me a working autoinst.xml (autoyast script) file. I need one from a fully automated installation. I'd like to use it for comparison to see where mine has a problem and is thus requiring me to do two clicks to complete the install. Thanks, Jesse

1 0

Pxelinux process hangs
by Jesse Pretorius 10 Jun '04

10 Jun '04

Hi to all, I've now setup DHCPD, TFTPD and all the appropriate bits afaik to get the PXE-based boot and install to run. When I do a PXE-based boot, I receive an address, it downloads pxeconfig.cfg/default and runs to the point where the line indicates the start of the install program with ">>> SuSE Linux installation program" and the rest of the line is known to you. The problem I have is that it hangs there. What am I missing? Contents of pxeconfig.cfg/default: -- begin file -- default linux serial 0,9600n8 label linux kernel linux append console=ttyS0,9800 console=tty0 load_ramdisk=1 initrd=initrd insmod=pcnet32 autoyast=http://192.168.240.1/autoinst.xml install=nfs://192.168.240.1/srv/nfs -- end file -- Naturally 'initrd', 'linux', 'pxelinux.0' are all in /tftpboot/ Can anyone point me in the right direction? Thanks, Jesse

1 1

Creating a autoyast script for SLD
by Jesse Pretorius 10 Jun '04

10 Jun '04

Hi, I'm trying to create an autoyast script for SLD and have only been moderately successful. I used the autoyast module through the ncurses interface (no GUI on my server) to create a basic file with the partitioning info and a basic package selection. I the edited the file to change the package selection to use some of the SLD .sel files instead of the SLES8 .sel files. I'm finding that the script creation utility is basically designed to create a script file for SLES rather than for any SUSE distro and thus it's rather limiting and I have to edit the text files by hand to do the distro-specific settings. Is there a way to have the autoyast module pick up the details of the distro I want to customise a script for from a file path or something? There does appear to be a setting which allows you to indicate where your package sources are, which I've set. but it doesn't make a difference. Also, I'm finding that my script does the selections automatically now, but the installation still wants me to select 'Accept' to continue the installation. What's missing - I'm guessing it's something in the script file? I'm looking to do a completely hands-off installation. TIA, Jesse

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