openSUSE Autoinstall February 2004

autoinstall@lists.opensuse.org

41 participants
46 discussions

by Paul Edgar

All, When the installation reads the .xml file, is it parsed and executed in a sane order, or does the installer execute the xml file from top to bottom? Paul Edgar IBM Linux Technology Center

17 years, 7 months

How to avoid booting confirmation?

by Robert Pollak

Hello! I use the appended control file autoinst.xml on a floppy during installation from the original SLES8 CDs. At the end of the "Finishing Basic Installation" screen, i am asked > The LILO boot sector has been written to disk. You can restore > the old boot sector in the installed system with "lilo -u /dev/sda" > > Now booting your system... > [OK-Button] , and the installer waits for interactive confirmation. How can i change the control file such that this confirmation is not needed? Or can't it be suppressed by any of the <mode> entries? -Robert ****************autoinst.xml**************** <?xml version="1.0"?> <!DOCTYPE profile SYSTEM "/usr/share/YaST2/include/autoinstall/profile.dtd"> <profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <configure> <users config:type="list"> <user> <encrypted config:type="boolean">true</encrypted> <user_password>XXXXXX</user_password> (<- pw removed) <username>root</username> </user> </users> </configure> <install> <bootloader> <location>mbr</location> </bootloader> <general> <clock> <hwclock>GMT</hwclock> <timezone>Europe/Vienna</timezone> </clock> <keyboard> <keymap>german</keymap> </keyboard> <mode> <installation config:type="boolean">true</installation> <upgrade config:type="boolean">false</upgrade> <confirm config:type="boolean">false</confirm> <interactive_boot config:type="boolean">false</interactive_boot> <reboot config:type="boolean">false</reboot> </mode> </general> <partitioning config:type="list"> <drive> <device>/dev/sda</device> <initialize config:type="boolean">true</initialize> <partitions config:type="list"/> <use>all</use> </drive> </partitioning> <software> <base>Minimal</base> </software> </install> </profile>

17 years, 7 months

linuxrc not seeing embedded info during AutoYaST installs

by Lamont R. Peterson

Hello. I am new to this list. I have been using SUSE LINUX since 6.0 (in 1997). I have build info file autoinstalls in the past. Recently, I started working on creating autoinstalls for SLES8 (and SUSE LINUX Professional 9.0). I have everything working except for three things: 1) When linuxrc starts it can not find the (NFS) installation media. The NIC has been detected and the AutoYaST file has been retrieved (I think), but it takes twelve (12) keypresses to tell it to use NFS, DHCP and accept the values the DHCP server sent. Twelve keypresses is not hands-off, which my boss wants. Here are the lines from within my AutoYaST file: <init> <info_file> <![CDATA[ # # start_linuxrc_conf # install: nfs://192.0.2.1/netinstall/suse/sles/8/ usedhcp: 1 textmode: 1 # end_linuxrc_conf #]]> </info_file> <instmode>nfs</instmode> <profile_protocol>nfs</profile_protocol> <profile_server>192.0.2.1</profile_server> <server>192.0.2.1</server> <serverdir>/export/netinstall</serverdir> <textmode config:type="boolean">true</textmode> <usedhcp config:type="boolean">true</usedhcp> </init> 2) After LILO is installed, there is a dialog box that does not timeout on it's own, telling me that I can reinstall the old bootsector using a lilo command. The boss wants the installations to be completely hands-off. 3) YaST runs in graphical mode during installation, not text-mode. I believe this should be fixed when problem #1 above is repaird. These installs may have to run on headless machines in the future, so the boss wants them ready. He also thinks that they will run measurably faster this way (though I do not see how whether you use text or graphical mode could affect hard drive and network performance appreciably). Your help is appreciated. TIA. -- Monty Peterson <lrp(a)xmission.com>

17 years, 7 months

Re: [suse-autoinstall] Package selection

by Mario Goppold

Am Freitag, 27. Februar 2004 14:19 schrieb Anas Nashif: > did you refresh the source settings in yast2 source manager? > > Anas > No i haven't, after reload it works. Thank you. But why must the source-medium stand alone? If i add a second below my repository no packages where found. Even if it deaktivated. Again thank you for your fast help. -- Mario Goppold, TBZ-PARIV GmbH, Bernsdorfer Str. 210-212, 09126 Chemnitz Tel.: 0371/5221215 Fax: 0371/5221216 1024D/67123521 2001-01-29 Mario Goppold (tbz-pariv) <mgoppold(a)tbz-pariv.de> Key fingerprint = 44FE 7411 0723 0A76 C201 7A0A C9D8 D36F 6712 3521

17 years, 8 months

Package selection

by Mario Goppold

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi list, i have a problem with PackageSelection: I create a local repository from SuSE9.0 DVD (x86_64) and create my own Package-Selection. I also updateted the kernel and the perl packages. I have removed the original: rm -f /root/current/suse/x86_64/k_deflt-2.4.21-102.x86_64.rpm rm -f /root/current/suse/x86_64/k_smp-2.4.21-102.x86_64.rpm rm -f /root/current/suse/x86_64/perl-5.8.1-43.x86_64.rpm Downloaded the new ones and copy them to the repository: cp k_deflt-2.4.21-201.x86_64.rpm /root/current/suse/x86_64 cp k_smp-2.4.21-201.x86_64.rpm /root/current/suse/x86_64 cp perl-5.8.1-77.x86_64.rpm /root/current/suse/x86_64 cd /root/current/suse create_package_descr -l english -l german /root/current/suse/ start yast2 autoyast select my xml-file start iso-creation and get following error-message: Paketquelle /root/current Pakete 33 Fehlende Pakete /root/current/./suse/x86_64/k_deflt-2.4.21-102.x86_64.rpm /root/current/./suse/x86_64/k_smp-2.4.21-102.x86_64.rpm /root/current/./suse/x86_64/perl-5.8.1-43.x86_64.rpm and here the yast-log with added some messages: ... [YCP] autoinstall/iso.ycp(checkPackageAvail):146 MG checkPackageAvail Package database=/root/current/./suse/setup/descr/packages [YCP] autoinstall/iso.ycp(getRpmPath):116 MG getRpmPath dataDir= ./suse [YCP] autoinstall/iso.ycp(getRpmPath):126 MG getRpmPath /root/current/./suse/x86_64/ash-0.2-256.x86_64.rpm [YCP] autoinstall/iso.ycp(getRpmPath):116 MG getRpmPath dataDir= ./suse [YCP] autoinstall/iso.ycp(getRpmPath):126 MG getRpmPath /root/current/./suse/x86_64/ash.rpm [YCP] autoinstall/iso.ycp(checkPackageAvail):156 MG Package ash 0.2 256 x86_64 pacsize 289978 pacsize1 -1 ... [YCP] autoinstall/iso.ycp(getRpmPath):116 MG getRpmPath dataDir= ./suse [YCP] autoinstall/iso.ycp(getRpmPath):126 MG getRpmPath /root/current/./suse/x86_64/k_deflt-2.4.21-102.x86_64.rpm [YCP] autoinstall/iso.ycp(getRpmPath):116 MG getRpmPath dataDir= ./suse [YCP] autoinstall/iso.ycp(getRpmPath):126 MG getRpmPath /root/current/./suse/x86_64/k_deflt.rpm [YCP] autoinstall/iso.ycp(checkPackageAvail):156 MG Package k_deflt 2.4.21 102 x86_64 pacsize -1 pacsize1 -1 [YCP] autoinstall/iso.ycp(getRpmPath):116 MG getRpmPath dataDir= ./suse [YCP] autoinstall/iso.ycp(getRpmPath):126 MG getRpmPath /root/current/./suse/x86_64/k_deflt-2.4.21-102.x86_64.rpm [YCP] autoinstall/iso.ycp(getRpmPath):116 MG getRpmPath dataDir= ./suse [YCP] autoinstall/iso.ycp(getRpmPath):126 MG getRpmPath /root/current/./suse/x86_64/k_smp-2.4.21-102.x86_64.rpm [YCP] autoinstall/iso.ycp(getRpmPath):116 MG getRpmPath dataDir= ./suse [YCP] autoinstall/iso.ycp(getRpmPath):126 MG getRpmPath /root/current/./suse/x86_64/k_smp.rpm [YCP] autoinstall/iso.ycp(checkPackageAvail):156 MG Package k_smp 2.4.21 102 x86_64 pacsize -1 pacsize1 -1 [YCP] autoinstall/iso.ycp(getRpmPath):116 MG getRpmPath dataDir= ./suse [YCP] autoinstall/iso.ycp(getRpmPath):126 MG getRpmPath /root/current/./suse/x86_64/k_smp-2.4.21-102.x86_64.rpm [YCP] autoinstall/iso.ycp(getRpmPath):116 MG getRpmPath dataDir= ./suse and so on ... in /root/current/suse/setup/descr/packages the is no k_deflt-2.4.21-102: ... ##---------------------------------------- =Pkg: k_deflt 2.4.21 201 x86_64 +Req: mkinitrd /bin/cp /bin/sed /bin/touch /bin/awk /bin/sh /bin/sh /bin/sh /bin/sh rpmlib(PartialHardlinkSets) <= 4.0.4-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(PayloadIsBzip2) <= 3.0.5-1 - -Req: +Prq: mkinitrd /bin/cp /bin/sed /bin/touch /bin/awk /bin/sh /bin/sh /bin/sh /bin/sh rpmlib(PartialHardlinkSets) <= 4.0.4-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(PayloadIsBzip2) <= 3.0.5-1 - -Prq: +Prv: kernel k_deflt = 2.4.21-201 - -Prv: =Grp: System/Kernel =Lic: GPL =Src: k_deflt 2.4.21 201 src =Tim: 1077132976 =Loc: 1 k_deflt-2.4.21-201.x86_64.rpm =Siz: 15496924 46756274 ##---------------------------------------- ... And now my question: What do i wrong? What does Pkg::GetPackages (`selected , false); in /usr/share/YaST2/include/autoinstall/iso.ycp ? With the original rpms in place there are no errors and my selection works fine. Many thanks! Mario. - -- Mario Goppold, TBZ-PARIV GmbH, Bernsdorfer Str. 210-212, 09126 Chemnitz Tel.: 0371/5221215 Fax: 0371/5221216 1024D/67123521 2001-01-29 Mario Goppold (tbz-pariv) <mgoppold(a)tbz-pariv.de> Key fingerprint = 44FE 7411 0723 0A76 C201 7A0A C9D8 D36F 6712 3521 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQFAPzEBydjTb2cSNSERArIXAJ9NZwul/EA2m5R+LxgDmXdiQZ3k6gCfZW4J cqwBKfOwhv/QWyINJnwN1vI= =ZVKf -----END PGP SIGNATURE-----

17 years, 8 months

How to configure GRUB for boot on SCSI and IDE?

by K.-W. Grabbe

Hello, I want to install systems with IDE and SCSI harddisks with one autoinst.xml. The installation work´s fine, but how to configure GRUB for this case?? Has anyone experience? Regards, K.-W. Grabbe -- GMX ProMail (250 MB Mailbox, 50 FreeSMS, Virenschutz, 2,99 EUR/Monat...) jetzt 3 Monate GRATIS + 3x DER SPIEGEL +++ http://www.gmx.net/derspiegel +++

17 years, 8 months

Rules based builds

by Ness, Todd

What version of autoyast does rules based builds start with? Todd Ness

17 years, 8 months

Startup links renamed?

by Ness, Todd

I have a custom rpm that installs during my autoinstall. It installs /etc/init.d/rc5.d/S95startscript during the reboots and final system configuration the link gets renamed to /etc/init.d/rc5.d/S01startscript this is a problem as it needs to start later in the boot process. Does anybody have an explanation as to why this happens. Oh, by the way, I fix the links in a post install script, and they still get changed after that. thanks Todd Ness

17 years, 8 months

Autoyast, Linuxrc and Slow network card....??????????

by damien.selles＠eu.effem.com

Hi all, Some of my HP server have got NC7700 network cards...and I have got a big issue with them.. Indeed, I launch an autoyast install, having given all the parameter (hostname, netmask, ip etc..) yast tries to configured my network card one after the other and fails to mout the depot with all of them.. Actually the NC7700 need about 20 sec to initialize the network communication correctly... but autoyast / linuxrc only waits half a second one it has config a card before trying to mount the depot.... --> Is there a smart way for me to force a longer "sleep" between the config and the mount ? --> I have identified in the linuxrc source in net.c a line I could modify to force a longer sleep.. but I perform the makefile.. the linuxrc generated does not allow an autoyast install.. any help on that topic? --> Or would you have a solution for reducing the initialization delay of my network cards? Best regards, Damien.

17 years, 8 months

Load initrd hangs (SuSe 9.0)

by Dominic Lukwata

Hi, We have set up an Installations Server for SuSe 9.0 as specified in the documentations of Anas Nashif. We have used original files from the SuSe 9.0 Pro distribution. I like to use it for a network install of SuS9.0 to a number of workstations. The client boots and PXE is startet und makes contact to a dhcp-Server. The it loads the linux kernel. But when its starts loading the raddisk it hangs: Loading initrd ... And the boot fails. We have now spent around over a week on this problem and are stuck now. Does anybody have a hint how to make this work. Thanks Dominic

17 years, 8 months

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

openSUSE Autoinstall February 2004