July 2006 - openSUSE Autoinstall - openSUSE Mailing Lists

RE: [suse-autoinstall] SLES 10 RC2 remove-packages section?
by Matt Gillard 05 Mar '08

05 Mar '08

I dont have kinternet installed. This is what doesnt seem to work: <software> <patterns config:type="list"> <pattern>default</pattern> <pattern>Basis-Devel</pattern> <pattern>x11</pattern> </patterns> <packages config:type="list"> <packages>perl-libwww-perl</packages> <packages>net-snmp</packages> <packages>kernel-source</packages> </packages> <remove-packages config:type="list"> <packages>pptp</packages> <packages>smpppd</packages> <packages>ppp</packages> <packages>wvdial</packages> <packages>mutt</packages> </remove-packages> </software> In y2log it mentions that those packages should be removed, but it goes ahead and installs them anyway. I can do it manually on the command line: # rpm -e pptp smpppd ppp wvdial mutt and that works fine so I know I have no dependency problems. matt > -----Original Message----- > From: Uwe Gansert [mailto:ug@suse.de] > Sent: Friday, 30 June 2006 12:50 AM > To: suse-autoinstall(a)suse.com > Subject: Re: [suse-autoinstall] SLES 10 RC2 remove-packages section? > > > On Thursday 29 June 2006 16:45, Manfred Hollstein wrote: > > > If that fails, you have kinternet installed; add that to > the list and it > > should work. > > good point. > <remove-packages> can not break dependencies and so it's very > likely that > there is still a package that needs those packages. > I did a very small installation with no X - so it worked for me. > > -- > ciao, Uwe Gansert > > Uwe Gansert, Server Technologies Team > SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nuernberg, Germany > Fax: +49-(0)911-74053-476, Web: http://www.suse.de/~ug > now playing Covenant - Wasteland > > -- > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > For additional commands, e-mail: suse-autoinstall-help(a)suse.com > > This email and any attachments may contain privileged and confidential information and are intended for the named addressee only. If you have received this e-mail in error, please notify the sender and delete this e-mail immediately. Any confidentiality, privilege or copyright is not waived or lost because this e-mail has been sent to you in error. It is your responsibility to check this e-mail and any attachments for viruses. No warranty is made that this material is free from computer virus or any other defect or error. Any loss/damage incurred by using this material is not the sender's responsibility. The sender's entire liability will be limited to resupplying the material.

4 6

Scripting dirinstall?
by Teun 25 Feb '07

25 Feb '07

Does anyone know if it is possible to use the 'dirinstall' from the command line? For instance i would like to be able to do something like: # yast dirinstall -d /someroot -s mypackages.sel If i do yast -h it says: "Usage: /sbin/yast [OPTIONS] [MODULE] [module specific parameters]" But is there a way to find out what 'module specific parameters' are available for a specific module? Thanks, Teun

3 2

Problems with bootloader configuration in autoyast SLES10 RC3
by Matt Gillard 13 Sep '06

13 Sep '06

I have logged SR#10273247971 for this but I thought I would get peoples thoughts here as well. Problem is with the <default> global parameter in the <bootloader> section of autoyast. This works fine: <bootloader> <loader_type>lilo</loader_type> <location>mbr</location> </bootloader> Default kernel is SLES_10 as expected. This doesnt work, during boot loader installation an error is given that there is no default value given in lilo.conf. This occurs if I put an entry in the <default> tag or not. <bootloader> <global> <default>SLES_10</default> <gfxmenu></gfxmenu> <prompt>1</prompt> <timeout config:type="integer">5</timeout> </global> <loader_type>lilo</loader_type> <location>mbr</location> </bootloader> ie: This also gives the same error for the default tag. It should default to SLES_10 - I should not have to specify it. <bootloader> <global> <default></default> <gfxmenu></gfxmenu> <prompt>1</prompt> <timeout config:type="integer">5</timeout> </global> <loader_type>lilo</loader_type> <location>mbr</location> </bootloader> And this also the same error: <bootloader> <global> <gfxmenu></gfxmenu> <prompt>1</prompt> <timeout config:type="integer">5</timeout> </global> <loader_type>lilo</loader_type> <location>mbr</location> </bootloader> The reason I am doing this is because I do *not* want a graphical menu so I want to specify nothing for <gfxmenu> which seems to work ok. The text of the error during the bootloader config/installation phase is: "Value expected for 'default' at or above line 11 in file /etc/lilo.conf." And sure enough in /mnt/etc/lilo.conf at that point of the installation default has no value. thanks -- Matt Gillard UNIX Systems Engineer Coles Myer Ltd | Lvl 4 236 Bourke St | +61 3 963 51926 This email and any attachments may contain privileged and confidential information and are intended for the named addressee only. If you have received this e-mail in error, please notify the sender and delete this e-mail immediately. Any confidentiality, privilege or copyright is not waived or lost because this e-mail has been sent to you in error. It is your responsibility to check this e-mail and any attachments for viruses. No warranty is made that this material is free from computer virus or any other defect or error. Any loss/damage incurred by using this material is not the sender's responsibility. The sender's entire liability will be limited to resupplying the material.

4 13

SLES 10: more than one primary partition?
by Holger Reif 21 Aug '06

21 Aug '06

Hi, I'm trying to use the partition scheme that used for partitioning SLES8 and SLES9 systems. The minimal autoinst.xml snippet looks like <partitioning config:type="list"> <drive> <initialize config:type="boolean">true</initialize> <partitions config:type="list"> <partition> <filesystem config:type="symbol">VAR_boot_filesystem</filesystem> <format config:type="boolean">true</format> <mount>/boot</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">1</partition_nr> <size>96M</size> </partition> <partition> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <mount>swap</mount> <partition_id config:type="integer">130</partition_id> <partition_nr config:type="integer">5</partition_nr> <size>8192M</size> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <mount>/</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">2</partition_nr> <size>max</size> </partition> </partitions> <use>all</use> </drive> What I expect is: 1st primary 96M /boot 2nd primary some 130G / 1st logical 6G swap What I get is: / # fdisk -l Disk /dev/cciss/c0d0: 146.8 GB, 146807930880 bytes 255 heads, 63 sectors/track, 17848 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/cciss/c0d0p1 1 13 104391 83 Linux /dev/cciss/c0d0p2 14 17848 143259637+ f W95 Ext'd (LBA) /dev/cciss/c0d0p5 14 16803 134865643+ 83 Linux /dev/cciss/c0d0p6 16804 17848 8393931 82 Linux swap / Solaris BTW. If I do not specify partition_id and partition_nr for swap then root get's first logical partion and swap second one. Is there any chance to force / to be a primary partition w/o using part.info? http://www.suse.de/~ug/autoyast_doc/CreateProfile.Partitioning.html#id25297… sugests that my snippet should do what I want... br Holger Reif -- Echte DSL-Flatrate dauerhaft für 0,- Euro*. Nur noch kurze Zeit! "Feel free" mit GMX DSL: http://www.gmx.net/de/go/dsl

2 2

SLES10 - Bootloader configuration
by tobias.mucke＠man-mit.com 02 Aug '06

02 Aug '06

Hi list, familiar with SuSE autoinstallation environments since ALICE I trying hard right now to implement an AutoYaST environment with SLES10. Understanding that there are some changes compared to AutoYaST delivered with SLES9 I guess the following scenario is a nice starting point. 1. Install a standard system manually 2. Clone this system with AutoYaST (last option before installation is finished) 3. Try to understand the XML configuration step by step 4. Implement AutoYaST environment by rules and classes Right now I have the following problem: Starting with a whole file called autoinst.xml I cut out (without any changes) the bootloader section to copy it into another file called bootloader.xml. This one is included through the rules concept which works fine for other configuration items. If I don't include the bootloader.xml not right at the beginning GRUB is not configured! Man, that was quite hard to find out (first I used classes and met the same failure). I would like to track the problem, so that we come from a very undetailed view "GRUB is not configured, because of XML include failure" to the real technical problem. What can I do to support the development? Thanks a lot. Mit freundlichen Grüßen Tobias Mucke ------------------------------------------------------------------------------- MAN IT Services GmbH Abt. MIT-EE Linux-System-Technik Ohmstr. 12 D-85757 Karlsfeld Büro: Dachauer Str. 667 D-80995 München Tel.: +49 (0) 89 1580 5269 mailto:tobias.mucke@man-mit.com http://www.man.de ------------------------------------------------------------------------------- This message and any attachments are confidential and may be privileged or otherwise protected from disclosure. If you are not the intended recipient, please telephone or email the sender and delete this message and any attachment from your system. If you are not the intended recipient, you must not copy this message or attachment or disclose the contents to any other person.

2 2

CD Creator
by Paul DiSciascio 31 Jul '06

31 Jul '06

Has anyone had any luck using the CD Creator interface to roll a CD from an autoinst.xml file? I tried it, but what it created is complete junk: lots of files missing. So then I attempted to loop through the pattern files I want to use and just copy all the appropriate rpms onto my CD, but I wind up missing lots of dependencies that way, and sorting through them is taking a long time. Any help is appreciated. Thanks, Paul P.S. is there a command-line interface to the CD Creator?

1 0

Re: [suse-autoinstall] sax2 in a post-install script
by Laura Jordana 31 Jul '06

31 Jul '06

Thank you Lee and Uwe, using the full path worked like a charm! Lee Mayes wrote: > Hi Laura, > > I use the following snippet in the scripts stanza, it seems to work: > > <chroot-scripts config:type="list"> > <script> > <chrooted config:type="boolean">true</chrooted> > <filename>sax-config</filename> > <interpreter>shell</interpreter> > <location></location> > <source><![CDATA[#!/bin/bash > test -x /usr/sbin/sax2 || exit 0 > /usr/sbin/sax2 --auto > ]]></source> > </script> > </chroot-scripts> > > Best Regards, > > Lee > On Fri, 2006-07-28 at 13:16 -0700, Laura Jordana wrote: >> This is happening even when I put it in the post-script. I don't get it, >> because once the system boots I can run sax2 just fine. I must be >> missing something. >> >> Laura Jordana wrote: >>> I found the culprit - /var/adm/autoinstall/logs tells me sax2 is not >>> being found. Should it be in a post-install script in this case? I'll >>> try that again and then see what the logs say. >>> >>> Uwe Gansert wrote: >>>> On Monday 03 July 2006 19:38, Laura Jordana wrote: >>>> >>>>> Is there something wrong? I put this directly under an existing chroot >>>>> script. After the </chroot-scripts> tag of course. It's all in between >>>>> the <configure> tags so I can't figure out why it doesn't seem to be >>>>> running. I tried commenting out the <X11> section as well, and that >>>>> didn't seem to do anything either. Any suggestions? >>>> take a look at /var/adm/autoinstall/logs >>>> there you can find some logs about the scripts running >>>> Maybe there is something useful in them. >>>>

1 0

Including NVIDIA Driver into autoinstall
by André Hirschi 31 Jul '06

31 Jul '06

Good evening I'm still on my way to a fully automated SuSE 10.1 Installation. I'm currently stuck with the NVIDIA Driver. Has anybody managed to do that? I tried to do it with several ways, like including a small script into my autoinst.xml, but everything fails. The last thing I tried was going with "init-scripts", but that gave me the error: WARNING: Skipping the runlevel check (the utility 'runlevel' failed to run). Next error is that I appear to be running an X server etc (what is wrong, default runlevel is 3). Any suggestions on how to solve this? Kind regards André

3 4

How to install all packages at once?
by Trond Eivind Glomsrød 31 Jul '06

31 Jul '06

Scenario: Automated installs of SLES10 from a repository with "CD1" etc, installdir given as http://<...>/os_sles10_x8664/CD1 We're trying to run some chroot scripts, which according to the docs are run after all packages are installed. Unfortunately, that's not correct - some packages (from other CDs) are installed after boot (with no further interaction, even). And one of those packages is needed for the post script. In order to work around this.... * Is there a way to make it behave like one would expect: install all packages before booting? Yast knows about the repositories containing CD2-4. * alternatively, is there a way to make autoyast run the chroot script when it actually has installed all the packages instead of when it currently does it? (before the boot) Or failing that, is there an easy way to create a "DVD"-repository from the CDs, to work around this behaviour? The repository docs only mentions how to create it from CDs. -- Trond Eivind Glomsrød Technical Manager Scali - www.scali.com Scaling the Linux Datacenter

2 1

locations of classes
by Michael T. Halligan 31 Jul '06

31 Jul '06

Quick question about classes. If I create a class file say for general partitioning, and then do a network install from a path of ftp://10.10.10.10/SUSE .. with my control fiel in ftp://10.10.10.10/SUSE/blah.xml, would I just call class.xml from blah.xml without a path, and put class.html into the same directory that blah.xml resides in?

2 1