openSUSE Autoinstall January 2008

autoinstall@lists.opensuse.org

25 participants
19 discussions

linuxrc - netdevice=<hwaddress>
by John Willis 18 Dec '12

18 Dec '12

Does anyone know if any of the SLES releases 9 or 10 support passing the linuxrc option netdevice=<hardware mac address> ? I noticed Red Hat has had this for sometime and it seems totally missing in SuSE which seems really odd. I'm still scratching my head if we really are still passing only by kernel interface name. I read in the change log for linuxrc-1.8.6-3 a change that "sounds" like this feature. * Mon Mar 14 2005 - snwint(a)suse.de - s390: fix segfault in net_list_s390_devs() - extra root image was sometimes not used - allow netdevices to be specified by hwaddress But it looks like linuxrc-1.8.6-3 is only available in SuSE Professional 9.3. "any" commentary would be sincerely appreciated the feature also seems to be fairly minor since any delimiter seperating the octets in the hwaddr string could be used to identify the difference between an interface name and interface hw address if i could figure out a generic method of overriding the linuxrc with a custom script and daisy chain it back into linuxrc after setting up the interface name, I would.. and have a slight idea on how to do that.. but i'd rather find out i'm just missing something and the feature is already there Thanks!

3 2

[opensuse-autoinstall] Error in autoyast install process
by Wayman Smith 10 Mar '08

10 Mar '08

Hello, I am attempting to perform an autoinstall process with SuSE 10.1 sp1 using autoyast and a custom autoinst.xml file. The install process reads the autoinst.xml correctly, and performs all steps up until the Install boot manager process. Here, I receive the error /sbin/mkinitrd: line 3297: /etc/fstab: No such file or directory No '/' mountpoint spceified in /etc/fstab It should also be noted that my autoinst.xml file fails RNG validation (https://bugzilla.novell.com/show_bug.cgi?id=211014#c21) I have attached my autoinst.xml file also. Might these two problems be related? --W. Smith

8 11

RE: [suse-autoinstall] SLES 10 RC2 remove-packages section?
by Matt Gillard 05 Mar '08

05 Mar '08

I dont have kinternet installed. This is what doesnt seem to work: <software> <patterns config:type="list"> <pattern>default</pattern> <pattern>Basis-Devel</pattern> <pattern>x11</pattern> </patterns> <packages config:type="list"> <packages>perl-libwww-perl</packages> <packages>net-snmp</packages> <packages>kernel-source</packages> </packages> <remove-packages config:type="list"> <packages>pptp</packages> <packages>smpppd</packages> <packages>ppp</packages> <packages>wvdial</packages> <packages>mutt</packages> </remove-packages> </software> In y2log it mentions that those packages should be removed, but it goes ahead and installs them anyway. I can do it manually on the command line: # rpm -e pptp smpppd ppp wvdial mutt and that works fine so I know I have no dependency problems. matt > -----Original Message----- > From: Uwe Gansert [mailto:ug@suse.de] > Sent: Friday, 30 June 2006 12:50 AM > To: suse-autoinstall(a)suse.com > Subject: Re: [suse-autoinstall] SLES 10 RC2 remove-packages section? > > > On Thursday 29 June 2006 16:45, Manfred Hollstein wrote: > > > If that fails, you have kinternet installed; add that to > the list and it > > should work. > > good point. > <remove-packages> can not break dependencies and so it's very > likely that > there is still a package that needs those packages. > I did a very small installation with no X - so it worked for me. > > -- > ciao, Uwe Gansert > > Uwe Gansert, Server Technologies Team > SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nuernberg, Germany > Fax: +49-(0)911-74053-476, Web: http://www.suse.de/~ug > now playing Covenant - Wasteland > > -- > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > For additional commands, e-mail: suse-autoinstall-help(a)suse.com > > This email and any attachments may contain privileged and confidential information and are intended for the named addressee only. If you have received this e-mail in error, please notify the sender and delete this e-mail immediately. Any confidentiality, privilege or copyright is not waived or lost because this e-mail has been sent to you in error. It is your responsibility to check this e-mail and any attachments for viruses. No warranty is made that this material is free from computer virus or any other defect or error. Any loss/damage incurred by using this material is not the sender's responsibility. The sender's entire liability will be limited to resupplying the material.

4 6

[opensuse-autoinstall] PXE installation and endless loop
by Wayman Smith 31 Jan '08

31 Jan '08

Hello, I am implementing a PXE installation with autoyast, and it has been working well. However, the system continues to boot from PXE and the installation repeats itself over and over. I will not have access to the machines to disable PXE in the bios. I have look at the autoyast documentation and Section 7.2.3 recommends a solution of adding an entry to autoyast.xml profile. I have tried this option, however I still receive the same result. This is what I have added to my autoinst.xml <pxe> <pxe_localboot config:type="boolean">true</pxe_localboot> <pxelinux-config> DEFAULT linux LABEL linux localboot 0 </pxelinux-config> <tftp-server>192.168.66.1</tftp-server> <pxelinux-dir>/pxelinux.cfg</pxelinux-dir> </pxe> I also am using dhcp and the hexadecimal file names. What section of the autoinst.xml should the pxe section be inserted in? I have made alot of progress with my installation, thanks for all the support. Wayman -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

8 10

Re: [opensuse-autoinstall] AutoYast SLES9 SP3 problem with hostname via DHCP
by chrroe＠uni.de 31 Jan '08

31 Jan '08

Here is a little round-up about my issues: Problem Nr. 1: aaa_base-9-29.46.i586.rpm produces a 2595 bytes log /etc/sysconfig/kernel file with nothing but null- bytes in it. Solution for Nr.1: In our PXE-Environment we are using for the "kernel" and "initrd" files that ones from SLES9 without any SP. During an AutoYast installation "SUSE LINUX Enterprise Server 9 installation program v1.6.36" is displayed. I made some tests with the versions from the SLES9 SP3 CDs. There it says "v1.6.53", and works like a charm: Even when no hostname is provided in my eth_default_dhcp.xml the file /etc/sysconfig/kernel gets created with almost perfect content (BusLogic apperas twice in INITRD_MODULES=). Hopefully merely copying the correct file in our production-systems is enough in order to get a neat environment. Problem Nr.2: After installation of postfix-2.1.1-1.17.i586.rpm with AutoYast the file /etc/postfix/main.cf contains a line with myhostname = .testdomain.com instead of myhostname = testhost.testdomain.com. With this mistake postfix is unstartable. Workaround for Nr.2: Either call SuSEconfig.postfix when hostname is available. or call "postconf myhostname=`hostname -f`" when hostname is available. (I tend to the second one, perhaps in a kind of post-postinstallation script) Using dhcpcd (like Stefan suggested) I made the following experiences: During first AutoYast stage it is possible to call the following in the alt+F2 shell: / # hostname linux / # /lbin/dhcpcd -k / # /lbin/dhcpcd -D / # hostname testhost But with the solution for Nr.1 this seems to be not neccesary anymore. During the second AutoYast stage you can use similar commands. But then errors are thrown: linux:/ # hostname linux linux:/ # dhcpdcd -k **** dhcpcd: not running linux:/ # dhcpcd -D linux:/ # ERROR: Interface eth0 is not configured for dhcp. So don't use '-o dhcp'. linux:/ # hostname linux Later, when the second stage has finished and the installed system is completing the boot process, recieving the IP address fails at all: eth0 (DHCP) . . . . . no IP address yet... backgrounding eth0 interface could not be set up When I don't use any commands in the 2nd stage, booting works correctly! Well, as a conclusion I think I found acceptable work-arounds, but this makes me not 100% happy. Nevertheless I learned some new things about (SUSE) Linux while my investigations ;-). Thanks for your participation. Bye Christoph ---- Hol Dir jetzt Deine coole @uni.de E-Mail Adresse. Der einzigartige Webservice und auch noch kostenlos. -- www.uni.de -- -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 0

[opensuse-autoinstall] module via driverupdate
by Frank Steiner 31 Jan '08

31 Jan '08

Hi, I added the latest 3w-9xxx.ko modul that I compiled from the 3ware sources against the SLES10-SP1 installer kernel to a driverupdate, because I need support for the 3ware SAS controller. Now it happens that the AY installed loads the 3w-9xxx modul, but doesn't find a controller. Then later it removes it and loads it again and then finds the controller (I got this from the /var/log/boot.msg and the output on tty3. I specified "insmod=3w-9xxx" in the pxelinux.cfg because I want this controller to be recognized as first scsi device (for its raid to become sda). It seems that AY first loads the old modul from the initrd, then detects the other controllers, and after that reloads the 3ware module from the driverupdate. Is that the intended way? Do I have to put the module into the initrd to make it load before all others? 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. * -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 0

[opensuse-autoinstall] no nameserver entry in resolv.conf
by Thomas Vogt 30 Jan '08

30 Jan '08

Hello Is there a way to add nameserver values to the resolv.conf with autoyast.xml? After the installation of OpenSuSE 10.3 (i386) with autoyast my resolv.conf is always empty. Everything else works fine. XML config: <dns> <dhcp_hostname config:type="boolean">false</dhcp_hostname> <dhcp_resolv config:type="boolean">false</dhcp_resolv> <domain>mydomain</domain> <hostname>myhostname</hostname> <nameservers config:type="list"> <nameserver>1.2.3.4</nameserver> <nameserver>1.2.3.5</nameserver> </nameservers> </dns> I also tried it with a post-script but with no luck. <scripts> <post-scripts config:type="list"> <script> <debug config:type="boolean">true</debug> <feedback config:type="boolean">false</feedback> <filename>myscript</filename> <interpreter>shell</interpreter> <location></location> <network_needed config:type="boolean">true</network_needed> <source><![CDATA[shell #!/bin/sh # Sort out resolv.conf cat > /etc/resolv.conf <<EOF nameserver 1.2.3.4 nameserver 1.2.3.5 EOF ]]></source> </script> </post-scripts> </scripts> Any idea? Regards, Thomas -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

4 3

[opensuse-autoinstall] fetch profile via nfs in 10.3
by Ulrich Hoelscher 29 Jan '08

29 Jan '08

Hi, in 10.2 I deploy the autoyast profiles via nfs, this works out of the box. To use it I call autoyast=nfs://.../autoinst.xml If i try it with 10.3 this is not possible. The installation sources are also deployed via nfs, which works fine. After starting the installation in autoyast mode it not possible to mount the nfs share. The reason is the locks can not be handled. As a work around I use http to deploy the profiles and nfs to deploy the rpms. Is this a bug or a desired feature? regards Ulrich -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

4 5

[opensuse-autoinstall] Autoinstall without X
by Wayman Smith 29 Jan '08

29 Jan '08

Hello, I have a need to install NVIDIA drivers during my autoinstall process. Installing these drivers requires that X not be running. Does autoyast have an option to install without X? Regards, W. Smith -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

3 2

[opensuse-autoinstall] Is AY using stuff from the installed system?
by Frank Steiner 25 Jan '08

25 Jan '08

Hi, still playing around with SLES-updates to a SuSE system. Got it all working by copying the SLES RPMs into the updates/ dir. But now writing the lilo.conf fails at the end of the installation (just no file is created at all and AY complains sth. went wrong with the bootloader). This happens when the the packages limal limal-bootloader limal-perl from SLES10 are in the updates/ dir and are installed in the otherwise SuSE 10.1 system. I find this quite confusing: Doesn't the installer contain all modules that it needs for writing config files in the installed system? Of course AY takes stuff like lilo and mk_initrd from the installed system, but for generating config files, too? This is not a problem here, of course, I'm just curious about the way AY works. 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. * -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

3 3

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

openSUSE Autoinstall January 2008