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