April 2003 - openSUSE Autoinstall - openSUSE Mailing Lists

Re: [suse-autoinstall] SLES8 autoyast failure
by Donald W Watson 16 Apr '03

16 Apr '03

Christoph, Thanks for the quick reply. Unfortunately, those entries also do not work (same results), indicating that perhaps I'm not getting a good network connection. During bootup, I get the following messages: Sending DHCP request to eth0 Sending DHCP request to eth0 Since there is no connection to a DHCP server, these requests time out. Does this indicate that perhaps the "ip=192.168.1.2" directive is not working? Sincerely, Don Watson Linux Technology and Solutions; Beaverton, OR 503-578-4861/TL: 775-4861; dwatson(a)us.ibm.com Christoph Thiel <ct(a)kki.org> To: Donald W Watson/Beaverton/IBM@IBMUS cc: suse-autoinstall(a)suse.com 04/16/2003 02:27 Subject: Re: [suse-autoinstall] SLES8 autoyast failure PM Please respond to ct Hi there, On Wed, 16 Apr 2003, Donald W Watson wrote: > linux autoyast=nfs://192.168.1.1/autoinst.xml You have to specify the right path. It should be something like: linux autoyast=nfs://192.168.1.1/home/test/images/autoinst.xml > install=nfs://192.168.1.1/sles8_install Again: install=nfs://192.168.1.1/home/test/images/sles8_install Cheers, -- Christoph Thiel (ct(a)kki.org, cthiel1(a)linux01.gwdg.de) -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

2 2

SLES8 autoyast failure
by Donald W Watson 16 Apr '03

16 Apr '03

I would like to use SLES8 autoyast and nfs to find the autoinst.xml file and to perform package installation, but have failed. I can do autoinstall with the xml file on floppy using the CD's for the installation. I have nfs working correctly on a SLES8 server (192.168.1.1) which is on a local network. The server's /etc/exports file contains this line: /home/test/images *(ro,no_root_squash) The autoinst.xml file exists on the directory /home/test/images, and I have copied the installation CD's to a subdirectory (sles8_install) on /home/test/images. I can mount the nfs filesystem on an nfs client on the local network and see the files. 192.168.1.2 is an unused address on the local network. On the boot options line on the installation menu page I enter: linux autoyast=nfs://192.168.1.1/autoinst.xml install=nfs://192.168.1.1/sles8_install netdevice=eth0 ip=192.168.1.2 insmod=eepro100 I enter the following data at the prompts: Please choose the network protocol NFS Automatic configuration via DHCP? No Please enter your IP address 192.168.1.2 Please enter your netmask 255.255.255.0 If you need a gateway . . . 192.168.1.2 Please enter IP address of your name server <esc> Please enter IP address of the NFS server 192.168.1.1 Please enter the directory on the server images This results in the error: An error occurred while trying to mount the nfs directory. Reason given by server: Permission denied If I leave out the boot option "install=nfs:/192.168.1.1/sles8_install" the installation cannot find the autoinst.xml file. I have also been unsuccessful using ftp, even though it also appears to be set up correctly since I can ftp the files from elsewhere. What am I doing wrong with the networking? Sincerely, Don Watson Linux Technology and Solutions

2 1

Partition during autoinstall
by ahmed＠mindspring.com 16 Apr '03

16 Apr '03

Using autoyast 2.6.4, I can't find an option (in the gui) to reuse the existing Linux partitions during an automatic installation. If the disk was previously partitioned, I get out of space errors on installation. Are there any bugs in 2.6.4 that are fixed in the newer version, or features added, esp around partitioning? Thanks, Ahmed

3 2

Efficient class structure?
by Jochen Lillich 14 Apr '03

14 Apr '03

Hi, I'd like to use autoyast for automating the installation of our training class rooms. The PCs in one room have equal hardware, but there may be differences from room to room. Software configuration varies from course to course. I divided the settings into a class "base" that provides the general configuration. Course specific configurations are stored in the class "courses". The third class "room" has the settings for the different rooms (eg. X11). But since there is no DHCP, how do I provide the correct IP address for every PC? Do I have to create another class "PC" with settings for every single computer in every room? Or is there a more efficient possible strategy? Best regards, Jochen -- ---------------------------------------------------------------- *Jochen Lillich*, Dipl.-Inform. (FH) Consultant/Trainer @ /TeamLinux GbR/ Tel. +49 7254 985187-0 http://www.teamlinux.de ----------------------------------------------------------------

1 0

Re: Re: [suse-autoinstall] LILO message halts auto-install
by ahmed＠mindspring.com 11 Apr '03

11 Apr '03

That worked. I had added it earlier but the file was overwritten Thanks -------Original Message------- From: Anas Nashif <nashif(a)suse.de> Sent: 04/10/03 11:56 AM To: ahmed(a)mindspring.com Subject: Re: [suse-autoinstall] LILO message halts auto-install > > * ahmed(a)mindspring.com <ahmed(a)mindspring.com> [Apr 09. 2003 21:56]: > Thanks for the info so far :o) > Once the installation gets to the bootloader section, it stops with a message from lilo that it is going to save the MBR. > How can I supress the message? Using the report resource, disable showing messages. Anas > Thanks > Ahmed > > -- > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > For additional commands, e-mail: suse-autoinstall-help(a)suse.com -- Anas Nashif <nashif(a)suse.com>, SuSE Linux AG Montreal (Laval), Canada -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com >

1 0

VNC and X configuration
by Christoph Thiel 10 Apr '03

10 Apr '03

Hi there, I just started using AutoYaST recently. On the whole I realy thrilled of it. But now I cam to a point, where I experience a strange behavior of AutoYaST: After installing SuSE 8.2 Pro via NFS and monitoring that installation process with VNC, X does not work. (A installation without VNC on the same machine with the same AutoYaST configuration gets X working perfectly!) (Btw: Using a very short password (4 chars) for VNC makes the use of VNC impossible. :)) Well, and now I wonder if AutoYaST (or YaST itself?) is supposed to behave like that. Cheers, -- Christoph Thiel (ct(a)kki.org, cthiel1(a)linux01.gwdg.de)

1 0

LILO message halts auto-install
by ahmed＠mindspring.com 10 Apr '03

10 Apr '03

Thanks for the info so far :o) Once the installation gets to the bootloader section, it stops with a message from lilo that it is going to save the MBR. How can I supress the message? Thanks Ahmed

2 2

AutoYast2 Problems in 8.2
by skabrond＠tws.at 10 Apr '03

10 Apr '03

Hi, i used AutoYast2 for Installation of a couple of 8.1 boxes (cloned) and was satisfied with its operation, despite the lack of some documentation i managed to figure out myself and partly fixed with postinstall-scripts. Now - in 8.2 - if found one thing that isn't working anymore. Services i want to be enabled and started in some runlevels (runlevel-Editor) do not get enabled anymore, e.g. i have an autoinst.xml that states that apache should get started in runlevel 3 and 5 - but on the target system, its still disabled, no symlinks to the rc-Directories have been created. This is how the runlevel-section generated by Autoinstall looks like: -8<---snip--- <runlevels> <default>5</default> <services config:type="list"> <service> <service_name>apache</service_name> <service_start>3 5</service_start> </service> <service> <service_name>lpd</service_name> <service_start>3 5</service_start> </service> <service> <service_name>nmb</service_name> <service_start>3 5</service_start> </service> <service> <service_name>smb</service_name> <service_start>3 5</service_start> </service> <service> <service_name>smbfs</service_name> </service> </services> </runlevels> -8<---snip--- Interesting enough, smbfs, which i never need, gets disabled, which is enabled by default after a fresh installation ... Anybody got any idea? BTW, a small problem also occurs with the hardware-clock setting. Even if you configure the autoinst.xml for "clock in localtime", the installation of the clone still defaults to UTC. Anyway - this can be corrected in the cloned system by using the sysconfig-Editor to generate the following setting: -8<---snip--- <sysconfig config:type="list"> <sysconfig_entry> <sysconfig_key>HWCLOCK</sysconfig_key> <sysconfig_path>/etc/sysconfig/clock</sysconfig_path> <sysconfig_value>--localtime</sysconfig_value> </sysconfig_entry> </sysconfig> -8<---snip--- Also - it is reasonable to delete the kernel of the master system from which you clone from the list of installed packages (in most cases k_dflt) as the cloned system being installed automatically chooses the appropiate kernel, which can be - as in my case - k_smp, which leads you to two installed kernels and a complaining package manager. But anyway - i like the enhancements in the new version - but i don't like the bugs ;-) Greetings Wolfgang

1 0

Problem: Analysing your system...
by Ugnius Ramanauskas 10 Apr '03

10 Apr '03

During Yast (suse 8.1) installation, there is a screen telling "Analysing your system...". On that my computer stops and doesn't respond for a long time. Can I somehow fix it? Or bypass it? Thanks in advance - Ugnius

1 0

Re: Re: [suse-autoinstall] LILO message halts auto-install
by ahmed＠mindspring.com 09 Apr '03

09 Apr '03

Sorry, SLES 8.0 -------Original Message------- From: Anas Nashif <nashif(a)suse.de> Sent: 04/09/03 04:39 PM To: ahmed(a)mindspring.com Subject: Re: [suse-autoinstall] LILO message halts auto-install > > * ahmed(a)mindspring.com <ahmed(a)mindspring.com> [Apr 09. 2003 21:56]: > Thanks for the info so far :o) > Once the installation gets to the bootloader section, it stops with a message from lilo that it is going to save the MBR. > How can I supress the message? What are you installing exactly? 8.1? Anas > Thanks > Ahmed > > -- > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > For additional commands, e-mail: suse-autoinstall-help(a)suse.com -- Anas Nashif <nashif(a)suse.com>, SuSE Linux AG Montreal (Laval), Canada >

1 0