October 2003 - openSUSE Autoinstall - openSUSE Mailing Lists

SWAT (Samba Web Admnistration Tool) installation with Yast2, SuSe 8.2
by Yvon Nedonchelle 11 Dec '03

11 Dec '03

Hello. I have installed the Samba packages supplied with SuSe 8.2, using Yast2. Samba works fine but SWAT is not usable. When calling http://localhost:901 from Konqueror, the answer is : Impossible to connect to localhost (port 901). Looks funny because I had no problem with older version of SuSe. The various files involved, /etc/inedt, /etc/services look fine. What should I do to obtain SWAT ? Thanks -- Yvon Nedonchelle

2 1

Post-package.
by Miro 14 Nov '03

14 Nov '03

Hi, I am trying to install proftpd and proftpd-inetd using the "post-package" tag, but cant get it to work no matter what.! i've created a new package description with create_package_descr, and when i launch yast on the target system, the proftpd and proftpd-inetd packages are available. Here is the software section of the autoinstall.xml: <software> <post-packages config:type="list"> <package>proftpd</package> <package>proftpd-inetd</package> </post-packages> <base>Miniftp</base> The post-package tag dosent even work if proftpd is included in the Miniftp.sel file. but installs fine without the post-package tag. The reason why i want to use the post-package tag is that when i install the proftpd-inetd package without the tag, the original file (inetd.conf) is renamed to .newrpm and the new inetd.conf now only contains the proftpd section.! -- Thanks and best regards Miro Barbu.

3 2

Re: [suse-autoinstall] info file location
by damien.selles＠eu.effem.com 03 Nov '03

03 Nov '03

Hi larry, That depends on the way you created your bootable cd. Assuming you did it with el torrito method, I suggest you put the info file in the same place as the image of your bootable floppy. for example on the Suse CD, this image is in /boot/loader/ then just copy your infofile in taht directory. Once the image of the floppy will be loaded, infofile will be considered to be placed on the root. hoping this will help you, Regards, Damien Selles Larry O'Neil <larry(a)netsoc.ucd.ie> netsoc.ucd.ie 30/10/2003 16:41 To: suse-autoinstall(a)suse.com cc: Subject: [suse-autoinstall] info file location Hi, i have the autoinstallation working perfectly with the info file on the floppy, but is there a way to read the info file from a bootable cd? placing it on the root of the cd doesnt seem to work... has anobody got any suggestions? Thank you Larry O'Neill -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

2 2

Modifications to CD1
by Robison, Jonathon (M.) 02 Nov '03

02 Nov '03

I have come to the conclusion that because of the differences in hardware in all my test clients, I cannot use the normal autoyast xml file methods. I have been forced to instead change default.sel to ensure my package choices. This ensures that the normal installations hardware setup systems work to make sure my clients get what their individual hardware needs. My next step is two-fold. I need to strip CD1 of all the rpm packages, and modify the boot choices so that the "Installation" options use my NFS server instead of the CD. Anyone care to point me in the right direction on that one? Secondly, during the normal install process users are asked to choose between "Minimal, Minimal with X, default " etc., etc. I need to change that to 1. Normal office user 2. J2EE Developer 3. Systems Developer 4. Kitchen sink. This is NOT in the "choose individual packages" selection, but rather the normal install menu that comes before that. Any ideas on how to change the normal install process/CD to show my menu choices instead of the regular ones? Regards, Jonathon M. Robison Linux Integration Architect SIE/Advanced Technology Ford Motor Company

2 1

Problems with existing raids
by Matthew Reeves 30 Oct '03

30 Oct '03

I'm having a problem with autoinstall on systems with preexisting raids. I've got a prescript that wipes out the disk partitions on install but when yast gets to the creating raid section it fails. Is there a way around this? Thanks, Matt

2 1

info file location
by Larry O'Neil 30 Oct '03

30 Oct '03

Hi, i have the autoinstallation working perfectly with the info file on the floppy, but is there a way to read the info file from a bootable cd? placing it on the root of the cd doesnt seem to work... has anobody got any suggestions? Thank you Larry O'Neill

1 0

Questions about per-CD repository
by Fermín Galán 23 Oct '03

23 Oct '03

Hello, >From 5.5.1 of http://www.suse.de/~nashif/autoinstall/8.1/autoyast2.pdf there are two ways of building SuSE 8.1 repository: 1. Single directory. If generated from merging CDs, create_packages_descr have to be run to rebuild packages database. 2. Many directory (one per CD). I'm performing tests with the second configuration, but I have some questions: 1. Do I need to run create_packages_descr inside each CD directory? For example cd /data/SUSE81/CD1/suse /usr/lib/YaST/bin/create_package_descr cd /data/SUSE81/CD2/suse /usr/lib/YaST/bin/create_package_descr cd /data/SUSE81/CD3/suse /usr/lib/YaST/bin/create_package_descr ... 2. Section 4.1.5.3 explains how to add custom packages to the repository, adding it to the appropriated subdirectory (noarch, i386, i586, etc.) and then running create_package_descr. In the case of just one directory, there is no doubt about where to place the .rpm, but what about when having per-CD directories? For example, what 'noarch' (CD1/suse/noarch, CD2/suse/noarch/, etc) to use? 3. What is a how to use the EXTRA_PROV_FILE file (-x switch of create_package_descr)? 4. When I'm trying to autoinstall using the per-CD repository (install=nfs://server/data/SUSE81/CD1/ autoyast=nfs://server/data/profile.xml and the like) I seems like the autoinstaller couldn't see .rpms not in CD1 (that is, .rpms in CD2, CD3, CD4 and CD5). Maybe a problem building the packages database? What packages databases are used by the autoinstaller (only CD1/suse/setup/descr or also CD2/suse/setup/descr, CD3/suse/setup/descr, etc.)? Thanks in advance! --------- Fermín

2 1

install into a partition
by Michael Binder 23 Oct '03

23 Oct '03

Hi, is it possible to install SuSE via autoyast into an empty existing Partition without changing other partitons?? If yes - is there an example-xml-stream for this? thanks ------------------------------------------------------------------------------- Michael Binder Gesellschaft f. wissenschaftliche Datenverarbeitung mbH Goettingen Am Fassberg D-37077 Goettingen Phone: +49 551/201-1529 Fax: +49 551/21119 E-Mail: mbinder(a)gwdg.de

1 0

Re: [suse-autoinstall] more autoinstall questions
by Robison, Jonathon (M.) 22 Oct '03

22 Oct '03

It's my understanding that the system always boots into runlevel 3 on the first boot. Reboot and it should go to 5. Regards, Jonathon M. Robison Linux Integration Architect SIE/Advanced Technology Ford Motor Company 313-323-9529

2 1

more autoinstall questions
by Dan Transue 22 Oct '03

22 Oct '03

Hello, It's me again :-) I've done several hands off autoinstalls and have a couple of problems. First of all, I am not going to run level 5 despite the following in my autoinst.xml file: <runlevels> <default>5</default> <services config:type="list"/> </runlevels> It always comes up in run-level 3. /etc/inittab has the correct entry (id:5:initdefault) so after I reboot, everything is fine. Is this a bug? Does something tell the system to only go to run-level 3? Along the same lines, the keyboard keymapping is always de despite the fact that I have en_US set for language and english-us set for keymap: <keyboard> <keymap>english-us</keymap> </keyboard> <language>en_US</language> After I run yast2 keyboard and hit accept (English is already selected) everything seems fine. Is de the default and the XF86Config file just not being written properly? yast2 seems to be updating /etc/sysconfig/keyboard. What might be wrong here? Root password and pre-scripts/post-scripts are not being executed at all. Here is what I have: Root: <users config:type="list"> <user> <encrypted config:type="boolean">true</encrypted> <user_password>password</user_password> <username>root</username> </user> </users> I've tried "password" as above and the MD5 encrypted string with the same results. No password is set. pre-post-scripts: <post-scripts> <script> <filename>post.sh</filename> <interpreter>shell</interpreter> <source><![CDATA[#!/bin/sh echo "Running Post-install script" ls -lR /tmp df -k /bin/rpm -e autofs /sbin/yast2 -i autofs4 cat /etc/modules.conf | sed -e 's/^#.*alias autofs/alias autofs/' > ttt.new && mv ttt.new /etc/modules.conf /sbin/depmod -a ]]></source> </script> </post-scripts> <pre-scripts> <script> <filename>pre.sh</filename> <interpreter>shell</interpreter> <source><![CDATA[#!/bin/sh echo "Running pre-install script" ls -lR /tmp df -k ]]></source> </script> </pre-scripts> Neither one works. What am I missing? What is the controlling factor when doing an unattended install? When I do this with CD's I don't have these problems! I'm sure there are and will be other questions but that's it for now. Thanks in advance, -dan

1 0

Remove lvm prescripts for autoyast
by howardc 22 Oct '03

22 Oct '03

Hi, I made that script based in a script posted in the list. But it's different from the original. Some bug fixes. enjoy: ######################## <pre-scripts config:type="list"> <script> <filename>/vgremove.sh</filename> <interpreter>shell</interpreter> <source> <![CDATA[ #!/bin/sh vgs=`find /dev -name vg*` insmod lvm-mod vgscan for vg in $vgs do if [ -d $vg ] ; then vgchange -a y $vg lvs=`ls $vg` for lv in $lvs do if [ $lv != "group" ]; then lvremove -f $vg/$lv fi done vgchange -a n $vg vgremove $vg fi done mkswap /dev/cciss/c0d0 exit 0 ]]> </source> </script> </pre-scripts> ##################### __________________________________________________________________________ Acabe com aquelas janelinhas que pulam na sua tela. AntiPop-up UOL - É grátis! http://antipopup.uol.com.br/

1 0

Server OS and repository versions must match?
by Fermín Galán 21 Oct '03

21 Oct '03

Hello, I have been using (since a couple of month ago and without significant problems) a server repository to network-install clients. The server ran SuSe 8.1 and had a SuSE 8.1 repository. The problems arise when changing server OS to SuSE 8.2, but without changing the repository (SuSE 8.1). Now, when I try to network-install a SuSE 8.1 client system, I get a error message telling me about problems with 'so' (dynamic libraries) files. The things seems starting to fail after "integrating the shared objects of the installation system...". The next message in the console log is "ld cannot mmap /usr/lib/lib.opt.so.0", followed by several similar message about other so libraries and a halt. Is not possible to have a SuSE 8.2 to serve a SuSE 8.1 repostory? Must match OS and repository version in the server? Any idea or suggestion? Thanks in advance! --------- Fermín

2 2

suse 82 autoyast install order
by Egan Ford 21 Oct '03

21 Oct '03

I have observed the following install order with sles8 and suse81: run pre script install packages run chroot script reboot run post script With suse82: run pre script install SOME packages run chroot script reboot install rest of packages run post script Is there a script I can insert between the reboot and the "install rest of packages" with suse82?

2 1

Autoyast addon/package selection
by Egan Ford 21 Oct '03

21 Oct '03

How do I determine legal names to use for base, add-on, and package from the contents of the CD? Also is there a way to specify everything?

2 1

partition woes
by Dan Transue 21 Oct '03

21 Oct '03

Greetings, I'm having a problem with autoinstall and partition sizing. I have it doing everything correctly (as far as I can tell so far) but no matter what I put for partition size, I keep getting an error popup telling me that "The selected partitions are not big enough to contain a minimal installation". Here is what I have: <partitioning config:type="list"> <drive> <device>/dev/hda</device> <partitions config:type="list"> <partition> <crypt_fs config:type="boolean">false</crypt_fs> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <mount>/</mount> <size>max</size> </partition> <partition> <crypt_fs config:type="boolean">false</crypt_fs> <crypt_key></crypt_key> <format config:type="boolean">true</format> <mount>swap</mount> <size>auto</size> </partition> </drive> </partitioning> I have set the max size to 20gb (and other numbers too) to no avail. Can someone point me in the right direction? There is just under 30 gb of unpartitioned space on a 40 GB drive. Win2k is on the first 8 gb. Thanks in advance. -dan

2 1

Create a Packagedatabase
by Michael Schulz 21 Oct '03

21 Oct '03

Hello, I createt the the direcotry /home/suse in this dir I created an i586,i686 and an noarch folder. In this folders I copied the content of the folders i586,i686 and noarch from the CD1, CD2 and CD3. After this I did this: linux:/ # cd /home/suse linux:/home/suse # create_package_descr -d /home/suse using settings: datadirs: /home/suse languages: english output dir: ./setup/descr/ creating output directory ./setup/descr/ extra_provides: /usr/share/autoinstall/EXTRA_PROV .............................................................................................................................................. done processed 1423 packages now recoding to UTF-8: packages packages.DU packages.en linux:/home/suse # Then I added the dir /home/suse to the YAST2 Installation Source. There are now only this source. When I now want to sellect any packets from my autoyast PACKAGESELECTION I didn't see anything. Can anybody say me why I can't select the Packages. 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! +++

1 0

Re: [suse-autoinstall] Avoid Accept COPYRIGHT
by damien.selles＠eu.effem.com 20 Oct '03

20 Oct '03

Hi, You can just rename/remove the file **/media.1/info.txt In case of a fully automated install, it can be helpfull.. Regards, Damien. Alfred Isele <Alfred.Isele(a)fujitsu-siemens.com> fujitsu-siemens.com 20/10/2003 16:06 To: suse-autoinstall(a)suse.com cc: Subject: [suse-autoinstall] Avoid Accept COPYRIGHT Hello! How can I get rid of the COPYRIGHT "Accept" question at the start of an autoyast installation? Regards Alfred -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

Avoid Accept COPYRIGHT
by Alfred Isele 20 Oct '03

20 Oct '03

Hello! How can I get rid of the COPYRIGHT "Accept" question at the start of an autoyast installation? Regards Alfred

1 0

Installation repositiry from CD images
by Harald.Milz＠computacenter.com 20 Oct '03

20 Oct '03

Hi, I am trying to set up an installation server from the respective CD images. I would like to just keep the images on the machine and mount them loop,ro, like /pub/SLD /pub/SLD/CD1 /pub/SLD/CD2 /pub/SLD/CD3 /pub/SLD/CD4 /pub/SLD/CD5 /pub/SLD/ISO /pub/SLES8-AMD64 /pub/SLES8-AMD64/ISO /pub/SLES8-AMD64/SLES8-CD1 /pub/SLES8-AMD64/SLES8-CD2 /pub/SLES8-AMD64/SLES8-CD3 /pub/SLES8-AMD64/SLES8-CD4 etc.... The ISO directories keep the images, the CD1,2,3.. directories are the mountpoints. I can't find any way to actually treat this structure as installation repositories. Has anybody had the same problem and can provide a nice solution? I would guess order / instorder is a solution but SLD and SuSE-8.2 don't have the yast directory. Seems I don't get it. Mit freundlichen Gruessen - Best regards Harald Milz Senior Consultant Enterprise Computing Solutions CC CompuNet AG & Co. oHG A part of Computacenter plc Hoerselbergstrasse 7, 81677 Muenchen, Germany Phone: +49 (0)89 45712-161, Fax: -331, Mobile: +49 (0)173 3866604 E-Mail : Harald.Milz(a)computacenter.com Visit us on the Internet: http://www.computacenter.com This email is confidential. If you are not the intended recipient, you must not disclose or use the information contained in it. If you have received this mail in error, please tell us immediately by return email and delete the document.

1 0

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

17 Oct '03

That's it, thank You! Now it works... -----Ursprüngliche Nachricht----- Von: Aaron McSorley [mailto:aaron.mcsorley@amd.com] Gesendet am: Dienstag, 14. Oktober 2003 19:26 An: Martin.Linten(a)rzf.fin-nrw.de Cc: nashif(a)suse.de; suse-autoinstall(a)suse.com Betreff: Re: AW: [suse-autoinstall] auto install with service pack try using separate directories for unitedlinux and sles8 and try using tabs(not spaces) in your order and instorder files On Tue, 14 Oct 2003 Martin.Linten(a)rzf.fin-nrw.de wrote: > 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 > > > > > -- _______ 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 -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

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

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

14 Oct '03

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> > > > > > >

2 1

Values for base and addon keys
by Dan Transue 14 Oct '03

14 Oct '03

Greetings, Where do I find out what are the valid values for the base and addon keys in the autoinst.xml file? I keep getting errors in my software configuration section of the install and am trying to strip it down to bare-bolts and work my way back up! Any help would be greatly appreciated! Thanks in advance. -dan

2 1

minor yast2/autoyast bugs(?)
by darby 14 Oct '03

14 Oct '03

(sorry if this gets posted twice) Hi, Noticed a couple minor bugs (feature requests?) with yast2/autoyast: * The file browser selection doesn't reflect the current file being edited. * When configuring software selections, if you select "default system" and then enter "detailed selection" and uncheck "office apps", that setting doesn't seem to stick. If you leave the software selection and return to it, "office apps" has a check by it again. * When adding a new drive partition, the boot loader section automatically configures itself to use that partition. But if you replace that partition, the bootloader doesn't update itself to the change. This is using yast2/autoyast with SuSE 8.2. Like I said, minor stuff, but thought I'd pass it along... Thanks, Darby

3 2

partition error
by Berge, Harry ten 14 Oct '03

14 Oct '03

Hi, At the start of the installation autoyast pauses with the following error: "The partitioning on your disk /dev/hdc is not readable by the partitioning tool 'parted' that YaST2 uses to change the partition table". But this is not correct, because parted *CAN* read the partition table. This disk is a set of 2 disks with a LVM partition. I want YaST2 to leave this disk alone. I did some research by myself and I can see in the logfile (/var/log/YaST2/y2log) that the module StorageDevices indeed returns a 'false'. In the next fragment of the logfile first there is the detection of the disk on /dev/hdb, and then of /dev/hdc. 2003-10-16 19:31:03 <1> linux(543) [YCP] modules/StorageDevices.ycp(CheckPartedValid):861 disk /dev/hdb ret:true 2003-10-16 19:31:03 <1> linux(543) [YCP] modules/StorageDevices.ycp(CheckPartedValid):861 disk /dev/hdc ret:false Anyone an idea why this 'CheckPartedValid' returns false? Is it possible to disable this 'scan' of disks? > Met vriendelijke groet / Mit freundlichen Grüßen / Kind Regards, > H.J. ten Berge Test & Integration HITT Traffic Oude Apeldoornseweg 41-45 P.O. Box 717 NL-7300 AS, APELDOORN The Netherlands Telephone +31-55-543 26 34 Fax +31-55-543 25 53 E-mail mailto:berge@hitt.nl Internet http://www.hitt-traffic.nl

1 0

Using PXELinux for 8.1 Auto Install
by fetak＠comcast.net 13 Oct '03

13 Oct '03

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>

2 1

[Fwd: Returned mail: see transcript for details]
by Robison, Jonathon (M.) 13 Oct '03

13 Oct '03

Sorry for the spam folks, but this seems the only way to tell this guy that his email is bouncing. William Wolfe - yer bouncing! --jmr

1 0

RE: [suse-autoinstall] Terrible trouble installing SuSE 8.2
by Robison, Jonathon (M.) 13 Oct '03

13 Oct '03

Strange as it may sound, could it be perhaps that the reiser module is not being loaded when you did the module load (prior to CD reading, etc.)? Try adding reiserfs.o to your list of modules to load from floppy. Reiser is not compiled into the default kernel. It is a module to the kernel. Perhaps the reason ext2/3 worked is because that most likely IS compiled into the kernel. The rule of thumb I always use is /boot gets ext2, / gets reiser. Of course, I could be full of sh*t, but it's worth a try. I install on all kinds of SCSI drives all the time, and never have a problem, but then I install by booting the CD (which does load the reiser module during boot). --Jon Robison On Mon, 2003-10-13 at 07:35, William Wolfe wrote: > Hi Antoine, > > Merveilleux, merci beaucoup !! > > Yes, just by using a different file system type YaST is able to > continue the installation on my SCSI hardware. It is rolling away > right now, loading from the CD. > > > So the learning experience from this is that Reiser FS is not > compatable with Wide SCSI disks ? That seems to exclude a lot of SCSI > users from the benefits of the FS type that is selected by default by > the YaST partitioning tool. I think I should look a bit more into the > different FS types supported by SuSE, and look for the best > compromise of good use of space, journaling and fault tollerance and > something that works with my hardware. I also need to read up about > LVM on Linux, because on some of my machines I will want to stack up > the SCSI disks. But that is further up the learning curve. > > Now how do we go about making an addition to the product documentation > ? There is no mention of the significance of the FS type and your > hardware in the User Guide. I had a look in the Administrators > Guide, and FS types are discusses in the appendinx at the back, but I > didn't notice any mention of limitations with SCSI in the ReiserFS > section. Should this be added to the SuSE Support Database as an > article ? Is there some other knowledge base that accumulates this > sort of wisdom ? > > Thanks again. I can't wait to start clicking away on the KDE screen. > All the Best, William. > > > Theytaz Antoine <Antoine.Theytaz(a)gmvs.migros.ch> wrote: > hello William, > > your kernel seem to hang when dealing with reiserfs filesystem > (module) and > your SCSI controller/disk > > So try choosing the ext2 filesystem instead of reiserfs, just to see > what's > happening this time :) > > > Antoine > > > -----Message d'origine----- > De : William Wolfe [mailto:w_j_wolfe@yahoo.co.uk] > EnvoyÃ© : lundi, 13. octobre 2003 10:31 > ÃEUR : suse-autoinstall(a)suse.com > Objet : [suse-autoinstall] Terrible trouble installing SuSE 8.2 > > > HELP, please. > > This is my first installation experience of linux, after years as a > Windows + UNIX user. I am using the SuSE 8.2 Professional CD > installation, having just bought it on Saturday. > > I am making a commitment to move away from Windows after a year of > virus scares and systems crashing frequently. It sounds like Linux has > come a long way in recent years on the desktop and availablility of > friendly > apps. I'm really looking forward to getting it working. > > So I set out on a fresh start with Linux. I started the install using > a > floppy bootdisk that I downloaded, with a couple of module disks until > the CD takes over. (This PC won't boot from CD) Using YaST, I deleted > the partitions used by Windows and manually created partitions to load > SuSE. But it doesn't seem to matter if I create the partitions or take > what is suggested, after formatting the partitions of the hard disk, > the installation comes to a halt when YaST tries to mount the > partitions. I > keep getting stuck at this point :-(( and cant seem to get round it. > Please help. > > I get a pop up error message saying > > YaST2 > > Could not mount partition /dev/sda4 to /mnt/. > > Continue if you know what you are doing, but it would be safer to > reboot and try again. > > If I click continue it pops up a similar message for the next > partition. If I click the other buttons it hangs. > > I'm quite confused about what's going wrong. Some discussions I read > suggest problems with the partitioning information. Others hint at > bugs > in the YaST utility. > > If anyone could point me in the right direction I'd be very > greatefull. > > > > I had manually created the following partitions using the partition > features for YaST > > All are primary partitions. > > /dev/sda1 in format EXT2 23.5Mb for /boot > > /dev/sda2 in format swap 258.8Mb for swap > > The rest in format reiserfs for / root, which becomes /dev/sda4 > > > > Here is some more information from other screens, and the > specification > of the PC is at the bottom. > > I tried searching the web and the SuSE Support Database, but even > after > trying the following solutions I can't get round this problem. > > SDB Manual Partitioning with YaST2 > http://sdb.suse.de/en/sdb/html/thallma_y2_partition.html > > SDB Partitioning for SuSE Linux > http://sdb.suse.de/en/sdb/html/thallma_partition.html > > These discussions seem to show the same symptom, but don't show a > solution :- > > http://lists.suse.com/archive/suse-linux-e/2002-Jul/2625.html > > http://lists.suse.com/archive/suse-linux-e/2002-Jun/3234.html > > > > Just before launching the install I swtiched the display > > When I examine screen Ctrl + Alt + F2 > > and used a command to confirm the contents of the partition table > > > > # fdisk -l > > Disk /dev/sda: 4294 MB, 429467293 bytes > > 255 heads, 63 sectors/track, 522 cylinders > > Units = of 16065 * 512 = 8225280 bytes > > Device Boot Start End Blocks Id System > > /dev/sda1 1 3 24066 83 Linux > > /dev/sda2 4 36 265072+ 82 Linux > > /dev/sda3 37 62 208845 83 Linux > > /dev/sda4 63 522 3694950 83 Linux > > > > After seeing the error message I tried to use this screen to manually > mount the partition with this command > > # mount -v /dev/sda4 / > > mount: you didn't specify a filesystem type for > > I will try type reiserfs > > (Which is fine because that is what I specified when creating the > partition ) > > > > When I examine screen Ctrl + Alt + F3 I see good progress until the > last few lines which are as follows... > > Setting up localhost.....done > > going for automatic install > > mount: /var/adm/mount/boot/root: we need a loop device > > mount: using /dev/loop0 > > rmmod usb-storage > > starting /mounts/instsys/sbin/inst_setup yast > > > > When I examine screen Ctrl + Alt + F4 I see steady progress then a > full > screen of data as the mounting begins. > > Oct 12 17:01:05 (none) kernel: Oops: 0000 2.4.20-4GB #1 Wed Apr 16 > 14:50:03 UTC 2003 > > Oct 12 17:01:05 (none) kernel: CPU: 0 > > Oct 12 17:01:05 (none) kernel: EIP: 0010:[<00000000>] Not tainted > > Oct 12 17:01:05 (none) kernel: EFLAGS: 00010246 > > and so on........ > > The last lines read.. > > Oct 12 17:01:05 (none) kernel: Modules: > [(reiserfs::)] > > Oct 12 17:01:05 (none) kernel: Code: Bad EIP value. > > Thank you in advance for your help. > > I look forward to hearing from you. > > Cheers, William. > > > > Pentium P160 > > 64 Mb memory > > Micron Electronics Motherboard > > PhoenixBIOS > > SCSI Adapter card AHA-2940 ULTRA/ULTRA W > > Hard disk CONNER CFP4207SV 4.28Gb > > > > > > > --------------------------------- > Want to chat instantly with your online friends? Get the FREE > Yahoo!Messenger > > -- > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > For additional commands, e-mail: suse-autoinstall-help(a)suse.com > > > > --------------------------------- > Want to chat instantly with your online friends? Get the FREE > Yahoo!Messenger >

1 0

RE: [suse-autoinstall] Terrible trouble installing SuSE 8.2
by Theytaz Antoine 13 Oct '03

13 Oct '03

hello William, your kernel seem to hang when dealing with reiserfs filesystem (module) and your SCSI controller/disk So try choosing the ext2 filesystem instead of reiserfs, just to see what's happening this time :) Antoine -----Message d'origine----- De : William Wolfe [mailto:w_j_wolfe@yahoo.co.uk] Envoyé : lundi, 13. octobre 2003 10:31 À : suse-autoinstall(a)suse.com Objet : [suse-autoinstall] Terrible trouble installing SuSE 8.2 HELP, please. This is my first installation experience of linux, after years as a Windows + UNIX user. I am using the SuSE 8.2 Professional CD installation, having just bought it on Saturday. I am making a commitment to move away from Windows after a year of virus scares and systems crashing frequently. It sounds like Linux has come a long way in recent years on the desktop and availablility of friendly apps. I'm really looking forward to getting it working. So I set out on a fresh start with Linux. I started the install using a floppy bootdisk that I downloaded, with a couple of module disks until the CD takes over. (This PC won't boot from CD) Using YaST, I deleted the partitions used by Windows and manually created partitions to load SuSE. But it doesn't seem to matter if I create the partitions or take what is suggested, after formatting the partitions of the hard disk, the installation comes to a halt when YaST tries to mount the partitions. I keep getting stuck at this point :-(( and cant seem to get round it. Please help. I get a pop up error message saying YaST2 Could not mount partition /dev/sda4 to /mnt/. Continue if you know what you are doing, but it would be safer to reboot and try again. If I click continue it pops up a similar message for the next partition. If I click the other buttons it hangs. I'm quite confused about what's going wrong. Some discussions I read suggest problems with the partitioning information. Others hint at bugs in the YaST utility. If anyone could point me in the right direction I'd be very greatefull. I had manually created the following partitions using the partition features for YaST All are primary partitions. /dev/sda1 in format EXT2 23.5Mb for /boot /dev/sda2 in format swap 258.8Mb for swap The rest in format reiserfs for / root, which becomes /dev/sda4 Here is some more information from other screens, and the specification of the PC is at the bottom. I tried searching the web and the SuSE Support Database, but even after trying the following solutions I can't get round this problem. SDB Manual Partitioning with YaST2 http://sdb.suse.de/en/sdb/html/thallma_y2_partition.html SDB Partitioning for SuSE Linux http://sdb.suse.de/en/sdb/html/thallma_partition.html These discussions seem to show the same symptom, but don't show a solution :- http://lists.suse.com/archive/suse-linux-e/2002-Jul/2625.html http://lists.suse.com/archive/suse-linux-e/2002-Jun/3234.html Just before launching the install I swtiched the display When I examine screen Ctrl + Alt + F2 and used a command to confirm the contents of the partition table # fdisk -l Disk /dev/sda: 4294 MB, 429467293 bytes 255 heads, 63 sectors/track, 522 cylinders Units = of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sda1 1 3 24066 83 Linux /dev/sda2 4 36 265072+ 82 Linux /dev/sda3 37 62 208845 83 Linux /dev/sda4 63 522 3694950 83 Linux After seeing the error message I tried to use this screen to manually mount the partition with this command # mount -v /dev/sda4 / mount: you didn't specify a filesystem type for I will try type reiserfs (Which is fine because that is what I specified when creating the partition ) When I examine screen Ctrl + Alt + F3 I see good progress until the last few lines which are as follows... Setting up localhost.....done going for automatic install mount: /var/adm/mount/boot/root: we need a loop device mount: using /dev/loop0 rmmod usb-storage starting /mounts/instsys/sbin/inst_setup yast When I examine screen Ctrl + Alt + F4 I see steady progress then a full screen of data as the mounting begins. Oct 12 17:01:05 (none) kernel: Oops: 0000 2.4.20-4GB #1 Wed Apr 16 14:50:03 UTC 2003 Oct 12 17:01:05 (none) kernel: CPU: 0 Oct 12 17:01:05 (none) kernel: EIP: 0010:[<00000000>] Not tainted Oct 12 17:01:05 (none) kernel: EFLAGS: 00010246 and so on........ The last lines read.. Oct 12 17:01:05 (none) kernel: Modules: [(reiserfs:<c0c00060>:<c0c30f74>)] Oct 12 17:01:05 (none) kernel: Code: Bad EIP value. Thank you in advance for your help. I look forward to hearing from you. Cheers, William. Pentium P160 64 Mb memory Micron Electronics Motherboard PhoenixBIOS SCSI Adapter card AHA-2940 ULTRA/ULTRA W Hard disk CONNER CFP4207SV 4.28Gb --------------------------------- Want to chat instantly with your online friends? Get the FREE Yahoo!Messenger

2 1

Terrible trouble installing SuSE 8.2
by William Wolfe 13 Oct '03

13 Oct '03

HELP, please. This is my first installation experience of linux, after years as a Windows + UNIX user. I am using the SuSE 8.2 Professional CD installation, having just bought it on Saturday. I am making a commitment to move away from Windows after a year of virus scares and systems crashing frequently. It sounds like Linux has come a long way in recent years on the desktop and availablility of friendly apps. I'm really looking forward to getting it working. So I set out on a fresh start with Linux. I started the install using a floppy bootdisk that I downloaded, with a couple of module disks until the CD takes over. (This PC won't boot from CD) Using YaST, I deleted the partitions used by Windows and manually created partitions to load SuSE. But it doesn't seem to matter if I create the partitions or take what is suggested, after formatting the partitions of the hard disk, the installation comes to a halt when YaST tries to mount the partitions. I keep getting stuck at this point :-(( and cant seem to get round it. Please help. I get a pop up error message saying YaST2 Could not mount partition /dev/sda4 to /mnt/. Continue if you know what you are doing, but it would be safer to reboot and try again. If I click continue it pops up a similar message for the next partition. If I click the other buttons it hangs. I'm quite confused about what's going wrong. Some discussions I read suggest problems with the partitioning information. Others hint at bugs in the YaST utility. If anyone could point me in the right direction I'd be very greatefull. I had manually created the following partitions using the partition features for YaST All are primary partitions. /dev/sda1 in format EXT2 23.5Mb for /boot /dev/sda2 in format swap 258.8Mb for swap The rest in format reiserfs for / root, which becomes /dev/sda4 Here is some more information from other screens, and the specification of the PC is at the bottom. I tried searching the web and the SuSE Support Database, but even after trying the following solutions I can't get round this problem. SDB Manual Partitioning with YaST2 http://sdb.suse.de/en/sdb/html/thallma_y2_partition.html SDB Partitioning for SuSE Linux http://sdb.suse.de/en/sdb/html/thallma_partition.html These discussions seem to show the same symptom, but don't show a solution :- http://lists.suse.com/archive/suse-linux-e/2002-Jul/2625.html http://lists.suse.com/archive/suse-linux-e/2002-Jun/3234.html Just before launching the install I swtiched the display When I examine screen Ctrl + Alt + F2 and used a command to confirm the contents of the partition table # fdisk -l Disk /dev/sda: 4294 MB, 429467293 bytes 255 heads, 63 sectors/track, 522 cylinders Units = of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sda1 1 3 24066 83 Linux /dev/sda2 4 36 265072+ 82 Linux /dev/sda3 37 62 208845 83 Linux /dev/sda4 63 522 3694950 83 Linux After seeing the error message I tried to use this screen to manually mount the partition with this command # mount -v /dev/sda4 / mount: you didn't specify a filesystem type for I will try type reiserfs (Which is fine because that is what I specified when creating the partition ) When I examine screen Ctrl + Alt + F3 I see good progress until the last few lines which are as follows... Setting up localhost.....done going for automatic install mount: /var/adm/mount/boot/root: we need a loop device mount: using /dev/loop0 rmmod usb-storage starting /mounts/instsys/sbin/inst_setup yast When I examine screen Ctrl + Alt + F4 I see steady progress then a full screen of data as the mounting begins. Oct 12 17:01:05 (none) kernel: Oops: 0000 2.4.20-4GB #1 Wed Apr 16 14:50:03 UTC 2003 Oct 12 17:01:05 (none) kernel: CPU: 0 Oct 12 17:01:05 (none) kernel: EIP: 0010:[<00000000>] Not tainted Oct 12 17:01:05 (none) kernel: EFLAGS: 00010246 and so on........ The last lines read.. Oct 12 17:01:05 (none) kernel: Modules: [(reiserfs:<c0c00060>:<c0c30f74>)] Oct 12 17:01:05 (none) kernel: Code: Bad EIP value. Thank you in advance for your help. I look forward to hearing from you. Cheers, William. Pentium P160 64 Mb memory Micron Electronics Motherboard PhoenixBIOS SCSI Adapter card AHA-2940 ULTRA/ULTRA W Hard disk CONNER CFP4207SV 4.28Gb --------------------------------- Want to chat instantly with your online friends? Get the FREE Yahoo!Messenger

2 1

SLES autoinstall over http/ftp
by SLATER,CHRIS (HP-Roseville,ex1) 10 Oct '03

10 Oct '03

I saw in a previous email that http installs are not yet supported for SLES. Two questions: 1) When is it expected to be supported? 2) Are ftp installs supported? Thanks, Chris Christopher R. Slater Unix Customer Engineer Americas Service Delivery Operation - Specialized Services - Hewlett Packard Company, Roseville Site (916) tn785-1802 http://ecardfile.com/id/chris_slater

1 0

RE: [suse-autoinstall] Problems with example 4.10
by SLATER,CHRIS (HP-Roseville,ex1) 09 Oct '03

09 Oct '03

Are you sure you have an IDE drive? You might try taking out that line. Then it will just use the first device it finds (be that hda1 or sda1). Chris Christopher R. Slater Unix Customer Engineer Americas Service Delivery Operation - Specialized Services - Hewlett Packard Company, Roseville Site (916) tn785-1802 http://ecardfile.com/id/chris_slater -----Original Message----- From: Michal Kubecek [mailto:mike@mk-sys.cz] Sent: Thursday, October 09, 2003 3:57 PM To: suse-autoinstall(a)suse.com Subject: Re: [suse-autoinstall] Problems with example 4.10 On Mon, Oct 06, 2003 at 12:25:42PM +0200, Fermín Galán wrote: > I'm trying to reproduce example 4.10 at > > http://www.suse.de/~nashif/autoinstall/8.2/html/createprofile.partitioni > ng.html > > I have the following pre-partitioned system: ... > ... but when the autoinstallation begins, I get an error telling that > there is no space in /dev/hda! > > Some hint about what could be happening? Do you have the update image for autoyast installed? This happened to me with the original version from DVD (or CD's). The problem was repaired later (see the archive). Michal Kubecek -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

Problems with example 4.10
by Fermín Galán 09 Oct '03

09 Oct '03

Hello everyone. I'm trying to reproduce example 4.10 at http://www.suse.de/~nashif/autoinstall/8.2/html/createprofile.partitioni ng.html I have the following pre-partitioned system: Device Boot Start End Blocks Id System /dev/hda1 1 383 3076416 c Win95 FAT32 (LBA) /dev/hda2 384 422 313267+ 82 Linux swap /dev/hda3 * 423 1315 7173022+ 83 Linux In the control file I'm using *exactly* the same XML of the example: <partitioning config:type="list"> <drive> <partitions config:type="list"> <partition> <create config:type="boolean">false</create> <format config:type="boolean">true</format> <mount>/</mount> <partition_id config:type="integer">131</partition_id> </partition> <partition> <create config:type="boolean">false</create> <format config:type="boolean">true</format> <filesystem config:type="symbol">swap</filesystem> <mount>swap</mount> <partition_id config:type="integer">130</partition_id> </partition> </partitions> </drive> </partitioning> ... but when the autoinstallation begins, I get an error telling that there is no space in /dev/hda! Some hint about what could be happening? Thanks in advance! --------- Fermín

3 2

source directory ?
by tcook 09 Oct '03

09 Oct '03

I have about 60 64bit Opteron systems that I need to install automatically with suse. I got the first one installed fine. Then I ran the Yast control center and went to misc and ran (clone this machine) then I tried to make iso. And the source fails for some reason so I deleted all the source that was in the source config area and added the cdrom and it still fails. I need help with this source issue. Unable to locate source. ( I am coming from a redhat back ground so I am familiar with kickstart and today is the first time I have used suse). Tim Cook Linux apps C: T: ""Of all the things I've lost in my life, I miss my mind the most"" "Ozzy Ozbourne"

2 1

[ot] daemontools - rpms.
by Tarjei Huse 08 Oct '03

08 Oct '03

Hi, I saw in the archives that someone made a set daemontools rpms. Would you be so kind and send them to me? Thanks, Tarjei

1 0

Secure PXE/DHCP/AutoYaST installation?
by Harald.Milz＠computacenter.com 07 Oct '03

07 Oct '03

Hi, as I am aware that there is no out-of-the-box solution for the inherent PXE/DHCP security problem I am trying to find out how to at least make the second stage more secure. At the moment, since DHCP is broadcast, everybody with physical access to a network can install a fake DHCP server serving his or her own kernel images with back doors. As long as there is no cryptographically secure authentication on the server side a client can never be sure about the DHCP server's identity. Unfortunately, Intel dropped BIS development and support, and no hardware vendor actually supports BIS. That said, does anybody have a good idea to at least identify the install server reliably before YaST starts its work? I was thinking about using a preinstall script which uses SSH/SSL to talk to a server but the preinstall script will (or will not) be provided by a fake DHCP server so there's a catch-22 situation. Any idea? I suspect we have to abandon PXE/DHCP altogether and go for a boot CD in each server, with the install server's address hardwired. A client could use DHCP but only for getting its IP address and network parameters, but then identify the install server using SSL (in a YaST pre-install script) and then go ahead. The AutoYaST config XML file(s) would have to be on the CD as well to prevent hackers from tampering. Any comments? TIA!! Mit freundlichen Gruessen - Best regards Harald Milz Consultant Enterprise Computing Solutions CC CompuNet AG & Co. oHG

1 0

RV: [suse-autoinstall] Problems with example 4.10
by Fermín Galán 07 Oct '03

07 Oct '03

Third try :) > I cant reproduce this. Works fine for me. > Can you send me the y2log files please. I attach the last lines (I have tried to send the entire file, but mailer daemon doesn't allow big messages) of: /var/log/YaST/y2log: (...) 2003-10-08 08:51:18 <1> linux(398) [Interpreter] clients/autoinst_setup.ycp:20 Loading YCP module Timezone 2003-10-08 08:51:20 <1> linux(398) [YCP] modules/Timezone.ycp(Set):168 Set default timezone: <Europe/Madrid> 2003-10-08 08:51:20 <1> linux(398) [YCP] modules/Timezone.ycp(Set):171 Set timezone:Europe/Madrid sel:0 name:Europa / EspaÃ±a 2003-10-08 08:51:20 <1> linux(398) [Interpreter] clients/autoinst_setup.ycp:24 Loading YCP module Bootloader 2003-10-08 08:51:20 <1> linux(398) [Interpreter] modules/Bootloader.ycp:24 Loading YCP module BootCommon 2003-10-08 08:51:20 <1> linux(398) [Interpreter] routines/lilolike.ycp:22 Loading YCP module BootCommon 2003-10-08 08:51:20 <1> linux(398) [Interpreter] routines/switcher.ycp:19 Loading YCP module BootGRUB 2003-10-08 08:51:20 <1> linux(398) [Interpreter] routines/switcher.ycp:20 Loading YCP module BootLILO 2003-10-08 08:51:20 <1> linux(398) [Interpreter] routines/switcher.ycp:21 Loading YCP module BootSILO 2003-10-08 08:51:20 <1> linux(398) [Interpreter] routines/switcher.ycp:22 Loading YCP module BootMILO 2003-10-08 08:51:20 <1> linux(398) [Interpreter] routines/switcher.ycp:23 Loading YCP module BootABOOT 2003-10-08 08:51:20 <1> linux(398) [Interpreter] routines/switcher.ycp:24 Loading YCP module BootELILO 2003-10-08 08:51:20 <1> linux(398) [Interpreter] routines/switcher.ycp:26 Loading YCP module BootS390 2003-10-08 08:51:20 <1> linux(398) [Interpreter] routines/switcher.ycp:27 Loading YCP module BootPPC 2003-10-08 08:51:20 <1> linux(398) [Interpreter] clients/autoinst_setup.ycp:28 Loading YCP module AutoinstStorage 2003-10-08 08:51:20 <1> linux(398) [Interpreter] modules/AutoinstStorage.ycp:16 Loading YCP module Summary 2003-10-08 08:51:20 <1> linux(398) [Interpreter] clients/autoinst_setup.ycp:29 Loading YCP module AutoinstScripts 2003-10-08 08:51:20 <1> linux(398) [Interpreter] clients/autoinst_setup.ycp:30 Loading YCP module AutoinstGeneral 2003-10-08 08:51:20 <1> linux(398) [Interpreter] clients/autoinst_setup.ycp:31 Loading YCP module AutoinstSoftware 2003-10-08 08:51:20 <1> linux(398) [YCP] modules/AutoinstGeneral.ycp(AutoinstGeneral::Write):183 Writing general settings: keymap -> spanish, timezone -> Europe/Madrid 2003-10-08 08:51:20 <1> linux(398) [YCP] modules/Keyboard.ycp(SetLanguage):794 Setting keyboard to: <spanish> 2003-10-08 08:51:20 <1> linux(398) [YCP] modules/Keyboard.ycp(SetLanguage):805 Description for keyboard <spanish>: <[_("Spanish"), $["ncurses":"es.map.gz"]]> 2003-10-08 08:51:20 <1> linux(398) [YCP] modules/Keyboard.ycp(SetLanguage):809 Retranslating for: es_ES 2003-10-08 08:51:20 <1> linux(398) [YCP] modules/Keyboard.ycp(SetLanguage):818 x11data=$["Apply":"xfree86:complete:complete:en_US(pc102)+es:pc(pc102)", "MapName":"Standard Keyboard [ pc102 ]", "Protocol":"Standard", "XkbLayout":"es", "XkbModel":"pc102"] 2003-10-08 08:51:20 <1> linux(398) [YCP] modules/Keyboard.ycp(Keyboard::SetConsole):982 Setting console keyboard to: <spanish> 2003-10-08 08:51:20 <1> linux(398) [YCP] modules/Keyboard.ycp(Keyboard::SetConsole):984 loadkeys command: </bin/loadkeys es.map.gz> 2003-10-08 08:51:20 <1> linux(398) [YCP] modules/Keyboard.ycp(SetLanguage):794 Setting keyboard to: <spanish> 2003-10-08 08:51:20 <1> linux(398) [YCP] modules/Keyboard.ycp(SetLanguage):805 Description for keyboard <spanish>: <[_("Spanish"), $["ncurses":"es.map.gz"]]> 2003-10-08 08:51:20 <1> linux(398) [YCP] modules/Keyboard.ycp(SetLanguage):809 Retranslating for: es_ES 2003-10-08 08:51:20 <1> linux(398) [YCP] modules/Keyboard.ycp(SetLanguage):818 x11data=$["Apply":"xfree86:complete:complete:en_US(pc102)+es:pc(pc102)", "MapName":"Standard Keyboard [ pc102 ]", "Protocol":"Standard", "XkbLayout":"es", "XkbModel":"pc102"] 2003-10-08 08:51:20 <1> linux(398) [YCP] modules/Keyboard.ycp(Keyboard::SetX11):1016 Setting X11 keyboard to: <spanish> 2003-10-08 08:51:20 <1> linux(398) [YCP] modules/Keyboard.ycp(Keyboard::SetX11):1032 Setting X keyboard: /usr/X11R6/bin/xkbset -l "xfree86:complete:complete:en_US(pc102)+es:pc(pc102)" 2003-10-08 08:51:22 <1> linux(398) [YCP] modules/Timezone.ycp(Timezone::Set):171 Set timezone:Europe/Madrid sel:0 name:Europa / EspaÃ±a 2003-10-08 08:51:22 <1> linux(398) [agent-system] SystemAgent.cc(Execute):1077 mkdir /tmp/YaST2-00398-7FC2eY/pre-scripts 2003-10-08 08:51:22 <1> linux(398) [agent-system] SystemAgent.cc(Execute):1077 mkdir /tmp/YaST2-00398-7FC2eY/pre-scripts/logs 2003-10-08 08:51:22 <1> linux(398) [YCP] modules/AutoinstStorage.ycp(AutoinstStorage::Write):127 Initial Target map: $["/dev/hda":$["bios_id":"0x80", "bus":"IDE", "cyl_count":2490, "cyl_size":8224768, "label":"msdos", "max_primary":4, "model":"ST320423A", "name":"1. IDE, 19.07 GB, /dev/hda, ST320423A", "partitions":[$["detected_fs":`unknown, "device":"/dev/hda1", "fsid":12, "fstype":"Win95 FAT32 LBA", "nr":1, "region":[0, 383], "type":`primary, "used_fs":`unknown], $["detected_fs":`reiser, "device":"/dev/hda2", "fsid":130, "fstype":"Linux swap", "nr":2, "region":[383, 39], "type":`primary, "used_fs":`reiser, "uuid":"78505d8d-80d9-47fc-933f-76270d7190cb"], $["detected_fs":`unknown, "device":"/dev/hda3", "fsid":131, "fstype":"Linux native", "nr":3, "region":[422, 893], "type":`primary, "used_fs":`unknown]], "scrpath":.hda, "unique":"nBbg.6HsYcc+W4l7"]] 2003-10-08 08:51:22 <1> linux(398) [YCP] modules/AutoinstStorage.ycp(AutoinstStorage::Write):137 Drives=[$["device":"/dev/hda", "size":8224768]] 2003-10-08 08:51:22 <1> linux(398) [YCP] modules/AutoinstStorage.ycp(AutoinstStorage::Write):161 New Auto-Install tagetMap: $["/dev/hda":$["partitions":[$["create":false, "format":true, "mount":"/", "partition_id":131], $["create":false, "filesystem":`swap, "format":true, "mount":"swap", "partition_id":130]]]] 2003-10-08 08:51:22 <1> linux(398) [YCP] modules/AutoinstStorage.ycp(AutoinstStorage::Write):211 Creating partition plans for /dev/hda 2003-10-08 08:51:22 <1> linux(398) [YCP] modules/Partitions.ycp(PrepBoot):177 ret:false 2003-10-08 08:51:23 <1> linux(398) [YCP] modules/BootCommon.ycp(BootCommon::getLoaderType):452 Bootloader detection returned grub 2003-10-08 08:51:23 <1> linux(398) [YCP] modules/Storage.ycp(GetSubDevFilterList):1953 GetSubDevFilterList partitions [$["detected_fs":`unknown, "device":"/dev/hda1", "fsid":12, "fstype":"Win95 FAT32 LBA", "nr":1, "region":[0, 383], "type":`primary, "used_fs":`unknown], $["detected_fs":`reiser, "device":"/dev/hda2", "fsid":130, "fstype":"Linux swap", "nr":2, "region":[383, 39], "type":`primary, "used_fs":`reiser, "uuid":"78505d8d-80d9-47fc-933f-76270d7190cb"], $["detected_fs":`unknown, "device":"/dev/hda3", "fsid":131, "fstype":"Linux native", "nr":3, "region":[422, 893], "type":`primary, "used_fs":`unknown]] 2003-10-08 08:51:23 <1> linux(398) [YCP] modules/Storage.ycp(GetSubDevFilterList):1953 GetSubDevFilterList partitions [$["detected_fs":`unknown, "device":"/dev/hda1", "fsid":12, "fstype":"Win95 FAT32 LBA", "nr":1, "region":[0, 383], "type":`primary, "used_fs":`unknown], $["detected_fs":`reiser, "device":"/dev/hda2", "fsid":130, "fstype":"Linux swap", "nr":2, "region":[383, 39], "type":`primary, "used_fs":`reiser, "uuid":"78505d8d-80d9-47fc-933f-76270d7190cb"], $["detected_fs":`unknown, "device":"/dev/hda3", "fsid":131, "fstype":"Linux native", "nr":3, "region":[422, 893], "type":`primary, "used_fs":`unknown]] 2003-10-08 08:51:23 <1> linux(398) [YCP] modules/Storage.ycp(CheckForLvmRootFs):968 root=$[] dev=$["nr":0] 2003-10-08 08:51:23 <1> linux(398) [YCP] modules/Storage.ycp(CheckForLvmRootFs):971 ret=false 2003-10-08 08:51:23 <1> linux(398) [YCP] modules/Storage.ycp(GetSubDevFilterList):1953 GetSubDevFilterList partitions [$["detected_fs":`unknown, "device":"/dev/hda1", "fsid":12, "fstype":"Win95 FAT32 LBA", "nr":1, "region":[0, 383], "type":`primary, "used_fs":`unknown], $["detected_fs":`reiser, "device":"/dev/hda2", "fsid":130, "fstype":"Linux swap", "nr":2, "region":[383, 39], "type":`primary, "used_fs":`reiser, "uuid":"78505d8d-80d9-47fc-933f-76270d7190cb"], $["detected_fs":`unknown, "device":"/dev/hda3", "fsid":131, "fstype":"Linux native", "nr":3, "region":[422, 893], "type":`primary, "used_fs":`unknown] (The first one seems to have been generated after the partitioning fail, but I don't really sure). Do you need any other log file or specific information? -------- Fermín

1 0

RE: [suse-autoinstall] Problems with <use> and <partition_type>
by SLATER,CHRIS (HP-Roseville,ex1) 07 Oct '03

07 Oct '03

Hi, I found that if I made my partitions sections look like the following, it would grab the first disk (be it /dev/sda or /dev/hda) and autopartition it. See if it works for you: <partitioning config:type="list"> <drive> <use>all</use> </drive> </partitioning> Christopher R. Slater ITO Specialist MSDD/SSO Hewlett Packard Company, Roseville Site (916) tn785-1802 http://ecardfile.com/id/chris_slater -----Original Message----- From: Fermín Galán [mailto:fermin.galan@agora-2000.com] Sent: Friday, October 03, 2003 5:37 AM To: suse-autoinstall(a)suse.com Subject: [suse-autoinstall] Problems with <use> and <partition_type> Hello everyone. I'm trying to configure a control file that destroy the existing primary partition hda1 and install SuSE freed with the deletion. To do that, I use <use>1</use> in the control file, but it doesn't seem to work. However <use>5,6,7</use> works, I guest it is due to 1 is a primary partition and 5,6,7 are logical units. It seems like autoyast has problems deleting a primary partition. Or not? Although I destroy the partition previously to the installation (with fdisk, for example) I also have problems with <partition_type>primary</partition_type>. It only seems to work when there is no other partitions in the disk. For example, if an extended partition previously exists, the partitions specified in the control file aren't created. Is possible to install SuSE in primary partitions when a extended partition already exist? How? I'm using SuSE 8.1, autoyast2-installation-2.6.42. Will the problem be fixed using a recent patched version? Is the problem fixed in SuSE 8.2? Any help to solve these problems is welcome. Thanks in advance! --------- Fermín -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

3 4

cannot use keyboard other than language
by Michal Kubecek 06 Oct '03

06 Oct '03

I have a problem with automatic installation of SuSE Linux 8.1 and 8.2. I need to select czech language but english (US) keyboard map. Generated XML file contains <keyboard> <keymap>english-us</keymap> </keyboard> <language>cs_CZ</language> but the system is installed with czech keyboard map anyway. Is there a way to use czech language but english-US keyboard map? Michal Kubecek

4 6

Re: [suse-autoinstall] Problems with <use> and <partition_type>
by damien.selles＠eu.effem.com 06 Oct '03

06 Oct '03

Hi, 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. Maybe you should try to do the same with hda1 : -> try to remove or erase hda1 with a pre-script. I hope it will help you. Regards, Damien Selles. Fermín Galán <fermin.galan(a)agora-2000.com> agora-2000.com 03/10/2003 14:36 To: <suse-autoinstall(a)suse.com> cc: Subject: [suse-autoinstall] Problems with <use> and <partition_type> Hello everyone. I'm trying to configure a control file that destroy the existing primary partition hda1 and install SuSE freed with the deletion. To do that, I use <use>1</use> in the control file, but it doesn't seem to work. However <use>5,6,7</use> works, I guest it is due to 1 is a primary partition and 5,6,7 are logical units. It seems like autoyast has problems deleting a primary partition. Or not? Although I destroy the partition previously to the installation (with fdisk, for example) I also have problems with <partition_type>primary</partition_type>. It only seems to work when there is no other partitions in the disk. For example, if an extended partition previously exists, the partitions specified in the control file aren't created. Is possible to install SuSE in primary partitions when a extended partition already exist? How? I'm using SuSE 8.1, autoyast2-installation-2.6.42. Will the problem be fixed using a recent patched version? Is the problem fixed in SuSE 8.2? Any help to solve these problems is welcome. Thanks in advance! --------- Fermín -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

2 1

[suse-autoinstall]How to automate network card installation ?
by Helmut Auer 01 Oct '03

01 Oct '03

Hello List, I'm new here and I hope I'm at the right place. I have a selfmade Installation CD which contains a backup of my SuSE 8.0 system. I can install this image easily on a similar machine with a different network card. Then I start 'yast2 -S lan' , delete the already configured network card from the original system, add the new network card ( which is correctly found ) and configure it with DHCP and gave it a different hostname. Is there a way to automate these steps within a script ? Thanks in advance --- Helmut Auer, helmut(a)helmutauer.de

1 0

RE: [suse-autoinstall] Scripting troubles
by Robison, Jonathon (M.) 01 Oct '03

01 Oct '03

Strangely enough, when I removed the extra path stuff, it worked. ;-) It also worked fine w/o the terminal definitions, etc. It came up during the last stage of the install, when it was already in a (frame-based?) graphical install mode. Seemed to go OK, except for the x11 one. It apparently hadn't yet installed a number of the base XFree packages it needed to do 'yast2 x11'. I'll keep your text in mind. Do the scripts execute in the order I enter them in autoyast? If so, I may need to re-order things. --Jon Robison -----Original Message----- From: Anas Nashif [mailto:nashif@suse.de] Sent: Tue 9/30/2003 8:13 PM To: Robison, Jonathon (M.) Cc: suse-autoinstall(a)suse.com Subject: Re: [suse-autoinstall] Scripting troubles Robison, Jonathon (M.) wrote: > Strangely enough, /var/adm/autoinstall has nothing but empty > directories in it, with the exception of ./cache/installedSystem.xml > Script name has to be without any additional path information, only a file name, and nothing else. You scripts wont work, as you are executing some gui stuff in a script. I have made a small test and it can work if you change the virtual terminal, for example, this would work: /bin/chvt 3 exec < /dev/tty3 > /dev/tty3 exec /sbin/yast2 proxy /bin/chvt 1 This would bring up the proxy configuration in text mode on the 3rd terminal. This can be used with other yast2 modules I guess.. Anas > --Jon Robison > > On Tue, 2003-09-30 at 10:44, damien.selles(a)eu.effem.com wrote: > > Hi, > > Did you check the logs generated by your chroot scripts? > > after the installation you should be able to access them here -> > /var/adm/autoinstall/logs/ > > and another question: why do you use /tmp/ in your filename? Maybe > you should try without the /tmp/ before the filename. > > > Regards > > --------------------------------------------------------------- > Damien Selles > > > > > "Robison, Jonathon (M.)" <jrobiso2(a)ford.com> ford.com > > 30/09/2003 15:29 > > > To: suse-autoinstall(a)suse.com cc: > > > Subject: [suse-autoinstall] Scripting troubles > > > I have added a number of scripts to my xml file, and yet they never > get executed. I have tried pre, chroot, and post. > > These scripts are rather important, as they are intended to run parts > of yast2 after the install and help the user set up printing, etc. > and most especially, set suid on /usr/bin/smbmnt (otherwise users > cannot mount their windows shares themselves). > > Is there some known problem with the scripting? I've attached my XML > file just in case. > >

2 1

RE: [suse-autoinstall] Error configuring software base-selection
by Stefan Pahrmann 01 Oct '03

01 Oct '03

Sorry, I reinstalled the server from scratch, since I had no time to wait and it works now (unfortunatly i haven't saved the old logfiles). I can't figure out what I did wrong the first place, except that i used numbers in the path to the repesitory (eg. "/usr/install/8.2") with a softlink ("/usr/install/current"). I now placed it directly under /usr/install and as I said it works now. -Stefan -----Original Message----- From: Anas Nashif [mailto:nashif@suse.de] Sent: 27. september 2003 02:56 To: Stefan Pahrmann Cc: 'suse-autoinstall(a)suse.com' Subject: Re: [suse-autoinstall] Error configuring software base-selection Stefan Pahrmann wrote: > Hi, > > I'm trying to do an unattended install, where i put the install files > from 8.2 on a nfs-share and the xml-files on a http-server. The > installer retrieves the xml-file, but when autoyast tries to configure > the software-selections (i just use "default" for now) it put > following error-message on the screen: > > Error > Could not set base selection: default > > Any hints for solving this problem? > Possible causes: You NFS setup is not OK. Could you send me the y2logs? Anas > Best regards > Stefan > -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

Re: [suse-autoinstall] Scripting troubles
by Robison, Jonathon (M.) 01 Oct '03

01 Oct '03

Strangely enough, /var/adm/autoinstall has nothing but empty directories in it, with the exception of ./cache/installedSystem.xml --Jon Robison On Tue, 2003-09-30 at 10:44, damien.selles(a)eu.effem.com wrote: Hi, Did you check the logs generated by your chroot scripts? after the installation you should be able to access them here -> /var/adm/autoinstall/logs/ and another question: why do you use /tmp/ in your filename? Maybe you should try without the /tmp/ before the filename. Regards --------------------------------------------------------------- Damien Selles "Robison, Jonathon (M.)" <jrobiso2(a)ford.com> ford.com 30/09/2003 15:29 To: suse-autoinstall(a)suse.com cc: Subject: [suse-autoinstall] Scripting troubles I have added a number of scripts to my xml file, and yet they never get executed. I have tried pre, chroot, and post. These scripts are rather important, as they are intended to run parts of yast2 after the install and help the user set up printing, etc. and most especially, set suid on /usr/bin/smbmnt (otherwise users cannot mount their windows shares themselves). Is there some known problem with the scripting? I've attached my XML file just in case. -- Jonathon Robison < <mailto:jrobiso2@ford.com> jrobiso2(a)ford.com> Ford Motor Company -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

2 1