September 2004 - openSUSE Autoinstall - openSUSE Mailing Lists

Re: [suse-autoinstall] PXE install fails with SCSI disks
by Steve Glines 07 Dec '04

07 Dec '04

Hi Anas, Thanks for the help. I've made all the fixes you and Marcin Kurc suggested but the system still refuses to see the scsi disks. Here is the data. The target system is an HP Proliant ML350 G3 with a single 40GB SCSI disk. The script shown in sles9/CD1/docu/RELEASE-NOTES.en.html doesn't work so I've modified it thus (feel free to reuse it): #From the top directory umask 0 mkdir -p sles9/CD1 # now copy the contents of SLES CD1 into this directory echo "Mount CD1" read x mount /dev/cdrom sleep 10 cp -r /cdrom/* sles9/CD1 eject mkdir -p core9/CD1 # now copy the contents of SLES CD2 into this directory echo "Mount CD2" read x sleep 10 mount /dev/cdrom cp -r /cdrom/* core9/CD1 eject mkdir -p core9/CD2 # now copy the contents of SLES CD3 into this directory echo "Mount CD3" read x sleep 10 mount /dev/cdrom cp -r /cdrom/* core9/CD2 eject mkdir -p core9/CD3 # now copy the contents of SLES CD4 into this directory echo "Mount CD4" read x sleep 10 mount /dev/cdrom cp -r /cdrom/* core9/CD3 eject mkdir -p core9/CD4 now copy the contents of SLES CD5 into this directory echo "Mount CD5" read x sleep 10 mount /dev/cdrom cp -r /cdrom/* core9/CD4 eject mkdir -p core9/CD5 now copy the contents of SLES CD6 into this directory echo "Mount CD6" read x sleep 10 mount /dev/cdrom cp -r /cdrom/* core9/CD5 eject ln -s sles9/CD1/boot boot ln -s sles9/CD1/content content ln -s sles9/CD1/control.xml control.xml ln -s sles9/CD1/media.1 media.1 mkdir -p yast echo "/sles9/CD1 /sles9/CD1 /core9/CD1 /core9/CD1" > yast/instorder echo "/sles9/CD1 /sles9/CD1 /core9/CD1 /core9/CD1" > yast/order --------------------------------- After PXE booting the system stalls when it can't find a hard disk. When I look in /var/log/boot.log I find: kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter errorno=2 If I run "/sbin/modprobe -s -k scsi_hostadapter" directly from a shell I get "Kernel requires old modprobe no /sbin/modprobe.old." ------------------------------------------- Here is the current line from my default file: label suse kernel suse.kernel append initrd=suse.root ramdisk_size=65536 \ install=http://10.0.3.11/suse ---------------------------------------------- Here is the output of "find . -type d": . ./sles9 ./sles9/CD1 ./sles9/CD1/SLES-LICENSE ./sles9/CD1/SLES-LICENSE/cz ./sles9/CD1/SLES-LICENSE/de ./sles9/CD1/SLES-LICENSE/en_US ./sles9/CD1/SLES-LICENSE/es ./sles9/CD1/SLES-LICENSE/fr ./sles9/CD1/SLES-LICENSE/it ./sles9/CD1/SLES-LICENSE/nl ./sles9/CD1/SLES-LICENSE/pl ./sles9/CD1/SLES-LICENSE/pt_BR ./sles9/CD1/boot ./sles9/CD1/boot/loader ./sles9/CD1/docu ./sles9/CD1/docu/de ./sles9/CD1/docu/en ./sles9/CD1/docu/es ./sles9/CD1/docu/fr ./sles9/CD1/docu/HOWTOs ./sles9/CD1/docu/it ./sles9/CD1/docu/ja ./sles9/CD1/docu/ko ./sles9/CD1/docu/pt_BR ./sles9/CD1/docu/zh_CN ./sles9/CD1/dosutils ./sles9/CD1/dosutils/dparam ./sles9/CD1/dosutils/ext2tool ./sles9/CD1/dosutils/ext2tool/ext2fs ./sles9/CD1/dosutils/ext2tool/linux ./sles9/CD1/dosutils/ext2tool/src ./sles9/CD1/dosutils/ext2tool/sys ./sles9/CD1/dosutils/fips ./sles9/CD1/dosutils/fips/fips15 ./sles9/CD1/dosutils/fips/fips15/restorrb ./sles9/CD1/dosutils/fips/fips15/source ./sles9/CD1/dosutils/fips/fips20 ./sles9/CD1/dosutils/fips/fips20/restorrb ./sles9/CD1/dosutils/fips/fips20/source ./sles9/CD1/dosutils/gtar109 ./sles9/CD1/dosutils/gzip ./sles9/CD1/dosutils/install ./sles9/CD1/dosutils/lfn ./sles9/CD1/dosutils/loadlin ./sles9/CD1/dosutils/loadlin/doc ./sles9/CD1/dosutils/loadlin/src ./sles9/CD1/dosutils/ltools ./sles9/CD1/dosutils/pkunzip ./sles9/CD1/dosutils/putty ./sles9/CD1/dosutils/rawrite ./sles9/CD1/dosutils/rawwritewin ./sles9/CD1/dosutils/tightvnc ./sles9/CD1/dosutils/untgz ./sles9/CD1/dosutils/weirdx ./sles9/CD1/dosutils/weirdx/config ./sles9/CD1/dosutils/xfs186 ./sles9/CD1/dosutils/xfs32-11 ./sles9/CD1/dosutils/zipzp715 ./sles9/CD1/media.1 ./sles9/CD1/suse ./sles9/CD1/suse/i586 ./sles9/CD1/suse/noarch ./sles9/CD1/suse/nosrc ./sles9/CD1/suse/setup ./sles9/CD1/suse/setup/descr ./sles9/CD1/suse/src ./sles9/CD1/yast ./sles9/CD1/yast/core9 ./sles9/CD1/yast/core9/media.1 ./sles9/CD1/yast/core9/suse ./sles9/CD1/yast/core9/suse/setup ./sles9/CD1/yast/core9/suse/setup/descr ./core9 ./core9/CD1 ./core9/CD1/media.1 ./core9/CD1/suse ./core9/CD1/suse/i586 ./core9/CD1/suse/i686 ./core9/CD1/suse/noarch ./core9/CD1/suse/setup ./core9/CD1/suse/setup/descr ./core9/CD2 ./core9/CD2/media.2 ./core9/CD2/suse ./core9/CD2/suse/i586 ./core9/CD2/suse/i686 ./core9/CD2/suse/noarch ./core9/CD3 ./core9/CD3/media.3 ./core9/CD3/suse ./core9/CD3/suse/i586 ./core9/CD3/suse/i686 ./core9/CD3/suse/noarch ./core9/CD3/suse/src ./core9/CD4 ./core9/CD4/media.4 ./core9/CD4/suse ./core9/CD4/suse/nosrc ./core9/CD4/suse/src ./core9/CD5 ./core9/CD5/media.5 ./core9/CD5/suse ./core9/CD5/suse/nosrc ./core9/CD5/suse/src ./yast Marcin Kurc wrote: > > for graphical install you can say 'textmode=0' after 'install*' > please send me your 'default' file and output of 'find . -type d' in the > suse top directory > > > > thanks, > > Marcin Kurc > Linux Impact Team > Novell, Inc > > (973) 493-6235 > >>>>Steve Glines <sglines(a)is-cs.com> 09/01/04 3:37 pm >>> > Thanks - I missed that one and was following the instructions that came > with SUSE 9.1 Pro. It still boots into the non-X format via PXE and X > when I do a CDROM install. Is there a way to make it boot into Graphics > mode. The lab I'm building is supposed to simulate the experience of > installing via CDROM. By the way this is going to go into HP's main > learning lab. The Red Hat version is being used 30-50 times a day. > > Now I'm getting "Network error 404 not found." > > Cheers > Steve > > Marcin Kurc wrote: > >> >>it is not a problem with PXE, your installation tree is not configured >>correctly >>You should either use SLES9 system to build the tree or configure it >>according to the docu/RELEASE-NOTES.en.html which can be found on cd #1 >> >>Also, you need to point you install to top dir not CD1 i.e. >>'install=_/http://10.0.3.11/suse/_' >> >> >> >>thanks, >> >>Marcin Kurc >>Linux Impact Team >>Novell, Inc >> >>(973) 493-6235 >> >>>>>Steve Glines <sglines(a)is-cs.com> 09/01/04 2:30 pm >>> >>I’m building a PXE install lab for SUSE and other flavors of Linux. >> >>The DHCP and tftp servers are working. Note: I can fully install Red Hat >>from this lab but SUSE (SLES9 rc5) shows the following symptoms: >> >>1.a cdrom install on the target system runs to completion in graphics >>mode. System is an HP PC with SCSI disk. >>2.PXE install runs in non X-window mode (text) and fails to load scsi >>controllers – cannot find any disks. Fails even when modules are >>manually added. >> >>Here is the content of /tftpboot/pxelinux.cfg/default: >> >>default suse >>prompt 1 >>display boot.msg >>timeout 200 >> >>label redhat >> kernel redhat.kernel >> append initrd=redhat.root ramdisk_size=65536 >> >>label suse >> kernel suse.kernel >> append initrd=suse.root ramdisk_size=65536\ >>install=http://10.0.3.11/suse/CD1/ >> >>The file suse.kernel was copied from /boot/loader/linux in CD1 while >>suse.root was taken from /boot/loader/initrd in the same CD. >> >>I copied the contents of each CD into their own directories – I have CD1 >> – CD6 in the directory specified by http://10.0.3.11/suse/CD[1-6]. >> >>My test target system is a Celeron with 256MB Ram and an IDE disk; this >>setup fully installs SLES9. The only material change from this to the >>production lab is that the target system in the production lab has a >>SCSI disk and 1GB of ram. -- Steve Glines voice: 978-952-6340 www.is-cs.com fax: 978-952-8524 145 Foster Street cell: 617-549-7274 Littleton MA 01460 I'm a complex person. I have a real and an imaginary part.

3 6

Re: [suse-autoinstall] SLES9 autoinstall hangs at creating initrd
by Durk S. 05 Oct '04

05 Oct '04

Hi there, I've got exactly the same problem with a HP DL360 G3 using a network AutoYaST2 install. The last lines of y2log: 2004-09-30 13:57:50 <1> linux(697) [YCP] Storage.ycp:1573 CheckForLvmRootFs root=$["detected_fs":`ext2, "device":"/dev/cciss/c 0d0p7", "fs_options":$[], "fsid":131, "mount":"/", "nr":7, "region":[516, 16917], "type":`logical, "used_fs":`ext2, "uuid":"7f ca98f4-1cf7-4862-81c0-93866245ea3d"] dev=$["disk":"/dev/cciss/c0d0", "nr":7] 2004-09-30 13:57:50 <1> linux(697) [YCP] Storage.ycp:1576 CheckForLvmRootFs ret=false 2004-09-30 13:57:50 <1> linux(697) [YCP] Misc.ycp:146 WriteYaSTInf($["Keytable":"us.map.gz", "Language":"en_US", "RebootMsg":" 0", "Root":"reboot"]) = Keytable: us.map.gz Language: en_US RebootMsg: 0 Root: reboot 2004-09-30 13:57:50 <1> linux(697) [YCP] Bootloader.ycp:316 Writing bootloader configuration 2004-09-30 13:57:50 <3> linux(697) [libscr] Bootloader.ycp:361 No SCR instance found 2004-09-30 13:57:50 <1> linux(697) [YCP] Initrd.ycp:269 Initrd::Write called, changed: true, list: ["cciss"] 2004-09-30 13:57:50 <3> linux(697) [libscr] Initrd.ycp:294 No SCR instance found2004-09-30 13:57:50 <3> linux(697) [libscr] Initrd.ycp:296 No SCR instance found2004-09-30 13:57:50 <1> linux(697) [YCP] Initrd.ycp:304 Modules [] were added to initrd not using Initrd module 2004-09-30 13:57:50 <3> linux(697) [libscr] Initrd.ycp:313 No SCR instance found2004-09-30 13:57:50 <1> linux(697) [YCP] Initrd.ycp:316 Writing modules cciss 2004-09-30 13:57:50 <3> linux(697) [libscr] Initrd.ycp:317 No SCR instance found2004-09-30 13:57:50 <3> linux(697) [libscr] Initrd.ycp:318 No SCR instance found2004-09-30 13:57:50 <3> linux(697) [libscr] Initrd.ycp:323 No SCR instance found2004-09-30 13:57:50 <3> linux(697) [libscr] Initrd.ycp:326 No SCR instance found2004-09-30 13:57:50 <3> linux(736) [ui] YUI_widgets.cc(createRichText):857 Invalid arguments for the Label RichText: `RichText (`opt (`plainText), nil) 2004-09-30 13:57:50 <3> linux(736) [ui] YUI_widgets.cc(widgetWithId):2426 No widget with `id( `ok_help ) 2004-09-30 13:57:50 <3> linux(736) [libycp] Initrd.ycp:254 No widget with `id( `ok_help ) I hope there's a solution. Durk > Date: Wed, 29 Sep 2004 10:01:15 +0200 > Message-ID: > <CD998562990BEA4D98E5EE624E492B3A5B163E(a)SMCR030V.corp1.ad1.seb.net> > From: <anders.g.karlsson(a)seb.se> > Subject: [suse-autoinstall] SLES9 autoinstall hangs at creating initrd > > > Hi, > > I've run into a problem when doing an autoinstall (SLES9) from a CD that > I created using the YaST2 tools. Everything runs smooth up to the point > where it is "Creating initrd...", at this point the installation just > hangs. I'm trying to install on an HP DL380 G3 with the cciss hardware > raid driver. Anyone has the same experience? > > Regards, > Anders

4 7

SUSE 9.1 and SLES9 autoyast bug
by Dax Kelson 03 Oct '04

03 Oct '04

I have a chrooted postinstall script that works fine on SLES8 and SL9.0 but not SL9.1 and SLES9. The bug is that any changes done to the /etc/password and /etc/shadow files are lost. The two things I have tried: useradd -m -p '$1$J1n.X/QK$hj1vaqARqf.O/RWisMGRn1' visitor ..... echo 'visitor:x:1000:100::/home/visitor:/bin/bash' >> /etc/passwd echo 'visitor:$1$J1n.X/QK$hj1vaqARqf.O/RWisMGRn1:12686:0:99999:7:::' >> /etc/shadow cp -a /etc/skel /home/visitor chown -R visitor /home/visitor chgrp -R users /home/visitor In either case, the commands complete with no errors, but when the system comes up after the install is all finished, I have the following: # ls -al /home total 2 drwxr-xr-x 4 root root 96 Sep 25 12:53 . drwxr-xr-x 22 root root 512 Sep 25 06:52 .. drwxr-xr-x 7 guru users 568 Sep 25 12:53 guru drwxr-xr-x 7 1000 users 568 Sep 25 06:44 visitor ^^^^ Note the how just the UID is listed. This is futher proof that chown command did work correctly in the postinstall script, ie, when chown ran, the visitor account was in the /etc/passwd file. And there is no visitor line in the /etc/password and /etc/shadow file.

2 2

Rules and classes
by tobias.mucke＠de.man-mn.com 30 Sep '04

30 Sep '04

Hi everybody, since SuSE patched a timing problem in linuxrc concerning the delay between loading the kernel module for the network interface card and the network configuration AutoYaST is doing a fine job. In test environment I used until now one XML configuration file for my installation client. On the one hand I want to split up that large file in some smaller ones, on the other hand I want to use rules to generate the configuration file during autoinstallation process. There are two things documented, rules and classes. There is also a hint in the docs that both can be combined. But there aren't any details. I didn't find any advice in the mailing list either. What I am doing now is, that I have a alway true rule in rules.xml which includes a profile called autoyast2_general.xml. In that profile I include all other XML Configuration files with the class tags. Is there no better way? May I set a class directly as a result of a rule in rules.xml? The basic problem is that there is nothing in the docs about that. I didn't even find the class tags there. Don't get me wrong the documentation to AutoYaST is ok and also nice to read, but it is not complete. Last but not least I found a little bug in the docs. On page 27, Example 4.20. Customized Package selection. If you name the selection My.sel the line 6 should look like "=Sel: My" not "=Sel: LSB". Thanks in advance for your advice. Mit freundlichen Grüßen Tobias Mucke -------------------------------------------------------------------------------------------------- MAN Nutzfahrzeuge AG Informationssysteme Organisation (I) Dachauer Straße 667 D-80995 München Tel.: +49 (0) 89 1580 5269 Mail-Adresse: Tobias_Mucke(a)mn.man.de Internet-Adresse: http://www.man-trucks.com -------------------------------------------------------------------------------------------------- This message and any attachments are confidential and may be privileged or otherwise protected from disclosure. If you are not the intended recipient, please telephone or email the sender and delete this message and any attachment from your system. If you are not the intended recipient, you must not copy this message or attachment or disclose the contents to any other person.

1 0

<spooler> values
by Henrik Schmidt 30 Sep '04

30 Sep '04

I want to use lprng instead of cups. What do I use for <spooler></spooler> in my config file. Is it lprng or lpr. Where can I find documentation on this topic. I tried <spooler>lprng</spooler> and its working ok after install from command line with lpr/lpq. BUT kdeprintrc has still PrintSystem=cups instead of lpr. This is causing big trouble while trying to print with kdeprint. It will hang the window which has to be killed. I have to edit kdeprintrc by hand to make it work. Henrik -- Henrik Schmidt Christian-Albrechts-Universitaet zu Kiel Institut fuer Informatik +49 (431) 880 75 - 50 Fax or 43 Phone Olshausenstr. 40 http://www.ks.informatik.uni-kiel.de 24098 Kiel, Germany email: hbs(a)ks.informatik.uni-kiel.de

1 0

yast2 unattended clone
by head＠synex.de 29 Sep '04

29 Sep '04

Hi there, I want to to create a clone of an installation and store it together with the system backup. On recovery the basic system shall be installed according to that clone.xml before the backup is read back. Is there any way to create a clone without any user interaction? Regards, Oliver

1 0

SLES9 autoinstall hangs at creating initrd
by anders.g.karlsson＠seb.se 29 Sep '04

29 Sep '04

Hi, I've run into a problem when doing an autoinstall (SLES9) from a CD that I created using the YaST2 tools. Everything runs smooth up to the point where it is "Creating initrd...", at this point the installation just hangs. I'm trying to install on an HP DL380 G3 with the cciss hardware raid driver. Anyone has the same experience? Regards, Anders

2 1

Choosing kernel
by Antonio Beamud Montero 27 Sep '04

27 Sep '04

Hi all: I want to use a custom kernel when install an station, but Suse 8.0 uses a k_smp kernel... How I can tell autoyast to use other kernel? Thanks -- Antonio Beamud Montero <antonio.beamud(a)linkend.com> Jabber User: farruquit0(a)jabber.org [http://www.jabber.org]

1 0

configure section does not run
by Brad Hudson 24 Sep '04

24 Sep '04

Hi all: I'm booting to an http install and loading an xml file via http. The prepare and install portions of the "Auto-Installation Process" work, but the configure section gets skipped (see auto-installation process in the autoyast.pdf <figure 1.1>). The entire configure portion of the xml file (elb_x345.xml...below) is skipped. Has anyone run into this one before? I apologize for the large paste, but it should help. Brad Paste of elb_x345.xml: <?xml version="1.0"?> <!DOCTYPE profile SYSTEM "/usr/share/autoinstall/dtd/profile.dtd"> <profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <configure> <runlevel> <services config:type="list"> <service> <service_name>alsasound</service_name> <service_status>disable</service_status> </service> <service> <service_name>boot.device-mapper</service_name> <service_status>disable</service_status> </service> <service> <service_name>boot.isapnp</service_name> <service_status>disable</service_status> </service> <service> <service_name>boot.lvm</service_name> <service_status>disable</service_status> </service> <service> <service_name>boot.md</service_name> <service_status>disable</service_status> </service> <service> <service_name>boot.sysctl</service_name> <service_status>enable</service_status> </service> <service> <service_name>isdn</service_name> <service_status>disable</service_status> </service> <service> <service_name>nfs</service_name> <service_status>disable</service_status> </service> <service> <service_name>nfsboot</service_name> <service_status>disable</service_status> </service> <service> <service_name>nscd</service_name> <service_status>disable</service_status> </service> <service> <service_name>portmap</service_name> <service_status>disable</service_status> </service> <service> <service_name>powersaved</service_name> <service_status>disable</service_status> </service> <service> <service_name>slpd</service_name> <service_status>disable</service_status> </service> <service> <service_name>smbfs</service_name> <service_status>disable</service_status> </service> <service> <service_name>network</service_name> <service_status>enable</service_status> </service> <service> <service_name>xdm</service_name> <service_status>enable</service_status> </service> </services> </runlevel> <scripts> <post-scripts config:type="list"> <script> <filename>add_local_modules.pl</filename> <interpreter>perl</interpreter> <location></location> <source><![CDATA[#!/usr/bin/perl -w my $local_modules = "/etc/modprobe.conf.local"; for (my $i=0; $i<6; $i++) { `echo 'alias eth$i e1000' >> $local_modules`; } `echo '' >> $local_modules`; `echo 'options e1000 XsumRX=1,1,1,1,1,1 TxDescriptors=4096,4096,4096,4096,4096,4096 RxDescriptors=4096,4096,4096,4096,4096,4096 Speed=1000,1000,1000,1000,1000,1000 Duplex=2,2,2,2,2,2' >> $local_modules`;]]></source> </script> </post-scripts> <pre-scripts config:type="list"> <script> <filename>avoid_autoyast_boot_loop.sh</filename> <interpreter>shell</interpreter> <location></location> <source><![CDATA[#!/bin/bash /bin/eject ]]></source> </script> </pre-scripts> </scripts> <sysconfig config:type="list"> <sysconfig_entry> <sysconfig_key>SCHED_MAXTIMESLICE</sysconfig_key> <sysconfig_path>/etc/sysconfig/kernel</sysconfig_path> <sysconfig_value>300000</sysconfig_value> </sysconfig_entry> <sysconfig_entry> <sysconfig_key>SCHED_MINTIMESLICE</sysconfig_key> <sysconfig_path>/etc/sysconfig/kernel</sysconfig_path> <sysconfig_value>10000</sysconfig_value> </sysconfig_entry> </sysconfig> <x11> <color_depth config:type="integer">16</color_depth> <configure_x11 config:type="boolean">true</configure_x11> <display_manager>fvwm2</display_manager> <enable_3d config:type="boolean">false</enable_3d> <monitor> <display> <frequency config:type="integer">60</frequency> <height config:type="integer">600</height> <width config:type="integer">800</width> </display> <monitor_device>800X600@60HZ</monitor_device> <monitor_vendor> VESA</monitor_vendor> </monitor> <resolution>800X600</resolution> </x11> </configure> <install> <bootloader> <activate config:type="boolean">false</activate> <global config:type="list"> <global_entry> <key>color</key> <value>white/blue black/light-gray</value> </global_entry> <global_entry> <key>default</key> <value config:type="integer">0</value> </global_entry> <global_entry> <key>timeout</key> <value config:type="integer">8</value> </global_entry> <global_entry> <key>gfxmenu</key> <value>(hd0,1)/message</value> </global_entry> </global> <loader_device>/dev/sda</loader_device> <loader_type>grub</loader_type> <location>mbr</location> <repl_mbr config:type="boolean">false</repl_mbr> <sections config:type="list"> <section config:type="list"> <section_entry> <key>title</key> <value>Linux</value> </section_entry> <section_entry> <key>kernel</key> <value>(hd0,1)/vmlinuz root=/dev/sda3 vga=0x314 selinux=0 splash=silent resume=/dev/sda1 elevator=cfq showopts</value> </section_entry> <section_entry> <key>initrd</key> <value>(hd0,1)/initrd</value> </section_entry> </section> <section config:type="list"> <section_entry> <key>title</key> <value>Floppy</value> </section_entry> <section_entry> <key>root</key> <value>(fd0)</value> </section_entry> <section_entry> <key>chainloader</key> <value>+1</value> </section_entry> </section> <section config:type="list"> <section_entry> <key>title</key> <value>Failsafe</value> </section_entry> <section_entry> <key>kernel</key> <value>(hd0,1)/vmlinuz root=/dev/sda3 showopts ide=nodma apm=off acpi=off vga=normal noresume selinux=0 barrier=off nosmp noapic maxcpus=0 3</value> </section_entry> <section_entry> <key>initrd</key> <value>(hd0,1)/initrd</value> </section_entry> </section> </sections> </bootloader> <general> <clock> <hwclock>localtime</hwclock> <timezone>US/Central</timezone> </clock> <keyboard> <keymap>english-us</keymap> </keyboard> <language>en_US</language> <mode> <confirm config:type="boolean">false</confirm> <forceboot config:type="boolean">false</forceboot> </mode> <mouse> <id>22_exps2</id> </mouse> </general> <partitioning config:type="list"> <drive> <device>/dev/sda</device> <initialize config:type="boolean">true</initialize> <partitions config:type="list"> <partition> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <loop_fs config:type="boolean">false</loop_fs> <mount>swap</mount> <partition_id config:type="integer">130</partition_id> <partition_type>primary</partition_type> <size>2G</size> </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <fstopt>data=journal,acl</fstopt> <loop_fs config:type="boolean">false</loop_fs> <mount>/boot</mount> <mountby config:type="symbol">device</mountby> <noauto config:type="boolean">false</noauto> <partition_id config:type="integer">131</partition_id> <partition_type>primary</partition_type> <size>128M</size> </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <fstopt>data=journal,acl</fstopt> <loop_fs config:type="boolean">false</loop_fs> <mount>/</mount> <mountby config:type="symbol">device</mountby> <noauto config:type="boolean">false</noauto> <partition_id config:type="integer">131</partition_id> <partition_type>primary</partition_type> <size>4G</size> </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <fstopt>data=journal,acl</fstopt> <loop_fs config:type="boolean">false</loop_fs> <mount>/var</mount> <mountby config:type="symbol">device</mountby> <noauto config:type="boolean">false</noauto> <partition_id config:type="integer">131</partition_id> <size>8G</size> </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <fstopt>data=journal,acl</fstopt> <loop_fs config:type="boolean">false</loop_fs> <mount>/usr</mount> <mountby config:type="symbol">device</mountby> <noauto config:type="boolean">false</noauto> <partition_id config:type="integer">131</partition_id> <size>8G</size> </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <fstopt>data=journal,acl</fstopt> <loop_fs config:type="boolean">false</loop_fs> <mount>/opt</mount> <mountby config:type="symbol">device</mountby> <noauto config:type="boolean">false</noauto> <partition_id config:type="integer">131</partition_id> <size>max</size> </partition> </partitions> <use>all</use> </drive> </partitioning> <report> <errors> <log config:type="boolean">true</log> <show config:type="boolean">true</show> <timeout config:type="integer">10</timeout> </errors> <messages> <log config:type="boolean">true</log> <show config:type="boolean">false</show> <timeout config:type="integer">10</timeout> </messages> <warnings> <log config:type="boolean">true</log> <show config:type="boolean">true</show> <timeout config:type="integer">10</timeout> </warnings> <yesno_messages> <log config:type="boolean">true</log> <show config:type="boolean">true</show> <timeout config:type="integer">10</timeout> </yesno_messages> </report> <software> <addons config:type="list"> <addon>Basis-Sound</addon> <addon>SuSE-Documentation</addon> <addon>Various-Tools</addon> <addon>WBEM</addon> <addon>X11</addon> <addon>YaST2</addon> <addon>analyze</addon> <addon>HA</addon> <addon>Kde-Desktop</addon> <addon>Linux-Tools</addon> <addon>Base-System</addon> </addons> <base>default</base> </software> </install> </profile>

1 0

suse 9.1 Pro, rebuild distro with updates
by jan terje tønnessen 24 Sep '04

24 Sep '04

Hi ! I have an autoyast that works fine, but I would like to include a snapshot of the updates/patches in my installation tree. Anybody knows where to store updates and which files to update (scripts to run) to get the updates/patches 'active'. Br /Jan Terje

2 1

Re: [suse-autoinstall] PXE install fails with SCSI disks
by Anas Nashif 23 Sep '04

23 Sep '04

Steve, I asked you for more information but I got no answer to the questions below. Could you provide some more information about where it hangs? Anas Anas Nashif wrote: > This is indeed strange. Where does the installation exactly stop. In > YaST? In linuxrc? If in YaST, can you send me the log files from > /var/log/YaST2/ > > There should be no difference when installaing over network, same files > are used so I do not see why this is failing. > > Anas > > Steve Glines wrote: > >> suse.root is the initrd file talen from boot/loader on CD1. >> >> SG >> >> Anas Nashif wrote: >> >> >>> >>> Steve Glines wrote: >>> >>> >>>> I’m building a PXE install lab for SUSE and other flavors of Linux. >>>> >>>> The DHCP and tftp servers are working. Note: I can fully install Red >>>> Hat >>>> from this lab but SUSE (SLES9 rc5) shows the following symptoms: >>>> >>>> 1. a cdrom install on the target system runs to completion in >>>> graphics >>>> mode. System is an HP PC with SCSI disk. >>>> 2. PXE install runs in non X-window mode (text) and fails to load >>>> scsi >>>> controllers – cannot find any disks. Fails even when modules are >>>> manually added. >>>> >>>> Here is the content of /tftpboot/pxelinux.cfg/default: >>>> >>>> default suse >>>> prompt 1 >>>> display boot.msg >>>> timeout 200 >>>> >>>> label redhat >>>> kernel redhat.kernel >>>> append initrd=redhat.root ramdisk_size=65536 >>>> >>>> label suse >>>> kernel suse.kernel >>>> append initrd=suse.root ramdisk_size=65536\ >>>> install=http://10.0.3.11/suse/CD1/ >>> >>> >>> >>> What is suse.root exactly? >>> >>> Btw, To get graphical installer, you need to add vga=791 or something >>> similar. >>> >>> Anas >>> >> >>

2 2

RE: [suse-autoinstall] What tools are available to help with remo te installs of headless machines.
by Connector Email 23 Sep '04

23 Sep '04

Ssh ;) -----Original Message----- From: Leendert Meyer [mailto:leen.meyer@home.nl] Sent: Thursday, September 23, 2004 1:49 PM To: suse-autoinstall(a)suse.com Subject: Re: [suse-autoinstall] What tools are available to help with remote installs of headless machines. On Thursday 23 September 2004 21:13, Colin Murphy wrote: > This is purely from the point of view of wanting to 'play' with some of the > machines I get given. All the machines will be different, different > hardware, different resources, different needs. > > I want to do remote installs, using vnc, on headless machines. I have tried > this feature out a little on machines that have keyboard and display using > local and network installation media and being able to control an install > from the comfort of my own desk was a great boon. I would now like to be > able to do installs on machines where I just plug in a power and network > cable and floppy of CD. > > What I really want is a way to start an installation with the further > option 'vnc=1 vncpassword=whatever' passed as the default install option, > using either a floppy or CD. > > Are there any tools to help me build such boot installation media? Install the package 'autoyast2'. Docs are in /usr/share/docs/packages/autoyast2 Run YaST from 'yast autoyast'. Here's a (partial but working) GRUB menu.lst that I used to install SuSE Linux 9.1: #dhcp bootp gfxmenu (nd)/9.1/message color white/blue black/light-gray default 2 timeout 8 title Installation - Automatic with SSH kernel (nd)/9.1/linux insmod=tulip UseSSH=1 SSHPassword=123 autoyast=http://10.0.0.1/pub/suse/profiles/ install=http://10.0.0.1/pub/suse/i386/9.1 vga=0x31A splash=silent showopts initrd (nd)/9.1/initrd (Kmail wrapped the long line starting with 'kernel (nd)/... into 3 lines). You need to install tftpboot on the server, copy boot/loader/{linux,initrd} to tftpboot/9.1/. Boot the client via GRUB with previous menu.lst or with a GRUB boot floppy with prior menu.lst on it. See http://www.suse.de/~nashif/autoinstall/ for a GRUB bootfloppy and instructions. BTW, installing remotely can be a tricky task if the boot process fails. Unless there is someone on the other side in case of boot failure, or you have physical access to the 'remote' client, you're pretty much lost in such a case (I was). 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

What tools are available to help with remote installs of headless machines.
by Colin Murphy 23 Sep '04

23 Sep '04

This is purely from the point of view of wanting to 'play' with some of the machines I get given. All the machines will be different, different hardware, different resources, different needs. I want to do remote installs, using vnc, on headless machines. I have tried this feature out a little on machines that have keyboard and display using local and network installation media and being able to control an install from the comfort of my own desk was a great boon. I would now like to be able to do installs on machines where I just plug in a power and network cable and floppy of CD. What I really want is a way to start an installation with the further option 'vnc=1 vncpassword=whatever' passed as the default install option, using either a floppy or CD. Are there any tools to help me build such boot installation media? Thanks on advance. -- Colin Murphy - A man for all seasons but I especially like pepper.

2 1

Installation Server and CD Creation
by Morten K. Poulsen 23 Sep '04

23 Sep '04

Hi list, I am not sure this is the list to rant about the "Installation Server" YaST module, but here goes: I have installed SLES 9 (RC5 - I was told that it was the GM) on a host and want to make a CD for auto-installation. I did that with SLES 8 and it was a mess because of "multiple installation sources." With SLES 8 i ended up dropping SLES and just using UnitedLinux plus my own packages. OK, now on to the problems I have with SLES 9. a) I have tried different combinations of packages (CDs) in a single or different repositories. You can see the directory listings at the bottom of this mail (appendix A). 1) Both SLES and CORE - one package repository First I tried making one (Installation Server -> Change -> Add -> Source Name: "all9" -> [X] Use ISO Images Instead of CDs -> select each of the six ISOs) with both SLES 9 and CORE 9. I am able to select this in Software Source Media (it identifies itself as "SUSE SLES Version 9"), but I am unable to install any packages from it. Only the installed packaged are shown in Install and Remove Software. 2) Only SLES Then I tried making a repository with only the SLES CD (#1). I used the same procedure as above, but called it "sles9" and only selected the first ISO. When I select it in Software Source Media (it also identifies itself as "SUSE SLES Version 9"), I get the exact same result as before: No installable packages. 3) Only CORE Then I tried making a repository with only the CORE CDs (#2-6). I used the same procedure again, and called it "core9". When I select it in Software Source Media (it identifies itself as "SUSE CORE Version 9"), I am able to install packages from it. But - obviously - I can only install the CORE packages. 4) Both SLES and CORE - two different package repositories If I select both the package repository that I named "sles9" and the one I named "core9", I am still able to install the CORE packages, but still not the SLES packages. The result is the same, no matter which is first in the Software Source Media list. b) When I use the CD Creator YaST module, I get an "Error while writing settings" at "Saving CD Creator Configuration," no files are copied to the selected directory and no ISO file is created. This is the same, no matter if I select Packages by "Package Manager" or "AutoYaST Control File," and no matter if I select CORE, SLES or both as package source. I have tried to locate online documentation about this, but so far I haven't found any. Am I looking in the wrong places? I hope someone can help, or tell me where to go looking for help about this, as I would like to get started with using SLES 9 in our production environment. Best regards, Morten Appendix (I guess this mail is getting long) A) 1) mopo@flimmer-new:~> find all9/ -type d all9/ all9/yast all9/SUSE-CORE-Version-9 all9/SUSE-CORE-Version-9/CD1 all9/SUSE-CORE-Version-9/CD1/suse all9/SUSE-CORE-Version-9/CD1/suse/i586 all9/SUSE-CORE-Version-9/CD1/suse/i686 all9/SUSE-CORE-Version-9/CD1/suse/setup all9/SUSE-CORE-Version-9/CD1/suse/setup/descr all9/SUSE-CORE-Version-9/CD1/suse/noarch all9/SUSE-CORE-Version-9/CD1/media.1 all9/SUSE-CORE-Version-9/CD2 all9/SUSE-CORE-Version-9/CD2/suse all9/SUSE-CORE-Version-9/CD2/suse/i586 all9/SUSE-CORE-Version-9/CD2/suse/i686 all9/SUSE-CORE-Version-9/CD2/suse/noarch all9/SUSE-CORE-Version-9/CD2/media.2 all9/SUSE-CORE-Version-9/CD3 all9/SUSE-CORE-Version-9/CD3/suse all9/SUSE-CORE-Version-9/CD3/suse/src all9/SUSE-CORE-Version-9/CD3/suse/i586 all9/SUSE-CORE-Version-9/CD3/suse/i686 all9/SUSE-CORE-Version-9/CD3/suse/noarch all9/SUSE-CORE-Version-9/CD3/media.3 all9/SUSE-CORE-Version-9/CD4 all9/SUSE-CORE-Version-9/CD4/suse all9/SUSE-CORE-Version-9/CD4/suse/src all9/SUSE-CORE-Version-9/CD4/suse/nosrc all9/SUSE-CORE-Version-9/CD4/media.4 all9/SUSE-CORE-Version-9/CD5 all9/SUSE-CORE-Version-9/CD5/suse all9/SUSE-CORE-Version-9/CD5/suse/src all9/SUSE-CORE-Version-9/CD5/suse/nosrc all9/SUSE-CORE-Version-9/CD5/media.5 all9/SUSE-SLES-Version-9 all9/SUSE-SLES-Version-9/CD1 all9/SUSE-SLES-Version-9/CD1/boot all9/SUSE-SLES-Version-9/CD1/boot/loader all9/SUSE-SLES-Version-9/CD1/docu all9/SUSE-SLES-Version-9/CD1/docu/de all9/SUSE-SLES-Version-9/CD1/docu/en all9/SUSE-SLES-Version-9/CD1/docu/es all9/SUSE-SLES-Version-9/CD1/docu/fr all9/SUSE-SLES-Version-9/CD1/docu/ja all9/SUSE-SLES-Version-9/CD1/docu/it all9/SUSE-SLES-Version-9/CD1/docu/ko all9/SUSE-SLES-Version-9/CD1/docu/HOWTOs all9/SUSE-SLES-Version-9/CD1/docu/pt_BR all9/SUSE-SLES-Version-9/CD1/docu/zh_CN all9/SUSE-SLES-Version-9/CD1/suse all9/SUSE-SLES-Version-9/CD1/suse/src all9/SUSE-SLES-Version-9/CD1/suse/i586 all9/SUSE-SLES-Version-9/CD1/suse/nosrc all9/SUSE-SLES-Version-9/CD1/suse/setup all9/SUSE-SLES-Version-9/CD1/suse/setup/descr all9/SUSE-SLES-Version-9/CD1/suse/noarch all9/SUSE-SLES-Version-9/CD1/yast all9/SUSE-SLES-Version-9/CD1/yast/core9 all9/SUSE-SLES-Version-9/CD1/yast/core9/suse all9/SUSE-SLES-Version-9/CD1/yast/core9/suse/setup all9/SUSE-SLES-Version-9/CD1/yast/core9/suse/setup/descr all9/SUSE-SLES-Version-9/CD1/yast/core9/media.1 all9/SUSE-SLES-Version-9/CD1/dosutils all9/SUSE-SLES-Version-9/CD1/dosutils/lfn all9/SUSE-SLES-Version-9/CD1/dosutils/ext2tool all9/SUSE-SLES-Version-9/CD1/dosutils/ext2tool/src all9/SUSE-SLES-Version-9/CD1/dosutils/ext2tool/sys all9/SUSE-SLES-Version-9/CD1/dosutils/ext2tool/linux all9/SUSE-SLES-Version-9/CD1/dosutils/ext2tool/ext2fs all9/SUSE-SLES-Version-9/CD1/dosutils/fips all9/SUSE-SLES-Version-9/CD1/dosutils/fips/fips15 all9/SUSE-SLES-Version-9/CD1/dosutils/fips/fips15/restorrb all9/SUSE-SLES-Version-9/CD1/dosutils/fips/fips15/source all9/SUSE-SLES-Version-9/CD1/dosutils/fips/fips20 all9/SUSE-SLES-Version-9/CD1/dosutils/fips/fips20/restorrb all9/SUSE-SLES-Version-9/CD1/dosutils/fips/fips20/source all9/SUSE-SLES-Version-9/CD1/dosutils/gzip all9/SUSE-SLES-Version-9/CD1/dosutils/rawrite all9/SUSE-SLES-Version-9/CD1/dosutils/putty all9/SUSE-SLES-Version-9/CD1/dosutils/untgz all9/SUSE-SLES-Version-9/CD1/dosutils/loadlin all9/SUSE-SLES-Version-9/CD1/dosutils/loadlin/doc all9/SUSE-SLES-Version-9/CD1/dosutils/loadlin/src all9/SUSE-SLES-Version-9/CD1/dosutils/dparam all9/SUSE-SLES-Version-9/CD1/dosutils/zipzp715 all9/SUSE-SLES-Version-9/CD1/dosutils/ltools all9/SUSE-SLES-Version-9/CD1/dosutils/gtar109 all9/SUSE-SLES-Version-9/CD1/dosutils/weirdx all9/SUSE-SLES-Version-9/CD1/dosutils/weirdx/config all9/SUSE-SLES-Version-9/CD1/dosutils/xfs186 all9/SUSE-SLES-Version-9/CD1/dosutils/tightvnc all9/SUSE-SLES-Version-9/CD1/dosutils/xfs32-11 all9/SUSE-SLES-Version-9/CD1/dosutils/pkunzip all9/SUSE-SLES-Version-9/CD1/dosutils/rawwritewin all9/SUSE-SLES-Version-9/CD1/dosutils/install all9/SUSE-SLES-Version-9/CD1/media.1 all9/SUSE-SLES-Version-9/CD1/SLES-LICENSE all9/SUSE-SLES-Version-9/CD1/SLES-LICENSE/de all9/SUSE-SLES-Version-9/CD1/SLES-LICENSE/cz all9/SUSE-SLES-Version-9/CD1/SLES-LICENSE/es all9/SUSE-SLES-Version-9/CD1/SLES-LICENSE/fr all9/SUSE-SLES-Version-9/CD1/SLES-LICENSE/it all9/SUSE-SLES-Version-9/CD1/SLES-LICENSE/nl all9/SUSE-SLES-Version-9/CD1/SLES-LICENSE/pl all9/SUSE-SLES-Version-9/CD1/SLES-LICENSE/en_US all9/SUSE-SLES-Version-9/CD1/SLES-LICENSE/pt_BR mopo@flimmer-new:~> ls -l all9/ |cut -b 24- 28 2004-09-20 13:08 boot -> SUSE-SLES-Version-9/CD1/boot 31 2004-09-20 13:08 content -> SUSE-SLES-Version-9/CD1/content 35 2004-09-20 13:08 control.xml -> SUSE-SLES-Version-9/CD1/control.xml 31 2004-09-20 13:08 media.1 -> SUSE-SLES-Version-9/CD1/media.1 168 2004-09-20 13:19 SUSE-CORE-Version-9 72 2004-09-20 13:08 SUSE-SLES-Version-9 104 2004-09-20 13:23 yast 2) mopo@flimmer-new:~> find sles9/ -type d sles9/ sles9/yast sles9/SUSE-SLES-Version-9 sles9/SUSE-SLES-Version-9/CD1 sles9/SUSE-SLES-Version-9/CD1/boot sles9/SUSE-SLES-Version-9/CD1/boot/loader sles9/SUSE-SLES-Version-9/CD1/docu sles9/SUSE-SLES-Version-9/CD1/docu/de sles9/SUSE-SLES-Version-9/CD1/docu/en sles9/SUSE-SLES-Version-9/CD1/docu/es sles9/SUSE-SLES-Version-9/CD1/docu/fr sles9/SUSE-SLES-Version-9/CD1/docu/ja sles9/SUSE-SLES-Version-9/CD1/docu/it sles9/SUSE-SLES-Version-9/CD1/docu/ko sles9/SUSE-SLES-Version-9/CD1/docu/HOWTOs sles9/SUSE-SLES-Version-9/CD1/docu/pt_BR sles9/SUSE-SLES-Version-9/CD1/docu/zh_CN sles9/SUSE-SLES-Version-9/CD1/suse sles9/SUSE-SLES-Version-9/CD1/suse/src sles9/SUSE-SLES-Version-9/CD1/suse/i586 sles9/SUSE-SLES-Version-9/CD1/suse/nosrc sles9/SUSE-SLES-Version-9/CD1/suse/setup sles9/SUSE-SLES-Version-9/CD1/suse/setup/descr sles9/SUSE-SLES-Version-9/CD1/suse/noarch sles9/SUSE-SLES-Version-9/CD1/yast sles9/SUSE-SLES-Version-9/CD1/yast/core9 sles9/SUSE-SLES-Version-9/CD1/yast/core9/suse sles9/SUSE-SLES-Version-9/CD1/yast/core9/suse/setup sles9/SUSE-SLES-Version-9/CD1/yast/core9/suse/setup/descr sles9/SUSE-SLES-Version-9/CD1/yast/core9/media.1 sles9/SUSE-SLES-Version-9/CD1/dosutils sles9/SUSE-SLES-Version-9/CD1/dosutils/lfn sles9/SUSE-SLES-Version-9/CD1/dosutils/ext2tool sles9/SUSE-SLES-Version-9/CD1/dosutils/ext2tool/src sles9/SUSE-SLES-Version-9/CD1/dosutils/ext2tool/sys sles9/SUSE-SLES-Version-9/CD1/dosutils/ext2tool/linux sles9/SUSE-SLES-Version-9/CD1/dosutils/ext2tool/ext2fs sles9/SUSE-SLES-Version-9/CD1/dosutils/fips sles9/SUSE-SLES-Version-9/CD1/dosutils/fips/fips15 sles9/SUSE-SLES-Version-9/CD1/dosutils/fips/fips15/restorrb sles9/SUSE-SLES-Version-9/CD1/dosutils/fips/fips15/source sles9/SUSE-SLES-Version-9/CD1/dosutils/fips/fips20 sles9/SUSE-SLES-Version-9/CD1/dosutils/fips/fips20/restorrb sles9/SUSE-SLES-Version-9/CD1/dosutils/fips/fips20/source sles9/SUSE-SLES-Version-9/CD1/dosutils/gzip sles9/SUSE-SLES-Version-9/CD1/dosutils/rawrite sles9/SUSE-SLES-Version-9/CD1/dosutils/putty sles9/SUSE-SLES-Version-9/CD1/dosutils/untgz sles9/SUSE-SLES-Version-9/CD1/dosutils/loadlin sles9/SUSE-SLES-Version-9/CD1/dosutils/loadlin/doc sles9/SUSE-SLES-Version-9/CD1/dosutils/loadlin/src sles9/SUSE-SLES-Version-9/CD1/dosutils/dparam sles9/SUSE-SLES-Version-9/CD1/dosutils/zipzp715 sles9/SUSE-SLES-Version-9/CD1/dosutils/ltools sles9/SUSE-SLES-Version-9/CD1/dosutils/gtar109 sles9/SUSE-SLES-Version-9/CD1/dosutils/weirdx sles9/SUSE-SLES-Version-9/CD1/dosutils/weirdx/config sles9/SUSE-SLES-Version-9/CD1/dosutils/xfs186 sles9/SUSE-SLES-Version-9/CD1/dosutils/tightvnc sles9/SUSE-SLES-Version-9/CD1/dosutils/xfs32-11 sles9/SUSE-SLES-Version-9/CD1/dosutils/pkunzip sles9/SUSE-SLES-Version-9/CD1/dosutils/rawwritewin sles9/SUSE-SLES-Version-9/CD1/dosutils/install sles9/SUSE-SLES-Version-9/CD1/media.1 sles9/SUSE-SLES-Version-9/CD1/SLES-LICENSE sles9/SUSE-SLES-Version-9/CD1/SLES-LICENSE/de sles9/SUSE-SLES-Version-9/CD1/SLES-LICENSE/cz sles9/SUSE-SLES-Version-9/CD1/SLES-LICENSE/es sles9/SUSE-SLES-Version-9/CD1/SLES-LICENSE/fr sles9/SUSE-SLES-Version-9/CD1/SLES-LICENSE/it sles9/SUSE-SLES-Version-9/CD1/SLES-LICENSE/nl sles9/SUSE-SLES-Version-9/CD1/SLES-LICENSE/pl sles9/SUSE-SLES-Version-9/CD1/SLES-LICENSE/en_US sles9/SUSE-SLES-Version-9/CD1/SLES-LICENSE/pt_BR mopo@flimmer-new:~> ls -l sles9/ |cut -b 24- 28 2004-09-20 13:34 boot -> SUSE-SLES-Version-9/CD1/boot 31 2004-09-20 13:34 content -> SUSE-SLES-Version-9/CD1/content 35 2004-09-20 13:34 control.xml -> SUSE-SLES-Version-9/CD1/control.xml 31 2004-09-20 13:34 media.1 -> SUSE-SLES-Version-9/CD1/media.1 72 2004-09-20 13:34 SUSE-SLES-Version-9 48 2004-09-20 13:34 yast 3) mopo@flimmer-new:~> find core9/ -type d core9/ core9/suse core9/suse/src core9/suse/i586 core9/suse/i686 core9/suse/nosrc core9/suse/setup core9/suse/setup/descr core9/suse/noarch core9/media.1 core9/media.2 core9/media.3 core9/media.4 core9/media.5 mopo@flimmer-new:~> ls -l core9/ |cut -b 24- 3906522 2004-07-02 20:19 ARCHIVES.gz 3734181 2004-07-02 20:17 ChangeLog 604 2004-07-02 20:15 content 31 2004-07-02 20:18 directory.yast 23022 2004-07-02 20:21 INDEX.gz 42719 2004-07-02 20:19 ls-lR.gz 128 2004-07-02 20:18 media.1 96 2004-07-02 20:19 media.2 96 2004-07-02 20:19 media.3 96 2004-07-02 20:19 media.4 96 2004-07-02 20:19 media.5 192 2004-07-02 20:15 suse -- Morten K. Poulsen <lists.suse.com(a)afdelingp.dk> http://www.afdelingp.dk/

2 2

Re: Re: [suse-autoinstall] Controlfile + Rules doesn't work
by Kai Moeller 23 Sep '04

23 Sep '04

Hi there, Here a supplement to my privious Mail in the morning: I'm sure that the MAC Address of my Ethernet Adapter is the right on and It is only 1 Ethernet Adapter in this Machine! But it didn't work anymore :( Is it possible do define a default rule/profile for a machine where no rules defined? Another question (presupposed the rules.xml is running soon :-) Howto do a based config combined with a Machine cut preconfig for every machine with another hardware and another Hostnames and so on... I'm sorry, but theres not enough documentation about the rules and classes, the section is very short. best regards Kai Möller

1 0

SLES8: No reboot after autoyast
by Oliver Schwabedissen 23 Sep '04

23 Sep '04

Hi, I'm also having a reboot problem, this one is with SLES8. Up to now all installations went fine: after autoyast completes the system does a reboot and executes my own startup scripts in rc3.d to finish the installation. Yesterday I installed a similar machine (HP DL380 G3, other machines were IBM x235, x360 and HP ML370/570), but after autoyast finished the server didn't reboot but entered runlevel 5. This is due to a bug in autoyast. We specify runlevel 3 in autoyast.xml and then configure X11, but this sets the runlevel to 5 in /etc/inittab. So as a workaround (suggested by SuSE support) we added the "3" as a kernel parameter for the bootloader to force the machine to runlevel 3 (and then execute the startup script). All the other machines did a reboot after autoyast installation finished, this one doesn't... What can be the reason? Only differences between installations are in network configuration (ip address, nic modules etc.) and partitioning (1 or 2 RAIDs). All machines are configured with forceboot=false and reboot=false in the general section. AFAIK the reboot parameter is only for a reboot before the first initial reboot takes place (and doesn't work at all) and forceboot is documented nowhere... Oliver -- +++ GMX DSL Premiumtarife 3 Monate gratis* + WLAN-Router 0,- EUR* +++ Clevere DSL-Nutzer wechseln jetzt zu GMX: http://www.gmx.net/de/go/dsl

2 6

Antwort: Re: [suse-autoinstall] Controlfile + Rules doesn't work
by Kai Moeller 23 Sep '04

23 Sep '04

>Hi, > >In the rules you have to use lower case mac address. > >Anas Hi, in your documentatin you wrote in an example to use it uppercase! (ie. rules and classes > system attributes) But I've tried it upper and lowercase but it still doesn't work! Same failure... same message to me... I should enter the full path to my profile! Greetings Kai Moeller

1 0

Controlfile + Rules doesn't work
by Kai Moeller 23 Sep '04

23 Sep '04

Hi there, after working without any rules or templates, I would create some rules to merge my autoyast profile for different workstations. My Profile directory is: '/pub/suse/9.1/autoyast/' ... I starts the autoyast routine on the commandline without a speficy profile (Autoyast=nfs://10.xxx.xxx.62/pub/suse/9.1/autoyast/) my rules.xml is in '/pub/suse/9.1/autoyast/rules/rules.xml' and contains following lines: <CTYPE autoinstall SYSTEM "/usr/share/autoinstall/dtd/rules.dtd"> <autoinstall xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config ="http://www.suse.com/1.0/configns"> <rules config:type="list"> <rule> <mac> <match>00B0D0E25C86</match> <match_type>exact</match_type> </mac> <result> <profile>km2.xml</profile> <continue config:type="boolean">false</continue> </result> </rule> </rules> </autoinstall> the needed profile is in '/pub/suse/9.1/autoyast/' and is should be accessable to any user! Before AutoYast starts parsing my Controlfile, it receive the rules.xml and want to receive my controlfile to merge it. There's my problem, at this stage autoyast tells me, it couldn't find my profile and i should enter the fullpath to the controlfile. But I'm sure, the controlfile is in '/pub/suse/9.1/autoyast/' with filename "km2.xml" if I symlink my HexIP to my controlfile it works fine! Any Solutions? Best regards Kai Moeller

2 1

sles9 and autoyast boot disks
by Brad Hudson 23 Sep '04

23 Sep '04

does anyone have any step through procedures on creating a boot disk & info file on a floppy in order to perform an autoyast installation via an nfs server (install=nfs://<server>/sles9 autoyast=nfs://<server>/sles9/profiles/<profile>)? i have not found this info in the autoyast.pdf or the html docs. i have a need to perform repetitive manufacturing of a standard config. any info would be of value. bh

2 1

SLES9 hangs at Creating initrd
by Aaron McSorley 23 Sep '04

23 Sep '04

SLES9 AMD64 manual network PXE install hangs at "Finishing Basic Installation" => "Install boot manager" -> "Creating initrd ..." Does this ring any bells? If not let me know and I'll provide more information. This is short because I'm out of time Thanks -Aaron

2 1

[suse-autoinstall] First Baby Steps - 9.1 Pro and auto Yast.
by Ted Hilts 22 Sep '04

22 Sep '04

I included [SLE] because there were several people on that listing that were trying to help me on my auto - install question. I've got the full box set for SuSe 9.1 pro. When I do this installation I want to do it in a way that can automatically create the same installation on other machines. I have been reading the box set manuals (but nothing found as a step by step guide for auto install). I acquired the .pdf file for auto-Yast from a SuSe site for auto installation thanks to those on [SLE]. I think auto-Yast is an alternate name for YAST2 but it could be an option in regular Yast that evokes YAST2? I am a bit confused on this as I only used YAST (text version) several years ago.. What I am looking for is the first few steps using these cd-roms (in the box set) to install SuSe 9.1 Pro while also ensuring that the final product will be suitable for building SuSe 9.1 Pro in the same way on other machines having different hard drives and format types as well as different CPU, chip set support, audio, video drivers, host name, IP Address and that sort of thing. (I realize that I have to check out the hardware compatibility issues first and I've done that). Can someone with experience on auto installations provide me with these first few installation steps and alert me to any problems that they know will probably arise. Thank you in advance for your kindness in this regard -- also I will be several days in responding. Ted

1 0

unknown partition table error
by Stephens, Bill {PBSG} 21 Sep '04

21 Sep '04

I'm testing installs on a Dell 1750 server no raid, single hard drive. About 1 in 5 times I'm getting an error while attempting to format the swap partition indicating that the installer can't format the partition. When I Hit alt+F4, I see an errorindicating "sda: unknown partition table". If I reboot, 95% of the time the system formats installs fine. Any ideas what might be going on? Thanks

1 0

Autologin KDE after Installation complete...
by Kai Moeller 21 Sep '04

21 Sep '04

Hi there! My ControlFile + Unattended Setup works great... But is it possible to autologin in KDE after setup is completed? I tried to copy my own kdmrc to /etc/opt/kde3/share/config/kdm/kdmrc via post-install script, but than my login doesn't work anymore! Any other solutions? best regards Kai Moeller

1 0

Reboot After Install
by Stephens, Bill {PBSG} 21 Sep '04

21 Sep '04

My system isn't rebooting after the install completes. It's still running at runlevel 5, with build networking definitions started. I need to reboot the system after the build process is complete to ensure it starts up with a completely clean environment. How do I force a reboot after installation and customization completes?

2 1

Re: [suse-autoinstall] Install CD
by Marcin Kurc 17 Sep '04

17 Sep '04

take the boot directory from the first cd and run the folowing command mkisofs -R -r -J -b boot/loader/isolinux.bin -no-emul-boot -boot-load-size 4 -boot-info-table -no-bak -o ../suse_boot.iso . I'm not sure about 9.1, but isn't there a some kind of miniboot iso shipped with it? >>>Stephens, Bill {PBSG} <Bill.Stephens(a)pbsg.com> 09/17/04 11:55 am >>> In the 9.0 yast2 autoinstallation xml gui, there was a utility to create a stripped down bootable installation CD. That option seems to be gone from 9.1 :-<. I would like to create a stripped down CD Image. I've tried deleting the suse directory from the generic install cd 1, but then the cd won't boot due to a checksum error. How do I go about creating a stripped down bootable install CD? All my source files are on an NFS mount (probably moving to an FTP install). Thanks, Bill

2 1

Install CD
by Stephens, Bill {PBSG} 17 Sep '04

17 Sep '04

In the 9.0 yast2 autoinstallation xml gui, there was a utility to create a stripped down bootable installation CD. That option seems to be gone from 9.1 :-<. I would like to create a stripped down CD Image. I've tried deleting the suse directory from the generic install cd 1, but then the cd won't boot due to a checksum error. How do I go about creating a stripped down bootable install CD? All my source files are on an NFS mount (probably moving to an FTP install). Thanks, Bill

1 0

extend /usr
by Patrick B. O'Brien 17 Sep '04

17 Sep '04

How are you SuseUsers extending O/S filesystems like /usr? /dev/dasda1 / ext3 defaults 1 1 /dev/dasdb1 /usr ext3 defaults 1 2 /dev/dasdc1 swap swap pri=42 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0 proc /proc proc defaults 0 0

1 0

Online update
by Patrick B. O'Brien 16 Sep '04

16 Sep '04

While doing an online update on my Suse 8.0 Box I'm getting the following screen. Not sure where or what this screen wants? I tried my www.portal.suse.com user and password, but no joy? Authorization ? ? ? ??server, fetch the ? ? Enter the registration data. ? ??????????????? ? ??files, and install ? ? ?Registration data?????????? ? ? ??the patches. ? ? ? Code: ? ? ??????????????? ? ?? Manual Update ? ? ? ???????????????????????? ? ? ? ? ??will display all ? ? ? Password: ? ? ? ? ??available patches ? ? ? ???????????????? ? ? ??????????????? ? ??and you can choose ? ? ???????????????????????????? ? ? ??which patches should? ? [x] Keep registration data ? e?????????????? ? ??be installed. ? ? [Login][Abort] ? [Expert]? ? ??Information about ? ??????????????????????????

1 0

RE: [suse-autoinstall] run update from the command line
by Ness, Todd 16 Sep '04

16 Sep '04

Online_update --help Pick the options that work best for you -----Original Message----- From: Patrick B. O'Brien [mailto:pobrien@doit.nv.gov] Sent: Thursday, September 16, 2004 10:53 AM To: suse-autoinstall(a)suse.com Subject: [suse-autoinstall] run update from the command line I use YAST2 to update my Suse 8.0 Box. I want to update from the command line too. What command do I run to do O/S updates from the command line? Tia -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

run update from the command line
by Patrick B. O'Brien 16 Sep '04

16 Sep '04

I use YAST2 to update my Suse 8.0 Box. I want to update from the command line too. What command do I run to do O/S updates from the command line? Tia

1 0

Re: [suse-autoinstall] SuSE 9.1 network interface naming schema problem
by fschuett 16 Sep '04

16 Sep '04

Am Mittwoch, 15. September 2004 17:16 schrieb Mike Rose: > Hi, > > We just disliked the mac address naming convention so did this in our > post_install script (and a few other things): > Thank you both for your help. Bye, Frank Schütte > On Wed, 15 Sep 2004, Jonathon M. Robison wrote: > > The old naming schema can be restored manually. Just re-name the files. > > I cannot recall if you have to edit anything in /etc/sysconfig/hardware > > (files which point to hardware addresses, etc.) or > > edit /etc/modules.conf. It's been a while since I did it, but now mine > > are ifcfg-eth0 and ifcfg-eth1. > > > > --Jonathon Robison > > > > On Wed, 2004-09-15 at 12:44 +0200, fschuett wrote: > > > Hallo, > > > > > > for several similar machines I used to autoinstall just one machine and > > > copy the installed system to the others. For some reasons this is in my > > > environment less work than to autoinstall every machine. > > > > > > In 9.1 the naming schema for the first ethernet device changed from > > > "eth0" to "eth-id-<MAC address>". > > > Since the MAC address is unique for each machine, the copied systems > > > don't recognize their network interface. > > > > > > Does anybody know a possibility to restore the old naming schema or > > > correct the problem maybe by running a post-install script? > > >

1 0

AW: WG: [suse-autoinstall] installing SLES8 using autoyast and wi thou tany user interaction
by Lenz, Fabian 16 Sep '04

16 Sep '04

How can I use Service Pack 3 in the Installation process? I use the multiple source installation with service pack 3, described in the documentation. But nothing changed. 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/ -----Ursprüngliche Nachricht----- Von: Anas Nashif [mailto:nashif@suse.de] Gesendet: Montag, 13. September 2004 17:51 An: Lenz, Fabian Cc: suse-autoinstall(a)suse.com Betreff: Re: WG: [suse-autoinstall] installing SLES8 using autoyast and withou tany user interaction You need to use Service Pack 3 to fix this. Anas Lenz, Fabian wrote: > > 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/ > > -----Ursprüngliche Nachricht----- > Von: Lenz, Fabian > Gesendet: Montag, 13. September 2004 14:00 > An: 'Kohrs, Steven' > Betreff: AW: [suse-autoinstall] installing SLES8 using autoyast and withou tany user interaction > > Hello! > > I have the same problem and the EULA is pop up bevor i can install! > I have the xml-Tags included, but nothing changed! > <general> > ... > <mode> > <confirm config:type="boolean">false</confirm> > <reboot config:type="boolean">false</reboot> > </mode> > ... > </general> > > What can I do? > Some people said I have to re-spool the CD, but what do they mean with re-spool??? > > 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/ > > -----Ursprüngliche Nachricht----- > Von: Kohrs, Steven [mailto:skohrs@fnni.com] > Gesendet: Freitag, 14. Mai 2004 15:47 > An: jochen.kirn(a)daimlerchrysler.com > Cc: suse-autoinstall(a)suse.com > Betreff: Re: [suse-autoinstall] installing SLES8 using autoyast and withou tany user interaction > > On Fri, 2004-05-14 at 01:41, jochen.kirn(a)daimlerchrysler.com wrote: > >> >> >>Hi everyone, >> >>I'm currently creating an autoyast.xml file for an unattended >>installation >>of SLES8 (using PXE). >>so far everything went fine, except after the software rpms are >>installed a >>window pops up (textmode) >>telling me that the boot loader was succesfully written to disc which >>I >>have to approve by clicking ok. >> >>I guess there is a way (xml-tag) to perform a complete and silent >>installation without any user interaction > > > > Jochen, > > I believe this is what you're looking for: > > <general> > ... > <mode> > <confirm config:type="boolean">false</confirm> > <reboot config:type="boolean">false</reboot> > </mode> > ... > </general> > > -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

FW: Need to know if autoinstall can solve a problem for me
by Greg Wallace 15 Sep '04

15 Sep '04

I am brand new to this list. I'm hoping autoinstall can help me with a problem I'm having. I am trying to migrate from SuSE 8.1 Pro to SuSE 9.0 Pro. The conversion goes fine, and everything works afterward (well there is one minor glitch, but that's something I can work on as I have time). My major concern, however, is being able to recover from a major system crash. I tried to go on from 9.0 to 9.1 and had problems. I had backed up 9.0, so I figured all I would have to do would be to re-install 9.0 out of the box, recover my backup, and I'd be right back in business in 9.0. Well, it didn't work that way. Many things that had been working when I did the conversion from 8.1 to 9.0 no longer worked when I did the recovery. I ended up having to restore my 8.1 installation to get a working system back. My suspicion is that the out of the box install of 9.0 installs some packages that the 8.1 to 9.0 conversion process didn't install. I'm thinking that, during the conversion, SuSE could see from what I had that certain packages would conflict and so made necessary adjustments. During the recovery, since SuSE had nothing to go on during that initial out of the box install, it put some packages on there that were incompatible with what I had in my backup. So, when I recovered the backup, I had a mishmash situation with the packages and that's why certain things would no longer function. Of course, all of this is speculation on my part, but I can't think of any logical reason why a conversion would work just fine but an out of the box install followed by a recovery would not. So, that's what brought me to this list. I'm hoping this installation problem is something that autoinstall could help resolve. What I would like to do is simply point to my backup during the initial install and say "only install the packages that are in this backup, no more and no less". My hope is that this is exactly the type of thing that autoinstall would handle. I notice that my backups generate an autoinstall list in addition to the file containing the actual backup data. I'm thinking this file must be usable somehow in an autoinstall process to instruct SuSE as to the particular packages that need to be loaded for the installation. I also suspect that there may be different degrees of autoinstall, all the way from being able to simply push a button (so to speak) and have the entire install take place to variations where part of the install is manual and part is automated. The main thing I want to automate is the package part. If I have to intervene during other parts of the installation, that's no big deal. Of course, if the amount of effort needed to get everything fully automated is not that much greater, then I would (of course) be interested in that also. Am I on the right track in thinking that this is right up autoinstall's alley (so to speak)? Could some sort of a basic autoinstall procedure take care of what I'm trying to get done here? Any help greatly appreciated. Yours truly, Greg Wallace

1 0

64 or 32??
by Patrick B. O'Brien 15 Sep '04

15 Sep '04

What command can I issue telling me if I'm a 64 or 32 bit?

4 3

SuSE 9.1 network interface naming schema problem
by fschuett 15 Sep '04

15 Sep '04

Hallo, for several similar machines I used to autoinstall just one machine and copy the installed system to the others. For some reasons this is in my environment less work than to autoinstall every machine. In 9.1 the naming schema for the first ethernet device changed from "eth0" to "eth-id-<MAC address>". Since the MAC address is unique for each machine, the copied systems don't recognize their network interface. Does anybody know a possibility to restore the old naming schema or correct the problem maybe by running a post-install script? Bye, Frank Schütte fschuett(a)gymnasium-himmelsthuer.de

3 2

SuSE 9.1 SSH Network Install fails
by werbung＠kuhnle.net 15 Sep '04

15 Sep '04

Hi, I am trying to do a network install with SuSE 9.1 on a headless (and keyboardless) machine. After inital booting and ssh login, yast displays the following error message: unicode_start skipped on /dev/pts/0 No keyboard detected. Trying to connect via serial interface /dev/ttyS0. On your terminal computer start the user interface with y2base "serial(115200):/dev/ttyS0" qt --auto-fonts or y2base "serial(115200):/dev/ttyS1" qt --auto-fonts or start the YaST2 menu by typing "yast2" and select YaST2/Remote Install This is because yast calls hwinfo, which sets "Keyboard: 0" in /etc/install.inf, causing YaST2 to fail at the following section: if [ ! "$update" -a "$Keyboard" = "0" -a ! "$Braille" -a "$NOTISERIES" != 0 -a "$NOTHVCCONSOLE" != 0 -a "$HOSTTYPE" != "s390" -a "$HOSTTYPE" != "s390x" -a -z "$Console" ] ; then log "no keyboard?" echo "No keyboard detected. Trying to connect via serial interface /dev/ttyS0." ... fi Is there any workaround/fix? Regards, Jochen

3 10

Setting a default root password
by Nicholas DeClario 14 Sep '04

14 Sep '04

Hey guys. During my auto install I want a default root password to be put in place. I checked numberous documentation and searched quite a bit and couldn't come up with anything. I was going to just do something like 'echo "password" | passwd root --stdin' in a post-install script but the 'passwd' included in SuSE does not support the --stdin option I've seen in the past. I would prefer not to hack up passwd to add this functionality as well. Am I missing something obvious? Is there anyway this can be done? Any help would be appreciated. Thanks, -Nick

5 6

WG: [suse-autoinstall] installing SLES8 using autoyast and withou tany user interaction
by Lenz, Fabian 13 Sep '04

13 Sep '04

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/ -----Ursprüngliche Nachricht----- Von: Lenz, Fabian Gesendet: Montag, 13. September 2004 14:00 An: 'Kohrs, Steven' Betreff: AW: [suse-autoinstall] installing SLES8 using autoyast and withou tany user interaction Hello! I have the same problem and the EULA is pop up bevor i can install! I have the xml-Tags included, but nothing changed! <general> ... <mode> <confirm config:type="boolean">false</confirm> <reboot config:type="boolean">false</reboot> </mode> ... </general> What can I do? Some people said I have to re-spool the CD, but what do they mean with re-spool??? 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/ -----Ursprüngliche Nachricht----- Von: Kohrs, Steven [mailto:skohrs@fnni.com] Gesendet: Freitag, 14. Mai 2004 15:47 An: jochen.kirn(a)daimlerchrysler.com Cc: suse-autoinstall(a)suse.com Betreff: Re: [suse-autoinstall] installing SLES8 using autoyast and withou tany user interaction On Fri, 2004-05-14 at 01:41, jochen.kirn(a)daimlerchrysler.com wrote: > > > > Hi everyone, > > I'm currently creating an autoyast.xml file for an unattended > installation > of SLES8 (using PXE). > so far everything went fine, except after the software rpms are > installed a > window pops up (textmode) > telling me that the boot loader was succesfully written to disc which > I > have to approve by clicking ok. > > I guess there is a way (xml-tag) to perform a complete and silent > installation without any user interaction Jochen, I believe this is what you're looking for: <general> ... <mode> <confirm config:type="boolean">false</confirm> <reboot config:type="boolean">false</reboot> </mode> ... </general> -- Sincerely, Steve Kohrs Distributed Systems 402.633.7058 This email and any files attached with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error delete this message and notify the sender at 402-341-0500. If you are not the named recipient you should not disseminate, distribute or copy this email or any attachment.

2 1

xml2hostconf + kickstart = autoyast ?
by Erik Sjölund 13 Sep '04

13 Sep '04

Just wanted to drop a note about a somewhat related project. http://xml2hostconf.sourceforge.net ( GPL-licensed ) It is used to generate kickstart files for RedHat/Fedora. And it generates RPMs consisting of configuration files. Autoyast have the Classes/Rules system. Xml2hostconf tries to solve the same problem with RPM dependencies and "kickstart-groups". Some differences: * autoyast is SUSE specific, xml2hostconf is RedHat/Fedora-specific ( I don't know if it is possible to modify xml2hostconf to generate some autoyast configuration ) * xml2hostconf, is not only used for things at install time. When it generates configuration RPMs, already installed systems will also get them by way of yum or apt-get. This means you don't have to reinstall a system to get the new configuration files! * xml2hostconf lacks the "Rules" functionality of autoyast. There is no such rule processing at install time. The configuration for each host is generated in advance. * xml2hostconf lacks a gui. * xml2hostconf lacks most of the "configuration and installation options" of autoyast ( http://www.suse.de/~nashif/autoinstallation/9.1/html/configuration.html ). xml2hostconf only handles what a kickstart file can do. The rest is left to the system administrator to put in post-install scripts and in generated configuration RPMs. Comments? cheers, Erik Sjölund

3 2

no space left doing autoinstall, etc...
by Noprianto 13 Sep '04

13 Sep '04

Hi all :) I am new to SUSE and have to learn about AutoInstall. I am very surprised with this facility :) I have configured control file ( i have it on NFS server, and reachable). Then, i create 3 bootdisk (because my target ws has no CDROM and bootrom). Booting was succeed. Everything from uncompresing kernel was fine. But, problem started when the install systems created device. Install system prints a lot of: /dev/xxx mknod xxx... /dev/xxx no space left after it, it prints someting like: SUSE Install System v.1.6.19 and hang out. I dont know whats happening. My target client has only 32 Megs of RAM. Is it the cause of that error? This is kernel cmdline for my target ws: i chose manual instalation as type: autoyast=nfs://192.168.0.1/PUB/SUSEINSTALL MEM=32 Am i doing something incorrect or all problems are caused by insufficient RAM of my ws? Thanks for reading this :) BTW, can anyone share with me procedure doing autoinstallation? - create control file and save it somewhere accesible - turn on ws and choose (manual) instalation - set the command line autoyast=<location_of_control_file> - what else - what else - what else My last question : - what is happening if i have not set some values in autoyast configuration? For example, what will happened if i have not set the soundcard device of ws? Will it autodetected or just left not detected? Thanks all :) Any comment is appreciated... Nop __________________________________ Do you Yahoo!? Yahoo! Mail is new and improved - Check it out! http://promotions.yahoo.com/new_mail

2 1

RE: [suse-autoinstall] Setting a default root password
by Ness, Todd 08 Sep '04

08 Sep '04

The most simple solution on the older SuSE 8 versions is to do a postinstall script with a perl command to insert the proper encrypted password into the shadow file. /usr/bin/perl -pi -e 's#^root:.*$#root:<your pw here>:12415:0:10000::::#' /etc/shadow If it has been fixed in the newer versions there is xml code to support setting the password. <users config:type="list"> <user> <encrypted config:type="boolean">true</encrypted> <user_password>your pw here</user_password> <username>root</username> </user> </users> -----Original Message----- From: Nicholas DeClario [mailto:nick@demandred.dyndns.org] Sent: Wednesday, September 08, 2004 2:43 PM To: suse-autoinstall(a)suse.com Subject: [suse-autoinstall] Setting a default root password Hey guys. During my auto install I want a default root password to be put in place. I checked numberous documentation and searched quite a bit and couldn't come up with anything. I was going to just do something like 'echo "password" | passwd root --stdin' in a post-install script but the 'passwd' included in SuSE does not support the --stdin option I've seen in the past. I would prefer not to hack up passwd to add this functionality as well. Am I missing something obvious? Is there anyway this can be done? Any help would be appreciated. Thanks, -Nick -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

Fwd: [suse-autoinstall] Installing with Fibre attached drive onto local scsi device
by Aaron Amauba 08 Sep '04

08 Sep '04

OK, once again let me know if I shouldnt post this here. Im still a noob I got back to this and it turned out to be a simple fix after I did some digging. the qla2300 module needed to come after the scsi module in /etc/sysconfig/kernel I changed INITRD_MODULES="scsi_mod sd_mod cdrom ide-cd qla2300 mptscsih reiserfs" to INITRD_MODULES="scsi_mod sd_mod cdrom ide-cd mptscsih qla2300 reiserfs" then mkinitrd and replace the initrd and linux in the boot/loader directory on my installation media (Which was a NFS mount) After the installation was completed, the system came up ok. Maybe all this is in the doc's somewhere, but I never did find it. Anyone know where its at or have any links I should look at? Note: forwarded message attached. --------------------------------- Do you Yahoo!? Win 1 of 4,000 free domain names from Yahoo! Enter now.

1 0

LPRng installation problem
by Henrik Schmidt 07 Sep '04

07 Sep '04

Network autoinstall with PXE of SuSE 9.1 : I use autoinstall to install LPRng instead of CUPS for various reasons. It works fine but locks up as soon as I want to use kprinter. I can fix calling KDE print manager and setting the print system from CUPS to LPRng *for each user* manually. Is it possible to set a system variable in config.xml for autoyast during install to avoid doing it by hand ? Why is the print manager set to CUPS by default without CUPS being installed at all ? Henrik -- Henrik Schmidt Christian-Albrechts-Universitaet zu Kiel Institut fuer Informatik +49 (431) 880 75 - 50 Fax or 43 Phone Olshausenstr. 40 http://www.ks.informatik.uni-kiel.de 24098 Kiel, Germany email: hbs(a)ks.informatik.uni-kiel.de

1 0

[Fwd: Re: [suse-autoinstall] Additional rpm packages are not found on media? (error 11283)]
by Stephan A. Rickauer 04 Sep '04

04 Sep '04

Hard to believe, but it works! Thanks Jan. However, it would be really helpful to know, why it has to be i586 and not "noarch". Furthermore, I'd like to specify my own subdirs, like "uni" or something similar ... isn't that possible? Stephan A. Rickauer ---------------------------- Institut für Neuroinformatik IT-Koordinator Universität / ETH Zürich Winterthurerstr. 190 CH-8057 Zürich Tel: +41 1 635 30 50 Sek: +41 1 635 30 52 Fax: +41 1 635 30 53 http://www.ini.unizh.ch ------------------------ Jan-Marc Pilawa wrote: > Schon probiert die rpms in i586 abzulegen? Meine habe ich dort angelegt und > genau das getan, was in der Mail beschrieben stand. > > Mit freundlichen Gruessen / Sincerely > > Jan Pilawa > -------- Original Message -------- Subject: Re: [suse-autoinstall] Additional rpm packages are not found on media? (error 11283) Date: Thu, 8 Jul 2004 14:22:12 +0200 From: Jan-Marc Pilawa <j.pilawa(a)tu-bs.de> Organization: Rechenzentrum To: Stephan A. Rickauer References: <40ED38D7.7020101(a)ini.phys.ethz.ch> Schon probiert die rpms in i586 abzulegen? Meine habe ich dort angelegt und genau das getan, was in der Mail beschrieben stand. Mit freundlichen Gruessen / Sincerely Jan Pilawa -- + Kontakt ----------------------------------------------------+ + Systembetreuung Rechenzentrum TU Braunschweig + + Hans-Sommer-Str. 65, D-38092 Braunschweig + + Tel: +49 531 391-5548 E-Mail: j.pilawa(a)tu-bs.de ____________+

3 6

PXE install fails with SCSI disks
by Steve Glines 03 Sep '04

03 Sep '04

I’m building a PXE install lab for SUSE and other flavors of Linux. The DHCP and tftp servers are working. Note: I can fully install Red Hat from this lab but SUSE (SLES9 rc5) shows the following symptoms: 1. a cdrom install on the target system runs to completion in graphics mode. System is an HP PC with SCSI disk. 2. PXE install runs in non X-window mode (text) and fails to load scsi controllers – cannot find any disks. Fails even when modules are manually added. Here is the content of /tftpboot/pxelinux.cfg/default: default suse prompt 1 display boot.msg timeout 200 label redhat kernel redhat.kernel append initrd=redhat.root ramdisk_size=65536 label suse kernel suse.kernel append initrd=suse.root ramdisk_size=65536\ install=http://10.0.3.11/suse/CD1/ The file suse.kernel was copied from /boot/loader/linux in CD1 while suse.root was taken from /boot/loader/initrd in the same CD. I copied the contents of each CD into their own directories – I have CD1 – CD6 in the directory specified by http://10.0.3.11/suse/CD[1-6]. My test target system is a Celeron with 256MB Ram and an IDE disk; this setup fully installs SLES9. The only material change from this to the production lab is that the target system in the production lab has a SCSI disk and 1GB of ram. Help! Please Cheers -- Steve Glines voice: 978-952-6340 www.is-cs.com fax: 978-952-8524 145 Foster Street cell: 617-549-7274 Littleton MA 01460 I'm a complex person. I have a real and an imaginary part.

2 1

Re: [suse-autoinstall] PXE install fails with SCSI disks
by Steve Glines 03 Sep '04

03 Sep '04

Hi Marcin, Thanks for the help. I've made the fixes you suggested but the system still refuses to see the scsi disks. Here is the data. The target system is an HP Proliant ML350 G3 with a single 40GB SCSI disk. The script shown in sles9/CD1/docu/RELEASE-NOTES.en.html doesn't work so I've modified it thus (feel free to reuse it): #From the top directory umask 0 mkdir -p sles9/CD1 # now copy the contents of SLES CD1 into this directory echo "Mount CD1" read x mount /dev/cdrom sleep 10 cp -r /cdrom/* sles9/CD1 eject mkdir -p core9/CD1 # now copy the contents of SLES CD2 into this directory echo "Mount CD2" read x sleep 10 mount /dev/cdrom cp -r /cdrom/* core9/CD1 eject mkdir -p core9/CD2 # now copy the contents of SLES CD3 into this directory echo "Mount CD3" read x sleep 10 mount /dev/cdrom cp -r /cdrom/* core9/CD2 eject mkdir -p core9/CD3 # now copy the contents of SLES CD4 into this directory echo "Mount CD4" read x sleep 10 mount /dev/cdrom cp -r /cdrom/* core9/CD3 eject mkdir -p core9/CD4 now copy the contents of SLES CD5 into this directory echo "Mount CD5" read x sleep 10 mount /dev/cdrom cp -r /cdrom/* core9/CD4 eject mkdir -p core9/CD5 now copy the contents of SLES CD6 into this directory echo "Mount CD6" read x sleep 10 mount /dev/cdrom cp -r /cdrom/* core9/CD5 eject ln -s sles9/CD1/boot boot ln -s sles9/CD1/content content ln -s sles9/CD1/control.xml control.xml ln -s sles9/CD1/media.1 media.1 mkdir -p yast echo "/sles9/CD1 /sles9/CD1 /core9/CD1 /core9/CD1" > yast/instorder echo "/sles9/CD1 /sles9/CD1 /core9/CD1 /core9/CD1" > yast/order --------------------------------- After PXE booting the system stalls when it can't find a hard disk. When I look in /var/log/boot.log I find: kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter errorno=2 If I run "/sbin/modprobe -s -k scsi_hostadapter" directly from a shell I get "Kernel requires old modprobe no /sbin/modprobe.old." ------------------------------------------- Here is the current line from my default file: label suse kernel suse.kernel append initrd=suse.root ramdisk_size=65536 \ install=http://10.0.3.11/suse ---------------------------------------------- Here is the output of "find . -type d": . ./sles9 ./sles9/CD1 ./sles9/CD1/SLES-LICENSE ./sles9/CD1/SLES-LICENSE/cz ./sles9/CD1/SLES-LICENSE/de ./sles9/CD1/SLES-LICENSE/en_US ./sles9/CD1/SLES-LICENSE/es ./sles9/CD1/SLES-LICENSE/fr ./sles9/CD1/SLES-LICENSE/it ./sles9/CD1/SLES-LICENSE/nl ./sles9/CD1/SLES-LICENSE/pl ./sles9/CD1/SLES-LICENSE/pt_BR ./sles9/CD1/boot ./sles9/CD1/boot/loader ./sles9/CD1/docu ./sles9/CD1/docu/de ./sles9/CD1/docu/en ./sles9/CD1/docu/es ./sles9/CD1/docu/fr ./sles9/CD1/docu/HOWTOs ./sles9/CD1/docu/it ./sles9/CD1/docu/ja ./sles9/CD1/docu/ko ./sles9/CD1/docu/pt_BR ./sles9/CD1/docu/zh_CN ./sles9/CD1/dosutils ./sles9/CD1/dosutils/dparam ./sles9/CD1/dosutils/ext2tool ./sles9/CD1/dosutils/ext2tool/ext2fs ./sles9/CD1/dosutils/ext2tool/linux ./sles9/CD1/dosutils/ext2tool/src ./sles9/CD1/dosutils/ext2tool/sys ./sles9/CD1/dosutils/fips ./sles9/CD1/dosutils/fips/fips15 ./sles9/CD1/dosutils/fips/fips15/restorrb ./sles9/CD1/dosutils/fips/fips15/source ./sles9/CD1/dosutils/fips/fips20 ./sles9/CD1/dosutils/fips/fips20/restorrb ./sles9/CD1/dosutils/fips/fips20/source ./sles9/CD1/dosutils/gtar109 ./sles9/CD1/dosutils/gzip ./sles9/CD1/dosutils/install ./sles9/CD1/dosutils/lfn ./sles9/CD1/dosutils/loadlin ./sles9/CD1/dosutils/loadlin/doc ./sles9/CD1/dosutils/loadlin/src ./sles9/CD1/dosutils/ltools ./sles9/CD1/dosutils/pkunzip ./sles9/CD1/dosutils/putty ./sles9/CD1/dosutils/rawrite ./sles9/CD1/dosutils/rawwritewin ./sles9/CD1/dosutils/tightvnc ./sles9/CD1/dosutils/untgz ./sles9/CD1/dosutils/weirdx ./sles9/CD1/dosutils/weirdx/config ./sles9/CD1/dosutils/xfs186 ./sles9/CD1/dosutils/xfs32-11 ./sles9/CD1/dosutils/zipzp715 ./sles9/CD1/media.1 ./sles9/CD1/suse ./sles9/CD1/suse/i586 ./sles9/CD1/suse/noarch ./sles9/CD1/suse/nosrc ./sles9/CD1/suse/setup ./sles9/CD1/suse/setup/descr ./sles9/CD1/suse/src ./sles9/CD1/yast ./sles9/CD1/yast/core9 ./sles9/CD1/yast/core9/media.1 ./sles9/CD1/yast/core9/suse ./sles9/CD1/yast/core9/suse/setup ./sles9/CD1/yast/core9/suse/setup/descr ./core9 ./core9/CD1 ./core9/CD1/media.1 ./core9/CD1/suse ./core9/CD1/suse/i586 ./core9/CD1/suse/i686 ./core9/CD1/suse/noarch ./core9/CD1/suse/setup ./core9/CD1/suse/setup/descr ./core9/CD2 ./core9/CD2/media.2 ./core9/CD2/suse ./core9/CD2/suse/i586 ./core9/CD2/suse/i686 ./core9/CD2/suse/noarch ./core9/CD3 ./core9/CD3/media.3 ./core9/CD3/suse ./core9/CD3/suse/i586 ./core9/CD3/suse/i686 ./core9/CD3/suse/noarch ./core9/CD3/suse/src ./core9/CD4 ./core9/CD4/media.4 ./core9/CD4/suse ./core9/CD4/suse/nosrc ./core9/CD4/suse/src ./core9/CD5 ./core9/CD5/media.5 ./core9/CD5/suse ./core9/CD5/suse/nosrc ./core9/CD5/suse/src ./yast Marcin Kurc wrote: > > for graphical install you can say 'textmode=0' after 'install*' > please send me your 'default' file and output of 'find . -type d' in the > suse top directory > > > > thanks, > > Marcin Kurc > Linux Impact Team > Novell, Inc > > (973) 493-6235 > >>>>Steve Glines <sglines(a)is-cs.com> 09/01/04 3:37 pm >>> > Thanks - I missed that one and was following the instructions that came > with SUSE 9.1 Pro. It still boots into the non-X format via PXE and X > when I do a CDROM install. Is there a way to make it boot into Graphics > mode. The lab I'm building is supposed to simulate the experience of > installing via CDROM. By the way this is going to go into HP's main > learning lab. The Red Hat version is being used 30-50 times a day. > > Now I'm getting "Network error 404 not found." > > Cheers > Steve > > Marcin Kurc wrote: > >> >>it is not a problem with PXE, your installation tree is not configured >>correctly >>You should either use SLES9 system to build the tree or configure it >>according to the docu/RELEASE-NOTES.en.html which can be found on cd #1 >> >>Also, you need to point you install to top dir not CD1 i.e. >>'install=_/http://10.0.3.11/suse/_' >> >> >> >>thanks, >> >>Marcin Kurc >>Linux Impact Team >>Novell, Inc >> >>(973) 493-6235 >> >>>>>Steve Glines <sglines(a)is-cs.com> 09/01/04 2:30 pm >>> >>I’m building a PXE install lab for SUSE and other flavors of Linux. >> >>The DHCP and tftp servers are working. Note: I can fully install Red Hat >>from this lab but SUSE (SLES9 rc5) shows the following symptoms: >> >>1.a cdrom install on the target system runs to completion in graphics >>mode. System is an HP PC with SCSI disk. >>2.PXE install runs in non X-window mode (text) and fails to load scsi >>controllers – cannot find any disks. Fails even when modules are >>manually added. >> >>Here is the content of /tftpboot/pxelinux.cfg/default: >> >>default suse >>prompt 1 >>display boot.msg >>timeout 200 >> >>label redhat >> kernel redhat.kernel >> append initrd=redhat.root ramdisk_size=65536 >> >>label suse >> kernel suse.kernel >> append initrd=suse.root ramdisk_size=65536\ >>install=http://10.0.3.11/suse/CD1/ >> >>The file suse.kernel was copied from /boot/loader/linux in CD1 while >>suse.root was taken from /boot/loader/initrd in the same CD. >> >>I copied the contents of each CD into their own directories – I have CD1 >> – CD6 in the directory specified by http://10.0.3.11/suse/CD[1-6]. >> >>My test target system is a Celeron with 256MB Ram and an IDE disk; this >>setup fully installs SLES9. The only material change from this to the >>production lab is that the target system in the production lab has a >>SCSI disk and 1GB of ram. -- Steve Glines voice: 978-952-6340 www.is-cs.com fax: 978-952-8524 145 Foster Street cell: 617-549-7274 Littleton MA 01460 I'm a complex person. I have a real and an imaginary part.

1 0

Changing kernel in the install distribution. How?
by Ermanno Polli 03 Sep '04

03 Sep '04

Hi, I asked this question on the suse-linux-e list, but I had no answer. The reason for asking what is in the subject line is I've found my motherboard is no longer supported by SuSE. The last version I was able to install was the 8.0. Trying to install the 8.2 cause a hang just after the "loading kernel" window after having hit the "install" menu item in the installation. So I built a kernel from the sources (2.4.20) but I'm not able to upgrade all the 8.0 packages. I downloaded the 8.2 distribution to disk and I tried to point YOU to that directory, but YOU refused it (Unable to mount or something). So I'm wondering if I could "build" an install CD with *my* kernel, instead of the SuSE supplied one. Is it possible? What are the passes to achive this goal? Thank you very much. Ermanno Polli INFN-LNF

1 0

X11 configuration, SLES8
by Oliver Schwabedissen 03 Sep '04

03 Sep '04

Hello, I have a problem with configuring X11 when installing SLES8. I want to configure X11, but don't want KDE to start when the server comes up. So I configured runlevel 3 and X11 like this: [...] <runlevels> <default>3</default> </runlevels> <x11> <color_depth config:type="integer">16</color_depth> <configure_x11 config:type="boolean">true</configure_x11> <display_manager>kdm</display_manager> <enable_3d config:type="boolean">false</enable_3d> <monitor> <display> <max_hsync config:type="integer">60</max_hsync> <max_vsync config:type="integer">60</max_vsync> <min_hsync config:type="integer">31</min_hsync> <min_vsync config:type="integer">30</min_vsync> </display> <monitor_device>1024X768@60HZ</monitor_device> <monitor_vendor>LCD</monitor_vendor> </monitor> <resolution>1024x768</resolution> <start_x11 config:type="boolean">false</start_x11> </x11> </configure> However, when autoinstall finishes the system boots to runlevel 5, which is now also the default runlevel in /etc/inittab. Why does autoyast ignore my configured runlevel? Doesn't <start_x11 config:type="boolean">false</start_x11> mean that X11 should not be started automatically? I'm starting installation by booting from SP3 CD1 with an info file on floppy. It then connects to the installation server through NFS. Oliver -- Superg�nstige DSL-Tarife + WLAN-Router f�r 0,- EUR* Jetzt zu GMX wechseln und sparen http://www.gmx.net/de/go/dsl

1 1

Multiple Versions on one Installationserver
by Brigitte Warnecke-Schaer 02 Sep '04

02 Sep '04

Hello, I'm new to autoyast and it's configurationsystem. I wondered if/how it is possible to install different Version e.g. SLES 9 SuSE 9.0 and 9.1 Pro from 1 Installationserver. How can I bulid a class in which I can Specfy thefor example the Path of the Version I'd like to install. I couldn't find anything about that in the Documentation. Thanks for your help. -- Best regards Brigitte Warnecke-Schaer

2 1

Re: [suse-autoinstall] PXE install fails with SCSI disks
by Marcin Kurc 01 Sep '04

01 Sep '04

it is not a problem with PXE, your installation tree is not configured correctly You should either use SLES9 system to build the tree or configure it according to the docu/RELEASE-NOTES.en.html which can be found on cd #1 Also, you need to point you install to top dir not CD1 i.e. 'install=http://10.0.3.11/suse' thanks, Marcin Kurc Linux Impact Team Novell, Inc (973) 493-6235 >>>Steve Glines <sglines(a)is-cs.com> 09/01/04 2:30 pm >>> I'm building a PXE install lab for SUSE and other flavors of Linux. The DHCP and tftp servers are working. Note: I can fully install Red Hat from this lab but SUSE (SLES9 rc5) shows the following symptoms: 1.a cdrom install on the target system runs to completion in graphics mode. System is an HP PC with SCSI disk. 2.PXE install runs in non X-window mode (text) and fails to load scsi controllers * cannot find any disks. Fails even when modules are manually added. Here is the content of /tftpboot/pxelinux.cfg/default: default suse prompt 1 display boot.msg timeout 200 label redhat kernel redhat.kernel append initrd=redhat.root ramdisk_size=65536 label suse kernel suse.kernel append initrd=suse.root ramdisk_size=65536\ install=http://10.0.3.11/suse/CD1/ The file suse.kernel was copied from /boot/loader/linux in CD1 while suse.root was taken from /boot/loader/initrd in the same CD. I copied the contents of each CD into their own directories * I have CD1 * CD6 in the directory specified by http://10.0.3.11/suse/CD[1-6]. My test target system is a Celeron with 256MB Ram and an IDE disk; this setup fully installs SLES9. The only material change from this to the production lab is that the target system in the production lab has a SCSI disk and 1GB of ram. Help! Please Cheers -- Steve Glines voice: 978-952-6340 www.is-cs.com fax: 978-952-8524 145 Foster Street cell: 617-549-7274 Littleton MA 01460 I'm a complex person. I have a real and an imaginary part. -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0