openSUSE Autoinstall October 2002

autoinstall@lists.opensuse.org

36 participants
65 discussions

Suse 7.2 & Ibm NetFinit 5000
by Joao Carlos 24 Oct '02

24 Oct '02

Hello I Am trying to install suse 7.2 on Ibm NetFinit 5000, however afert kernel load scsi modules and I try to start Installation, Suse do not access cdrom and show message 'could mount cdrom'. When I Try to load cdrom manual through menu 'Load Cdrom Driver' appears message. CDrom is already loaded! My Cdrom is a IDE - LG CRD8322B ATAPI My SCSI Driver is Ibm ServerRAID Somebody can help me. Joao

1 0

RE: [suse-autoinstall] Post-Chroot Problem and SMP-Kernel-Bug
by Kugelberg, Thorsten 24 Oct '02

24 Oct '02

Hey, >But I have a problem with the post-chroot script. I wrote an script to >change the IP and a lot of other things. But the script is never >started. I created the file with yast2 a couple of times or write it my >one, but nothing helps! >I´ve attached the autoinstall.xml. The xml file looks good to me... Are the scripts created under /var/adm/autoinstall/scripts? And if so, how do the logs look like? And what about the other scripts? are they executed? >Another problem is the smpkernel. I think there is a bug with the >eepro100 drivers. They don´t work with the smp kernel, the driver loads >but there is no RX or TX. When I append "nosmp maxcpus=0" every thing >works fine. The k_deflt kernel works good, too. We normally do not have such a Problem! Which kernel do you use in detail? Regards Thorsten

1 0

Antwort: [suse-autoinstall] Post-Chroot Problem and SMP-Kernel-Bug
by Michael.Jeromin＠mummert.de 24 Oct '02

24 Oct '02

Hi Jens, I don't know if this will help you, but have you realized that the chroot-scripts are now in a new section?! Since SuSE 8.1 they are in the scripts section and not as under 8.0 directly in the configure section. Another point is that they won't be executed in the new target file system but in the old root filesystem, if I remember our experiences well ... Hope this will help you !! Cheers, Michael Mit freundlichen Grüßen Michael Jeromin Consultant Integrated Business Consulting Mummert Consulting AG Tel.: 0179 / 4778310 Fax: 0251 / 98158 - 4634 Jens Kühnel <listuser@kue An: suse-autoinstall(a)suse.com hnel.org> Kopie: (Blindkopie: Michael Jeromin/mummert/de) Thema: [suse-autoinstall] Post-Chroot Problem and SMP-Kernel-Bug 24.10.02 09:09 Hi *, first a thanks to Anas! You installer makes it a lot easier to setup a classroom. The grub-bootdisk is also excelent! No F*** Bootdisk compiling! :-) But I have a problem with the post-chroot script. I wrote an script to change the IP and a lot of other things. But the script is never started. I created the file with yast2 a couple of times or write it my one, but nothing helps! I´ve attached the autoinstall.xml. Another problem is the smpkernel. I think there is a bug with the eepro100 drivers. They don´t work with the smp kernel, the driver loads but there is no RX or TX. When I append "nosmp maxcpus=0" every thing works fine. The k_deflt kernel works good, too. I hope someone will help me with this problems. CU Jens <?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> <nfs config:type="list"> <nfs_entry> <mount_point>/install</mount_point> <nfs_options>ro,wsize=8192,rsize=8192,soft,intr</nfs_options> <server_path>10.0.0.1:/install</server_path> </nfs_entry> </nfs> <scripts> <chroot-scripts config:type="list"> <script> <filename>ipaddress.sh</filename> <interpreter>shell</interpreter> <source> <![CDATA[# # (C) 2002 Jens Kuehnel spam(a)kuehnel.org # (just change the spam to my given name :-) # License GLP # # current IP to SuSE8-Configuration # takes current IP from the installation system and write it in the configfiles # hostname is taken from rev-lookup # cat > /etc/resolv.conf << EOF nameserver 10.0.0.1 search linux.foo domain linux.foo EOF #The ip Address is allready available ! :-) #IP=$(ifconfig eth0 | grep "inet addr" | cut -d : -f 2 | cut -d " " -f 1) echo $IP > /tmp/ipaddresse cat > /etc/sysconfig/network/ifcfg-eth0 <<EOF IPADDR=$IP NETMASK=255.0.0.0 NETWORK=10.0.0.0 BROADCAST=10.255.255.255 STARTMODE=onboot UNIQUE="1234" EOF host $IP | cut -d " " -f 5 | cut -d . -f -3 > /etc/HOSTNAME HOSTNAME=$(cat /etc/HOSTNAME) echo $HOSTNAME > /tmp/ipaddresse-hostname cat > /etc/hosts <<EOF # # hosts This file describes a number of hostname-to-address # mappings for the TCP/IP subsystem. It is mostly # used at boot time, when no name servers are running. # On small systems, this file can be used instead of a # "named" name server. # Syntax: # # IP-Address Full-Qualified-Hostname Short-Hostname # 127.0.0.1 localhost $IP $HOSTNAME EOF cat > /etc/sysconfig/network/routes << EOF default 10.0.0.1 - - EOF ]]> </source> </script> <script> <filename>you-infos.sh</filename> <interpreter>shell</interpreter> <source> <![CDATA[ echo "ftp://10.0.0.1/pub/suse" > /etc/suseservers chattr +i /etc/suseservers cat > /etc/sysconfig/onlineupdate <<EOF # # While starting YOU ( YaST2-Online-Update ) the default ftp serverlist # will be updated by the call "wget" to www.suse.de. This list will be # stored under /etc/suseservers. # Set YAST2_LOADFTPSERVER to "no", if you do not want to reload the # ftp serverlist. # YAST2_LOADFTPSERVER="no" # # Registration code for business products # REG_CODE="" # # Registration password for business products # REG_PASSWORD="" # # User for used proxy # PROXY_USER="" # # Password for used proxy # PROXY_PASSWORD="" EOF ]]> </source> </script> <script> <filename>nettime.sh</filename> <interpreter>shell</interpreter> <source> <![CDATA[# # update Time from install and write to hardware-clock # ntpdate 10.0.0.1 hwclock --systohc ]]> </source> </script> </chroot-scripts> <post-scripts config:type="list"/> <pre-scripts config:type="list"/> </scripts> <security> <encryption>md5</encryption> </security> <users config:type="list"> <user> <encrypted config:type="boolean">true</encrypted> <user_password>$1$hcZxkyzz$WPiSFiwbrSPEGfkln.G.w0</user_password> <username>root</username> </user> <user> <encrypted config:type="boolean">true</encrypted> <user_password>$1$CzzzYyzz$udBZLLbPuIHZoPJMaH9gc0</user_password> <username>linux</username> </user> </users> <x11> <color_depth config:type="integer">16</color_depth> <configure_x11 config:type="boolean">true</configure_x11> <display_manager>kdm</display_manager> <enable_3d config:type="boolean">true</enable_3d> <resolution>1024x768</resolution> <start_x11 config:type="boolean">false</start_x11> </x11> </configure> <install> <bootloader> <activate config:type="boolean">true</activate> <lba_support config:type="boolean">true</lba_support> <linear config:type="boolean">false</linear> <location>mbr</location> </bootloader> <general> <clock> <hwclock>localtime</hwclock> <timezone>Europe/Berlin</timezone> </clock> <keyboard> <keymap>german</keymap> </keyboard> <language>de_DE</language> <mode> <confirm config:type="boolean">false</confirm> <forceboot config:type="boolean">true</forceboot> <interactive_boot config:type="boolean">false</interactive_boot> <reboot config:type="boolean">false</reboot> </mode> </general> <partitioning config:type="list"> <drive> <device>/dev/hda</device> <initialize config:type="boolean">true</initialize> <partitions config:type="list"> <partition> <crypt_fs config:type="boolean">false</crypt_fs> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <mount>swap</mount> <partition_id config:type="integer">131</partition_id> <size>200M</size> </partition> <partition> <crypt_fs config:type="boolean">false</crypt_fs> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <mount>/</mount> <partition_id config:type="integer">131</partition_id> <size>4000M</size> </partition> </partitions> <use>all</use> </drive> </partitioning> <report> <errors> <log config:type="boolean">true</log> <show config:type="boolean">true</show> <timeout config:type="integer">100</timeout> </errors> <messages> <log config:type="boolean">true</log> <show config:type="boolean">true</show> <timeout config:type="integer">100</timeout> </messages> <warnings> <log config:type="boolean">true</log> <show config:type="boolean">true</show> <timeout config:type="integer">100</timeout> </warnings> </report> <software> <addons config:type="list"> <addon>Basis-Devel</addon> <addon>Basis-Sound</addon> <addon>Gnome</addon> <addon>Kde-Desktop</addon> <addon>Kde</addon> <addon>LAMP</addon> <addon>LDAP-Server</addon> <addon>Multimedia</addon> <addon>Network</addon> <addon>SuSE-Documentation</addon> <addon>X11</addon> </addons> <base>default</base> <packages config:type="list"> <package>mc</package> </packages> </software> </install> </profile> -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

RE: [suse-autoinstall] Disable CANCEL Button
by Kugelberg, Thorsten 23 Oct '02

23 Oct '02

Hello, if I understood SuSE right, this is not possible! But in my opinion it is even more important to close the shells on tty2,5,6 and 9! I am doing this within my prescript: kill -9 $(ps -ef | grep bash | grep tty2 | grep -v grep | awk '{ print $2 }') kill -9 $(ps -ef | grep bash | grep tty5 | grep -v grep | awk '{ print $2 }') kill -9 $(ps -ef | grep bash | grep tty6 | grep -v grep | awk '{ print $2 }') kill -9 $(ps -ef | grep lsh | grep tty9 | grep -v grep | awk '{ print $2 }') not very nice but it works. Anas said that an option like 'noshells' will be implemented into yast. I really hope that there will be something for the cancel buttons. If I remember right, there was something like that with SuSE 7.x autoinstall... Regards Thorsten -----Original Message----- From: Joachim.Tork(a)gad.de To: suse-autoinstall(a)suse.com Sent: 22.10.2002 14:48 Subject: [suse-autoinstall] Disable CANCEL Button Hello everybody, I wonder if it is possible to diable the CANCEL button during installation. Does anybody know ? Joachim -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

3 3

RE: [suse-autoinstall] How to save package sets in suse 8.1?
by Kugelberg, Thorsten 23 Oct '02

23 Oct '02

Hallo, >I get the new package names (of an already installed 8.1 system) >with the command rpm: > ># rpm -qa | sed -e 's/-[0-9].*$//' > new_rpm_list.tmp just to make your life a little bir easier: RPM has the Option to give you the names of the installes packages. So you do not need the sed: 'rpm -qa --qf "%{NAME}\n"' Regards Thorsten

2 1

Tip: Using VNC with autoinstall
by Anas Nashif 23 Oct '02

23 Oct '02

Hi, We have vnc support during installation but I have never made any use of it till a couple of days ago and I found it very usefull when auto-installing remote machines. To enable vnc, enter vnc=1 VNCPassword=<some password> on the command line. The installer will then show a URL on the console which you can connect to using a java enabled browser. Now you can monitor the installation in the browser.. Regards, Anas -- Anas Nashif <nashif(a)suse.com>, SuSE Linux AG Montreal (Laval), Canada

2 1

Disable CANCEL Button
by Joachim.Tork＠gad.de 22 Oct '02

22 Oct '02

Hello everybody, I wonder if it is possible to diable the CANCEL button during installation. Does anybody know ? Joachim

1 0

Speichern einer Konfiguration
by Claudia Goldbrunner 22 Oct '02

22 Oct '02

Hallo Wir haben vor ein paar Tagen SuSE 8.1 Prof installiert und dabei mit Erschrecken festgestellt, dass es nicht mehr moeglich ist, waehrend der Installation mit YAST die Konfiguration auf Diskette zu speichern um spaeter dann mit Hilfe dieser Diskette, auf anderen Rechnern die selbe Konfiguration installieren zu koennen. Versteckt sich diese Moeglichkeit jetzt irgendwo anders (nicht mehr im YAST) ? Ich kann mir fast nicht vorstellen, dass man dieses Feature nicht mehr integriert hat, da dass der Tod eines jeden admins ist, wenn er auf allen Rechnern die Packete von Hand installieren muss. Waere wirklich dankbar, wenn mir jemand verraten kann, was mit diesem Feature passiert ist. Gruss Claudia

2 1

How to save package sets in suse 8.1?
by "König, Oliver" 22 Oct '02

22 Oct '02

Hi, in suse 8.1 I can't find a simple feature of Yast2 in SuSE 8.0 in the menu "Install/Remove software" : "load/save package selections". Is there any possibility for that in SuSE 8.1. Since we have only few machines that are often configured quite differently, we'd like to install them by hand and simply copy the package selection set from another machine... Greetings ok ---------------------------------------------------- Oliver Koenig Center of Structure Technologies Institute of Mechanical Systems LEO C12 ETH Zurich CH-8092 Zurich Phone : +41 1 632 23 28 Fax : +41 1 632 17 02 Mail : okoenig(a)imes.mavt.ethz.ch WWW : http://www.imes.ethz.ch/st/ ----------------------------------------------------

2 1

Re: [suse-autoinstall] Manual steps on automated installation. And a BUG
by Holger Hellmuth 21 Oct '02

21 Oct '02

Hate to reply to my own mail, but I forgot to mention: The bug report is for vanilla Suse 8.1, but I haven't seen a patch on suse claiming to correct the problem, so I guess it still is a problem. Holger.

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 October 2002