- openSUSE Autoinstall

Re: SuSE 8.0 loadlin failure
by Rose Lopez Carreno 12 May '02

12 May '02

I'm having a problem with the password section of the autoinst.xml file. That section of my .xml file is: <users config:type="list" > <user> <encrypted config:type="boolean" >false</encrypted> <user_password>123456</user_password> <username>root</username> </user> </users> After installation, I can log in successfully as root with no password. Rose Lopez Carreno Servers Software Development Phone: (919) 543-9284 8-441-9284 (tieline) Email=rlopezca(a)us.ibm.com

2 1

help suse 8.0 workstation installation
by linux＠linuxkini.com 04 May '02

04 May '02

dear, I just buy a new Suse 8.0 workstation. I got a trouble when I want to install it. I choose a Manual Installation option, but it's always running Yast2. My computer can't run Yast2, I'd always use Yast1 to install the Suse O/S. pls somebody help me, how to install my Suse 8.0 with or without use Yast2. best regards, ocky yonathan <ocky(a)linuxkini.com>

1 0

autoinst.xml - creating additional config files (problem + workaround)
by Hella.Breitkopf＠varetis.de 02 May '02

02 May '02

Hi List, I had problems creating config-files in this way (either my syntax is wrong, or it's a bug): (Remark: Between <configure> and </configure> is more stuff of course, which *did* work - I snipped that in my examples. The xml itself is correct, says tidy -e -xml .) ----start-extract-from-NON-working-configuration-xml-- <configure> <files config:type="list" > <listentry> <config_file> <file_path>/etc/zzzz-config-file-creation-test</file_path> <file_contents> <![CDATA[ ##### # /etc/zzzz-config-file-creation-test # test config file ##### # test, whether autoyast can add complete config files # xml-tree: configure->files->listentry->config_file->file-contents ]]> </file_contents> </config_file> </listentry> </files> <configure> ----stop-extract-from-NON-working-configuration-xml-- I expected to find a file named "/etc/zzzz-config-file-creation-test" on the new-installed box but found nothing like this in /etc or anywhere else. My workaround (this does work - at least on my box): ----start-extract-from-WORKING-configuration-xml-- <configure> <post-scripts config:type="list" > <script> <filename>create-file-workaround</filename> <interpreter>shell</interpreter> <source><![CDATA[ cat << __END__ > /etc/zzzz-config-file-creation-test-workaround ############ # /etc/zzzz-config-file-creation-test-workaround # this file is complete nonsense and can be deleted ############ 123 456 # file created with shell script and "here document" # xml-tree configure->post-scripts->script->source __END__ ]]> </source> </script> </post-scripts> </configure> ----stop-extract-from-WORKING-configuration-xml-- A file named /etc/zzzz-config-file-creation-test-workaround was created and filled. So, did I do something wrong in the upper example or can somebody verify this problem? Best regards, Hella -- -- -- -- -- hella breitkopf, unix + network administrator varetis AG , munich

2 1

Yast2 Autoinstall Custom CDs?
by Kevin Winner 02 May '02

02 May '02

Will Yast2 autoinstall ever support creation of custom CDs to allow for adding additional custom rpms like alice does now with make_inst_cd? Thanks, Kevin

2 1

autoinst.xml - nfs specification
by Rose Lopez Carreno 02 May '02

02 May '02

I am having a problem with the nfs portion of the autoinst.xml file. I specify an nfs install and the installation proceeds w/CD's. Here is the nfs section of my .xml file: Can you see anything I left out/need? <networking> <dns> <dhcp_hostname config:type="boolean" >false</dhcp_hostname> <domain></domain> <hostname></hostname> <nameservers config:type="list" /> <searchlist config:type="list" /> </dns> <interfaces config:type="list" > <interface> <BOOTPROTO>static</BOOTPROTO> <BROADCAST>1.2.255.255</BROADCAST> <IPADDR>1.2.3.7</IPADDR> <NETMASK>255.255.0.0</NETMASK> <NETWORK>1.2.0.0</NETWORK> <STARTMODE>onboot</STARTMODE> <UNIQUE></UNIQUE> <device>eth0</device> <module>e100</module> <options></options> </interface> </interfaces> <routing config:type="list" /> </networking> <nfs config:type="list" > <nfs_entry> <mount_point>/</mount_point> <nfs_options>defaults</nfs_options> <server_path>1.2.3.10:/nfs/suse80</server_path> </nfs_entry> </nfs> Rose Lopez Carreno xSeries Software Deployment Phone: (919) 543-9284 8-441-9284 (tieline) Email=rlopezca(a)us.ibm.com

2 1

[suse-autoinstall] full solution: fetching the autoyast control.xml via NFS
by Hella.Breitkopf＠varetis.de 01 May '02

01 May '02

Problem was: Using a nfs source for the control.xml file didn't work as described. ** Doesn't work (as input to the boot prompt): linux autoyast=nfs://ip-of-nfs1:/path/control.xml install=nfs://ip-nfs2:/other-path/suse8.0 (one will be asked for a valid path to a control file, later) ** Doesn't work , either: linux autoyast=nfs://ip-of-nfs1/path/control.xml install=nfs://ip-nfs2:/other-path/suse8.0 (no colon after nfs-server1's ip in the autoyast statement) Anas Nashif <nashif(a)suse.de> gave the tip: >Try without the : in the URL <snip> > >So the URL should look like this: > install=nfs://123.123.123.111/installs/suse8.0 Ah - the trick is to leave out *both* times the colon .. If one of these lines on the boot prompt, it works: ** Works: linux autoyast=nfs://ip-nfs1/path/control.xml install=nfs://ip-nfs2/other-path/suse8.0 ** Works, too: linux autoyast=http://ip-www/control.xml install=nfs://ip-nfs2:/other-path/suse8.0 (Here the colon after the nfs-server ip doesn't hurt in the install statement) Anis Nashif mentions further: > This is a known issue and it was fixed and > an updated version will be available for nfs installs soon. Is there a open list of "known issues" ? (I've got some more small issues, but if they are known, I don't want to bother the list with them.) And - soon is approximatly when? (Should I start to play with autoinstall boot CDs with the old version or is it worth to wait for the new version?) Regards, Hella

2 1

fetching the autoyast control.xml via NFS
by Hella.Breitkopf＠varetis.de 29 Apr '02

29 Apr '02

Hi List, as everybody else, I'm playing with this nice new toy^h^h^h tool. I like it very much - but sometimes one runs still in some small problems: Fetching the file as "autoinst.xml" from floppy works fine, and typing an http path to the control file to the boot prompt, too : autoyast=http://123.123.123.231/1.xml works as advertised. But if I try to give a NFS path for the control file like this autoyast=nfs://123.123.123.231:/autoinstall/1.xml yast doesn't find the control file on the first try and asks for it later in the installation again. When I fill out that GUI request with the same data, it *does* work. (The directory is exported to everybody and the file is readable by everybody.) The boot prompt takes an NFS installation source without further questions: install=nfs://123.123.123.111:/installs/suse8.0 Anybody who does fetch the contol file via NFS successfully ? Other experiences ? Best regards, Hella -- -- -- -- -- hella breitkopf unix + network administrator varetis AG

2 1

Further plans ...
by Marcel Ritter 29 Apr '02

29 Apr '02

Hi there! I did a couple of test installations with SuSE 8.0 and the new autoinstall - works fine so far. But I'd like to have some more possibilities to change settings Are there plans to implement new YaST2 modules for autoinst configuration? I currently work with kxmledit, but in some cases it's hard to see where you're going ... Ciao, Marcel

2 1

Re: [suse-autoinstall] Anyone using AutoYast2 with PXE?
by Anas Nashif 22 Apr '02

22 Apr '02

* Marcel Ritter <Marcel.Ritter(a)rrze.uni-erlangen.de> [Apr 22. 2002 18:22]: > > > On Mon, 22 Apr 2002, Anas Nashif wrote: > > > * Marcel Ritter <Marcel.Ritter(a)rrze.uni-erlangen.de> [Apr 22. 2002 18:12]: > > > > > > Why do you need a floppy image with PXE? > > > > > > To boot with all modules you need to use the images available in > > > > > > suse/images/boot on the first CD. > > > > > > > > > > That's exactly what I missed :-) If I recall correctly on SuSE 7.3 I had > > > > > to hack it myself - if it's already done on SuSE 8.0 -> great :-) > > > > Not really, these files has always been there :-) That is exactly what > > > > we need to create the bootable CDs... > > > > > > If you say so :-) > > > > > > ... first installation is running - one little problem: > > > > > > How to I load aic7xxx_old instead of aic7xxx (which causes some trouble > > > with my controller)? I had a look at the docu but I couldn't find anything > > > similar to the ALICE insmod list. > > You can either add insmod=aic7xxx_old on the command line or have > > a linuxrc conf file (info) on the boot media with the keyword insmod > > just as it was possible with earlier versions. > > I see - so it's the same as it was with ALICE. Not exactly, it is the same as it was with autoyast1. There is another, still untested way to load modules.. In the bootloader directive of the control file you can add a list of initrd modules, i.e. <bootloader> ... <initrd_modules config:type="list"> <initrd_module>aic7xxx_old</initrd_module> </initrd_modules> ... </bootloader> The problem is, by the time this is evaluated, aic7xxx is already loaded... Another way to do it is to use the pre-install scripts, by using rmmod aic7xxx insmod aic7xxx_old I am not 100% sure this will work though. Anas > > > See http://www.suse.de/~nashif/autoinstall/linuxrc.html > > for more information. > > > > Anas Nashif > > Thanx again, > Marcel -- Anas Nashif <nashif(a)suse.com>, SuSE Linux AG Montreal (Laval), Canada

1 0

Re: [suse-autoinstall] Anyone using AutoYast2 with PXE?
by Marcel Ritter 22 Apr '02

22 Apr '02

> > > Why do you need a floppy image with PXE? > > > To boot with all modules you need to use the images available in > > > suse/images/boot on the first CD. > > > > That's exactly what I missed :-) If I recall correctly on SuSE 7.3 I had > > to hack it myself - if it's already done on SuSE 8.0 -> great :-) > Not really, these files has always been there :-) That is exactly what > we need to create the bootable CDs... If you say so :-) ... first installation is running - one little problem: How to I load aic7xxx_old instead of aic7xxx (which causes some trouble with my controller)? I had a look at the docu but I couldn't find anything similar to the ALICE insmod list. > Anas > -- > Anas Nashif <nashif(a)suse.com>, SuSE Linux AG > Montreal (Laval), Canada Ciao, Marcel

2 1