May 2004 - openSUSE Autoinstall - openSUSE Mailing Lists

Re: installing SLES8 using autoyast and without any user interaction / problems with existing /dev/md?
by jochen.kirn＠daimlerchrysler.com 14 May '04

14 May '04

Steve, hmm, i already have these options included (see below), that's why I'm wondering <general> ... <mode> <confirm config:type="boolean">false</confirm> <forceboot config:type="boolean">false</forceboot> <interactive_boot config:type="boolean">false</interactive_boot> <reboot config:type="boolean">false</reboot> </mode> ... </general> in addition if I reinstall a previously installed system (which already has some raid devices, e.g. /dev/md0) autoyast complains that it can't create those raid devices because the autoyast installation process already detected the old raid device (of the old installation) and brings it up, thus it bugs me that it can't create a new one (with same name). A manual workaround for me is to switch to the second console (ALT+F2) and do the following 1) erase partition table manually (since putting it in a pre-installation-script doesn't helped either). $ dd if=/dev/zero bs=512 count=1 of=/dev/sda $ dd if=/dev/zero bs=512 count=1 of=/dev/sdb 2) reboot & restart autoyast installation Mit freundlichen Grüssen/best regards Jochen Kirn

2 1

Re: [suse-autoinstall] installing SLES8 using autoyast and withou tany user interaction
by Kohrs, Steven 14 May '04

14 May '04

On Fri, 2004-05-14 at 01:41, jochen.kirn(a)daimlerchrysler.com wrote: > > > > Hi everyone, > > I'm currently creating an autoyast.xml file for an unattended > installation > of SLES8 (using PXE). > so far everything went fine, except after the software rpms are > installed a > window pops up (textmode) > telling me that the boot loader was succesfully written to disc which > I > have to approve by clicking ok. > > I guess there is a way (xml-tag) to perform a complete and silent > installation without any user interaction Jochen, I believe this is what you're looking for: <general> ... <mode> <confirm config:type="boolean">false</confirm> <reboot config:type="boolean">false</reboot> </mode> ... </general> -- Sincerely, Steve Kohrs Distributed Systems 402.633.7058 This email and any files attached with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error delete this message and notify the sender at 402-341-0500. If you are not the named recipient you should not disseminate, distribute or copy this email or any attachment.

1 0

installing SLES8 using autoyast and without any user interaction
by jochen.kirn＠daimlerchrysler.com 14 May '04

14 May '04

Hi everyone, I'm currently creating an autoyast.xml file for an unattended installation of SLES8 (using PXE). so far everything went fine, except after the software rpms are installed a window pops up (textmode) telling me that the boot loader was succesfully written to disc which I have to approve by clicking ok. I guess there is a way (xml-tag) to perform a complete and silent installation without any user interaction thanks for any help Jochen Kirn

1 0

SuSE 9.1 autoinstall printer problem
by fschuett 11 May '04

11 May '04

Hallo, I use the autoinstall feature with 8.2 for our school network and it works great. I try to update to 9.1 and adapted the xml files to this. During the installation process there is an error similar to "cannot contact cups server" and the printer is not installed. The printer is attached to a printserver box D-Link DP-300 and with YaST the same printer configuration works fine. So I think the problem ist autoinstall related. Does anyone have a solution to this? I attach the installedSystem.xml file. Thank you. Bye -- Frank Schütte Gymnasium Himmelsthür fschuett(a)gymnasium-himmelsthuer.de

1 0

memo on windows
by A.L Paul 10 May '04

10 May '04

Hi all,I need to reassure someone just how unrealiable a windows platform can be especially if its used as a server of any sort and is a proxy to the internet.Also,and more importantly,I need facts and figures on the linux equivalent so that I can put things into proper perspective for them to wake up to reality. thanks Paul.

1 0

Minor problem w/ info file and custom kernel package
by Nicoya Helm 08 May '04

08 May '04

I'm just in the beginning stages of understanding SuSE's autoinstall process, which I'm implementing for an OpenMosix cluster. The scenario is that I have a server w/ the appropriate media directories, a standard SuSE boot CD, and a floppy w/ a custom autoinst.xml and info file at the root. And using SuSE 9.0 Yast 2. Problem 1: Info file not working. Because this is on a cluster, and for various reasons we don't want to run DHCP on the control node, I would like to use an info file to statically assign IP info and have the YaST look for the nfs install directory. Here's the contents of my info file: netdevice: eth0 ip: 192.168.1.200 netmask: 255.255.255.0 gateway: 192.168.1.200 install: nfs://192.168.1.1/usr/local/SuSE/current autoyast: floppy During the boot process the system searches for the info file, loads usb drivers, etc., searches for autoinstall file, then says "Sending DHCP request to eth0". I've watched, and the system reads the floppy drive both times. If I use this info file and autoinst.xml file on a network that has a DHCP server available, the network card grabs an IP, finds the nfs share, and proceeds to install according to my autoinst settings. But it fails if I use it on the cluster segment where no DHCP is available. I can do a manual installation, load the card drivers and manually enter all the IP and NFS info, and the autoinstallation proceed wonderfully. So my question is - what's wrong w/ my info file that the systems keep trying to use DHCP instead of the static info? Clearly they're getting at least some of the info from the file since the install finds the NFS shared okay. Problem 2: Not so much a problem as looking for additional tips/docu resources for how to make a custom kernel as part of the autoinstall process. I need to have the openmosix kernel installed, and am looking for the best way to accomplish this automatically. I tried to have it install as an addon package like any other RPM (like section 4.5.3 of the documentation says for general RPMS) - the install completes partially, then fails. However, I'm thinking I may be confused and should be adding it as a kernel package (is this any different than a standard RPM?) per section 4.5.4 of the documentation. If so, other than specifying the "kernel" property, is there anything different I will need to do to get the custom kernel to install automatically? Any suggestions very much appreciated! Nicoya Helm University of Kansas Medical Center nhelm2(a)kumc.edu

2 1

dhcpd.leases and SLES8 autoinstall
by Frank Samuel 07 May '04

07 May '04

Hi, I have a question regarding to autoinstall for SLES8. During the autoinstall of a node. The following two new leases are noticed in the dhcp.leases file. I feel surprised when I read the latter lease. Could someone explain what is the meaning of uid "\001\000PE\000\244\022"; Thanks a lot. lease 192.168.0.19 { starts 5 2004/05/07 10:35:48; ends 6 2004/05/08 10:35:48; binding state active; next binding state free; hardware ethernet 00:50:45:00:a4:12; } lease 192.168.0.19 { starts 5 2004/05/07 10:36:11; ends 6 2004/05/08 10:36:11; binding state active; next binding state free; hardware ethernet 00:50:45:00:a4:12; uid "\001\000PE\000\244\022"; } __________________________________ Do you Yahoo!? Win a $20,000 Career Makeover at Yahoo! HotJobs http://hotjobs.sweepstakes.yahoo.com/careermakeover

1 0

Re: [suse-autoinstall] Upgrade 9.0 -> 9.1 went totally wrong
by Wolfgang.Bauer＠schoellerbank.at 07 May '04

07 May '04

Hi Roy, no, my specs are: Athlon XP 1600, 768 MB RAM, 80 GB IDE (ATA-100), Geforce 440 MX, SB live, 2x ethernet, 1 firewire-card The funny thing was, that I was always told that the upgrade-program could not mount my root-partition but when I chose "reset options" (by not changing any options before) it recognised the root-partition... I guess, there could be a bug somewhere in the upgrade-program... I would love to track this problem down, but I fear that all logs were deleted. Yours, Gery ------------------------------------------------------------------- Dipl.-Ing. Wolfgang Gernot Bauer, Leiter Internet Schoellerbank AG, Sterneckstrasse 5, 5024 Salzburg, Austria/Europe Tel.: ++43-662-8684-364, Fax.: ++43-662-8684-44364 Email: mailto:wolfgang.bauer@schoellerbank.at, WWW: http://www.schoellerbank.at Diese Nachricht dient ausschließlich zu Informationszwecken und ist nur für den Gebrauch des Empfängers bestimmt. This message is only for informational purposes and is intended solely for the use of the addressee. Roy Butler <roy.butler@jpl. nasa.gov> An suse-autoinstall(a)suse.com 06.05.2004 22:27 Kopie Thema Re: [suse-autoinstall] Upgrade 9.0 -> 9.1 went totally wrong Gery, Is your root-partition on an SATA drive? If so, maybe the upgrade feature isn't accomodating the device file change between the 2.4 and 2.6 kernels. Roy Wolfgang.Bauer(a)schoellerbank.at wrote: > > > > > Hello everybody, > > I tried to install SuSE 9.1 yesterday by trying to Upgrade my > 9.0-installation. The nightmare was as follows: > > The first problem I encountered was that yast was not able to mount my > root-partition (reiserfs) although my 9.0-installation worked properly... > > After a few tries, I used the "Auto-Repair Installed System"-feature (if > you still use 9.0 - DONT USE THIS FEATURE!!!). First it worked very nicely > until it got to the point where it checked the installation. The > repair-function noticed that the 9.1-installation was faulty (right, as it > was a 9.0-installation) and upgraded some packages. After a reboot the > system did not come up (could not find kernel). Well, yast-installation > again - could not mount root-filesystem. Damn. > > I tried many things but when I used "Reset Options" from the menu on the > bottom YAST COULD MOUNT MY PARTITION - there were no other settings but (by > magic) now it worked (could this be a bug?!). But as the repair-system > changed my old 9.0-installation "There was an error upgrading your system". > > After I copied all my /home-data to my windowspartition via text-console > and freshly installed 9.1, I had a running linux-system again. But I really > have to say: poor upgrade-system. It used to work better with older > Suse-distributions... > > Btw. I'm not a Linux novice (I use Linux since 1994) but it seems that you > must not rely on "automatic upgrade functionalities"... > > Sad, sad. > > Gery > ------------------------------------------------------------------- > Dipl.-Ing. Wolfgang Gernot Bauer, Leiter Internet > Schoellerbank AG, Sterneckstrasse 5, 5024 Salzburg, Austria/Europe > Tel.: ++43-662-8684-364, Fax.: ++43-662-8684-44364 > Email: mailto:wolfgang.bauer@schoellerbank.at, WWW: > http://www.schoellerbank.at > > Diese Nachricht dient ausschließlich zu Informationszwecken und ist nur für > den Gebrauch des Empfängers bestimmt. > This message is only for informational purposes and is intended solely for > the use of the addressee. > > > -- > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > For additional commands, e-mail: suse-autoinstall-help(a)suse.com > > -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

SuSE SLES 8 and United Linux 1.0 autoinstall
by Frank Samuel 07 May '04

07 May '04

I have a question regarding to SLES8 autoinstall. I've done some experiments for SLES8 autoinstall without SP3. One experiment I did is copying the CDs to a dir of /usr/local/SLES8 in the order of UnitedLinux 3,2,1 and SLES8 and then removed some packages not used. After installation, Welcome to SuSE SLES8 ... will be in the file of /etc/issue. I didn't notice any problem happen during the installation. So is it a valid method? Another issue is how can I possibly install UnitedLinuxinstead of SLES8 using autoinstall? Copying three CDs of United Linux seems won't work. Thanks. __________________________________ Do you Yahoo!? Win a $20,000 Career Makeover at Yahoo! HotJobs http://hotjobs.sweepstakes.yahoo.com/careermakeover

2 2

Upgrade 9.0 -> 9.1 went totally wrong
by Wolfgang.Bauer＠schoellerbank.at 06 May '04

06 May '04

Hello everybody, I tried to install SuSE 9.1 yesterday by trying to Upgrade my 9.0-installation. The nightmare was as follows: The first problem I encountered was that yast was not able to mount my root-partition (reiserfs) although my 9.0-installation worked properly... After a few tries, I used the "Auto-Repair Installed System"-feature (if you still use 9.0 - DONT USE THIS FEATURE!!!). First it worked very nicely until it got to the point where it checked the installation. The repair-function noticed that the 9.1-installation was faulty (right, as it was a 9.0-installation) and upgraded some packages. After a reboot the system did not come up (could not find kernel). Well, yast-installation again - could not mount root-filesystem. Damn. I tried many things but when I used "Reset Options" from the menu on the bottom YAST COULD MOUNT MY PARTITION - there were no other settings but (by magic) now it worked (could this be a bug?!). But as the repair-system changed my old 9.0-installation "There was an error upgrading your system". After I copied all my /home-data to my windowspartition via text-console and freshly installed 9.1, I had a running linux-system again. But I really have to say: poor upgrade-system. It used to work better with older Suse-distributions... Btw. I'm not a Linux novice (I use Linux since 1994) but it seems that you must not rely on "automatic upgrade functionalities"... Sad, sad. Gery ------------------------------------------------------------------- Dipl.-Ing. Wolfgang Gernot Bauer, Leiter Internet Schoellerbank AG, Sterneckstrasse 5, 5024 Salzburg, Austria/Europe Tel.: ++43-662-8684-364, Fax.: ++43-662-8684-44364 Email: mailto:wolfgang.bauer@schoellerbank.at, WWW: http://www.schoellerbank.at Diese Nachricht dient ausschließlich zu Informationszwecken und ist nur für den Gebrauch des Empfängers bestimmt. This message is only for informational purposes and is intended solely for the use of the addressee.

2 1