November 2004 - openSUSE Autoinstall - openSUSE Mailing Lists

How do I prevent re-install?
by Dave Thacker 13 Nov '04

13 Nov '04

Goal: Unnattended install of SUSE 9.1 using autoyast2. I've successfully done a minimal installation using auto-yast on SuSE 9.1. After the client finished install, it rebooted. It's set to boot from PXE so it started up the entire install process. and started to install again. I have <forceboot config:type="boolean">false</forceboot> set in the config file. In chapter 4 of the docs it states: "Change starting from SUSE Linux 9.1/SLES9 The reboot property in the mode resource was used to force a reboot after initial system setup and before the system is rebooted for the first time. Currently after initial installation all systems must reboot, which makes thes option obsolete." Given that a reboot is inevitable, how do I stop a perpetual install loop? DT -- Dave Thacker Senior Systems Administrator Omni Hotels Reservation Center V:402-952-6535 F:402-334-8013 M: 402-981-4613 (24/7)

3 2

How to set up PXE server?
by Hugo 12 Nov '04

12 Nov '04

Hello! I asked this on another SuSE list and I was directed here. I tried to search the archives as well as google for the answers, but I really can't find any good tutorial or how to. Here is my problem: I have an old laptop without CD-drive. It really needs a new install and doing it from floppy isn't really a option. But it can boot from the network. Two uses for that computer (dual boot): 1) general web - for this I was planning SuSE (400MHz Celeron, with 128Mb) 2) Kids' CD-roms for my kid - I could not get these running with wine... so it means either win98 or win2k. The installed (and broken) OS is Win98, but I have original installation CD for both windows. I have found that PXE is something connected to a DHCP server. But the first problem is that I already have a DHCP server on my network (NAP box). I was planning on using my SuSE 9.1 pro for suplying the installations for the laptop, so how do I do this? Next problem is the windows... The only guides that I have seen involve booting linux... although not very throughout help for that either. I'd like to start the windows or SuSE 9.1 installation over the network. How do I prepare the installation CD's for this? I'm also planning to install my little old Norton Ghost 2003 for backup in which ever windows ends up working better with the CD-roms. Restoring the image means booting from floppy (which I can do when I get them installed in the first place) but it would be much nicer if I could boot that floppy from the network also (i.e. when the win98 gets messed up, just boot from the net and reinstall the image for win98.) I believe that I should be able to do this with SuSE 9.1... but how? -- HG

2 2

Keeping partitions with SuSE 9.2
by Andreas Haupt 12 Nov '04

12 Nov '04

Hello, when upgrading a host to a newer SuSE version I used the partitioning feature "Using existing mount table" with SuSE 9.1. This is explained under: http://www.suse.de/~nashif/autoinstall/9.1/html/CreateProfile.Partitioning.… With AutoYast in SuSE 9.2 this does not work any more. Yast complains with "Error: No proposal" under "Partitioning" when it shows the installation summary before the real installation. Has this feature been dismissed or is there a different syntax now? Thanks in advance Andreas -- | Andreas Haupt | E-Mail: andreas.haupt(a)hmi.de | Hahn-Meitner-Institut (DN) | WWW: | Glienicker Straße 100 | Phone: +49/30/8062-2597 | 14109 Berlin | Fax: +49/30/8062-2096

1 0

dtd problems on SLES9 PPC
by Frank Steiner 11 Nov '04

11 Nov '04

Hi, I'm installing SLES 9 on IBM pSeries (power4 cpus). I first installed it manually and grepped the xml files from cloning the machine to build a general installation. Two proplems arise: 1) That's what cloning the machine and saving the profile gives me for the bootloader: <bootloader> <activate config:type="boolean">true</activate> <board_type>chrp</board_type> <default>linux</default> <loader_device>/dev/sda1</loader_device> <loader_type>ppc</loader_type> <location>custom</location> <of_defaultdevice config:type="boolean">true</of_defaultdevice> <prep_boot_partition>/dev/sda1</prep_boot_partition> </bootloader> However, checking the file with nsgml and the dtd files from the autoyast2-installation.rpm tells me: nsgmls:profiles/part_hal_keep.xml:7:28:E: there is no attribute "config:type" nsgmls:profiles/part_hal_keep.xml:7:37:E: element "activate" undefined nsgmls:profiles/part_hal_keep.xml:8:17:E: element "board_type" undefined nsgmls:profiles/part_hal_keep.xml:9:14:E: document type does not allow element "default" here nsgmls:profiles/part_hal_keep.xml:13:36:E: there is no attribute "config:type" nsgmls:profiles/part_hal_keep.xml:13:45:E: element "of_defaultdevice" undefined nsgmls:profiles/part_hal_keep.xml:14:26:E: element "prep_boot_partition" undefined I ignore it because the xml file works for installing further machines, but I guess the dtd files should be corrected. 2) For checking the profiles while writing them, I copied the dtd files to a path relative to my profiles. My autoyast dir that I pass to autoyast has the structure rules/ profiles/ dtd/ where rules/ contains rules.xml. All my manually written profiles as well as the rules.xml start with <!DOCTYPE profile SYSTEM "../dtd/profile.dtd"> which works well when I check my files with nsgml. For installing, I use a rules.xml with: <rule> <arch> <match>ppc64</match> <match_type>exact</match_type> </arch> <result> <profile>profiles/lmuppc.xml</profile> <continue config:type="boolean">true</continue> </result> </rule> <rule> <hostaddress> <match>141.84.1.134</match> <match_type>exact</match_type> </hostaddress> <result> <profile>profiles/part_hal_keep.xml</profile> <continue config:type="boolean">true</continue> </result> </rule> where both of the profiles containt the "../dtd.." stuff. When I run the installation with this rules.xml, I get an error message /tmp/YaST2-.../rules/profiles/lmuppc.xml:2: warning: failed to load external entity "/tmp/YaST2-.../rules/dtd/profile.dtd" <!DOCTYPE profile SYSTEM "../dtd/profile.dtd"> Likely, the dtd file were not copied over to the /tmp/YaST2-.../rules/ dir. But, this error does not occur if I put the contents of part_hal_keep.xml into lmuppc.xml and work with only one profile in rules.xml! Then the whole installation runs through. Thus, only when using more than one profile in rules.xml, it fails. Any thoughts? 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. *

1 0

RE: [suse-autoinstall] upgrading from 9.0 to 9.2
by Ryan Allen 11 Nov '04

11 Nov '04

> -----Original Message----- > From: Thomas Schweikle [mailto:tps@vr-web.de] > Sent: Wednesday, November 10, 2004 1:50 AM > To: Ryan Allen > Subject: Re: [suse-autoinstall] upgrading from 9.0 to 9.2 > > Ryan Allen schrieb: > > > > > I'm quite lost. It currently appears that we cannot upgrade from 9.0 > to > > 9.2. I've set up the system to PXE boot, and transfer the files to the > > client with HTTP. The HTTP log on the 9.2 PXE/install server is > > reporting the following: > > > > [Tue Nov 09 15:02:12 2004] [error] [client 169.254.100.211] File does > > not exist: /srv/www/htdocs/suse/media.1/info.txt > > [Tue Nov 09 15:02:12 2004] [error] [client 169.254.100.211] File does > > not exist: /srv/www/htdocs/suse/part.info > > [Tue Nov 09 15:02:12 2004] [error] [client 169.254.100.211] File does > > not > > exist: /srv/www/htdocs/suse/driverupdate > > > > And it's right, those files do not exist. What are the secrets for > > getting autoinstall running on 9.2?? > > These Files exist on DVD an CDROM. Try copying them from there. > > -- > Thomas This is incorrect. The three files listed above are not included in the 9.2 media. They are not on the CDs or the DVDs. I appears that autoinstall is completely broken with 9.2. I have not heard from anybody on this list that has info on 9.2. Perhaps I am the only one who has tried it? Anas?? Thanks, -- Ryan

2 1

evms
by Edward Tast 10 Nov '04

10 Nov '04

Hello, Does anyone know if it is possible to setup evms with autoinstall? If so, can you please provide an example or point me in the right direction? Thanks much.....

1 0

RE: [suse-autoinstall] upgrading from 9.0 to 9.2
by Ryan Allen 09 Nov '04

09 Nov '04

Just wondering if anybody got this message.... I'm quite lost. It currently appears that we cannot upgrade from 9.0 to 9.2. I've set up the system to PXE boot, and transfer the files to the client with HTTP. The HTTP log on the 9.2 PXE/install server is reporting the following: [Tue Nov 09 15:02:12 2004] [error] [client 169.254.100.211] File does not exist: /srv/www/htdocs/suse/media.1/info.txt [Tue Nov 09 15:02:12 2004] [error] [client 169.254.100.211] File does not exist: /srv/www/htdocs/suse/part.info [Tue Nov 09 15:02:12 2004] [error] [client 169.254.100.211] File does not exist: /srv/www/htdocs/suse/driverupdate And it's right, those files do not exist. What are the secrets for getting autoinstall running on 9.2?? Thanks! -- Ryan > -----Original Message----- > From: Ryan Allen [mailto:r.allen@f5.com] > Sent: Monday, November 08, 2004 12:42 PM > To: suse-autoinstall(a)suse.com > Subject: [suse-autoinstall] upgrading from 9.0 to 9.2 > > > > Hi all, > > > > I'm trying to upgrade my autoyast setup from SUSE 9.0 to SUSE9.2. A few > questions: > > > > 1) Is there an automatic way to import my autoyast.xml file? When > I run the "check profile validity" command in the yast2 module, I get > many many errors. I "opened" the 9.0 .xml file in the 9.2 GUI, then > immediately saved it. Running diff between them showed many changes, > but still many errors. Any suggestions? > > 2) There is no "make ISO" image in the yast2 autoyast module like > 9.0 had. What is the easiest way to copy ONLY the required .rpm > packages from the source tree and make an iso image? I need to get our > standard server distribution to fit on one CD > > > > > > Thanks for your help, > > > > - Ryan > > > > > > >

1 0

Resolving dependencies
by Dave Thacker 09 Nov '04

09 Nov '04

Greetings list! We're about to embark on an adventure using autoyast2 on 10 new servers. Some of these servers will run heartbeat and/or ultramonkey, which requre changes from the default kernel. Once I've created an autoyast config, is there a way to test it for dependencies? If not, how can I capture the results of a working install and import them into autoyast2? TIA DT -- Dave Thacker Senior Systems Administrator Omni Hotels Reservation Center V:402-952-6535 F:402-334-8013 M: 402-981-4613 (24/7)

1 0

Re: [suse-autoinstall] New Stupid user Questions
by Robert Morrow 09 Nov '04

09 Nov '04

I have tryed to remove all executable permitions of the file and it still does not work... >>> Johannes Klug <Johannes.Klug(a)dreger.de> 11/09/04 7:52 AM >>> "Robert Morrow" <rmorrow(a)kumc.edu> wrote on 08.11.2004 15:46:07: > I have been put incharge of setting up an auto-install for 30 + > machines. I have does this befor using the autoyast utility and never > editing the xml at all. But as i am trying to do it again I can not seem > to get the install to read my autoinst.xml file. I am running Suse > Enterprise 9.1. > > Robert Morrow Hello Robert, check permissions of autoinst.xml. If it's executable, yast won't read it. I had this problem after carrying my xml file to another using a floppy disk. Regards, Johannes Klug

1 0

New Stupid user Questions
by Robert Morrow 09 Nov '04

09 Nov '04

I have been put incharge of setting up an auto-install for 30 + machines. I have does this befor using the autoyast utility and never editing the xml at all. But as i am trying to do it again I can not seem to get the install to read my autoinst.xml file. I am running Suse Enterprise 9.1. Robert Morrow

2 1