March 2005 - openSUSE Autoinstall - openSUSE Mailing Lists

Interactive option checked BEFORE scripts?
by Jesse Keating 25 May '05

25 May '05

I'm using the modified.xml method of dynamic autoinstall control files. One of the things I wanted dynamic was the interactive or not choice, controlled by: <mode> <confirm config:type="boolean">false</confirm> If this was set to true, it should be interactive. I have this being set in modified.xml, however it does not take effect. Is this option checked BEFORE the pre-scripts run? -- Jesse Keating RHCE Pogo Linux -- Linux Systems Engineer tel: (888) 828-7646 ex: 436

3 2

SLES9 Installation Tree
by Radzai, Bridgette A. 01 Apr '05

01 Apr '05

I have integrated SP1 into my current sles9 MS directory structure as outlined in Anas' 2/05/05 posting to Egan. I have updated my boot cd with the "linux" and "initrd" from the sp1 CD1. Modified the linuxrc.config. I believe something is incorrect with my directory structure, the installation server is found, loads the SUSE SLES CD1 successfully, but when it tries to find SUSE CORE CD1 I get: Insert 'SUSE LINUX Enterprise Server 9 CD2' URL http://...../sles9_x86/SUSE-SLES-Version-9/CD1 SuSE Linux = SuSE Linux AG 2000040702202411 ! = 20040702201519 Did my media.1 folders not get copied correctly? Thanks in advance for the assistance! Bridgette

2 1

Yast, autoyast, LDAP and home/small company networking
by Birger Kollstrand 28 Mar '05

28 Mar '05

Hi, I have looked around on the SuSE web nad searched the lists to find information on Yast and home/small company network setup. I have com up short on a couple of areas and would very much appreciate som help and guidance. Please redirect me to other mailing lists if this is not the right place. Here is what I want to accomplish on my 8 machine home network first. 1. Authenticate users towards OpenLDAP (or eDirectory) 2. Automount the home directories 3. Add roming possibility so the users can log on while not beeing able to contact the LDAP server. For this I have been thinking of using the http://www.padl.com/OSS/nss_updatedb.html . 4. I want to do this to new machines via autoyast. All machines are different so generating an immage is not good. 5. I want to be able to add necesary SW/Config already configured machines automagically. Now I have accomplished to set up the OpenLDAP server ( although there was no YAST module for that) and I have via YAST set up a client to successfully authenticate towards the OpenLDAP server. In the YAST module I have ticked of the "Start Automounter", but the home directory is not mounted upon login. I can mount the home directory manually without any problems. So the questions are : 1. What does the "Start Automounter" setting actually mean? 2. Is the nss_updatedb the right way to go to achieve the possibility for local login? 3. Can autoyast be used to achieve point 4 and 5 above? (What is the best documentation for autoyast? http://www.novell.com/documentation/nld/index.html?page=/documentation/nld/… ?) 4. There is no mailinglist for Yast. Is it possible to get in contact with the maintainer to discuss enhancements? I'm willing to test and (with my limited c++/qt skills) develop aditions in this area. regards Birger Kollstrand

1 0

Adding patches to Online Update Server
by suse_list 26 Mar '05

26 Mar '05

Hi, We have setup a local update server and are trying to figure out how to add our own patches to the patch server. I was looking through the autoinstall docs and can´t find anything to do with the Online Updates. I can find in the Updates that there are some of the <package_name>.info file and a patch file, but nothing specific as per explanation or quick way for us to add packages/patches to the server. Also we are still trying to configure the server so that it rsync´s with one of the other official online update servers out there like the cs.utah one, but it seems that none of them have the capability to talk to rsync (aka are not running a rsync server deamon). Anyone out there know one that works against a online update server supporting the SuSE 9.2 Professional build. Also what commands are you using to rsync with it. We would like to set it up as a cron job to check daily. If anyone has any info, it would be greatly appreciated Sascha

1 0

Rules.XML and nested rules
by suse_list 26 Mar '05

26 Mar '05

Hi, We currently have a PXE based build environment setup here with SuSE and autoyast for our 32bit workstations and it works great. Though now we are also adding 64bit workstations and need to fix the rules.xml file to support this. This is where our dilemma comes in. We basically would like to be able to setup the rules file with nested rules if that is possible so that we could basically have the following effect: if (workstation = 64bit) do if (hd size = a) profile = 64bit_a if (hd size = b) profile = 64bit_b .... etc ... else (workstation = 32bit) do if (hd size = a) profile = 32bit_a if (hd size = b) profile = 32bit_b ... etc ... Thus was messing around with the rules file and disovered this seems to be having issues. Here is the basic file: <?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> <arch> <match>x86_64</match> <match_type>exact</match_type> <rule> <disksize> <match>/dev/sda 100000</match> <match_type>lower</match_type> </disksize> <result> <profile>software_64bit_80GB_sda.xml</profile> <continue config:type="boolean">false</continue> </result> </rule> <rule> <disksize> <match>/dev/sda 200000</match> <match_type>lower</match_type> </disksize> <result> <profile>software_64bit_200GB_sda.xml</profile> <continue config:type="boolean">false</continue> </result> </rule> </arch> </rule> <rule> <arch> <match>i686</match> <match_type>exact</match_type> <rule> <disksize> <match>/dev/sda 100000</match> <match_type>lower</match_type> </disksize> <result> <profile>software_32bit_80GB_sda.xml</profile> <continue config:type="boolean">false</continue> </result> </rule> <rule> <disksize> <match>/dev/sda 200000</match> <match_type>lower</match_type> </disksize> <result> <profile>software_32bit_200GB_sda.xml</profile> <continue config:type="boolean">false</continue> </result> </rule> </arch> </rule> </rules> </autoinstall> If anyone has any idea, or even a better way for loading profiles, please let me know. Thanks Sascha

1 0

autoyast missing packages when creating iso
by Martyn Iles 25 Mar '05

25 Mar '05

I'm having a problem when trying to create an automatic install of SuSE to put on CDROM. This is SuSE 9.0, if that makes any difference. I go through AutoYaST, tell it to clone my config and then select the Create ISO option, but then I get: Missing Packages ./suse/i586/3ddiag-0.703-172.i586.rpm ./suse/i586/BASS-20030801-55.i586.rpm Plus loads of others Now, I've got the entire SuSE 9.0 (all 7Gb) on an FTP server of mine and if I go into YaST and install extra packages, they install fine. Note that this was NOT where I installed from - I used a remote ftp mirror for the install as my local copy hadn't finished downloading so I've been into Yast and changed the installation source (could autoyast be picking up the path to the original RPMS from somewhere?). If I ftp to the machine and cd to the directories listed above its fine: ftp> cd ./suse 250 CWD command successful. ftp> ls 200 PORT command successful. 150 Opening ASCII mode data connection for file list. i586 i686 noarch nosrc setup src 226 Transfer complete. ftp: 39 bytes received in 0.00Seconds 39000.00Kbytes/sec. ftp> cd i586 250 CWD command successful. ftp> ls 3dd* 200 PORT command successful. 150 Opening ASCII mode data connection for file list. 3ddiag-0.703-172.i586.rpm 226 Transfer complete. ftp: 27 bytes received in 2.12Seconds 0.01Kbytes/sec. ftp> So, any suggestions for what I've done wrong? I've spent over a day on this, had the SuSE available on multiptle FTP/HTTP sites and I just cannot get it to work! Does AutoYaST actually work (I've tried this on two different SuSE 9.0 machines)? If not, how else can I clone a SuSE 9.0 install so that it can be installed (without much user intervention) on multiple machines from a CDROM?

1 0

How do you define "Final Scripts"
by Wayne Gilmore 24 Mar '05

24 Mar '05

I was wondering where you would define the "Final Scripts" in the Autoyast control file? I see tags for pre-scripts, post-scripts, and chroot-scripts but no examples for "final scripts" It says it's new in SLES9. Thanks. Wayne

1 0

RE: [suse-autoinstall] Network Ports and /etc/sysconfig/network
by Suffin, Charles 23 Mar '05

23 Mar '05

Anas, Looks good now!!! You've really helped me out. The latest batch of RPMs create the files in /etc/sysconfig/network and they contain all the correct information, including the "UNIQUE=" data. Thank you so much for your assistance in getting this resolved. -- Charlie -----Original Message----- From: Anas Nashif [mailto:nashif@suse.de] Sent: Friday, March 18, 2005 12:28 PM To: Suffin, Charles Cc: suse-autoinstall(a)suse.com Subject: Re: [suse-autoinstall] Network Ports and /etc/sysconfig/network Hi, There is an update pending you might want to try which fixes some issues with network and autoyast. See http://www.suse.de/~nashif/autoyast2/rpms/sles9/sles9-i386/ You will need all rpms. Create a new source with those updates using the script: http://www.suse.de/~nashif/autoyast2/scripts/create_update_source.sh and put all the above rpms in there. Dont forget to run create_package_descr after you have copied the rpms. then, you will need something like that: <interfaces config:type="list"> <interface> <bootproto>dhcp</bootproto> <device>eth0</device> <startmode>onboot</startmode> </interface> <interface> <bootproto>dhcp</bootproto> <device>eth1</device> <startmode>onboot</startmode> </interface> </interfaces> <modules config:type="list"> <module_entry> <device>eth0</device> <module>e1000</module> </module_entry> <module_entry> <device>eth1</device> <module>e100</module> </module_entry> </modules> Please report if that works for you. Anas Suffin, Charles wrote: > Hi folks, > > It seems that the auto-installation of network ports (which are described in > the XML control file) doesn't create files in /etc/sysconfig/network. > However, if you run YaST2 Network Devices (left) Network Card (right) and > add a network port, a file in /etc/sysconfig/network like > ifcfg-eth-id-AA:BB:CC:DD:EE:FF is created -- the name corresponds to the MAC > address of the card. > > Here's a snippet from my XML. Anyone know why auto-install isn't creating > the file(s) in /etc/sysconfig/network? Or, do you know what source code I > should look at to figure this out? : > > <interfaces config:type="list"> > <interface> > <bootproto>dhcp</bootproto> > <device>eth0</device> > <startmode>onboot</startmode> > </interface> > <interface> > <bootproto>dhcp</bootproto> > <device>eth1</device> > <startmode>onboot</startmode> > </interface> > </interfaces> > <modules config:type="list"> > <module_entry> > <device>bus-pci-0000:01:03.0</device> > <module>e1000</module> > </module_entry> > <module_entry> > <device>bus-pci-0000:01:06.0</device> > <module>e100</module> > </module_entry> > </modules> > > -- Charlie > > p.s./ I'm talking about auto-installation of SLES9 and SLES9-SP1. > > ----- > A. Charles Suffin > Senior Software Engineer > Stratus Technologies, Inc. (http://www.stratus.com) > 111 Powdermill Road > Maynard, MA 01754-3409 > US (978)461-7590 > > > -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

Adding SLES9 SDK to Yast-installsource for autoyast
by suselist＠nlsn.nu 23 Mar '05

23 Mar '05

Hi, Is it possible to add the SLES9 SDK CDs to the install repository to make it possible to select the package-sections in the xml-file? (Both source/binary and eclipse CDs). Regards Daniel

1 0

Configuring sudo
by Mitko Haralanov 22 Mar '05

22 Mar '05

Is there a way to configure the sudoer file (in the style of sysconfig) or do I have to do it in the post-install scripts? Thanx -- Mitko Haralanov mitko(a)pathscale.com http://www.pathscale.com ========================================== Build a system that even a fool can use and only a fool will want to use it.

1 0