October 2005 - openSUSE Autoinstall - openSUSE Mailing Lists

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

passing boot ( interactively) options to grub combined with with using the menu.lst
by Hans-Joachim Ehlers 25 Nov '05

25 Nov '05

Hi folks, i am trying to move a Suse Installation CD to a USB-Stick so i can use the USB Stick for installation. The suse installation has the wonderfull option that you can add on a command line additional parameters to the kernel . Like: -> Select Installation -> On the command line add: hostname=myws At the moment i am able to boot from the USB-Stick with grub and can select 'Installation' from the grub menu. But how do i add additional parameter to grub without the need to modify the menu.lst ? Like the isolinux.cfg when booting from cd/dvd Extract from the menu.lst .. title Installation root (hd0,0) kernel /boot/loader/linux root=dev/sda1 vga=791 initrd /boot/loader/initrd tia Hajo ============================ Hans-Joachim Ehlers UNIX Systems Engineer EUMETSAT Am Kavalleriesand, 31 64295, Darmstadt, Germany Tel : +49 6151 807-7307 mailto:hansjoachim.ehlers@eumetsat.int http://www.eumetsat.int

2 1

Re: [suse-autoinstall] Best practices for adding external package sources?
by Michael T. Halligan 03 Nov '05

03 Nov '05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Michael, Is there a good searchable site for the archives? Right now, the best I've found is http://lists.suse.com/archive/suse-autoinstall/ and not very useful... Perhaps a FAQ on this topic would be appropriate at this point, if anybody @ Novell is reading this.. Since it comes up so often. Mihcael On Oct 18, 2005, at 4:03 PM, Michael Marion wrote: > On 18 Oct, Michael T. Halligan wrote: > > >> I have two dilemmas with AutoYast I'm sure somebody here will be able >> to help me solve. They're >> really the same issue, and that is adding external rpms. >> > > Both of what you want to do can be easily solved using a custom > path with > custom RPMS. > > Look in the archives for the subject: > > Additional Package & Silent install > > One message of which also talks about 2 other threads with more in- > depth info. > > -- > Mike Marion-Unix SysAdmin/Staff Engineer-http://www.qualcomm.com > Frasier: "...we know for whom the bell tolls." > [A bell dinging is heard, everyone looks around a little confused] > Martin: "Anybody else hear that?" > Daphne: "Oh! The biscuits!" --Fraiser > > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Darwin) iD8DBQFDXx9AwjCqooJyNAMRArHOAJ94RnQFYkwOuurmFUGocMH0CrVKGACdHO2s pEdANrCvZt0Y8lj4Bq8z3OM= =7Az6 -----END PGP SIGNATURE-----

4 6

(Auto-)install multiple languages?
by Thomas Ribbrock 03 Nov '05

03 Nov '05

Hi all, after I just finished my first succesful autoinstall (yeah!) :-) I am left with a couple of questions as to how to improve it further. One thing I need to do is to automatically install more than one language - basically like you do under YaST2 in the "language" module with adding "Secondary Languages". I have seached through http://www.suse.de/~ug/autoyast_doc/ as well as through the archive of this list http://marc.theaimsgroup.com/?l=suse-autoinstall&r=1&w=2 but came up empty. Is there an easy way to accomplish this? If not, I can think of only two alternatives: - Manually add all language related packages for the languages I need to the package list (brrrrr...) - Try to do some script-wizardry in post-install or init? I have yet to figure out whether I can convince YaST2 to add the secondary languages from the commandline - if not, I'm down to the first option... Any hints (including docs I might have missed...) are welcome! Cheerio, Thomas

4 7

Strange behaviour of autoinstall
by Bernhard Duebi 02 Nov '05

02 Nov '05

Dear everybody, I have two problems: 1) CD Creator doesn't respect SP2 2) ncompress package is not installed I use a custom CD to install all our servers. I create the CD with SuSE Yast CD Creator. With SLES9 SP1 everything was fine. With SP2 I noticed that not all files on the CD are up to date. The driverupdate file comes from the SP1 CDs. The /boot comes even from the original SLES9 CDs. I fixed this by copying the SP2 files into the directory and regenerating the ISO image by hand, but I think this is the job of CD Creator. I need /usr/bin/uncompress to install one of our enterprise tools. In SP1 this was in the sharutils package. With SP2 it moved to the ncompress package. Though, I added the ncompress package to my XML file and recreated the ISO image. When I install a machine with this new CD, the GUI tells me that the ncompress package is being installed. The Yast logfiles, tell me that the installation of ncompress was successful. But if I do a rpm –q ncompress it tells me that ncompress is not installed and I can't find the /usr/bin/uncompress on disk. If I do rpm –ihv /media/cdrom/suse/*/ncompress*.rpm it installs cleanly. I also installed the machine with an install-server using the same XML files. The result is the same. The logfiles tell me that ncompress was successfully installed, but the files are not on disk. Any idea what's happening here ? Sincerely Bernhard Dübi

2 1

Re: [suse-autoinstall] Warum ist SLES9
by Petteri Hakkarainen 28 Oct '05

28 Oct '05

Kaikki RPM:t eivät aina asennu. Petteri -----Original Message----- From: Christian Goetze <cg(a)sensage.com> To: suse-autoinstall(a)suse.com Date: Fri, 28 Oct 2005 11:58:37 -0700 Subject: [suse-autoinstall] Warum ist SLES9 "Full-Installation" nicht full installation? Wieso werden nicht alle *-devel rpms installiert wenn ich "Full Installation" auswaehle? Im Moment muss ich eine Menge extra *-devel RPMs explizit angeben... -- cg -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

2 1

Warum ist SLES9 "Full-Installation" nicht full installation?
by Christian Goetze 28 Oct '05

28 Oct '05

Wieso werden nicht alle *-devel rpms installiert wenn ich "Full Installation" auswaehle? Im Moment muss ich eine Menge extra *-devel RPMs explizit angeben... -- cg

1 0

SuSE 10.0: howto put an info file into initrd
by Gunreben, Peter (Peter) 28 Oct '05

28 Oct '05

Hi, if you want to put an "info" file into the SuSE 10.0 initrd, e.g. for creating an autoinstall-CD, you can do it in the following way: ============= 8< ============ mv initrd{,.gz} gunzip initrd.gz echo info | cpio -o -H newc -A -F initrd gzip -9 initrd mv initrd{.gz,} ============= 8< ============ It took me a while to notice the necessary "-H newc" option. Regards, Peter.

3 2

Rules compatibility between Novell OES1 and SLES 9 x64
by Dwayne McGarty 28 Oct '05

28 Oct '05

Greetings, I presently have an autoyast set up to deliver Novell OES1 (SLES9 i386 based). I wish to build some servers with just the SLES9 x64 distribution and was hoping to use the same rules.xml file to kick things off. Here is the rules.xml that is presently working for OES1: <?xml version="1.0"?> <!DOCTYPE autoinstall SYSTEM "/usr/share/autoinstall/dtd/rules.dtd"> <autoinstall xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <rules config:type="list"> <rule> <product> <match>*</match> <match_type>exact</match_type> </product> <result> <profile>profiles/templates/base.xml</profile> <continue config:type="boolean">true</continue> </result> </rule> <rule> <mac> <match>*</match> <match_type>exact</match_type> </mac> <result> <profile>profiles/mac/@mac@/eth0.xml</profile> <continue config:type="boolean">true</continue> </result> </rule> <rule> <custom1> <script> <![CDATA[ #!/bin/sh PATH=/bin:/sbin:/usr/bin:/usr/sbin if [ -n "`grep build= /proc/cmdline`" ] then echo -n `cat /proc/cmdline | sed -e 's/.*build=\(.*\)/\1/' -e 's/^\(.*\) BOOT.*/\1/'` else echo -n "hse9-32" fi ]]> </script> <match>*</match> <match_type>exact</match_type> </custom1> <result> <profile>profiles/software/@custom1@.xml</profile> <continue config:type="boolean">false</continue> </result> </rule> </rules> </autoinstall> The SLES9 x64 autoyast attempts using the same rules.xml file but seems to not match any of the rules and prompts for the location of a proper rules file. On inspecting the /var/log/YaST2/y2log file, it appears that the bit of shell scripting being kicked off to compare the product/mac strings to the * character are failing and returning 1 instead of 0 as they do with the OES1 installation. ie the scripts are treating the wildcard (*) character literally. Does the SLES9 x64 autoyast support the use of wildcards in the match? If not, what can I use instead Thanks for any help...

2 1

adding new istall source in yast2
by Edward Dunagin 26 Oct '05

26 Oct '05

when i get the menu, there is a spot for the server name, which i put in as: download.opensuse.org/ choosing http and : disribution/-OSS-stable/inst-source-java/ as the directory on server, then i get an error, (which by the way, is unintelligble(?) : InstSrc:E_no_instsrc_on_media anyone know what i'm doing wrong and interpet the error message? thenks ...............ed Edward M Dunagin 4646 Glenwood Drive Bozeman, MT 59718 Mobile 406.570-0992 Skype-phone +1 406 322 2566 Digital 406.556.7282 __________________________________ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com

1 0