October 2003 - openSUSE Autoinstall - openSUSE Mailing Lists

post-install script as root
by Schulte Thomas ICM Bocholt 17 Oct '03

17 Oct '03

Hi, I have a problem running the post-install scripts. They don't seem to run as root. I need to run them as root because I try to mount a nfs partition. <scripts> <post-scripts config:type="list"> <script> <filename>post_install.sh</filename> <interpreter>shell</interpreter> <source> <![CDATA[#!/bin/sh # # post_install.sh mkdir -p /mnt/tmp mount -t nfs 14x.xxx.xx.xxx:/xx/x/x /mnt/tmp cp -r /mnt/tmp/xx/x/x/x/* /usr/local umount /mnt/tmp echo "Post Install done." > /var/log/post_install.log ]]> </source> </script> </post-scripts> </scripts> I get an error "Mount - Only root can do that". (SuSE 8.2, autoyast2-2.7.18-1) Any suggestions? Thomas ------------------------------------- Siemens AG Dipl.-Inform. Thomas Schulte ICM CP RD SD 23 Frankenstr.2 46393 Bocholt +49 2871 91 2156 schulte(a)siemens.com -------------------------------------

1 0

Re: [suse-autoinstall] Using PXELinux for 8.1 Auto Install
by fetak＠comcast.net 16 Oct '03

16 Oct '03

OK, the problem has been solved. I am writing this just for the record. As Aaron mentioned, the /boot/loader/initrd worked just fine. It was a DHCP server configuration problem (not defining the scopes correctly). It would have been a nicer if the install program actually give the error at that point. Fet > /boot/loader/initrd from the cdrom works for me > > dont know about this other problem though, maybe check file permissions on the > server or mount point. > > > On Mon, 13 Oct 2003 fetak(a)comcast.net wrote: > > > Thanks Aaron! That helped a lot. > > > > Now the problem is a bit peculiar; Installation error is "An error occured > during installation" and the Alt_F3 screen reports this: > > > > /mounts/instsys/sbin/inst_setup: cannot execute binary file > > > > What would have caused it? When I go to the shell on F2 screen, in fact I > cannot execute any of those "executable"s > > > > I have been using the initrd that would have been used for CD installations -- > so that it has all modules in it. I wonder if that makes any difference... > > > > Or, is there a way to specify the binary formats during installation? > > > > Thanks in advance, > > Fet > > > maybe add "install=" to your append line: > > > > > > > > > label auto > > > kernel linux > > > append initrd=initrd install="nfs://192.168.1.1/KS/SuSe81" > > > autoyast="nfs://192.168.1.1/KS/SuSe81/autoinst.xml" > > > > > > > > > Also try not to let the append line get too long, there seems to be a limit > on > > > how long it can be. > > > > > > > > > On Mon, 13 Oct 2003 fetak(a)comcast.net wrote: > > > > > > > > > > > Hello, > > > > > > > > I would like to use pxelinux to auto install SuSE81, but the installation > > > comes back with an error message "Could not find SuSE Linux Installation > Source. > > > Activate manual setup program." I wonder if any of the configuration files > I am > > > using are wrong... Does not seem to find the autoinst.xml file. The NFS > share > > > is setup correctly since I was able to run other installations out of > there... > > > > > > > > Thanks in advance, > > > > Fet > > > > > > > > The default file pxelinux using is as follows. This file is located under > > > pxelinux.cfg directory > > > > > > > > ---<default>--- > > > > default auto > > > > implicit 1 > > > > timeout 60 > > > > prompt 1 > > > > > > > > # manual > > > > label manual > > > > kernel linux > > > > append initrd=initrd ramdisk_size=65536 manual=1 > > > > label auto > > > > kernel linux > > > > append initrd=initrd load_initrd=1 insmod=e100 netdevice=eth0 > > > ramdisk_size=65536 autoyast=nfs://192.168.1.1/KS/SuSe81/autoinst.xml > > > > --</default---> > > > > > > > > And the autoinst.xml file specified above has the following contents: > > > > > > > > ---<autoinst.xml> > > > > <?xml version="1.0"?> > > > > <!DOCTYPE profile SYSTEM > "/usr/share/YaST2/include/autoinstall/profile.dtd"> > > > > <profile xmlns="http://www.suse.com/1.0/yast2ns" > > > xmlns:config="http://www.suse.com/1.0/configns"> > > > > <configure> > > > > <networking> > > > > <dns> > > > > <domain></domain> > > > > <hostname></hostname> > > > > <nameservers config:type="list"/> > > > > <searchlist config:type="list"/> > > > > </dns> > > > > <interfaces config:type="list"/> > > > > <routing> > > > > <ip_forwarding config:type="boolean">false</ip_forwarding> > > > > <routes config:type="list"/> > > > > </routing> > > > > </networking> > > > > <scripts> > > > > <chroot-scripts config:type="list"/> > > > > <post-scripts config:type="list"/> > > > > <pre-scripts config:type="list"/> > > > > </scripts> > > > > </configure> > > > > <install> > > > > <bootloader> > > > > <kernel_parameters></kernel_parameters> > > > > <lba_support config:type="boolean">false</lba_support> > > > > <location></location> > > > > </bootloader> > > > > <general> > > > > <clock/> > > > > <keyboard/> > > > > <language></language> > > > > <mode> > > > > <interactive config:type="boolean">false</interactive> > > > > <reboot config:type="boolean">false</reboot> > > > > </mode> > > > > <mouse/> > > > > </general> > > > > <init> > > > > <domain></domain> > > > > <gateway></gateway> > > > > <info_file> > > > > <![CDATA[ > > > > # > > > > # Don't remove the following line: > > > > # start_linuxrc_conf > > > > # > > > > install: nfs://192.168.1.1/LinuxImages/SuSe81 > > > > autoyast: nfs://192.168.1.1/KS/SuSe81 > > > > Usedhcp: 1 > > > > > > > > # end_linuxrc_conf > > > > # Do not remove the above comment > > > > #]]> > > > > </info_file> > > > > <instmode>nfs</instmode> > > > > <ip></ip> > > > > <keytable></keytable> > > > > <language></language> > > > > <nameserver></nameserver> > > > > <netmask></netmask> > > > > <partition></partition> > > > > <port></port> > > > > <profile_location>/KS/SuSe81</profile_location> > > > > <profile_port></profile_port> > > > > <profile_protocol>nfs</profile_protocol> > > > > <profile_server>192.168.1.1</profile_server> > > > > <server>192.168.1.1</server> > > > > <serverdir>/LinuxImages/SuSe81</serverdir> > > > > <textmode config:type="boolean">false</textmode> > > > > <usedhcp config:type="boolean">true</usedhcp> > > > > <workdomain></workdomain> > > > > </init> > > > > <partitioning config:type="list"> > > > > <drive> > > > > <device>/dev/hda</device> > > > > <initialize config:type="boolean">true</initialize> > > > > <partitions config:type="list"> > > > > <partition> > > > > <crypt_fs config:type="boolean">false</crypt_fs> > > > > <crypt_key></crypt_key> > > > > <filesystem config:type="symbol">swap</filesystem> > > > > <format config:type="boolean">true</format> > > > > <mount>swap</mount> > > > > <partition_id config:type="integer">131</partition_id> > > > > <size>auto</size> > > > > </partition> > > > > <partition> > > > > <crypt_fs config:type="boolean">false</crypt_fs> > > > > <crypt_key></crypt_key> > > > > <filesystem config:type="symbol">ext2</filesystem> > > > > <format config:type="boolean">true</format> > > > > <mount>/</mount> > > > > <partition_id config:type="integer">131</partition_id> > > > > <size>max</size> > > > > </partition> > > > > </partitions> > > > > <use>all</use> > > > > </drive> > > > > </partitioning> > > > > <raid config:type="list"/> > > > > <software> > > > > <addons config:type="list"> > > > > <addon>Advanced-Devel</addon> > > > > <addon>Basis-Devel</addon> > > > > <addon>Basis-Sound</addon> > > > > <addon>Games</addon> > > > > <addon>Kde</addon> > > > > <addon>Kde-Desktop</addon> > > > > <addon>Network</addon> > > > > <addon>Office</addon> > > > > <addon>SuSE-Documentation</addon> > > > > </addons> > > > > <base>Minimal</base> > > > > <packages config:type="list"/> > > > > </software> > > > > </install> > > > > </profile> > > > > --<\autoinst.xml> > > > > > > > > > > > > > > > > > > > > -- > _______ Aaron McSorley > \____ | Advanced Processor Validation > /| | | Micro Texas Microprocessor Division > | |___| | Devices e-mail: aaron.mcsorley(a)amd.com > |____/ \| Voice:512.602.0417 > pgr:512.604.0946 > >

1 0

Re: [suse-autoinstall] Installing an package
by Robison, Jonathon (M.) 16 Oct '03

16 Oct '03

Yast on the client end needs to be forced to re-read the whole descr area. Delete that current entry (for install/package source) in yast and re-enter it. This will force the re-read and should show your additional packages. -- Robison, Jonathon (M.) <jrobiso2(a)ford.com> Ford Motor Company On Thu, 2003-10-16 at 12:12, Alexander Luedtke wrote: > Hi there again, > > I've still problems in including my "selfmade" rpm packages into the > yast2 softwareinstaller / autoyast. > > I've done : > (after copying my rpm file to suse/i586 > /usr/lib/YaST2/bin/create_package_descr -l german -l english -l czech > -l > es -x ./EXTRA_PROV > that runs and make the new packages files under suse/setup/descr/ > > If I check the packages files then there are the entry's for my RPM > Packages. > > But when I try to find it in yast2 sw_single or yast2 autoyast then > the > result is empty > > Anyone an Idea ? > > thanks > > Alex > > Christoph Thiel wrote: > > >Hi there, > > > >On Thu, 16 Oct 2003, Alexander Luedtke wrote: > > > > > > > >>can I install packages which are not included in SuSE (I made a rpm > >>package my own) ? > >>And how can I do that ? > >> > >> > > > >Please read the mailinglist archive at > >http://lists.suse.com/archive/suse-autoinstall/ > > > > > >Cheers, > >-- > > Christoph Thiel > > (ct(a)kki.org, cthiel1(a)linux01.gwdg.de) > > > > > > > > -- > Alexander LÃ¼dtke > Systemadministrator > > Adresse: TUM - Garching Boltzmannstr. 3 85747 Garching b. MÃ¼nchen > Lehrstuhl: Frau Prof. Feldmann > Zimmer: 01.08.036 > > Tel: ++49 (89) 289 - 18039 > >

1 0

Installing an packages
by Alexander Luedtke 16 Oct '03

16 Oct '03

Hello, can I install packages which are not included in SuSE (I made a rpm package my own) ? And how can I do that ? thanks Alex

2 2

DMZ / Firewall issues...
by damien.selles＠eu.effem.com 16 Oct '03

16 Oct '03

Hi all, I faced some strange behavior of autoyast when performing installation throught a firewall... the machine I want to install with autoyast is in a dmz. => firewall between this machine and the depot. After the boot, I use the usual command line kernel linux autoyast=nfs:// ... install=nfs:// ... hostip=.. netmask=.. gateway=.. this line is correct and works with other machines not in the DMZ. I reach the step "searching for info file......" but. the system always gives me the message "source not found" and brings me to the manual mode. Then I reconfigure the network manually. The only detail that change with what I typed in the command line is the gateway (nothing in the filed) And now.. no problem... loading ramdisk ... Second strange things: while retrieving the control file... the system does not match his IP with the name of the file. thus I have to type the name of the file manually (its name is the IP address converted in hex) => What are the port I must open on my firewall so that everything is find? kind regards, Damien.

1 0

Parttioning 't'error
by Heirman, Steven 16 Oct '03

16 Oct '03

Hi , I have a odd problems when auto installing sles8 . The partitioning portion is not working but i can't figure out why. When parcing the xml file the system tells me that i already have a LV with the name rootvg ? sda1 on / sda2 on /boot sda3 extended sda4 linux LVM sda5 and 6 2 * swap created in extended sda3 Below is a part of my xml file that i use <partitioning config:type="list"> <drive> <device>/dev/sda</device> <partitions config:type="list"> <partition> <filesystem config:type="symbol">reiser</filesystem> <mount>/</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">1</partition_nr> <region config:type="list"> <region_entry config:type="integer">0</region_entry> <region_entry config:type="integer">131</region_entry> </region> <size>1069219841</size> </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <mount>/boot</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">2</partition_nr> <region config:type="list"> <region_entry config:type="integer">131</region_entry> <region_entry config:type="integer">17</region_entry> </region> <size>131596289</size> </partition> <partition> <partition_id config:type="integer">15</partition_id> <partition_nr config:type="integer">3</partition_nr> <region config:type="list"> <region_entry config:type="integer">148</region_entry> <region_entry config:type="integer">523</region_entry> </region> <size>4293328897</size> </partition> <partition> <mount>swap</mount> <partition_id config:type="integer">130</partition_id> <partition_nr config:type="integer">5</partition_nr> <region config:type="list"> <region_entry config:type="integer">148</region_entry> <region_entry config:type="integer">262</region_entry> </region> <size>2146664449</size> </partition> <partition> <mount>swap</mount> <partition_id config:type="integer">130</partition_id> <partition_nr config:type="integer">6</partition_nr> <region config:type="list"> <region_entry config:type="integer">410</region_entry> <region_entry config:type="integer">261</region_entry> </region> <size>2138439681</size> </partition> <partition> <partition_id config:type="integer">142</partition_id> <partition_nr config:type="integer">4</partition_nr> <region config:type="list"> <region_entry config:type="integer">671</region_entry> <region_entry config:type="integer">3749</region_entry> </region> <size>30826430465</size> <lvm_group>rootvg</lvm_group> </partition> </partitions> </drive> </partitioning> <lvm config:type="list"> <lvm_group> <lvm_name>rootvg</lvm_name> <pesize>128M</pesize> <logical_volumes config:type="list"> <lv> <lv_name>homelv</lv_name> <lv_size>2gb</lv_size> <lv_fs>reiser</lv_fs> <lv_mount>/home</lv_mount> </lv> <lv> <lv_name>optlv</lv_name> <lv_size>2gb</lv_size> <lv_fs>reiser</lv_fs> <lv_mount>/opt</lv_mount> </lv> <lv> <lv_name>tmplv</lv_name> <lv_size>512mb</lv_size> <lv_fs>reiser</lv_fs> <lv_mount>/tmp</lv_mount> </lv> <lv> <lv_name>usrlv</lv_name> <lv_size>4gb</lv_size> <lv_fs>reiser</lv_fs> <lv_mount>/usr</lv_mount> </lv> <lv> <lv_name>varlv</lv_name> <lv_size>1gb</lv_size> <lv_fs>reiser</lv_fs> <lv_mount>/var</lv_mount> </lv> </logical_volumes> </lvm_group> </lvm> Another question is i only can use this on a clean drive. When there is already something on the disk the partioning will also fail. Is there an option to clean the partition table whitin this xml file ? Regards Steven , Steven Heirman - System Engineer/Unix ---------------------------------------------------------------- St Pietersvliet 7 Tel : +3232207365

2 1

ati Driver problem
by Jim Frost 15 Oct '03

15 Oct '03

SuSE 8.2 Pro KDE 3.1.3, Crucial 8500 LE Radeon (ati clone) I recently updated the ati drivers for my desktop system. However, upon first re-boot I get the error message stating the initab is missing. This is after a runlevel is asked for. no matter what run level I enter the system locks up. I would be grateful of any help please. Thanks, Jim

2 1

Re: [suse-autoinstall] Parttioning 't'error
by damien.selles＠eu.effem.com 15 Oct '03

15 Oct '03

Hi Steven, extract from the post : "Re: [suse-autoinstall] Problems with <use> and <partition_type>" 03/10/2003. -------------------------------------- I had a problem that was somehow equivalent.. I wanted to use a volume group (vg00), but if a vg00 was already on my disks the installation crashed... (with all the config of <use> I could find) I solved the problem using a pre script the remove the vg. And now it works very well. --------------------------------------- here is the pre script I use: <pre-scripts config:type="list"> <script> <filename>pre.sh</filename> <interpreter>shell</interpreter> <source> <![CDATA[#! /bin/sh # this script remove the vg00 (if there is one!) # thus it allow yast to perform the partitioning. vg=/dev/vg00 insmod lvm-mod vgscan vgchange -a y $vg lvs=`ls -A $vg | grep -v "group"` for lv in $lvs do lvremove -f $vg/$lv done vgchange -a n $vg vgremove $vg ]]> </source> </script> </pre-scripts> You just have to adapt this chagning vg00 to rootvg. Best regards, Damien. "Heirman, Steven" <steven.heirman(a)compu-mark.com> compu-mark.com 15/10/2003 13:02 To: "'suse-autoinstall(a)suse.com'" <suse-autoinstall(a)suse.com> cc: Subject: [suse-autoinstall] Parttioning 't'error Hi , I have a odd problems when auto installing sles8 . The partitioning portion is not working but i can't figure out why. When parcing the xml file the system tells me that i already have a LV with the name rootvg ? sda1 on / sda2 on /boot sda3 extended sda4 linux LVM sda5 and 6 2 * swap created in extended sda3 Below is a part of my xml file that i use <partitioning config:type="list"> <drive> <device>/dev/sda</device> <partitions config:type="list"> <partition> <filesystem config:type="symbol">reiser</filesystem> <mount>/</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">1</partition_nr> <region config:type="list"> <region_entry config:type="integer">0</region_entry> <region_entry config:type="integer">131</region_entry> </region> <size>1069219841</size> </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <mount>/boot</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">2</partition_nr> <region config:type="list"> <region_entry config:type="integer">131</region_entry> <region_entry config:type="integer">17</region_entry> </region> <size>131596289</size> </partition> <partition> <partition_id config:type="integer">15</partition_id> <partition_nr config:type="integer">3</partition_nr> <region config:type="list"> <region_entry config:type="integer">148</region_entry> <region_entry config:type="integer">523</region_entry> </region> <size>4293328897</size> </partition> <partition> <mount>swap</mount> <partition_id config:type="integer">130</partition_id> <partition_nr config:type="integer">5</partition_nr> <region config:type="list"> <region_entry config:type="integer">148</region_entry> <region_entry config:type="integer">262</region_entry> </region> <size>2146664449</size> </partition> <partition> <mount>swap</mount> <partition_id config:type="integer">130</partition_id> <partition_nr config:type="integer">6</partition_nr> <region config:type="list"> <region_entry config:type="integer">410</region_entry> <region_entry config:type="integer">261</region_entry> </region> <size>2138439681</size> </partition> <partition> <partition_id config:type="integer">142</partition_id> <partition_nr config:type="integer">4</partition_nr> <region config:type="list"> <region_entry config:type="integer">671</region_entry> <region_entry config:type="integer">3749</region_entry> </region> <size>30826430465</size> <lvm_group>rootvg</lvm_group> </partition> </partitions> </drive> </partitioning> <lvm config:type="list"> <lvm_group> <lvm_name>rootvg</lvm_name> <pesize>128M</pesize> <logical_volumes config:type="list"> <lv> <lv_name>homelv</lv_name> <lv_size>2gb</lv_size> <lv_fs>reiser</lv_fs> <lv_mount>/home</lv_mount> </lv> <lv> <lv_name>optlv</lv_name> <lv_size>2gb</lv_size> <lv_fs>reiser</lv_fs> <lv_mount>/opt</lv_mount> </lv> <lv> <lv_name>tmplv</lv_name> <lv_size>512mb</lv_size> <lv_fs>reiser</lv_fs> <lv_mount>/tmp</lv_mount> </lv> <lv> <lv_name>usrlv</lv_name> <lv_size>4gb</lv_size> <lv_fs>reiser</lv_fs> <lv_mount>/usr</lv_mount> </lv> <lv> <lv_name>varlv</lv_name> <lv_size>1gb</lv_size> <lv_fs>reiser</lv_fs> <lv_mount>/var</lv_mount> </lv> </logical_volumes> </lvm_group> </lvm> Another question is i only can use this on a clean drive. When there is already something on the disk the partioning will also fail. Is there an option to clean the partition table whitin this xml file ? Regards Steven , Steven Heirman - System Engineer/Unix ---------------------------------------------------------------- St Pietersvliet 7 Tel : +3232207365 -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

AutoYast did not detect the NIC
by Michael Schulz 15 Oct '03

15 Oct '03

Hello I using Suse 9.0 and I have the following Problem. When I install an Server with AutoYast It do not detect my NIC. By an default installation Yast do this correct. Can anybody say me how I can solve this problem. Regards Michael -- NEU FÜR ALLE - GMX MediaCenter - für Fotos, Musik, Dateien... Fotoalbum, File Sharing, MMS, Multimedia-Gruß, GMX FotoService Jetzt kostenlos anmelden unter http://www.gmx.net +++ GMX - die erste Adresse für Mail, Message, More! +++

2 2

AW: [suse-autoinstall] auto install with service pack
by Martin.Linten＠rzf.fin-nrw.de 14 Oct '03

14 Oct '03

Hallo Anas, hallo list! I am trying to install sles8 with service pack 2 in an automated way. The kernel and the inird from the sp2-CD (chosen because of hardware support) are booted via pxe. When checking the software selection I always get a long list of dependency errors beginning with "aaa_skel not available..." and so on. Please help and tell me how I can do better! I suppose it has nothing to do with the /UnitedLinux-i386-1 directory, but maybe I am wrong... My nfs-exported directory for linuxrc looks like this: |--boot | `--loader |--content (file from sles8) |--media.1 (from sles8) |--sles8 | |--UnitedLinux | |--boot | |--docu | |--dosutils | |--media.1 | |--media.2 | |--media.3 | |--suse | `--yast |--sp2 | |--UnitedLinux | |--boot | |--docu | |--i386 | |--images | |--linux | `--media.1 `--yast |--ul |--instorder (file) `--order (file) I011-52:/autoinst/suse/sles8sp2/yast # cat order /sles8 /sles8 /sp2 /sp2 I011-52:/autoinst/suse/sles8sp2/yast # cat instorder # I want to prefer sp2 packages if possible /sp2 /sp2 /sles8 /sles8 Thanks a lot, Martin -----Ursprüngliche Nachricht----- Von: Anas Nashif [mailto:nashif@suse.de] Gesendet am: Dienstag, 15. Juli 2003 09:39 An: Aaron McSorley Cc: suse-autoinstall(a)suse.com Betreff: Re: [suse-autoinstall] auto install with service pack Hi, It can be done in an automated way. For example, my nfs export for SLES8 i386 with SP2 looks like this: |-- SP2 | |-- UnitedLinux | |-- boot | |-- docu | |-- i386 | |-- images | |-- linux | `-- media.1 |-- SuSE-Linux-SLES-i386-8 | `-- CD1 | |-- boot | |-- docu | |-- media.1 | |-- suse | `-- yast |-- UnitedLinux-i386-1 | |-- CD1 | | |-- UnitedLinux | | |-- boot | | |-- docu | | |-- dosutils | | `-- media.1 | `-- CD2 | |-- UnitedLinux | |-- boot | `-- media.2 |-- boot | `-- loader |-- media.1 `-- yast `-- ul in the directory yast, there are 2 files: order and instorder This is the content which references the location of the root of every source. (where the media.1 directory is available) # cat yast/instorder /UnitedLinux-i386-1/CD1 /UnitedLinux-i386-1/CD1 /SP2 /SP2 /SuSE-Linux-SLES-i386-8/CD1 /UnitedLinux-i386-1/CD1 avicenna:/work/CDs/sles8-i386 # cat yast/order /SP2 /SP2 /SuSE-Linux-SLES-i386-8/CD1 /SuSE-Linux-SLES-i386-8/CD1 /UnitedLinux-i386-1/CD1 /UnitedLinux-i386-1/CD1 (delimiter is tab) more details can be found at http://www.suse.de/~nashif/autoinstall/8.1/html/advanced.html#AEN1251 Hope that helps... Anas Aaron McSorley wrote: > Is there a method for incorporating a service pack into an > auto install of SLES8. > > I tried putting the service pack in its own directory in my auto install > repository > and giving it preference in the order and instorder directories. > The install starts ok but, after package install I get alot of package > install failures. > After hitting ok to the fail log it prompts me to insert the service > pack cdrom. > > I thought about just replacing the original packages with the new ones > from the service pack but, > I would like to keep the service pack separate from the original > repository so I can > install without it if I want. > > thanks > -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

2 1