October 2004 - openSUSE Autoinstall - openSUSE Mailing Lists

additional package requires/forcing install order
by Chris Carpinello 15 Oct '04

15 Oct '04

I have several thirdparty RPMs included within an autoinstall package selection. However, the requires list for these RPMs is very minimal and the RPMs get installed before the (undefined) prerequisite packages are installed. (For example, binutils and awk aren't installed yet when these packages attempt to use "cp" and "awk" because "binutils" and "awk" aren't in the requires list.) Without repackaging these RPMs from scratch with a lot of guesswork (the spec file isn't available), what options do I have to force additional prerequisites on these RPMs? Or is there a way to specify that a given package should be installed "later" rather than "sooner" in the process? In essence, I'm looking for something akin to EXTRA_PROV for requires (an "EXTRA_REQ" if you will). - Chris

1 0

services runlevel information ignored
by Chris Carpinello 15 Oct '04

15 Oct '04

I'm attempting to configure various services in a SuSE 9.1-based autoinstall. The default runlevel is recognized. However, the runlevel settings for the services (below) are being ignored during the CD install. User error or known bug? - Chris <configure> ... <runlevels> <default>3</default> <services config:type="list"> <service> <service_name>xdm</service_name> <service_status>disable</service_status> </service> <service> <service_name>smbfs</service_name> <service_status>disable</service_status> </service> <service> <service_name>slurpd</service_name> <service_status>disable</service_status> </service> <service> <service_name>ldap</service_name> <service_status>disable</service_status> </service> <service> <service_name>gpm</service_name> <service_status>disable</service_status> </service> <service> <service_name>apache2</service_name> <service_status>disable</service_status> </service> <service> <service_name>nfs</service_name> <service_status>disable</service_status> </service> <service> <service_name>nfsboot</service_name> <service_status>disable</service_status> </service> <service> <service_name>network</service_name> <service_start>2 3</service_start> </service> <service> <service_name>xntpd</service_name> <service_start>2 3</service_start> </service> </services> </runlevels> ... </configure>

1 0

X configuration for install and installed system
by Jesse Keating 15 Oct '04

15 Oct '04

I would like some more info regarding X config. The documentation says "FIXME" which doesn't help much. Using the autoyast module of yast2, I can set the monitor settings, and default depth, but there doesn't seem to be a way to hardcode the video chip. I would like to hardcode the 'VESA' driver to be used for both the install and the installed system. Is there a way to do this? -- Jesse Keating RHCE Pogo Linux -- Linux Systems Engineer tel: (888) 828-7646 ex: 436

1 0

Include file stubs in control xml
by Jesse Keating 15 Oct '04

15 Oct '04

I have a need to include external xml stubs in my control xml. Ideally, these stubs will be generated during a pre-script, and later included for things like disk partitioning, package selection, X configuration, stuff like that. Basically I'm a Kickstart admin, and I've written a python script that examines a system and some install time arguments and generates the above things on the fly according to our internal formulas. I need to replicate this system for SUSE installs using autoyast. Is this possible? -- Jesse Keating RHCE Pogo Linux -- Linux Systems Engineer tel: (888) 828-7646 ex: 436

5 11

use value for disk partitioning to reuse only Linux partitions
by Jesse Keating 12 Oct '04

12 Oct '04

I'm looking for the actual value that goes between <use></use> when listing out my partitions that says "Use only the existing Linux partitions". I'm pretty sure it exists given that the documentation talks about it, however I haven't seen the value listed. -- Jesse Keating RHCE Pogo Linux -- Linux Systems Engineer tel: (888) 828-7646 ex: 436

1 0

AW: [suse-autoinstall] Include file stubs in control xml
by Hollmann Frank 11 Oct '04

11 Oct '04

Hi, if SLES8 should be installed: rules don't work here. Frank Hollmann -----Ursprüngliche Nachricht----- Von: Martin Vidner [mailto:mvidner@suse.cz] Gesendet: Freitag, 8. Oktober 2004 10:23 An: Jesse Keating Cc: suse-autoinstall(a)suse.com Betreff: Re: [suse-autoinstall] Include file stubs in control xml On Thu, Oct 07, 2004 at 01:25:15PM -0700, Jesse Keating wrote: > I have a need to include external xml stubs in my control xml. > Ideally, these stubs will be generated during a pre-script, and later > included for things like disk partitioning, package selection, X > configuration, stuff like that. > > Basically I'm a Kickstart admin, and I've written a python script that > examines a system and some install time arguments and generates the > above things on the fly according to our internal formulas. I need to > replicate this system for SUSE installs using autoyast. Is this > possible? Hi Jesse, I think rules and classes could cover your needs: http://www.suse.de/~nashif/autoinstall/9.1/html/rulesandclass.html -- Martin Vidner, developer SuSE CR, s.r.o. e-mail: mvidner(a)suse.cz Drahobejlova 27 tel:+420-296542373 190 00 Praha 9, Czech Republic http://www.suse.cz -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

2 1

Updating install packages
by Ryan Allen 08 Oct '04

08 Oct '04

I have a http server that holds all the packages off my SuSE 9.0 CDs for remote installs. Is there an easy, automated method to update all the packages found on: http://www.suse.com/us/private/download/updates/90_i386.html I want to: 1) download JUST the packages listed as needing updating 2) put them in the directory I set up on the server 3) remove the old packages The only way I see to do this is one file at a time, without a bit of perl development, of course. What's the easiest way of doing this? Thanks, Ryan

1 0

Re: [suse-autoinstall] ISO Creation - Single CD Install
by Johannes Klug 07 Oct '04

07 Oct '04

"Jonathon M. Robison" <jrobiso2(a)ford.com> wrote on 07.10.2004 17:40:51: > I think you have to mess with the media.X files. Those files tell > the installer what CD has the needed rpm files. I just got a new idea: I'll install from DVD next. That way, YaST thinks there's only one "cd", methinks. I'll report if this was successful or not. Yet this will be next tuesday, earliest. Regards, Johannes

1 0

ISO Creation - Single CD Install
by Johannes Klug 07 Oct '04

07 Oct '04

Hello, I just tried to create an ISO file of my custom AutoYaST autoinst.xml file. The ISO was created, I burned it, and it really started to install. But then the installer asked me for the second SuSE 9.0 CD-ROM. I thought AutoYaST would copy all necessary rpms to ONE cd ... How can I make it burn a SINGLE cd-rom suitable for installation? Mit freundlichen Gruessen / Best regards Johannes Klug

1 0

Re: [suse-autoinstall] SLES9 autoinstall hangs at creating initrd
by Carl Pecinovsky 05 Oct '04

05 Oct '04

I don't see anything wrong with the directory structure, but you might want to check the PDF against the instructions given in the the release notes (CD1\docu\RELEASE-NOTES.en.html) under the section called "Setting up an installation server for network installations". Also, you should post at least the last part of the y2log. -Carl > I just cant get my network install to see the core distribution files. > It installs the SLES Admin guide then goes to "Finishing Basic Installation" > and hangs at "Creating initrd..." > I've followed http://yast2.suse.com/multiplesource/multiplesource.pdf > as closely as possible. > > Here is my directory > > ls -ld * > lrwxrwxrwx 1 root root 22 Oct 5 11:03 boot -> > sles9-x86_64/CD1/boot/ > lrwxrwxrwx 1 root root 24 Oct 5 11:03 content -> > sles9-x86_64/CD1/content > lrwxrwxrwx 1 root root 28 Oct 5 11:04 control.xml > -> sles9-x86_64/CD1/control.xml > drwxr-xr-x 6 root root 4096 Oct 5 11:03 core9-x86_64 > lrwxrwxrwx 1 root root 25 Oct 5 11:04 media.1 -> > sles9-x86_64/CD1/media.1/ > drwxr-xr-x 3 root root 4096 Oct 5 11:03 sles9-x86_64 > drwxr-xr-x 2 root root 4096 Oct 5 11:27 yast > > ls core9-x86_64/ sles9-x86_64/ yast/ > core9-x86_64/: > CD1 CD2 CD3 CD4 > > sles9-x86_64/: > CD1 > > yast/: > instorder order > > > cat yast/order > /sles9-x86_64/CD1 /sles9-x86_64/CD1 > /core9-x86_64/CD1 /core9-x86_64/CD1 > > cat yast/instorder > /sles9-x86_64/CD1 > /core9-x86_64/CD1 > > I can attach my y2log if anyone wants to see it. > > > Thanks for any help > Aaron > > > > On Mon, 4 Oct 2004, Durk S. wrote: > > > Okay peeps, as I already concluded earlier, my installation source wasn't > > completely okay. After some corrections, the AutoYaST install went like it > > should. > > > > Durk > > > >> Hey thanks! > >> > >> I've already found that PDF file, but this saves me a bit reading! ;-) > >> > >> Let's see if I can make a working network install this time. :-) > >> > >> Durk > >> > >>> Hi! > >>> > >>> Your source should look a bit different. > >>> > >>> From /usr/share/doc/packages/yast2-instserver/network-install.pdf: > >>> > >>> LINUX Enterprise Server 9 CD1 = SLES CD1 > >>> > >>> LINUX Enterprise Server 9 CD2 = CORE CD1 > >>> LINUX Enterprise Server 9 CD3 = CORE CD2 > >>> LINUX Enterprise Server 9 CD4 = CORE CD3 > >>> LINUX Enterprise Server 9 CD5 = CORE CD4 > >>> LINUX Enterprise Server 9 CD6 = CORE CD5 > >>> > >>> . > >>> |-- sles9-i386 > >>> | |-- CD1 > >>> | |-- boot > >>> | |-- docu > >>> | |-- media.1 > >>> | |-- suse > >>> | `-- yast > >>> |-- core9-i386 > >>> | |-- CD1 > >>> | |-- CD2 > >>> | `-- CD3 > >>> |-- boot -> sles9-i386/CD1/boot > >>> |-- media.1 -> sles9-i386/CD1/media.1 > >>> |-- content -> sles9-i386/CD1/content > >>> |-- control.xml -> sles9-i386/CD1/control.xml > >>> `-- yast SLES9 Network Install > >>> > >>> You have to set up a multisource installation as described in the PDF. > >>> > >>> Best regards, > >>> Andreas > >>> > >>> On Thu, 30 Sep 2004, Durk S. wrote: > >>> > >>>> Addition: > >>>> > >>>> I did a test with a floppy (for the profile) and SLES 9 CDs (as > >>>> installation source)... This actually works! So there must be > >>>> something wrong with my NFS installation source... or configuration > >>>> to find that source. > >>>> > >>>> The structure of the source looks like this: > >>>> > >>>> sles9 > >>>> sles9/boot > >>>> sles9/boot/root > >>>> sles9/boot/directory.yast > >>>> sles9/boot/README > >>>> sles9/boot/modules1 > >>>> sles9/boot/modules2 > >>>> sles9/boot/modules3 > >>>> sles9/boot/modules4 > >>>> sles9/boot/modules5 > >>>> sles9/boot/LIESMICH > >>>> sles9/boot/rescuefloppy > >>>> sles9/boot/loader > >>>> sles9/boot/loader/linux > >>>> sles9/boot/loader/10240768.spl > >>>> sles9/boot/loader/06400480.spl > >>>> sles9/boot/loader/memtest > >>>> sles9/boot/loader/message > >>>> sles9/boot/loader/12801024.spl > >>>> sles9/boot/loader/isolinux.bin > >>>> sles9/boot/loader/isolinux.cfg > >>>> sles9/boot/loader/initrd > >>>> sles9/boot/loader/16001200.spl > >>>> sles9/boot/loader/14001050.spl > >>>> sles9/boot/loader/bootlogo > >>>> sles9/boot/loader/08000600.spl > >>>> sles9/boot/README.DOS > >>>> sles9/boot/rescue > >>>> sles9/boot/LIESMICH.DOS > >>>> sles9/boot/bootdsk1 > >>>> sles9/boot/bootdsk2 > >>>> sles9/boot/bootdsk3 > >>>> sles9/boot/modules1.txt > >>>> sles9/boot/modules2.txt > >>>> sles9/boot/modules3.txt > >>>> sles9/boot/modules4.txt > >>>> sles9/boot/modules5.txt > >>>> sles9/sles9-i386/CD1/... (contents of SLES 9 CD 1) > >>>> sles9/sles9-i386/CD2/... (contents of SLES 9 CD 2) > >>>> sles9/sles9-i386/CD3/... (contents of SLES 9 CD 3) > >>>> sles9/sles9-i386/CD4/... (contents of SLES 9 CD 4) > >>>> sles9/sles9-i386/CD5/... (contents of SLES 9 CD 5) > >>>> sles9/sles9-i386/CD6/... (contents of SLES 9 CD 6) > >>>> sles9/yast > >>>> sles9/yast/order > >>>> sles9/yast/instorder > >>>> sles9/content > >>>> sles9/media.1 > >>>> sles9/media.1/directory.yast > >>>> sles9/media.1/media > >>>> sles9/media.1/products > >>>> sles9/media.1/info.txt > >>>> > >>>> I'm still figuring out this issue. > >>>> > >>>> Durk > >>>> > >>>>> Hi there, > >>>>> > >>>>> I've got exactly the same problem with a HP DL360 G3 using a > >>>>> network AutoYaST2 install. > >>>>> > >>>>> The last lines of y2log: > >>>>> > >>>>> 2004-09-30 13:57:50 <1> linux(697) [YCP] Storage.ycp:1573 > >>>>> CheckForLvmRootFs root=$["detected_fs":`ext2, > >>>>> "device":"/dev/cciss/c 0d0p7", "fs_options":$[], "fsid":131, > >>>>> "mount":"/", "nr":7, > >>>>> "region":[516, 16917], "type":`logical, "used_fs":`ext2, "uuid":"7f > >>>>> ca98f4-1cf7-4862-81c0-93866245ea3d"] > >>>>> dev=$["disk":"/dev/cciss/c0d0", "nr":7] 2004-09-30 13:57:50 <1> > >>>>> linux(697) [YCP] Storage.ycp:1576 CheckForLvmRootFs ret=false > >>>>> 2004-09-30 13:57:50 <1> linux(697) [YCP] Misc.ycp:146 > >>>>> WriteYaSTInf($["Keytable":"us.map.gz", "Language":"en_US", > >>>>> "RebootMsg":" 0", "Root":"reboot"]) = Keytable: us.map.gz > >>>>> Language: en_US > >>>>> RebootMsg: 0 > >>>>> Root: reboot > >>>>> 2004-09-30 13:57:50 <1> linux(697) [YCP] Bootloader.ycp:316 Writing > >>>>> bootloader configuration > >>>>> 2004-09-30 13:57:50 <3> linux(697) [libscr] Bootloader.ycp:361 No > >>>>> SCR instance found > >>>>> 2004-09-30 13:57:50 <1> linux(697) [YCP] Initrd.ycp:269 > >>>>> Initrd::Write called, changed: true, list: ["cciss"] > >>>>> 2004-09-30 13:57:50 <3> linux(697) [libscr] Initrd.ycp:294 No SCR > >>>>> instance found2004-09-30 13:57:50 <3> linux(697) [libscr] > >>>>> Initrd.ycp:296 No SCR instance found2004-09-30 13:57:50 <1> > >>>>> linux(697) [YCP] Initrd.ycp:304 Modules [] were added to initrd not > >>>>> using Initrd module > >>>>> 2004-09-30 13:57:50 <3> linux(697) [libscr] Initrd.ycp:313 No SCR > >>>>> instance found2004-09-30 13:57:50 <1> linux(697) [YCP] > >>>>> Initrd.ycp:316 Writing modules cciss 2004-09-30 13:57:50 <3> > >>>>> linux(697) [libscr] Initrd.ycp:317 No SCR instance found2004-09-30 > >>>>> 13:57:50 <3> linux(697) [libscr] Initrd.ycp:318 No SCR instance > >>>>> found2004-09-30 13:57:50 <3> linux(697) [libscr] Initrd.ycp:323 No > >>>>> SCR instance found2004-09-30 13:57:50 <3> linux(697) [libscr] > >>>>> Initrd.ycp:326 No SCR instance found2004-09-30 13:57:50 <3> > >>>>> linux(736) [ui] > >>>>> YUI_widgets.cc(createRichText):857 Invalid arguments for the Label > >>>>> RichText: `RichText > >>>>> (`opt (`plainText), nil) > >>>>> 2004-09-30 13:57:50 <3> linux(736) [ui] > >>>>> YUI_widgets.cc(widgetWithId):2426 No widget with `id( `ok_help ) > >>>>> 2004-09-30 13:57:50 <3> linux(736) [libycp] Initrd.ycp:254 No > >>>>> widget with `id( `ok_help ) > >>>>> > >>>>> I hope there's a solution. > >>>>> > >>>>> Durk > >>>>> > >>>>>> Date: Wed, 29 Sep 2004 10:01:15 +0200 > >>>>>> Message-ID: > >>>>>> <CD998562990BEA4D98E5EE624E492B3A5B163E(a)SMCR030V.corp1.ad1.seb.net> > >>>>>> From: <anders.g.karlsson(a)seb.se> > >>>>>> Subject: [suse-autoinstall] SLES9 autoinstall hangs at creating > >>>>>> initrd > >>>>>> > >>>>>> > >>>>>> Hi, > >>>>>> > >>>>>> I've run into a problem when doing an autoinstall (SLES9) from a > >>>>>> CD that I created using the YaST2 tools. Everything runs smooth up > >>>>>> to the point where it is "Creating initrd...", at this point the > >>>>>> installation just hangs. I'm trying to install on an HP DL380 G3 > >>>>>> with the cciss hardware raid driver. Anyone has the same > >>>>>> experience? > >>>>>> > >>>>>> Regards, > >>>>>> Anders > >>>>> > >>>>> > >>>>> > >>>>> -- > >>>>> To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For > >>>>> additional commands, e-mail: suse-autoinstall-help(a)suse.com > >>>> > >>>> > >>>> > >>>> > >>>> > >>> > >>> -- > >>> Andreas Vetter > >>> Universitaet Wuerzburg, Theoretische Physik 1 > >>> Am Hubland, 97074 Wuerzburg, Deutschland / Germany > >>> > >>> -- > >>> 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 > > > > > > > > > >

2 1