March 2004 - openSUSE Autoinstall - openSUSE Mailing Lists

root passwort, sound
by Dominic Lukwata 13 Apr '04

13 Apr '04

Hi all, we autoinstall Suse 9.0. It work better and better but there still some problems: 1. we have not succeeded to set a root passowrd per autoinstall. 2. The sound module makes post installation after the first log in and the Master volume ist at zero. We use the onboard sound on the motherboard ASUS P4P800 Delux Hier ist the sound section in the controll file <sound> <autoinstall config:type="boolean">true</autoinstall> <modules_conf config:type="list"> <module_conf> <alias>snd-card-0</alias> <model>82801DB-ICH4, Intel</model> <module>snd-intel8x0</module> <options> <snd_ac97_clock>0</snd_ac97_clock> <snd_enable>1</snd_enable> <snd_index>0</snd_index> </options> <unique_key>uniq.virtual</unique_key> </module_conf> </modules_conf> <volume_settings config:type="list"> <listentry> <Master config:type="integer">75</Master> </listentry> </volume_settings> </sound> Does any one has any hint how to fix these? Thanks Dominic

3 3

custom kernel
by Benjamin P Myers 31 Mar '04

31 Mar '04

Hi, I'm having a little trouble getting autoyast to install the desired kernel. I've compiled and packaged 'k_smp_vanilla' and 'k_deflt_vanilla' and would like to install them instead of the stock stuff, but it installs k_smp instead. I'm using autoyast2-2.6.41-3 on SuSE 8.1. Here's the section from my config: <software> <base>Minimal</base> <kernel>k_smp_vanilla</kernel> <packages config:type="list"> <package>compat</package> <package>apt</package> <package>cfengine</package> <package>xntp</package> </packages> </software> I'd like to avoid using a chroot script to do this, if possible. Any help would be appreciated. Regards, Ben

4 5

Disable console during installation?
by Jan-Marc Pilawa 30 Mar '04

30 Mar '04

Hello List, the graphical installation is a fine thing because my users can see what is going on and see the advertisements ;-) But how is it possible, that they can't use the open consoles? (/dev/tty2 f.e.) I don't like that they can read .Reh in /lib/YaST2 ;-) Best Regards Jan Pilawa. -- + Kontakt ----------------------------------------------------+ + Systembetreuung Rechenzentrum TU Braunschweig + + Hans-Sommer-Str. 65, D-38092 Braunschweig + + Tel: +49 531 391-5548 Mail: j.pilawa(a)tu-bs.de ______________+

2 1

Feature request list
by Frank Steiner 30 Mar '04

30 Mar '04

Hi Anas, following is a list of feature request (yes, a lot :-)) that we missed during installing a very heterogenous network of 60 hosts with SuSE 9.0. Maybe some of them can make into the next version :-) 1) One cannot specify the disk option for lilo.conf. This is very bad if you have a host with scsi and ide disks and want to boot from the scsi disk. 2) You cannot take over the paket selection that is saved from yast2 as selection file for autoyast. They are incompatible and must be edited manually. Main difference seem to be the version numbers in the file saved from yast2, while autoyast only uses the paket names without versions. Maybe one can add an option in yast2 to save paket selection for autoyast. Usually when you get a new SuSE version, you edit the paket selection on a test host with yast2, save it, and then want to insert it into your autoyast files... 3) It would be nice if you could include special kernel packages to be used outside of the general package repository, just like you could in autoyast1. That's because we often change the kernel to be used to the latest release from SuSE, but we would like to keep our install source unchanged, i.e., keep the 1:1 copy from the DVD as install source and just add a special kernel in some other directory. This was nice how it was done in autoyast1/ 4) Something like this would be nice in rules.xml: <karch> <operator>or</operator> <match>k_deflt</match> <match_type>exact</match_type> </karch> <karch> <operator>or</operator> <match>k_athlon</match> <match_type>exact</match_type> </karch> <result>...</result> for e.g. selection the same kernel package for k_deflt and k_athlon architectures. But it is not possible, because one cannot specify <karch> twice with "or". 5) Please bring back that fstab-search feature :-) It was one of the most powerful things autoyast1 could do. Now I have to create a partition profile for each host from the existing fstab (we have about 20 different partition configurations) and add all of them info the rules file. To tell autoyast "leave everything as it was if you find a fstab and just format / and /boot" was a great feature... 6) I would like to specify a rule without condition in rules.xml. Reason is to add a general profile from which all hosts start, and then add extension by testing certain conditions. But for a starting profile, no condition is needed. This would also make it easier to keep the profiles small. You could have a profile file containing all the scripts, one for all the network stuff, and then just add a few profiles in rules.xml without condititions. Sth. like - add general profile - add scripts profile - add network profile - now start to add some stuff conditionally... 7) The script feature again: It would be very nice if you could find a way to allow external scripts to be called directly from autoyast. This would help, because now you write post-install scripts, test them, edit them, then insert all the code into an xml file. Now, sth. goes wrong, you test again, and now the danger is that the script code in the xml file and the external script get inconsistent easily. Autoyast1 user to have that $I- Variable, pointing to the install source, so we just had created a SCRIPTS subdirectory unter the suse dir from the install source, and called all the scripts from there. Would it be difficult to add such a reference variable/tag in autoyast2, too? So that you can do anything on the install source, like call the scripts? 8) When using several profiles in rules.xml, it would be nice if you could specify in every profile (or with every tag) what should be merged and what should be overwritten. Sometimes you might want to redefine the whole <network> section, sometimes you might only want to add a second interface. So, e.g. sth. like <networking> <redefine> <dns> ... </dns> </redefine> <add> <interfaces config:type="list"> <interface> .. </interface> </interfaces> </add> </networking> should overwrite *all* dns specications used before, but *add* the interface specifications to all the interface stuff defined before. This would be very powerful, but I guess it would be hard to implement... 9) An easy way to add general includes would be nice. The entity include mechanism does not work in rules.xml. As we have to specify about 40 partition rules (depending on the IP and the type), we would like to use a separate file for this and include it to keep rules.xml small. 10) It would be nice if the value matched in a <match> tag in rules.xml could be referenced in the result section. Then one could e.g. match the IP in the match tag and use "profile-$ip.xml" as result. So with one rule you could add a special profile for each host by just adding a file "profile-xxx.xxx.xx.xxx.xml" in the profile subdir. 11) A match variable for hostname would be nice. It is available from dhcp, so it would be nice if you could match it. Yes, I know, a long list :-)) However, it is not that we don't like AY2 here at all ;-) It resolved many of the problems that we had with AY1 and we really like the new features. However, some of features above would greatly enhance it :-) cu, Frank -- Dipl.-Inform. Frank Steiner Web: http://www.bio.ifi.lmu.de/~steiner/ Lehrstuhl f. Bioinformatik Mail: http://www.bio.ifi.lmu.de/~steiner/m/ LMU, Amalienstr 17 Phone: +49 89 2180-4049 80333 Muenchen, Germany Fax: -4054 * Rekursion kann man erst verstehen, wenn man Rekursion verstanden hat. *

3 6

grub menu.lst without entry for floppy
by Jan-Marc Pilawa 30 Mar '04

30 Mar '04

Hello List, as I understood autoinstall: it tries to find all "valid" bootable devices and adds them to grubs menu. My question: Is it possible to disable the apperance of the "Floppy chainloader" without explicit partitioning and configuration of the bootloder? I have several Machines with a dual-boot configuration and I won't loose the flexibility of "auto-everything ;-)" in autoinstall. Best Regards Jan Pilawa. -- + Kontakt ----------------------------------------------------+ + Systembetreuung Rechenzentrum TU Braunschweig + + Hans-Sommer-Str. 65, D-38092 Braunschweig + + Tel: +49 531 391-5548 Mail: j.pilawa(a)tu-bs.de ______________+

1 0

Re: [suse-autoinstall] Static IP problem
by Jeff Crow 29 Mar '04

29 Mar '04

Leen, Thanks for the help. That did the trick! Jeff >>> Leendert Meyer <leen.meyer(a)home.nl> 3/25/2004 5:55:38 PM >>> On Thursday 25 March 2004 21:39, Jeff Crow wrote: > First a bit of background information. I am auto-installing SuSE Linux > (multiple versions, SLES 8, 9.0, etc.) vi HTTP. During the autoinstall > process I am using DHCP, ie when the machine first boots up it gets > assigned an address. However, during install I assign the machine a > static ip address, which is set up in the configuration file. > > Now the problem. After the sucessful completion of installation when I > log into the machine, the network interface is not configured with the > static IP address, but with a dynamic one. That's the IP# the install process gets. It is a dynamic IP#. > I can see this through ifconfig. If I reboot the machine, then the > static IP address gets bound to the NIC and everything is fine. Yes. Interface goes down, pc reboots, interface requests IP#... > I do have the 'Reboot after Installation' set to true ( <reboot > config:type="boolean">true</reboot> ). I do not think that's neccessary. Run a script at a convenient point that does a ifdown/ifup sequence: ifdown interface eth0 ifup interface eth0 Hmmm... now I think of it... as the system boots up /for the first time/, it goes through all the init-scripts, right? If so, perhaps a simple "ifdown interface eth0" before initial booting would be sufficient. Cheers, Leen -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

autoinst
by Manuel.Laesser＠telekurs.com 29 Mar '04

29 Mar '04

Hello today I tried to create my first CD using autoyasts option "Create ISO Image" in Media Management Section. After selecting the desired xml-file it gathers all rpms....so far so good. After this the iso image will be created. After 99% the status bar doesn't move anymore and I have to click on cancel (...hmmm....), but the iso image will be created and I can mount it with "-o loop....". I copy the mounted iso image to a directory, add some directories where my scripts and additional software resides and also delete some files I don't want to have on the CD (autorun.sh, COPYRIGHT, COPYING.tex....) I then create a new iso image with sles8:/usr/local/SuSE/current # mkisofs -V SU -J -R -o /home/tklsa/suse_TK_260304.iso -b boot/loader/isolinux.bin -no-emul-boo -boot-load-size 4 /home/tklsa/suse_260304ul-boo -boot-load-size 4 /home/tklsa/suse_260304 My new iso image with will be created. If I insert it into the server and boot the system I've got the following error message: ISOLINUX 1.62 0x3db44759 isolinux: Image checksum error, sorry Boot failed: press a key to retry... I didn't try to burn the iso image created by autoyast to a CD and boot the system with it. I don't know if the CD doesn't boot anymore because I added/deleted files from the original iso image and created a new one. Does anyone have some experiences with the same process? I'm using SLES8 and autoyast2-2.6.44-7 Thank you very much for your help. Mit freundlichen Grüssen, Manuel Laesser ----------------------------------------------------------- Telekurs Services Hardturmstrasse 201, 8005 Zürich Phone : +41 1 279 44 24 Fax : +41 1 279 34 44 mailto : manuel.laesser(a)telekurs.com -----------------------------------------------------------

1 1

[suse-autoinstall] inability to update
by Alexander A Klimenko 26 Mar '04

26 Mar '04

Every time I try to connect to various centers to update I get the following error message: Patch: xf86tools-44811 I am connected to the Internet via a Motorola CyberSurfr Wav cable modem through noos.fr. My browser works fine and I have no problem with mail. If anyone can help me here, I'd be much obliged. Alexander A Klimenko --

1 0

[suse-autoinstall] inability to update
by Alexander A Klimenko 26 Mar '04

26 Mar '04

1 0

Static IP problem
by Jeff Crow 26 Mar '04

26 Mar '04

First a bit of background information. I am auto-installing SuSE Linux (multiple versions, SLES 8, 9.0, etc.) vi HTTP. During the autoinstall process I am using DHCP, ie when the machine first boots up it gets assigned an address. However, during install I assign the machine a static ip address, which is set up in the configuration file. Now the problem. After the sucessful completion of installation when I log into the machine, the network interface is not configured with the static IP address, but with a dynamic one. I can see this through ifconfig. If I reboot the machine, then the static IP address gets bound to the NIC and everything is fine. I do have the 'Reboot after Installation' set to true ( <reboot config:type="boolean">true</reboot> ). Does anyone have an idea why this is happening and what I can do to resolve this so that the machine has the correct static IP address after installation? Thank you very much, Jeff Crow

2 1