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

Re: [suse-autoinstall] Newbie help wanted for installing java on suse 9
by Andy W. Barclay 25 Mar '04

25 Mar '04

Hi Frederic, This is the wrong forum for this question, but I'm sure I saw an answer to your question on the linuxquestions.org website. http://www.linuxquestions.org/questions/showthread.php?s=&threadid=161929&h… Frederic Durodie wrote: > Hi, > > I'm a bit new to linux and to SuSE (home user) and I try to install > java by > executing the file 'j2re-1_4_2_04-linux-i586.bin' which I downloaded from > www.java.com. I have now a directory /usr/local/java/j2re1.4.2_04. How > do I > get from there to java working under Konqueror ? Also in the end I > want to > run LimeWire. > > Thanks up front for all help, > Kind regards, > Frederic >

1 0

Newbie help wanted for installing java on suse 9
by Frederic Durodie 25 Mar '04

25 Mar '04

Hi, I'm a bit new to linux and to SuSE (home user) and I try to install java by executing the file 'j2re-1_4_2_04-linux-i586.bin' which I downloaded from www.java.com. I have now a directory /usr/local/java/j2re1.4.2_04. How do I get from there to java working under Konqueror ? Also in the end I want to run LimeWire. Thanks up front for all help, Kind regards, Frederic

1 0

/boot & ext3, grub, swap
by Manuel.Laesser＠telekurs.com 25 Mar '04

25 Mar '04

Hello I've got three questions 1. If I create a own filesystem for /boot It's always ext2 even if got ext3 specified in the autoinst.xml Workaround: Use tune2fs -j .... after Installation (post script) 2. Even I've got a autoinst.xml from Karl-Walter Grabbe which should install grub instead of lilo, I still have lilo installed after the unattendand installation. Below an extract of the bootloader section from Karl-Walter <bootloader> <loader_type>grub</loader_type> <specific> <activate config:type="boolean">true</activate> <grub_conf> <addr>0x8000</addr> <device>(null)</device> <discswitch config:type="boolean">true</discswitch> <menu>/boot/grub/menu.lst</menu> <s2prefix>--stage2=/boot/grub/stage2</s2prefix> <stage1>/boot/grub/stage1</stage1> <stage2>/boot/grub/stage2</stage2> </grub_conf> <repl_mbr config:type="boolean">false</repl_mbr> </specific> </bootloader> Some people told me to use a post script again to remove lilo and install and configure grub. But when I do this by hand I'll receive the following error messages: ************************** grub> root (hd0,0) Error 21: Selected disk does not exist grub> install --stage2=/boot/grub/stage2 /grub/stage1 d (hd0) /grub/stage2 0xgrub> install --stage2=/boot/grub/stage2 / grub/stage1 d (hd0) /grub/stage2 0x8grub> install --stage2=/boot/grub/stage2 /grub/stage1 d (hd0) /grub/stage2 0x8grub> .... Error 12: Invalid device requested grub> quit ************************** 3. If I use LVM in my xml file the swap partition will be created but I don't have any entry in /etc/fstab. Therefore a swap partition will never be activated. After I put the statement in /etc/fstab, made a mkswap /dev/systemvg/swap and swapon -a the swap partition is available. Unfortunately only for a short period of time because after about 10 minutes I receive a Filename Type Size Used Priority /dev/hda5 (deleted) partition 248968 2044 42 if I execute swapon -s. What does this "deleted" mean? Has this got a bad impact on my installation? 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 -----------------------------------------------------------

2 1

SLES9beta1 suspended-data signature
by Dustin Kirkland 24 Mar '04

24 Mar '04

Hi- I'm porting my SuSE Autoinstallation scripts to SLES9beta1. The installation seems to work fine until the first reboot. This causes the following error: resuming from /dev/hda5 Resuming from device hda5 Kernel panic: Resume Machine: Unable to find suspended-data signature ( - misspelled? Suggestions? Dustin

2 1

Partitioning question
by Daniel Groscost 24 Mar '04

24 Mar '04

Hello, I am trying to configure autoyast2 (autoinst.xml) to automatically use the partitions that I have created (but not formatted yet) with a pre-install script. This will be used for mass staging purposes. I intend to have three primary partitions: /dev/hda is the device. /dev/hda1 will mount to /boot - approx 100MB. Needs to be formatted reiser. /dev/hda2 will mount to / - MAX SIZE (total size minus swap size). Needs to be formatted reiser. /dev/hda3 will be swap (memory*2). Format swap. I'm calculating the hard drive figures inside of the pre-install script so I just need autoyast to just accept the drive configuration the way it is, format the partitions, and go on with the install. I've read through the advanced partitioning but each time I attempt to run through an install I get a response in autoyast saying ERROR: No proposal. Is there an easier way of accomplishing this? Below is the partitioning section of my autoinst.xml: <partitioning config:type="list"> <drive> <partitions config:type="list"> <partition> <create config:type="boolean">false</create> <filesystem>reiser</filesystem> <format config:type="boolean">true</format> <mount>/boot</mount> <partition_id config:type="integer">83</partition_id> </partition> <partition> <create config:type="boolean">false</create> <filesystem>reiser</filesystem> <format config:type="boolean">true</format> <mount>/</mount> <partition_id config:type="integer">83</partition_id> </partition> <partition> <create config:type="boolean">false</create> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <mount>swap</mount> <partition_id config:type="integer">82</partition_id> </partition> </partitions> </drive> </partitioning> Any help is appreciated. Thanks, > Daniel J. Groscost MCSA Windows Server 2003 > Systems Engineer > > Datavantage Corporation a wholly-owned subsidiary of MICROS Systems, Inc. > 6573 Cochran Rd., Suite L > Cleveland, OH 44139 > Tel: (440)498/4419 x265 > Fax: (440)498/4430 > Email: dgroscost(a)datavantagecorp.com > Web: http://www.datavantagecorp.com >

1 0

Does automatic control file ffind work for NFS?
by "Müller, Folkhard" 23 Mar '04

23 Mar '04

Hi everybody, I use autoyast2-2.8.14-20 and try to install Suse 9.0 to a couple of Workstations I use the grubfloppy from Anas's Website to boot the system to be installed. This is my menus.lst for the grubfloopy ---snip title autoinstall-bootp bootp tftpserver 172.18.127.43 root (nd) kernel (nd)/opt/ignite/linux install=nfs://172.18.127.126/.home/install/suse9.0/DVD1 autoyast=nfs://172.18.127.126/var/lib/autoinstall/repository initrd (nd)/opt/ignite/initrd --snap on 172.18.127.126 the installation server ll /var/lib/autoinstall/repository drwxr-xr-x 5 root root 272 Mar 23 09:33 . drwxr-xr-x 5 root root 128 Nov 14 2005 .. -rw-r--r-- 1 root root 390 Mar 22 18:07 AC127F57 -rw-r--r-- 1 root root 390 Mar 22 17:53 AC127F8C drwxr-xr-x 4 root root 96 Mar 22 17:47 classes lrwxrwxrwx 1 root root 8 Mar 22 18:07 hatti -> AC127F57 drwxr-xr-x 2 root root 48 Sep 24 20:44 rules drwxr-xr-x 2 root root 48 Sep 24 20:44 templates AC127F57 is HEX for 172.18.127.87 which is the TCP/IP of the client booted with the grubfloppy. ->My test system boots stage2 successfull ->Loads the kernel and initrd via tftp from the tftpserver 172.18.127.43. ->starts thekernel ->starts linuxrc 1.5 ->starts yast2 for automated install mounts the installation source But yast2 does not find the controlfile for autoyast The control file is available as: see above. The system to be installed ends up in a yast2 mask where the server and mountpoint of the controllfile is displayed as told to yast2 by the autoyast= statement to the kernel. (this shows the 'control file repository' is known!) If I extend the repository path by AC127F57 and hit enter the installation rolls on as expected. This shows that NFS works for 172.18.127.126/var/lib/autoinstall/repository. It seems as if the autochoose feature of the control file fails for a reson I cannot see! The /var/log/message file on the Installation server (172.18.127.126) shows, that no trial to mount /var/lib/autoinstall/repository is done,however, /.home/install/suse9.0/DVD1 is mounted succesfully. Only after I extend the repository path by the control file's name the nfs mount is done as seen in messages on the installation server. Does anybody can help ? -- Dipl. Phys. F.Mueller EPCOS AG Surface Acoustic Wave Components Division SAW RD EDA IS P.O. Box 80 17 09 Phone: ++49 89 636 23316 D-81617 Munich Fax: ++49 89 636 27304 Germany mailto: Folkhard.Mueller(a)epcos.com Web: http://www.epcos.com

2 2

Causing a partition to _not_ be mounted?
by Anton Altaparmakov 23 Mar '04

23 Mar '04

Hi, We are using autoyast2-2.8.14-68 (SUSE 9.0) to automatically install machines over the network. The machines have an existing NTFS partition which we do not want to touch. autoyast removes the other partitions and creates them as Linux ones. This all works fine. However, after the system is installed the NTFS partition is found in /etc/fstab like so: /dev/hda1 /windows/C ntfs ro,users,gid=users,umask=0002,nls=iso8859-1 0 0 But we don't want to have this in /etc/fstab! Is it possible to not create the fstab entry for this partition? If yes, how could this be done? If you want to see our autoinst.xml, I have made it available here: http://www-uxsup.csx.cam.ac.uk/~aia21/linux/autoinst.xml Thanks a lot in advance! Best regards, Anton -- Anton Altaparmakov <aia21 at cam.ac.uk> (replace at with @) Unix Support, Computing Service, University of Cambridge, CB2 3QH, UK Linux NTFS maintainer / IRC: #ntfs on irc.freenode.net WWW: http://linux-ntfs.sf.net/ & http://www-stu.christs.cam.ac.uk/~aia21/

1 0

Error saving bootloader configuration
by Kfir Lavi 23 Mar '04

23 Mar '04

Hi all, I'm trying to install SLES 8.0 for AMD64. Before the end of the installation i get this error: "An error occurred during saving bootloader configuration". In the end of the email i have included the bootloader section from linuxrc file. Important: I'm using pxe install. It works perfect with SUSE 9.0 AMD64 installation on the same computer, but with SLES 8.0 the installation didn't got DHCP after the kernel finished loading, and no manual config helped (module for nic installed good). I have seen that SUSE 9.0 have installer ver 1.5 and SLES 8.0 have ver 1.4, so i used the linux and initrd files from the SUSE 9.0 dvd. Now the installation works good, part of this boot loader issue. <snip>linuxrc<snip> <bootloader> <loader_device>/dev/hda</loader_device> <loader_type>grub</loader_type> <location>mbr</location> <specific> <activate config:type="boolean">false</activate> <device_map config:type="list"> <device_map_entry config:type="list"> <device>(hd0)</device> <device>/dev/hda</device> </device_map_entry> </device_map> <global config:type="list"> <listentry> <changed config:type="boolean">true</changed> <key>__intern__</key> <value> <changed_opts config:type="list"> <listentry>__location</listentry> </changed_opts> </value> </listentry> </global> <grub_conf> <addr>0x8000</addr> <device>(null)</device> <discswitch config:type="boolean">true</discswitch> <menu>/boot/grub/menu.lst</menu> <prefix>--stage2=/boot/grub/stage2</prefix> <stage1>/boot/grub/stage1</stage1> <stage2>/boot/grub/stage2</stage2> </grub_conf> <repl_mbr config:type="boolean">false</repl_mbr> <sections config:type="list"/> </specific> <write_settings/> </bootloader>

1 0

Creating ISO-Images from multiple sources
by Otto Bommer 22 Mar '04

22 Mar '04

Hi, I am using AutoYast from SuSE Professional 9.0 to install PC's with some standard configuration (Minimal+X11) plus additional specific .rpm's and configuration files. This works pretty well when I do the installation over the net: My current procedure: - Installation of SuSE9.0 over the net with bootp, tftp, PXELINUX with an AutoYast-Configuration - The AutoYast-Packet-Selection is based on 2 Installation-Sources 1. SuSE 9.0 dir:///store/SuSE/i386/9.0 2. nfs://InstallationServer//store/RPMS - Update of installed system with YOU 1st question/problem: When I want to create an ISO-Image based on this configuration AutoYast doesn't find the second installation source ;-( 2nd question/problem: I would like to include the updated rpm-packages from the YOU-Server into the installation procedure, so I wouldn't have to run YOU after the installation procedure. Is it possible to do this? Thanks in advance Otto Bommer

1 0

Building patch RPM updates .patch.rpm files
by IT Staff 22 Mar '04

22 Mar '04

Hello We are trying to build SuSE-compatible patch RPM updates (.patch.rpm files) in order to maintain quicker our home made RPM packages on our servers via the yast online_update utility. Is it possible to create such .patch.rpm files and what is the procedure ? Thanks in advance Kind regards

1 0

Newbies Installing 9.0
by suse＠mniceguy.privasend.com 22 Mar '04

22 Mar '04

I've got a computer store guy who's doing an upgrade on my computer. He knows practically nothing about Linux but wants to learn. I've used Mandrake 8 & RHL 9, but only know a little, graphical basic stuff. Goal is dual-boot WinXP and SUSE 9.0 Personal, which I bought at retail in a box. Is there anything we/he need to know/do other than insert the disc after he installs XP and assume/hope YAST will prompt...? Should we check compatibility, do other stuff first, panic about something else??? I *really* appreciate your help. -M!

3 2

if conditions in XML-File
by Manuel.Laesser＠telekurs.com 21 Mar '04

21 Mar '04

Hello is it possible to have "if-else conditions" statements in the autoinst.xml file. I would like to create a swap partition which is two times larger then available memory but neverlarger then 2GB. How could I solve this issue with autoyast? Does anyone has a good idea? Sorry for asking so many questions but you already helped me a lot! Thank you so much! Regards Manuel 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 0

Installing Linux
by Florian Schödel 20 Mar '04

20 Mar '04

Hi together, I want to install SuSE Linux 9.0 on my "targa visionary" notebook "xp-210". There ist just a problem: When the message "Analysiere Festplatte" ("analysing hard disks...") appears on the screen it doesn't complete the action. After 5 minutes I break up by pressing the power button because ctrl-alt-del doesn't work anymore. There is a toshiba hard drive I want to install linux on. The first partition contains w i n x p. If I select "Safe settings" from the boot screen, which appears when I start from the CD, the system will be frozen on detecting the pcmcia devices. Is this a known problem with this notebook or could I change any configuration? The hard drive was detected as a udma 5 drive by the bios. Thanks for your help Florian

1 0

Autoinstall and Network Installation prompting for CD rom
by RANGI, JAI 19 Mar '04

19 Mar '04

Hi I am trying to build Beowulf Type of cluster using Suse 9.0 64 bit processor. I installed all the softwares and have done all the configuration on one node, from there I made the exact copy of that node using autoyast tool. As we want all the nodes of the same type and all the nodes have same hardware architecture. Copy the autoinst.xml file /tftpboot/suse9.0/autoinst.xml-nodename (sd* in our case). Copy the installation DVD into /tftpboot/suse9.0 directory. Which is also NFS partition. Copy pxelinx.0 (LATEST, I know there is problem with pxelinux.0 that came with suse 9.0) in /tftpboot/suse9.0 Copy Linux and initrd from /tftpboot/suse9.0/boot/loader to /tftpboot/suse9.0/ Create default file in /tftpboot/suse9.0/pxelinux.cfg/C0A8016C (For IP 192.168.1.108 and same for other nodes) Here is what the default file (C0A8016C) looks like default Linux label Linux kernel linux append init=/linuxrc load_ramdisk=1 initrd=initrd root=/dev/ram insmod=bcm5700 netdevice=eth0 insmod=mptbase autoyast=nfs://192.168.1.1/autoinst.xml-sd6 install=nfs://192.168.1.1/ Now I boot the client machine using pxe boot and it boots, it gets the IP address reads the configuration file C0A8016C and says Missing Parameter in Config File.. Missing Parameter in config File.. and start the installation BUT this is what I get after loading modules.... ////////////////////////// Looking for Suse Linux CD.. Checking device /dev/hdc Ok, That didn't work See if we can activate another storage device Insmod mptbase Opps That didn't work, no further storage device found, giving up... Automatic Setup not possible ........///////////////// And it ask for the installation CD. Seems like the network card is not configure and it have problem with communication with NSF server, even though Network card got the fixed IP from DHCP server... Also from here If I go manually and try to load modules for network card which is bcm5700 it fails... Any idea what I might be doing wrong.... I have read so much on the mailing list archive but could not find any solution.... Thank You Jai Rangi Unix System Administrator, Computing Services, South Dakota State University Brookings SD 57006. email: jai_rangi(a)sdstate.edu Ph: 605 688 4689 Fax: 6056884605 ------------------------------------------------------- In the world with no fences, why would you need Gates ? - Linux -------------------------------------------------------

1 0

autoinstall with LVM, GRUB, SWAP
by Manuel.Laesser＠telekurs.com 19 Mar '04

19 Mar '04

Hello, I've got the following questions. 1. Is there a possibility in the autoinst.mxl to deselect lilo explicit so it won't be installed. I can't find a lilo statement in my package section but the rpm still will be installed. I got a hint from a friend. He told me that I should deselct lilo explicit in the autoinstall.xml. Is there a way to do this? Could this be a valuable way of having GRUB instead of LILO. If I understood Anas statement, then it's not possible to have GRUB if LVM is used with an autoinstall. Is there any workaround? Can I migrate from LILO to GRUB using a post installation script? 2. If you use LVM and create a logical volume for /, /home, /usr and swap the swap partition isn't activated and there is no entry in /etc/fstab but the logical volume exists. After I put the entry in /etc/fstab and made a mkswap, swapon -a the swap space was available. 10 minutes later I checkd with swapon -s or cat /proc/swaps and it was saying that the swap space was deleted??!! Did anyone receive a similar message? Thank you very much for your answer. I'm a little bit depressed, because I still have no concept how I can carry out my degree dissertation.....and time is bloody short!! :-( Regards Manuel

1 0

Desiring a bit of interation with autoyast process
by Bryan Fink 18 Mar '04

18 Mar '04

Hello. I'm working on setting up an autoyast installation system for a cluster computing environment. This seems like the perfect tool, except for one small part. When I start the autoyast install, I'd really like a small menu to ask me "Which node would you like this machine to be?" I'd like to be able to type a number (like 42), and then have the machines network set up so that it's IP is based on that number (like 10.0.0.42), and so is its hostname (like "node42"). What I've come up with is doing something like putting up a CGI script, such that I can run "linux autoyast=http://cgihost/autoyast.cgi?42", and have that CGI script send back an autoyast configuration file specifically generated for node42 (basically a dynamic equivalent of creating node1.xml through node255.xml and just passing in autoyast=node42.xml). Does anyone have a better idea? I really don't want to write a script that actually modifies ifconfig and stuff manually - that just seems to not be in the spirit of autoyast. I just haven't figured a way yet to have a pre-install script, run by autoyast, gather the data I want, and then proceed with these values (i.e. the xml file has no way to allow one part of the file to define a variable for a later part to use). Anyone know differently? Thanks, Bryan

1 0

[suse-autoinstall] Error with software base-selection.
by Kurt Östberg 18 Mar '04

18 Mar '04

Hi. Problem solved. I compered the contents of ls-lR.gz with what I actually got when I ftp'ed the whole suse9 from suse. It showed up that some files where missing, LAMP.sel,LAMP2.sel and X11.sel was some of them so that explains why it didn't work. /Kurre

1 0

Error with software base-selection.
by Kurt Östberg 18 Mar '04

18 Mar '04

Hi. I saw in the mailing-list a mail about this problem but no solution. The autoinstall stops with the message: "Error, Could not set base selection: default" Facts: Suse 9.0 ftp version A boot-cd with commandline options: autoyast=nfs://server/profiles/autoinst.xml install=nfs://server/suse9 The autoinst.xml parses into yast OK. A snort/tcpdump on the interface tells me that a lot of stuff from /suse9/suse/setup/descr/ on the server is transfered back to the client, so the nfs is working. The data that goes to the client is as far as I can see the contens of the files: selections and packages. So, why can't yast set the base selection? Any ideas out there. /Kurre

2 1

Re: [suse-autoinstall] RE: SLES 8, PXE, serial console, prompting for CD #1
by Andy W. Barclay 17 Mar '04

17 Mar '04

Hi, I've done some more research and I think I've found out whats going on. 1) The problem with the "Insert UnitedLinux Version 1.0 CD 1" only happens when I copy the SP3 CD #1 over the distribution. If I rsync only: suse linux standard server 8 CD to sles8 united linux CD #1 united linux CD #2 united linux CD #3 then all is well. (except, of course, the lilo thing). As soon as I copy over: unitedLinux-1.0-SP-3-i386-RC4-CD2.iso it starts prompting me..... I believe the problem is with the media.1/media file, because if I copy the media.1/media file from the original united linux CD #1, the thing starts working again. 2) The serial console. I've found that the order of the parameters is significant. When I specify "console=ttyS0,9800 console=tty0", it works. When I specify "console=tty0 console=ttyS0,9800", it doesn't work. Also, the textmode=1 is extraneous when using a serial console. 3) I've also found a mistake in one of the error messages. When I boot a machine that has only ide disks and the xml file refers to /dev/sda, it throws an error (as it should), but the error says, Partition "/" needs 1224.24 GB more disk space. I'm pretty sure that should be MB. Todd Ness wrote: >> very interesting, here is my pxe entry, I never get a graphical install, >> and want one. >> >> default linux >> serial 0,9600n8 >> label linux >> kernel linux >> append console=ttyS0,9800 console=tty0 load_ramdisk=1 initrd=initrd >> install=nfs://192.168.1.104/install/JDS >> autoyast=nfs://192.168.1.104/install/repository/autoinst.xml >> >> As far as answering any of your other problems I can not help, but maybe >> you can get a text install this way. I never get my questions answered. >> >> Todd >> >> On Tue, 2004-03-16 at 18:41, game82(a)unixpeople.com wrote: >> > >>>>In February, I posted that I was having two problems with the >>>>autoinstall of SLES8 - I wanted it to not prompt me to confirm >>>>lilo install, and I wanted it to use text mode. >>>> >>>>The response was to update to SP3 (gets rid of lilo) and to decrease >>>>the length of the command line (bug). >>>> >>>>Ok, I downloaded the iso images and re-spooled: >>>>Suse Standard Server 8 (came with the boxed product) >>>>UnitedLinux-1.0-SP-3-i386-RC4-CD1.iso >>>>UnitedLinux-1.0-SP-3-i386-RC4-CD2.iso >>>> >>>>then tried to install. >>>>Now, halfway through the install, it prompts me to insert 'UnitedLinux >>>>Version 1.0' CD 1. >>>> >>>>When I go to the details of the error, it says: >>>>SuSE Linux AG != SuSE Linux AG >>>>20031106141452 != 20021022150203 >>>> >>>>Ok, so I re-spooled again - this time just the two SP3 iso images and >>>>re-tried again. >>>>Same error. >>>> >>>>In addition, I can't seem to get the install to use the serial port as >>>>a console (all my servers are headless). >>>> >>>>It just doesn't seem to want to do that - here is my pxe entry: >>>>---------------------------------- >>>>label suse_standard_server_8 >>>> kernel suseKernel >>>> append initrd=s textmode=1 console=tty0 console=ttyS0,9600n8 >>>>ramdisk_size=64000 root=/dev/ram3 >>>>install=nfs://192.168.1.36/usr/software/l/s8 >>>>autoyast=nfs://192.168.1.36/usr/software/l/kickstart/y/s8.xml >>>>------------------------------------ >>>> >>>>Any ideas?

3 4

Onlineupdate for files on server
by Alexander.Gehrig＠rsd.rohde-schwarz.com 17 Mar '04

17 Mar '04

Hi All! I have a question about updateing the files befor installing: At the moment the client system will be installed with autoinstall and after installation an onlineupdate starts. How can i update the files on the server, is there a procedure for this kind of action? Thanks! Bye Alexander

4 3

autoyast and grub
by Manuel.Laesser＠telekurs.com 17 Mar '04

17 Mar '04

Hello, I would like to install GRUB instead of LILO using autoyast. If I use yast2 to create my xml file, I only have the possibility to install LILO. Does anyone have a xml file for GRUB? I'm using SLES8 with autoyast 2.6.36. Thank you very much for your help. Regards, Manuel ----------------------------------------------------------- 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 -----------------------------------------------------------

2 3

RE: SLES 8, PXE, serial console, prompting for CD #1
by game82＠unixpeople.com 17 Mar '04

17 Mar '04

In February, I posted that I was having two problems with the autoinstall of SLES8 - I wanted it to not prompt me to confirm lilo install, and I wanted it to use text mode. The response was to update to SP3 (gets rid of lilo) and to decrease the length of the command line (bug). Ok, I downloaded the iso images and re-spooled: Suse Standard Server 8 (came with the boxed product) UnitedLinux-1.0-SP-3-i386-RC4-CD1.iso UnitedLinux-1.0-SP-3-i386-RC4-CD2.iso then tried to install. Now, halfway through the install, it prompts me to insert 'UnitedLinux Version 1.0' CD 1. When I go to the details of the error, it says: SuSE Linux AG != SuSE Linux AG 20031106141452 != 20021022150203 Ok, so I re-spooled again - this time just the two SP3 iso images and re-tried again. Same error. In addition, I can't seem to get the install to use the serial port as a console (all my servers are headless). It just doesn't seem to want to do that - here is my pxe entry: ---------------------------------- label suse_standard_server_8 kernel suseKernel append initrd=s textmode=1 console=tty0 console=ttyS0,9600n8 ramdisk_size=64000 root=/dev/ram3 install=nfs://192.168.1.36/usr/software/l/s8 autoyast=nfs://192.168.1.36/usr/software/l/kickstart/y/s8.xml ------------------------------------ Any ideas?

2 1

Control file not found on hd->hd autoinstall...
by Johnny Ernst Nielsen 17 Mar '04

17 Mar '04

Good day, I am trying to get SuSE 9.0 Pro to autoinstall from harddisk to harddisk without using anything but the harddisk itself. What do I need to do to get autoyast to see the control file? This is my setup: 1 harddisk, partitioned like this: hda1: ext3, /boot (production system) hda2: ext3, for test system to mount as /boot hda3: swap hda4: extended hda5: ext3, / (production system) hda6: ext3, for test system to mount as / hda7: ext2, contains copies of install CDs in directories CD1-CD5 On the production system partitions I have a GRUB entry to start installation from harddisk: title Installer test-Linux fra harddisk kernel (hd0,6)/CD1/boot/loader/linux ramdisk_size=655536 splash=silent instmode=hd partition=hda7 serverdir=/CD1 autoyast=device://hda7/autoinst.xml initrd (hd0,6)/CD1/boot/loader/initrd I have created a control file, autoinst.xml, for autoyast and put it in the directory CD1 on hda7. When I boot the system and select the install entry in the GRUB boot menu, installation starts and autoyast autodetects some devices. But when autoyast tries to copy the control file it can not find the file and asks for a device and a file name. I can not get past that point. I have noticed that during the attempt to copy the control file autoyast writes: "Copying control file from device:/dev//autoinst.xml", leaving out the device. However, using the dialog box to enter the device and the file name does not help. The control file works fine when put on floppy. The installation from harddisk works fine if I leave out the autoyast variable at the GRUB boot prompt, although then I have to make all the selections manually. I have read the documentation that comes with the distro. I have searched the list archive. I have googled. No luck. Sorry if I missed the solution somewhere. What do I need to do to get autoyast to see the control file? Best regards :o) Johnny :o)

3 3

RE: [suse-autoinstall] Create installation cd using autoyast
by SLATER,CHRIS (HP-Roseville,ex1) 16 Mar '04

16 Mar '04

Hi Manuel, We actually do something very similar to this within Hewlett Packard. We have a web page where you can create a floppy or CD to autoinstall RedHat, Fedora, Debian and (in progress) various SuSE versions. You can get a glimpse at http://linuxcoe.com/designer There's a mail link there too if you want to discuss it with the main coder, Lee. Good luck! Chris -----Original Message----- From: Anas Nashif [mailto:nashif@suse.de] Sent: Tuesday, March 16, 2004 3:54 PM To: Manuel.Laesser(a)telekurs.com Cc: suse-autoinstall(a)suse.com Subject: Re: [suse-autoinstall] Create installation cd using autoyast Manuel.Laesser(a)telekurs.com wrote: > Hello, > for my degree dissertation I need to create an installation CD based > on > SLES8 with autoyast. Because our company wants to use this cd to install a > bunch of server it has to be very flexible. I've got the following > solution in my mind: > > - boot server with custom-made cd > - user has to enter ip-address, netmask, default-gw.... > - unattended installation using autoyast2 will start (installing base > system and all packages according to autoinst.xml) > - additional packages like service pack, company software, useraccounts of > all admins should be added > - configure server according to defined ip-address, netmask..... > > My questions now are: > > 1. Does this concept work out? Not with the released and fixed packages. I am currently working on a script to allow creation of SLES installation CDs. However it is still pending. > 2. Did anyone create a similar installation cd? > 3. Can anyone give me some hints, because I really don't know how to > approach this challenge! > Adding network data is not implemented in SLES8 (it will be available however in upcoming releases). Anas > Any comment is welcome! > > Regareds, Manuel > > ----------------------------------------------------------- > 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 > ----------------------------------------------------------- -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

Create installation cd using autoyast
by Manuel.Laesser＠telekurs.com 16 Mar '04

16 Mar '04

Hello, for my degree dissertation I need to create an installation CD based on SLES8 with autoyast. Because our company wants to use this cd to install a bunch of server it has to be very flexible. I've got the following solution in my mind: - boot server with custom-made cd - user has to enter ip-address, netmask, default-gw.... - unattended installation using autoyast2 will start (installing base system and all packages according to autoinst.xml) - additional packages like service pack, company software, useraccounts of all admins should be added - configure server according to defined ip-address, netmask..... My questions now are: 1. Does this concept work out? 2. Did anyone create a similar installation cd? 3. Can anyone give me some hints, because I really don't know how to approach this challenge! Any comment is welcome! Regareds, Manuel ----------------------------------------------------------- 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 -----------------------------------------------------------

2 1

Autoyast questions...
by Paul Edgar 16 Mar '04

16 Mar '04

All, When the installation reads the .xml file, is it parsed and executed in a sane order, or does the installer execute the xml file from top to bottom? Paul Edgar IBM Linux Technology Center

2 1

Antwort: [suse-autoinstall] Control file not found on hd->hd autoinstall...
by Alexander.Gehrig＠rsd.rohde-schwarz.com 16 Mar '04

16 Mar '04

Hi! I am looking for a rountine to do the same as you. I want to crate a partion, where i can boot from. Then image this partition an recreate it on many other systems (same partitionnumber). Then i want to install in this partion the Linux system. The Controlfile and the Files will be on a NFS-Server. But i did not find a solution to start the installation from a partion. Thanks for help! Bye Alexander |---------+---------------------------------> | | Johnny Ernst Nielsen | | | <johnny.ernst.nielsen@| | | get2net.dk> | | | | | | 16.03.2004 17:05 | | | | |---------+---------------------------------> >-------------------------------------------------------------------------------------------------------------------------------| | | | An: suse-autoinstall(a)suse.com | | Kopie: | | Thema: [suse-autoinstall] Control file not found on hd->hd autoinstall... | >-------------------------------------------------------------------------------------------------------------------------------| Good day, I am trying to get SuSE 9.0 Pro to autoinstall from harddisk to harddisk without using anything but the harddisk itself. What do I need to do to get autoyast to see the control file? This is my setup: 1 harddisk, partitioned like this: hda1: ext3, /boot (production system) hda2: ext3, for test system to mount as /boot hda3: swap hda4: extended hda5: ext3, / (production system) hda6: ext3, for test system to mount as / hda7: ext2, contains copies of install CDs in directories CD1-CD5 On the production system partitions I have a GRUB entry to start installation from harddisk: title Installer test-Linux fra harddisk kernel (hd0,6)/CD1/boot/loader/linux ramdisk_size=655536 splash=silent instmode=hd partition=hda7 serverdir=/CD1 autoyast=device://hda7/autoinst.xml initrd (hd0,6)/CD1/boot/loader/initrd I have created a control file, autoinst.xml, for autoyast and put it in the directory CD1 on hda7. When I boot the system and select the install entry in the GRUB boot menu, installation starts and autoyast autodetects some devices. But when autoyast tries to copy the control file it can not find the file and asks for a device and a file name. I can not get past that point. I have noticed that during the attempt to copy the control file autoyast writes: "Copying control file from device:/dev//autoinst.xml", leaving out the device. However, using the dialog box to enter the device and the file name does not help. The control file works fine when put on floppy. The installation from harddisk works fine if I leave out the autoyast variable at the GRUB boot prompt, although then I have to make all the selections manually. I have read the documentation that comes with the distro. I have searched the list archive. I have googled. No luck. Sorry if I missed the solution somewhere. What do I need to do to get autoyast to see the control file? Best regards :o) Johnny :o) -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

LVM with autoyast
by Manuel.Laesser＠telekurs.com 16 Mar '04

16 Mar '04

Hello, I would like to create the following partitions on a hp dl 380: - /boot (not part of LVM) - systemvg with - / - /var - /home - swap With the help from Damien I got the following xml file. The first time I used it on the Server it completed successfully but now, if I want to reinstall the server I always got the message: ------------------------------------------------------------------------------ vgcreate -A n -s 4096k systemvg /dev/cciss/c0d0p5 vgcreate - - volume group "systemvg" already exists ------------------------------------------------------------------------------ How can I get rid of this message so that autoyast will use the whole diskspace and recreate all partitions? I already tried with tag "<use>all</use>" but I'm not shure if I put it in the right place. Does anyone have some experiences with lvm? Thank you very much for your help. Manuel <partitioning config:type="list"> <drive> <device>/dev/cciss/c0d0</device> <partitions config:type="list"> <partition> <crypt_fs config:type="boolean">false</crypt_fs> <filesystem config:type="symbol">ext3</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> <region config:type="list"> <region_entry config:type="integer">0</region_entry> <region_entry config:type="integer">13</region_entry> </region> <size>98697217</size> </partition> <partition> <size>max</size> <lvm_group>systemvg</lvm_group> <partition_type>primary</partition_type> </partition> </partitions> <use>all</use> </drive> </partitioning> <lvm config:type="list"> <lvm_group> <lvm_name>systemvg</lvm_name> <pesize>4M</pesize> <logical_volumes config:type="list"> <lv> <lv_name>lvol1</lv_name> <lv_size>5G</lv_size> <lv_fs>ext3</lv_fs> <lv_mount>/</lv_mount> </lv> <lv> <lv_name>lvol2</lv_name> <lv_size>4G</lv_size> <lv_fs>ext3</lv_fs> <lv_mount>/var</lv_mount> </lv> <lv> <lv_name>lvol3</lv_name> <lv_size>1G</lv_size> <lv_fs>ext3</lv_fs> <lv_mount>/home</lv_mount> </lv> <lv> <lv_name>swap</lv_name> <lv_size>2G</lv_size> <lv_fs>swap</lv_fs> <lv_mount/> </lv> </logical_volumes> </lvm_group> </lvm>  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 -----------------------------------------------------------

2 1

[suse-autoinstall] LVM with autoyast
by Heirman, Steven 16 Mar '04

16 Mar '04

Hi Manuel Create a pre-script the removes existing volume group before it trys to create a new one <![CDATA[ #!/bin/sh vgs=$(vgscan | grep found | awk '{print $7}' | sed -e s/\"//g) insmod lvm-mod for vg in $vgs do vgchange -a y $vg lvs=$(lvscan | grep $vg | grep /dev | awk '{print $4}' | sed -e s/\"//g) for lv in $lvs do lvchange -a n $lv lvremove -f $lv done vgchange -a n $vg vgremove $vg done exit 0 ]]> This has to reside between the <configure></configure> entry' s in your autoyast file Good luck -----Original Message----- From: Manuel.Laesser(a)telekurs.com [mailto:Manuel.Laesser@telekurs.com] Sent: Tuesday, March 16, 2004 9:12 AM To: suse-autoinstall(a)suse.com Subject: [suse-autoinstall] LVM with autoyast Hello, I would like to create the following partitions on a hp dl 380: - /boot (not part of LVM) - systemvg with - / - /var - /home - swap With the help from Damien I got the following xml file. The first time I used it on the Server it completed successfully but now, if I want to reinstall the server I always got the message: ---------------------------------------------------------------------------- -- vgcreate -A n -s 4096k systemvg /dev/cciss/c0d0p5 vgcreate - - volume group "systemvg" already exists ---------------------------------------------------------------------------- -- How can I get rid of this message so that autoyast will use the whole diskspace and recreate all partitions? I already tried with tag "<use>all</use>" but I'm not shure if I put it in the right place. Does anyone have some experiences with lvm? Thank you very much for your help. Manuel <partitioning config:type="list"> <drive> <device>/dev/cciss/c0d0</device> <partitions config:type="list"> <partition> <crypt_fs config:type="boolean">false</crypt_fs> <filesystem config:type="symbol">ext3</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> <region config:type="list"> <region_entry config:type="integer">0</region_entry> <region_entry config:type="integer">13</region_entry> </region> <size>98697217</size> </partition> <partition> <size>max</size> <lvm_group>systemvg</lvm_group> <partition_type>primary</partition_type> </partition> </partitions> <use>all</use> </drive> </partitioning> <lvm config:type="list"> <lvm_group> <lvm_name>systemvg</lvm_name> <pesize>4M</pesize> <logical_volumes config:type="list"> <lv> <lv_name>lvol1</lv_name> <lv_size>5G</lv_size> <lv_fs>ext3</lv_fs> <lv_mount>/</lv_mount> </lv> <lv> <lv_name>lvol2</lv_name> <lv_size>4G</lv_size> <lv_fs>ext3</lv_fs> <lv_mount>/var</lv_mount> </lv> <lv> <lv_name>lvol3</lv_name> <lv_size>1G</lv_size> <lv_fs>ext3</lv_fs> <lv_mount>/home</lv_mount> </lv> <lv> <lv_name>swap</lv_name> <lv_size>2G</lv_size> <lv_fs>swap</lv_fs> <lv_mount/> </lv> </logical_volumes> </lvm_group> </lvm>  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 0

Antwort: Re: [suse-autoinstall] LVM with autoyast
by Peter.J.Bergmann＠merck.de 16 Mar '04

16 Mar '04

Hi, I handle this problem this way: entry in template.xml before vg - creation: insmod lvm-mod vgscan XX=/etc/lvmtab.d find $XX -type f | while read VG_PATH do echo "VG_PATH: >$VG_PATH<" VG=`basename $VG_PATH` echo ">$VG<" vgchange -a y $VG lvscan | grep $VG | while read COMMAND HIPHEN STATUS PATH SIZEA SIZEB do echo "------------------------" echo "PATH: $PATH" LV_PATH=`echo "$PATH" | /bin/sed s/\"//g` echo "LV_PATH: >$LV_PATH<" /sbin/lvremove -f $LV_PATH done vgchange -a n $VG vgremove $VG done Good luck and have a lot of fun! __________________________________ Peter Bergmann ISD/P - D40 / 109 Merck KGaA Frankfurter Strasse 250 D 64271 Darmstadt Phone: +49 (0)6151 72 4833 Mail: peter.j.bergmann(a)merck.de

1 0

autoyast - systems with 128mb and large rpms
by grant williamson 16 Mar '04

16 Mar '04

Hi, I have noticed that on systems with 128mb of memory, autoyast installation will not be able to handle large RPMS, i.e. Openoffice (50mb+). Performing an ftp install on suse9 using autoyast with a system of 128mb internal memory, the 64mb of ramdisk is really not enough. It will fail when it tries to download the OpenOffice rpm. Fails with unable to write to media error(The same install on the same machine, but with 256mb of internal memory works). Is there a way around this, apart from adding more memory to the machines? I looked into pre-script, but since filesystems get created after pre-script, this seems pointless. -- grant williamson <traxtopel(a)fastmail.fm>

1 0

Re: [suse-autoinstall] LVM with autoyast
by damien.selles＠eu.effem.com 16 Mar '04

16 Mar '04

Hi Manuel... you are right, to solve this issue, you can run a pre script like: <pre-scripts config:type="list"> <script> <filename>pre.sh</filename> <interpreter>shell</interpreter> <source> <![CDATA[#! /bin/sh # this script remove the systemvg (if there is one!) # thus it allow yast to perform the partitioning. vg=/dev/systemvg insmod lvm-mod vgscan vgchange -a y $vg lvs=`ls -A $vg | grep -v "group"` for lv in $lvs do lvremove -f $vg/$lv done vgchange -a n $vg vgremove $vg ]]> </source> </script> </pre-scripts> there may be more beautiful way to do it with Autoyast.. but I did not find it yet :)) regards, Damien. Manuel.Laesser(a)telekurs.com telekurs.com 16/03/2004 09:11 To: suse-autoinstall(a)suse.com cc: Subject: [suse-autoinstall] LVM with autoyast ------------------------------------------------------------------------------------------------------------------------------------------ Hello, I would like to create the following partitions on a hp dl 380: - /boot (not part of LVM) - systemvg with - / - /var - /home - swap With the help from Damien I got the following xml file. The first time I used it on the Server it completed successfully but now, if I want to reinstall the server I always got the message: ------------------------------------------------------------------------------ vgcreate -A n -s 4096k systemvg /dev/cciss/c0d0p5 vgcreate - - volume group "systemvg" already exists ------------------------------------------------------------------------------ How can I get rid of this message so that autoyast will use the whole diskspace and recreate all partitions? I already tried with tag "<use>all</use>" but I'm not shure if I put it in the right place. Does anyone have some experiences with lvm? Thank you very much for your help. Manuel <partitioning config:type="list"> <drive> <device>/dev/cciss/c0d0</device> <partitions config:type="list"> <partition> <crypt_fs config:type="boolean">false</crypt_fs> <filesystem config:type="symbol">ext3</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> <region config:type="list"> <region_entry config:type="integer">0</region_entry> <region_entry config:type="integer">13</region_entry> </region> <size>98697217</size> </partition> <partition> <size>max</size> <lvm_group>systemvg</lvm_group> <partition_type>primary</partition_type> </partition> </partitions> <use>all</use> </drive> </partitioning> <lvm config:type="list"> <lvm_group> <lvm_name>systemvg</lvm_name> <pesize>4M</pesize> <logical_volumes config:type="list"> <lv> <lv_name>lvol1</lv_name> <lv_size>5G</lv_size> <lv_fs>ext3</lv_fs> <lv_mount>/</lv_mount> </lv> <lv> <lv_name>lvol2</lv_name> <lv_size>4G</lv_size> <lv_fs>ext3</lv_fs> <lv_mount>/var</lv_mount> </lv> <lv> <lv_name>lvol3</lv_name> <lv_size>1G</lv_size> <lv_fs>ext3</lv_fs> <lv_mount>/home</lv_mount> </lv> <lv> <lv_name>swap</lv_name> <lv_size>2G</lv_size> <lv_fs>swap</lv_fs> <lv_mount/> </lv> </logical_volumes> </lvm_group> </lvm>  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 0

Re: [suse-autoinstall] autoyast on hp dl-380 with lvm
by damien.selles＠eu.effem.com 15 Mar '04

15 Mar '04

Hi, I would have corrected your file that way: <partitioning config:type="list"> <drive> <device>/dev/cciss/c0d0</device> <partitions config:type="list"> <partition> <crypt_fs config:type="boolean">false</crypt_fs> <filesystem config:type="symbol">ext3</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> <region config:type="list"> <region_entry config:type="integer">0</region_entry> <region_entry config:type="integer">13</region_entry> </region> <size>98697217</size> </partition> <partition> <size>36G</size> <lvm_group>systemvg</lvm_group> </partition> </partitions> <use>all</use> </drive> </partitioning> <lvm config:type="list"> <lvm_group> <lvm_name>systemvg</lvm_name> <pesize>4M</pesize> <logical_volumes config:type="list"> <lv> <lv_name>lvol1</lv_name> <lv_size>5G</lv_size> <lv_fs>ext3</lv_fs> <lv_mount>/</lv_mount> </lv> <lv> <lv_name>lvol2</lv_name> <lv_size>4G</lv_size> <lv_fs>ext3</lv_fs> <lv_mount>/var</lv_mount> </lv> <lv> <lv_name>lvol3</lv_name> <lv_size>1G</lv_size> <lv_fs>ext3</lv_fs> <lv_mount>/home</lv_mount> </lv> <lv> <lv_name>swap</lv_name> <lv_size>2G</lv_size> <lv_fs>swap</lv_fs> <lv_mount></lv_mount> </lv> </logical_volumes> </lvm_group> </lvm> I m not completely sure about the swap.. depending on the version of autoyast you are using.. I also advise you to have a look in: http://www.suse.de/~nashif/autoinstall/<your_version>/profile regards, Damien. Manuel.Laesser(a)telekurs.com telekurs.com 15/03/2004 14:47 To: suse-autoinstall(a)suse.com cc: Subject: [suse-autoinstall] autoyast on hp dl-380 with lvm ----------------------------------------------------------------------------------------------------------------------------- I'm trying to setup a hp dl 380 via autoyast (autoinst.xml) over a network installation. The xml is parsed properly but when the system comes to the harddisk partitioning, the system suddenly hangs. I reckon that the volume I want do create doesn't exist in /dev/[volumegroup_name] so the system is not able to create the partitions. Does anyone have experiences with lvm and unattendand installations? My xml file looks like: <partitioning config:type="list"> <drive> <device>/dev/cciss/c0d0</device> <partitions config:type="list"> <partition> <crypt_fs config:type="boolean">false</crypt_fs> <filesystem config:type="symbol">ext3</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> <region config:type="list"> <region_entry config:type="integer">0</region_entry> <region_entry config:type="integer">13</region_entry> </region> <size>98697217</size> </partition> <partition> <partition_id config:type="integer">142</partition_id> <partition_nr config:type="integer">2</partition_nr> <region config:type="list"> <region_entry config:type="integer">13</region_entry> <region_entry config:type="integer">4414</region_entry> </region> <size>36295901185</size> </partition> </partitions> <use>all</use> </drive> <drive> <device>/dev/systemvg</device> <partitions config:type="list"> <partition> <crypt_fs config:type="boolean">false</crypt_fs> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <mount>/</mount> <partition_id config:type="integer">131</partition_id> <partition_nr>home</partition_nr> <region config:type="list"> <region_entry config:type="integer">0</region_entry> <region_entry config:type="integer">1280</region_entry> </region> <size>5364514817</size> </partition> <partition> <crypt_fs config:type="boolean">false</crypt_fs> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <mount>/var</mount> <partition_id config:type="integer">131</partition_id> <partition_nr>root</partition_nr> <region config:type="list"> <region_entry config:type="integer">0</region_entry> <region_entry config:type="integer">1024</region_entry> </region> <size>4290772993</size> </partition> <partition> <crypt_fs config:type="boolean">false</crypt_fs> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <mount>swap</mount> <partition_id config:type="integer">131</partition_id> <partition_nr>swap</partition_nr> <region config:type="list"> <region_entry config:type="integer">0</region_entry> <region_entry config:type="integer">512</region_entry> </region> <size>2143289345</size> </partition> <partition> <crypt_fs config:type="boolean">false</crypt_fs> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <mount>/home</mount> <partition_id config:type="integer">131</partition_id> <partition_nr>var</partition_nr> <region config:type="list"> <region_entry config:type="integer">0</region_entry> <region_entry config:type="integer">256</region_entry> </region> <size>1069547521</size> </partition> </partitions> <use>all</use> </drive> </partitioning> Thank you very much any help! Regards 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 -----------------------------------------------------------

2 1

autoyast on hp dl-380 with lvm
by Manuel.Laesser＠telekurs.com 15 Mar '04

15 Mar '04

I'm trying to setup a hp dl 380 via autoyast (autoinst.xml) over a network installation. The xml is parsed properly but when the system comes to the harddisk partitioning, the system suddenly hangs. I reckon that the volume I want do create doesn't exist in /dev/[volumegroup_name] so the system is not able to create the partitions. Does anyone have experiences with lvm and unattendand installations? My xml file looks like: <partitioning config:type="list"> <drive> <device>/dev/cciss/c0d0</device> <partitions config:type="list"> <partition> <crypt_fs config:type="boolean">false</crypt_fs> <filesystem config:type="symbol">ext3</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> <region config:type="list"> <region_entry config:type="integer">0</region_entry> <region_entry config:type="integer">13</region_entry> </region> <size>98697217</size> </partition> <partition> <partition_id config:type="integer">142</partition_id> <partition_nr config:type="integer">2</partition_nr> <region config:type="list"> <region_entry config:type="integer">13</region_entry> <region_entry config:type="integer">4414</region_entry> </region> <size>36295901185</size> </partition> </partitions> <use>all</use> </drive> <drive> <device>/dev/systemvg</device> <partitions config:type="list"> <partition> <crypt_fs config:type="boolean">false</crypt_fs> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <mount>/</mount> <partition_id config:type="integer">131</partition_id> <partition_nr>home</partition_nr> <region config:type="list"> <region_entry config:type="integer">0</region_entry> <region_entry config:type="integer">1280</region_entry> </region> <size>5364514817</size> </partition> <partition> <crypt_fs config:type="boolean">false</crypt_fs> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <mount>/var</mount> <partition_id config:type="integer">131</partition_id> <partition_nr>root</partition_nr> <region config:type="list"> <region_entry config:type="integer">0</region_entry> <region_entry config:type="integer">1024</region_entry> </region> <size>4290772993</size> </partition> <partition> <crypt_fs config:type="boolean">false</crypt_fs> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <mount>swap</mount> <partition_id config:type="integer">131</partition_id> <partition_nr>swap</partition_nr> <region config:type="list"> <region_entry config:type="integer">0</region_entry> <region_entry config:type="integer">512</region_entry> </region> <size>2143289345</size> </partition> <partition> <crypt_fs config:type="boolean">false</crypt_fs> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <mount>/home</mount> <partition_id config:type="integer">131</partition_id> <partition_nr>var</partition_nr> <region config:type="list"> <region_entry config:type="integer">0</region_entry> <region_entry config:type="integer">256</region_entry> </region> <size>1069547521</size> </partition> </partitions> <use>all</use> </drive> </partitioning> Thank you very much any help! Regards 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 0

Re: [suse-autoinstall] Some Problems with AutoYaST
by damien.selles＠eu.effem.com 15 Mar '04

15 Mar '04

Hi Christian, For your issue number 2, you can have a look at the thread : "Re: [suse-autoinstall] is there a length limit on the line of parameters passed to isolinux.bin ?" on the 20/01/2004 in that mailing list your parameters line probably exceeds the maximum autorized length... you can even check this out, looking at the tty3 during the beginning of the installation and have a look at the parameter: "install:" you can also switch to tty9 and "cat /etc/install.inf" If all your parameters are there, that means the length limit is not the issue.... if they are not there (especially install) ... you found your issue number 2! regards, Damien Selles Christian Ehrlicher <Ch.Ehrlicher(a)gmx.de> gmx.de To: 11/03/2004 21:12 suse-autoinstall(a)suse.com cc: Subject: [suse-autoinstall] Some Problems with AutoYaST -------------------------------------------------------------------------------------------------------------------------------- -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello While playing around with AutoYaST I've found 2 problems: 1. Umlauts (öäü) in the user-defined scripts results in an non-loadable xml-file. AutoYaST didn't complain about this problem and also won't load other xml-files as well... I had this problem where I used an umlaut in a comment and it tooks really a long time until I've found this out :-( Also AutoYaST sometimes simply closed themself after I wanted to open such a xml-file 2. I can't boot without a dhcp/bootp - server. Here's my isolinux.cfg - entry: label linux kernel linux append initrd=initrd UseDHCP=no HostIP=192.168.10.100 IPAddr=192.168.10.100 ramdisk_size=65536 netdevice=eth0 ip=192.168.10.100 gateway=192.168.10.1 nameserver=192.168.10.1 autoyast=nfs://192.168.10.1/autoyast/suse install=nfs://192.168.10.1/autoyast/suse-cds/ While booting YaST tries to locate the dhcp/bootp - server although I gave them an ip explicitly. When I want to boot manually and select "Start installation/system->Start installation/update->Network->NFS" I can select an ip without accessing a dhcp/bootp-server, but this won't work at boot-time. Or am I missing a parameter? The second problem is really sad because they won't use a dhcp-server and so AutoYaST is useless for me :-( A nive feature which I would like to see implemented are the smb-client and server settings because this is needed in networks with windows. Christian -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFAUMg/nNKwkgf+zVMRAk7tAJwIkvKqVp5+tE6APoSAdGAGv5YMKACfcKg9 u4WWjqT32vNPRTq7pr/4/6Y= =+ZmI -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

Configuring PCMCIA cards
by kidtv＠metronet.co.uk 12 Mar '04

12 Mar '04

Hi, I am trying to install Suse 9.0 but I need a suitable driver module for my PCMCIA card to configure it to connect to my ADSL modem. Does anyone know where I can download one from or how to do it manually? Thanks Alistair

1 0

disk-to-disk auto-install with autoyast
by Wenk, Moritz 12 Mar '04

12 Mar '04

Hello, I am trying to do a disk-to-disk auto-installation with autoyast. I dumped everything on the first CD into the root of the first partition of the first disk and added a "info"-file on a diskette: InstMode: hd Partition: hda1 Install: device://hda1 RootImage: device://hda1/boot/root AutoYaST: device://hda1/autoyast.xml Booting the kernel from hdc1 works and the info-file is loaded but linuxrc stops with Looking for a SuSE Linux hard disk Checking partition: /dev/hda1 Nothing found on /dev/hda1 ...; giving up Any suggestions? Thanks, i. A. Moritz Wenk Software Developer Produkt Management International PLATINUM Server MAXDATA Computer GmbH&Co.KG Elbestraße 12 - 16 D-45768 Marl Telefon: +49 2365 952-2715 Telefax: +49 2365 952-2279 <http://www.maxdata.com/> http://www.maxdata.com

1 0

Some Problems with AutoYaST
by Christian Ehrlicher 11 Mar '04

11 Mar '04

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello While playing around with AutoYaST I've found 2 problems: 1. Umlauts (öäü) in the user-defined scripts results in an non-loadable xml-file. AutoYaST didn't complain about this problem and also won't load other xml-files as well... I had this problem where I used an umlaut in a comment and it tooks really a long time until I've found this out :-( Also AutoYaST sometimes simply closed themself after I wanted to open such a xml-file 2. I can't boot without a dhcp/bootp - server. Here's my isolinux.cfg - entry: label linux kernel linux append initrd=initrd UseDHCP=no HostIP=192.168.10.100 IPAddr=192.168.10.100 ramdisk_size=65536 netdevice=eth0 ip=192.168.10.100 gateway=192.168.10.1 nameserver=192.168.10.1 autoyast=nfs://192.168.10.1/autoyast/suse install=nfs://192.168.10.1/autoyast/suse-cds/ While booting YaST tries to locate the dhcp/bootp - server although I gave them an ip explicitly. When I want to boot manually and select "Start installation/system->Start installation/update->Network->NFS" I can select an ip without accessing a dhcp/bootp-server, but this won't work at boot-time. Or am I missing a parameter? The second problem is really sad because they won't use a dhcp-server and so AutoYaST is useless for me :-( A nive feature which I would like to see implemented are the smb-client and server settings because this is needed in networks with windows. Christian -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFAUMg/nNKwkgf+zVMRAk7tAJwIkvKqVp5+tE6APoSAdGAGv5YMKACfcKg9 u4WWjqT32vNPRTq7pr/4/6Y= =+ZmI -----END PGP SIGNATURE-----

1 0

RE: [suse-autoinstall] Installation from CD
by Ness, Todd 11 Mar '04

11 Mar '04

Anas, Is it possible to get the installation process to find package descriptions on any media other than media.1? As soon as I changed the name from media.6 to media.1 it saw my package descriptions and selection files, of course the required rpms on the real media 1 were not there. Todd -----Original Message----- From: Ness, Todd [mailto:todd.ness@eds.com] Sent: Monday, March 08, 2004 3:06 PM To: suse-autoinstall(a)suse.com Subject: RE: [suse-autoinstall] Installation from CD I have this working, the NFS builds work fine, but, when building from CD I do not get any software selection files. This is curios, I have the same suse/setup/descr/* files on the CD as the NFS repository. If anybody has any idea as to why the selections and software can not be found I would appreciate the help. Todd -----Original Message----- From: Ness, Todd [mailto:todd.ness@eds.com] Sent: Monday, March 08, 2004 2:24 PM To: suse-autoinstall(a)suse.com Subject: [suse-autoinstall] Installation from CD Is it possible to create a new bootable cd for a sles8 set, that has customized initrd, and suse/setup/descr, xmls files and customized packages that I could boot off without having to edit disk1 in the set? Example: I have a 5 disk set, I make my own rpms, I add some .sel files to suse/setup/descr, I make an info file in an initrd that installs via nfs, one for booting off cd and uses xml files located in /profiles of the initrd. Has a custom isolinux.cfg to choose which xml script to use. I then bundle all of that up into a bootable disk6 boot off of this disk, choose a boot menu choice. And then have it ask me to insert CD1? Thanks, Todd Ness -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

2 1

Configure autoyast for different network interface card´s ??
by K.-W. Grabbe 11 Mar '04

11 Mar '04

Hello, I want to install SuSE Linux on different Hardware with different network interface card´s. When I merge the classes with the parts of each Network configuration, the result ist the network hardware configuration of one of the systems. Has anybody experience? Regards K.-W. Grabbe -- +++ NEU bei GMX und erstmalig in Deutschland: TÜV-geprüfter Virenschutz +++ 100% Virenerkennung nach Wildlist. Infos: http://www.gmx.net/virenschutz

1 0

Re: [suse-autoinstall] PXE install trouble with initrd
by Achim Öhlenschläger 10 Mar '04

10 Mar '04

Anas Nashif schrieb: > Hi, > make sure you are using the latest pxelinux.0. I've downloaded syslinux version 2.08-1, now everything works perfectly. Thanks for the hint. > > Anas > > Achim Öhlenschläger wrote: > >> I'm trying to install Suse Linux on a single board computer >> (net4801) with no CD or floppy drive and the console is on a serial line via minicom. >> To do so, I'm following the instructions from the support database article: >> "Network Installation of SuSE Linux via PXE Boot" ... >> RAMDISK: Couldn't find valid RAM disk image starting at 0. >> Freeing initrd memory: 4545k freed >> kmod: failed to exec /sbin/modprobe -s -k block-major-3, errno = 2 >> VFS: Cannot open root device "" or 03:02 >> Please append a correct "root=" boot option >> Kernel panic: VFS: Unable to mount root fs on 03:02 ...

1 0

install option textmode & vga entry in grub
by grant williamson 10 Mar '04

10 Mar '04

Hi, I prefer to install using textmode(less bloat) however this means that as default I do not get the framebuffer once a machine is installed. I need to add a vga=.... to grubs menu.lst. Is there a way in a textmode install to add something to the autoinst.xml, so it will append this to the kernel on boot. -- grant williamson <traxtopel(a)fastmail.fm>

1 0

Change inst. source..?
by Miro Barbu 10 Mar '04

10 Mar '04

Is it possible to change the inst. source on the client with autoyast..? When autoinstiall is finished, the inst source points to my nfs mount. Instead it would be great if it could point to a public ftp-server. Thanks. Miro.

2 1

Re: [suse-autoinstall] Question/suggestion Linux Installation ove r Network]
by Dustin Kirkland 09 Mar '04

09 Mar '04

forgot to copy everyone else (sorry)

1 0

Re: [suse-autoinstall] Question/suggestion Linux Installation ove r Network
by Lenz, Fabian 09 Mar '04

09 Mar '04

When you boot from CD, there comes the Question, if you want to install or if you want to boot the local System, it is not possible to build in something like this? You load the kernel over the network and ask then, if you want to install or start the installed system. >Using syslog-ng on the remote logging server (boot server) you could use >something like that: >destination tftp { program("/usr/local/bin/client-booting"); }; >#destination tftp { file("/var/log/openwbem"); }; >log { source(src); filter(f_tftp); destination(tftp); }; >in syslog-ng.conf and let the script do the magic :-) This is a fine idea. i will test it. >Or I could add a message to the yast2 log which now supports syslog and >remote logging which says that it safe to change the config files on the >boot server. Such a message can be identified using a filter in >syslog-ng and the switching from netboot to localboot can be done. Which version supports syslog? This idea i think is the best, so you have a status and you can switch. The idea from Bjørn is very easy and not bad, but when you have more than 100 PC´s, you look for a better way. ;-)

2 1

PXE install trouble with initrd
by Achim Öhlenschläger 09 Mar '04

09 Mar '04

Hello, I hope this is the right list for my question. I'm trying to install Suse Linux on a single board computer (net4801) with no CD or floppy drive and the console is on a serial line via minicom. To do so, I'm following the instructions from the support database article: "Network Installation of SuSE Linux via PXE Boot" Initially I tried to install version 9.0, but to follow the instructions as close as possible I downloaded the necessary files for version 8.1 from the SuSE FTP server. Setting up the installation repository, the TFTP server and pxelinux was no problem and the board started the kernel via the network. According to the log on my TFTP server, also the inird is being loaded. However the boot procedure stops with the message: --Snip-- RAMDISK: Couldn't find valid RAM disk image starting at 0. Freeing initrd memory: 4545k freed kmod: failed to exec /sbin/modprobe -s -k block-major-3, errno = 2 VFS: Cannot open root device "" or 03:02 Please append a correct "root=" boot option Kernel panic: VFS: Unable to mount root fs on 03:02 --Snip-- My pxelinux.cfg/default file looks like: --snip-- SERIAL 0 19200 0 default suse81 ... label suse81 kernel linux81 append console=ttyS0,19200n81 initrd=initrd81 ramdisk_size=65536\ ide=nodma apm=off acpi=off insmod=natsemi\ install=nfs://192.168.1.99/usr/local/dist/suse ... implicit 0 display message prompt 1 timeout 100 --snip-- I've actually some more labels in my default file, because I was trying a lot of things like compiling my own kernel, trying different versions etc. but always with the same result. I have no clue what to do to make it work, any help would be greatly appreciated. Achim PS: By compiling the network driver into the kernel and specifying a NFS root I was able to get to a shell prompt, but I wasn't able to launch the installation from there either. So if somebody knows a recipe how to continue from there, that may also help.

3 2

RE: [suse-autoinstall] Installation from CD
by Ness, Todd 08 Mar '04

08 Mar '04

I have this working, the NFS builds work fine, but, when building from CD I do not get any software selection files. This is curios, I have the same suse/setup/descr/* files on the CD as the NFS repository. If anybody has any idea as to why the selections and software can not be found I would appreciate the help. Todd -----Original Message----- From: Ness, Todd [mailto:todd.ness@eds.com] Sent: Monday, March 08, 2004 2:24 PM To: suse-autoinstall(a)suse.com Subject: [suse-autoinstall] Installation from CD Is it possible to create a new bootable cd for a sles8 set, that has customized initrd, and suse/setup/descr, xmls files and customized packages that I could boot off without having to edit disk1 in the set? Example: I have a 5 disk set, I make my own rpms, I add some .sel files to suse/setup/descr, I make an info file in an initrd that installs via nfs, one for booting off cd and uses xml files located in /profiles of the initrd. Has a custom isolinux.cfg to choose which xml script to use. I then bundle all of that up into a bootable disk6 boot off of this disk, choose a boot menu choice. And then have it ask me to insert CD1? Thanks, Todd Ness -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

Installation from CD
by Ness, Todd 08 Mar '04

08 Mar '04

Is it possible to create a new bootable cd for a sles8 set, that has customized initrd, and suse/setup/descr, xmls files and customized packages that I could boot off without having to edit disk1 in the set? Example: I have a 5 disk set, I make my own rpms, I add some .sel files to suse/setup/descr, I make an info file in an initrd that installs via nfs, one for booting off cd and uses xml files located in /profiles of the initrd. Has a custom isolinux.cfg to choose which xml script to use. I then bundle all of that up into a bootable disk6 boot off of this disk, choose a boot menu choice. And then have it ask me to insert CD1? Thanks, Todd Ness

1 0

autoyast and loadorder of modules
by Helge Koehn 08 Mar '04

08 Mar '04

hi, we face a problem where we have to load kernelmodules in a specific order to get our scsi devices recognized correctly! we are doing an autoyastinstallation via pxe. we send with the append parameter in the pxe-config file the modules to load, that works. our scsi device are recognized in the correct order. in the autoyast.xml we are partitioning the scsi devices and write the bootloader to /dev/sda. the stuff from disk 1 is transfered to the installed system. after the first initial boot, the order we have with the append parameter in the pxe-config file no longer works, autoyast has build its own initrd for the initial boot and with that the devices are changing because of loading the adapterdrivers in the wrong order! how can we arrange that our wanted order of devices also works after the initial boot. so that /dev/sda remains /dev/sda and not switches to /dev/sdb thanks for an answer. helge.

1 0

Question/suggestion Linux Installation over Network
by Lenz, Fabian 06 Mar '04

06 Mar '04

Hello! I install Linux over network with pxe! There is a DHCP/tftp server and a nfs server. The installation works, but the installation starts always when the PC is booting. On page 41, chapter 7.1.2, example 7-2 and 7-3, is an example how to stop the installation after the reboot. Is there a way to solve the problem without remove a file or a symlink, like an autoyastdaemon? Here is the way how I install the PC´s now: (DHCP Discover) PC ------------------------------------------> DHCP Server (DHCP and tftp server are on one machine) <----------------------------------------- (DHCP Offer) (bootfile/tftpserver) ........ (tftp bootfile/pxelinux.o) PC -----------------------------------------> tftp server <---------------------------------------- -----------------------------------------> (tftp pxelinux.cfg) ......... (nfs mount) PC -----------------------------------------> nfs Server Installation starts *** new,my suggestion with autoyast daemon **** same as above, but asking the installion status before starting Sould I really install? PC ------------------------------------------> autoyast server ( e.g. IP from dhcp Option >128) <------------------------------------------ yes/no Start installation or locally boot and now after installation: Status Install ready PC ---------------------------------------------> autoyast daemon There could be an autoyast server (daemon), and the client would get the autoyast server ip from the dhcp server, option > 128! The autoyast on the install pc could ask or set a status via the daemon. So we would have a stateful installation with a central instance were the installation could be monitored and controlled. In some further versions something like 'ZenWorks light' could be possible, putting all the installation configs in a LDAP directory. This autoyast server could also be able to send the autoinst.xml and the package selection, which then could be taken from our LDAP directory. Fabian Lenz Azb Fachinformatiker für Systemintegration Deutsche Telekom AG Telekom Training BBi Koblenz Hausadresse: Blücherstr. 6-8, 56073 Koblenz Postanschrift: Postfach 9100, 56065 Koblenz Telefon (mobil): +49 (160) 3565851 E-Mail: mailto:Fabian.Lenz@telekom.de Intranet: http://ttc.telekom.de/

3 2

Re: [suse-autoinstall] Question/suggestion Linux Installation over Network
by damien.selles＠eu.effem.com 05 Mar '04

05 Mar '04

Hi Bjorn, And what if your boot disk crashes.. ? or even our MBR crashes... your system will re install automatically.. without warning... (and maybe making you loose some data.)? Don't you think Fabian's process allow you a better control over "re- installation"? Regards, Damien. Bjorn Tore Sund <bjornts(a)mi.uib.no> mi.uib.no To: 05/03/2004 13:46 suse-autoinstall(a)suse.com cc: Subject: Re: [suse-autoinstall] Question/suggestion Linux Installation over Network -------------------------------------------------------------------------------------------------------------------------- On Fri, 5 Mar 2004, Lenz, Fabian wrote: > Hello! > > I install Linux over network with pxe! There is a DHCP/tftp server and a nfs server. > The installation works, but the installation starts always when the PC is booting. > > On page 41, chapter 7.1.2, example 7-2 and 7-3, is an example how to stop the installation after the reboot. > Is there a way to solve the problem without remove a file or a symlink, like an autoyastdaemon? My approach to this is rather simpler, and I'll implement it sometime Real Soon Now(tm). I've got the hard drive before the NIC in the boot order in BIOS. On a new PC, there's no bootable MBR so the machine skips the hard drive and boots from the NIC. When you want to reinstall a machine all you have to do is make the hard drive unbootable: 'dd if=/dev/zero of=/dev/hda bs=512 count=1' before a reboot should do the trick - this bit I haven't tested yet... Bjørn -- Bjørn Tore Sund Phone: (+47) 555-84894 Stupidity is like a System administrator Fax: (+47) 555-89672 fractal; universal and Math. Department Mobile: (+47) 918 68075 infinitely repetitive. University of Bergen VIP: 81724 teknisk(a)mi.uib.no Email: bjornts(a)mi.uib.no http://www.mi.uib.no/ -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

2 1

UNSUSCRIBE ME PLEASE!
by Isabel Falcon 05 Mar '04

05 Mar '04

Ing. Isabel Falcón Consultor de Ventas Afina Sistemas ifalcon(a)afina.com.ve <mailto:ifalcon@afina.com.ve> Av Libertador Multicentro Empresarial del Este Torre Libertador Nucleo B Piso 3 Of B31 Chacao 1060 - Caracas - Venezuela tel: 58-212-2661163 // 7755 // 8980 fax: 58-212-2636502 mobile: 58-412-3729747 web: www.afina.com.ve <http://www.afina.com.ve> -----Original Message----- From: damien.selles(a)eu.effem.com [mailto:damien.selles@eu.effem.com] Sent: Viernes, 05 de Marzo de 2004 09:41 a.m. To: Bjorn Tore Sund Cc: suse-autoinstall(a)suse.com Subject: Re: [suse-autoinstall] Question/suggestion Linux Installation over Network Hi Bjorn, And what if your boot disk crashes.. ? or even our MBR crashes... your system will re install automatically.. without warning... (and maybe making you loose some data.)? Don't you think Fabian's process allow you a better control over "re- installation"? Regards, Damien. Bjorn Tore Sund <bjornts(a)mi.uib.no> mi.uib.no To: 05/03/2004 13:46 suse-autoinstall(a)suse.com cc: Subject: Re: [suse-autoinstall] Question/suggestion Linux Installation over Network -------------------------------------------------------------------------------------------------------------------------- On Fri, 5 Mar 2004, Lenz, Fabian wrote: > Hello! > > I install Linux over network with pxe! There is a DHCP/tftp server and a nfs server. > The installation works, but the installation starts always when the PC is booting. > > On page 41, chapter 7.1.2, example 7-2 and 7-3, is an example how to stop the installation after the reboot. > Is there a way to solve the problem without remove a file or a symlink, like an autoyastdaemon? My approach to this is rather simpler, and I'll implement it sometime Real Soon Now(tm). I've got the hard drive before the NIC in the boot order in BIOS. On a new PC, there's no bootable MBR so the machine skips the hard drive and boots from the NIC. When you want to reinstall a machine all you have to do is make the hard drive unbootable: 'dd if=/dev/zero of=/dev/hda bs=512 count=1' before a reboot should do the trick - this bit I haven't tested yet... Bjørn -- Bjørn Tore Sund Phone: (+47) 555-84894 Stupidity is like a System administrator Fax: (+47) 555-89672 fractal; universal and Math. Department Mobile: (+47) 918 68075 infinitely repetitive. University of Bergen VIP: 81724 teknisk(a)mi.uib.no Email: bjornts(a)mi.uib.no http://www.mi.uib.no/ -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

Autoyast on pSeries machines.
by Paul Edgar 03 Mar '04

03 Mar '04

We have written a series of scripts for SuSE SLES 8that will setup the machine for autoyast installation and reboot the machine for installation. All works well on Intel and opteron platforms, but when we try to make a PPC machine install we run into a few issues. 1. It looks like the machine installs the OS, until the first reboot. At that time the machine refuses to boot up. If we put the installation CD in the cdrom drive, boot with that, we can select 'Boot installed system". 2. After selecting this, the machine boots up and finishes up the installation just like normal. Here is what I see when the machine does it's first reboot during install. /dev/sda invalid device Then I go into rescue CD mode from the installation CD and look at /etc/yaboot.conf which does not exist. So I chroot the mounted and look at lilo.conf which has the following in it. This does not look correct from what I have seen when the system is installed macnually. default=linux timeout=100 boot= activate image = /boot/vmlinux label = linux root = /dev/sda3 initrd = /boot/initrd append = "" If I try to run lilo at this point, it errors out on boot= which should be /dev/sda1. Activate is an extra parameter I have not seen before. Image pointed to /boot/vmlinux.initrd initrd = was not there append = "" was not there Any suggestions, questions, or pointers would be helpful. -- Paul Edgar Verification Engineer Linux Technology Center / IBM External 512.838.1493 / TieLine 678-1493 javaoops(a)us.ibm.com No trees were destroyed in the sending of this message, however, a significant number of electrons were terribly inconvenienced.

4 7

How to avoid booting confirmation?
by Robert Pollak 03 Mar '04

03 Mar '04

Hello! I use the appended control file autoinst.xml on a floppy during installation from the original SLES8 CDs. At the end of the "Finishing Basic Installation" screen, i am asked > The LILO boot sector has been written to disk. You can restore > the old boot sector in the installed system with "lilo -u /dev/sda" > > Now booting your system... > [OK-Button] , and the installer waits for interactive confirmation. How can i change the control file such that this confirmation is not needed? Or can't it be suppressed by any of the <mode> entries? -Robert ****************autoinst.xml**************** <?xml version="1.0"?> <!DOCTYPE profile SYSTEM "/usr/share/YaST2/include/autoinstall/profile.dtd"> <profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <configure> <users config:type="list"> <user> <encrypted config:type="boolean">true</encrypted> <user_password>XXXXXX</user_password> (<- pw removed) <username>root</username> </user> </users> </configure> <install> <bootloader> <location>mbr</location> </bootloader> <general> <clock> <hwclock>GMT</hwclock> <timezone>Europe/Vienna</timezone> </clock> <keyboard> <keymap>german</keymap> </keyboard> <mode> <installation config:type="boolean">true</installation> <upgrade config:type="boolean">false</upgrade> <confirm config:type="boolean">false</confirm> <interactive_boot config:type="boolean">false</interactive_boot> <reboot config:type="boolean">false</reboot> </mode> </general> <partitioning config:type="list"> <drive> <device>/dev/sda</device> <initialize config:type="boolean">true</initialize> <partitions config:type="list"/> <use>all</use> </drive> </partitioning> <software> <base>Minimal</base> </software> </install> </profile>

2 2