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