October 2004 - openSUSE Autoinstall - openSUSE Mailing Lists

Alice with SuSE Linux 9.0
by Maverick-IT 24 Oct '04

24 Oct '04

Hello everybody, as I'm working in a big company, that also has a section for informatics it is my task to test and analyze the possibilities to install a Linux system with SuSE Linux 9.0 and ALICE. This is also my project for my exams, which I will do in the next months. So, this is very important to me. I really hope, that you can help me. My period for accomplishing this project begins on Wednesday, 3rd of November and I have to finish it on Friday, 3rd of December. I have informed myself a little bit about ALICE yet. I also have set up a work environment at home, so that I can test the system earlier. The documentation I found was from http://www.suse.de/~fabian/alice/. The problem I have lies with the fact, that this documentation was written by testing an earlier version of "alice.rpm" and SuSE Linux I think. For example on page 19 of this documentation there is the following command: "cp -r /usr/ lib/alice/samples alice".But in my rpm version of SuSE Linux 9.0 there is no folder called "Samples". I also can't do the next steps in this documentation. My questions are: "Is it possible to autoinstall a SuSE Linux 9.0 system only with ALICE?" "And if it is possible, does anybody have a documentation for this?" It would be very nice, if somebody could help me very fast, because my exams are dependent on this project. Yours, Marek Troschinski

2 1

autoinstall error logfiles?
by Chris Carpinello 21 Oct '04

21 Oct '04

Several sections of my autoinst.xml are being ignored (specifically, runlevels, users and groups). There's nothing in /var/log/YaST2 that indicates an error parsing autoinst.xml. The profile validates with and without DTD validation in YaST2. So, I'm wondering... Is there a logfile that contains error/parsing/execution messages related to an autoinstall profile? If there is, adding a top level section to http://www.suse.de/~nashif/autoinstall/9.1/html/index.html with this information would be welcome. - Chris

1 0

escaping characters in encrypted passwords necessary?
by Chris Carpinello 21 Oct '04

21 Oct '04

When specifying encrypted passwords in the <user_password> field, are there any regexp/shell characters that need to be escaped such as ".", "$" or the like? - Chris

1 0

YaST hanging from Firebird 1.5.1 RPM
by McKenna, Simon (RGH) 21 Oct '04

21 Oct '04

Hi, There seems to be a small issue with the install of Firebird 1.5.1 RPM using YaST. I have not seen this problem with any other RPM's installed via YaST. I tried posting to the Firebird support group first but got no response. >From a clean SuSE 9.1 Pro distribution (latest updates), if I install the FirebirdSS-1.5.1.4481-0.i686.rpm using YaST, right at the end of the install YaST appears to hang, and the only fix I've found is to kill the y2base process. Note that the Firebird install is successful, I can see the fbguard and fbserver processes, and can connect to the example db, and everything comes up fine after a restart, it's just YaST can't close itself after the install. Is anyone able to confirm/deny this problem? RPM is here: http://tinyurl.com/4sp9g (I tried both NPTL and non-NPTL) Also, I'm shifting my development environment from Windows to Linux, and am still very much feeling my way around, so can anyone please tell me if I should be using the NPTL version of Firebird with the SuSE 9.1 Pro distribution? (I found documentation stating SuSE 9 Enterprise uses NPTL, but not for 9.1 Pro) Thanks for any help. peace - si sshnug.com

1 0

SLES8/UL SP3 autoinstall CD create issue
by Jun Wang 20 Oct '04

20 Oct '04

Hi, I wanna create a customize SLES8/UL SP3 CD which include autoinst.xml and info file and could used for CD instmode automatic install. The problem i met was the size of SP3 CD is too large to fit in ISO9660 CD. Could any one told me the proper steps to create such CD? the steps I used as bellow: 1 loop mount the SP3 iso # mount -o loop SLES8-SP3.iso /media/cdrom 2 copy the content to a directory # mkdir -p /datashare/SLES8/UL/SP3 # cd /media/cdrom; cp -a . /datashare/SLES8/UL/SP3 when i run this command, the output give following error: cp: will not create hard link'/datashare/SLES8/UL/SP3/./i386/update/SuSE-SLES/8/patches'to directory'/datashare/SLES8/UL/SP3/./i386/update/UnitedLinux/1.0/patches' cp: will not create hard link'/datashare/SLES8/UL/SP3/./i386/update/SuSE-SLES/8/rpm'to directory'/datashare/SLES8/UL/SP3/./i386/update/UnitedLinux/1.0/rpm' cp: will not create hard link'/datashare/SLES8/UL/SP3/./i386/update/SuSE-SLES/8/scripts'to directory'/datashare/SLES8/UL/SP3/./i386/update/UnitedLinux/1.0/scripts' cp: will not create hard link'/datashare/SLES8/UL/SP3/./linux/suse/i386-sles8/install'to directory'/datashare/SLES8/UL/SP3/./linux/suse/i386-ul1/install' cp: will not create hard link'/datashare/SLES8/UL/SP3/./linux/suse/i386-sles8/y2update'to directory'/datashare/SLES8/UL/SP3/./linux/suse/i386-ul1/y2update' cp: will not create hard link'/datashare/SLES8/UL/SP3/./linux/suse/i386-sles8'to directory'/datashare/SLES8/UL/SP3/./linux/UnitedLinux/i386-sles8' cp: will not create hard link'/datashare/SLES8/UL/SP3/./linux/suse/i386-ul1'to directory'/datashare/SLES8/UL/SP3/./linux/UnitedLinux/i386-ul1' cp: will not create hard link'/datashare/SLES8/UL/SP3/./i386/update/SuSE-SLES/8/rpm/setup/descr' to directory'/datashare/SLES8/UL/SP3/./UnitedLinux/setup/descr' Best Regards, Wang Jun

2 1

rules and classes
by Kai Moeller 20 Oct '04

20 Oct '04

Hi there, i know, there are enough topics with the same question... I've see the answer of Anas, he said that the documentation is updatet, but i didn't find any new information about rules and classes. in my repository folder I created the folders rules/, /classes in the rules directory i put my rules.xml, that w0rks pretty good! I also put some class files in my classes folder (with subdir) and it works fine, too. But is it possible to merge some different configuration sections (which are saved in different files) like software.xml base.xml network.xml so that i could define a rule (check about the mac adress) or more rules to merge these 3 parts of control file to a new (master) controlfile? when i define a two rules like this: <rule> <disksize> <match>/dev/hda 1</match> <match_type>greater</match_type> </disksize> <result> <profile>base</profile> <continue config:type="boolean">true</continue> </result> </rule> <rule> <mac> <match>000475fcedbf</match> <match_type>exact</match_type> </mac> <result> <profile>base.xml</profile> <continue config:type="boolean">false</continue> </result> </rule> i want to merge the base.xml and network.xml (in my base.xml are no definitions about the network options) I tried these kind of config, it works, but without my network settings. So the autoinstall process didn't merge these files I know, that kind of solutions isn't the right way, but i didnt know better, please help me :o) Finally i want to create some rules (and/or) classes to have only 1 base controlfile and some network config templates with different settings for each machine. Thx best regards Kai Möller

1 0

[suse-autoinstall] Can anyone post some examples using rules and classes with custom attributes
by Anthony Staples 19 Oct '04

19 Oct '04

Hello, According to the autoinstall/autoyast doc (Chapter 6), there is a way in which to combine rules and classes to dynamically generate the control file. The doc is vague on exactly how to do this... Would someone be kind enough to post some examples of this, if you are doing it. Also, how do you combine the rules file and with shell scripts to use the available custom1-5 attributes? Thanks!!! Tony Staples astaples(a)humana.com The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.

3 2

Even More Customizing of SLES9 Autoinstall
by J.L.Francois 18 Oct '04

18 Oct '04

I have been moving my SLES8 autoinstallation info and control files to SLES9 and attempting to make sure I don't miss anything. I have: 1. Read docs at http://www.suse.de/~nashif/autoinstall/9.1/html/ 2. Updated my info files and made the change to "netsetup" The one thing I am sure I am missing is a way to ask for a "temporary" root password for initial login. What we want to do in SLES9, which we had customized for us in SLES8, is ask the installer for a temporary root password upfront at the same time we collect data in netsetup. I'd really like to know if a method exists where *any* information can be collected and used to modify a configuration file with a postinstall script by reading data written to install.inf during the execution of my own custom pre-install scripts. What we have already done is create a post-install script that automatically expires the root password ( passwd -e ) so we don't have to have installations with default root passwords that are known and documented laying around the enterprise. Any hints, tips, suggestions would be welcome. -- Jean L. Francois - Enterprise OS (LINUX) Load Development and Integration Engineering Group - Linux Counter Registered User #8863 1994-12-13 06:39:24

2 1

Automated Configuration of System Backup
by tobias.mucke＠de.man-mn.com 18 Oct '04

18 Oct '04

Hi everybody, if I understand the AutoYaST concept of SuSE right, each YaST2 module should work together with a XML file containing its configuration. What about the module "System Backup". May I configure that using AutoYaST? Mit freundlichen Grüßen Tobias Mucke -------------------------------------------------------------------------------------------------- MAN Nutzfahrzeuge AG Informationssysteme Organisation (I) Dachauer Straße 667 D-80995 München Tel.: +49 (0) 89 1580 5269 Mail-Adresse: Tobias_Mucke(a)mn.man.de Internet-Adresse: http://www.man-trucks.com -------------------------------------------------------------------------------------------------- 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.

1 0

Antwort: [suse-autoinstall] additional package requires/forcing installorder [FinanzIT: Viruscheck]
by Hartmut.Dunker＠finanzit.com 18 Oct '04

18 Oct '04

Hi Chris, we've also included thirdparty and own packages to our autoinstall. To force the required dependencies we add in the packages file under suse/setup/descr in the "+Req: -Req:" section the dependencies manually. That works fine for us. Cheers Hartmut Chris Carpinello <ccarpinello@lanc An: suse-autoinstall(a)suse.com ope.com> Kopie: Thema: [suse-autoinstall] additional package requires/forcing install order 15.10.2004 22:49 [FinanzIT: Viruscheck] 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 -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0