February 2006 - openSUSE Autoinstall - openSUSE Mailing Lists

SLES 9 SP2
by Kurt Chang 13 Feb '06

13 Feb '06

Hello, I have a question in regards to the auto install procedure. Using YAST, I set up a NFS share where I have loaded the 6 CD for SLES9 (64 bits) and then the three SP2 CD's. When I installed a server via NFS, I got the message, "Insert SUSE SLES 9 Service Pack 2 CD 1" right before SUSE is ready to install. I have another NFS server for 32 bit distro and I did not experience this problem. Any suggestion? Thank you very much for your help Kurt

1 0

/info files on boot CDs
by Ian Grant 13 Feb '06

13 Feb '06

Dear suse-autoinstall people, We have machines without floppies and we want to use an /info file. I understand I can make one and put it in the /initrd on the boot CD. I can probably manage this using the mkinitrd scripts etc, but how would I then create a boot CD ISO image? I am hoping there is a magic mkisofs command line that will fetch what I need out of the boot/loader directory of the SuSE 9.3 distribution and make me a new boot CD. Can anyone point me at more info? Thanks Ian

1 1

cant get Xinclude to work with suse 10
by mailing list 13 Feb '06

13 Feb '06

hi im having a problem getting my xinclude to work with suse 10. Heres are some parts of my autoinstall.xml <?xml version="1.0"?> <!DOCTYPE profile SYSTEM "/usr/share/autoinstall/dtd/profile.dtd"> <profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config=" http://www.suse.com/1.0/configns" xmlns:xinclude=" http://www.w3.org/2001/XInclude"> <bootloader> <activate config:type="boolean">false</activate> <loader_type>grub</loader_type> </bootloader> <files config:type="list"> <file> <file_contents><![CDATA[# $OpenLDAP: pkg/ldap/libraries/libldap/ldap.conf,v 1.9 2000/09/04 19:57:01 kurt Exp $ and a few lines down ... <general> <xinclude:include href=" http://192.168.100.19/autoyast/includes/hdd_prepare_scsi.xml"/> <clock> <hwclock>localtime</hwclock> <timezone>Europe/Berlin</timezone> </clock> <keyboard> <keymap>english-us</keymap> </keyboard> <language>en_US</language> <mode> <confirm config:type="boolean">false</confirm> <forceboot config:type="boolean">true</forceboot> </mode> <mouse> <id>21_imps2</id> </mouse> </general> yep ... that part seems to work ok .. since autoyast accepts it ... now to my hdd prepare_scsi.xml file: <partitioning config:type="list" xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns" xmlns:xinclude="http://www.w3.org/2001/XInclude"> <drive> <device>/dev/sda</device> <partitions config:type="list"> <partition> <crypt>twofish256</crypt> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <loop_fs config:type="boolean">false</loop_fs> <mount>swap</mount> <partition_id config:type="integer">130</partition_id> <size>+1GB</size> </partition> <partition> <crypt>twofish256</crypt> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <loop_fs config:type="boolean">false</loop_fs> <mount>/boot</mount> <partition_id config:type="integer">131</partition_id> <size>+100M</size> </partition> <partition> <crypt>twofish256</crypt> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <loop_fs config:type="boolean">false</loop_fs> <mount>/</mount> <partition_id config:type="integer">131</partition_id> <size>+12GB</size> </partition> <partition> <crypt>twofish256</crypt> <format config:type="boolean">false</format> <loop_fs config:type="boolean">false</loop_fs> <mount>/data/UserData</mount> <partition_id config:type="integer">131</partition_id> <size>max</size> </partition> </partitions> <type config:type="symbol">CT_DISK</type> <use>free</use> </drive> </partitioning> i didnt find any docu related to suse 10. I guess a lot of the syntax changed since 9.0 (the docu i found) Autoyast tells me: ERROR Error while configuring partitions Try Again In the log (/var/log/YaST2/y2log) i can see (at the eof) that the SDA was detected fine .. but thats it .. im stuck.. thank in advance for any help Florian Zuegner.

3 2

Random time for automatic online-update
by Guido Kölsch 09 Feb '06

09 Feb '06

Hi, i have a question about the random update-time in autoyast suse 9.3. It seems not working for me, because after install every machine has the same time for automatic update. Any hints? -- ------------------------------------------------------------------------ Guido Kölsch Max-Planck-Institut fuer Radioastronomie Phone: +49 (0)228 525 164 Auf dem Huegel 69, D-53121 Bonn, Germany FAX : +49 (0)228 525 229 email: gkoelsch(a)mpifr-bonn.mpg.de ------------------------------------------------------------------------

2 2

Configuring remote NTP servers using xml config file
by Richard Hobbs 08 Feb '06

08 Feb '06

Hello, I am trying to configure some remote NTP servers in the XML config file to be used with autoyast, and while it appears to be working, I would like to know if I'm doing it the correct or best way. Here is the <ntp> section from the config: ============================================================ <ntp-client> <configure_dhcp config:type="boolean">false</configure_dhcp> <peers config:type="list"> <peer> <address>127.127.1.0</address> <comment>################################################################### ############# ## /etc/ntp.conf ## ## Sample NTP configuration file. ## See package 'ntp-doc' for documentation, Mini-HOWTO and FAQ. ## Copyright (c) 1998 S.u.S.E. GmbH Fuerth, Germany. ## ## Author: Michael Andres, <ma(a)suse.de> ## ############################################################################ #### ## ## Radio and modem clocks by convention have addresses in the ## form 127.127.t.u, where t is the clock type and u is a unit ## number in the range 0-3. ## ## Most of these clocks require support in the form of a ## serial port or special bus peripheral. The particular ## device is normally specified by adding a soft link ## /dev/device-u to the particular hardware device involved, ## where u correspond to the unit number above. ## ## Generic DCF77 clock on serial port (Conrad DCF77) ## Address: 127.127.8.u ## Serial Port: /dev/refclock-u ## ## (create soft link /dev/refclock-0 to the particular ttyS?) ## # server 127.127.8.0 mode 5 prefer ## ## Undisciplined Local Clock. This is a fake driver intended for backup ## and when no outside source of synchronized time is available. ## </comment> <fudge_comment></fudge_comment> <fudge_options> stratum 10 # LCL is unsynchronized</fudge_options> <initial_sync config:type="boolean">false</initial_sync> <options> # local clock (LCL)</options> <type>__clock</type> </peer> <peer> <address>/var/lib/ntp/drift/ntp.drift # path for drift file</address> <comment> ## ## Outside source of synchronized time ## ## server xx.xx.xx.xx # IP address of server ## ## Miscellaneous stuff ## </comment> <initial_sync config:type="boolean">false</initial_sync> <options></options> <type>driftfile</type> </peer> <peer> <address>/var/log/ntp # alternate log file</address> <comment> </comment> <initial_sync config:type="boolean">false</initial_sync> <options></options> <type>logfile</type> </peer> <peer> <address>192.168.3.2</address> <comment></comment> <initial_sync config:type="boolean">true</initial_sync> <options></options> <type>server</type> </peer> <peer> <address>192.168.3.86</address> <comment></comment> <initial_sync config:type="boolean">false</initial_sync> <options></options> <type>server</type> </peer> <peer> <address>uk.pool.ntp.org</address> <comment></comment> <initial_sync config:type="boolean">false</initial_sync> <options></options> <type>server</type> </peer> </peers> <start_at_boot config:type="boolean">true</start_at_boot> <start_in_chroot config:type="boolean">true</start_in_chroot> </ntp-client> ============================================================ Our intention is to time sync from one (or both) of our internal servers (192.168.3.x) or, if they are unavailable, sync from uk.pool.ntp.org. Ideally, we would like to sync from 192.168.3.2 and 192.168.3.86 and to take an average of the two, but I don't know if NTP works like this. If it only syncs from a single server at a time, then 192.168.3.2 should be attempted first, then 192.168.3.86, and then uk.pool.ntp.org. Is our config going to give us what we require? Thanks in advance to those who can help, it's very much appreciated :-) Richard. -- Richard Hobbs (Systems Administrator) Toshiba Research Europe Ltd. - Speech Technology Group Web: http://www.toshiba-europe.com/research/ Normal Email: richard.hobbs(a)crl.toshiba.co.uk Mobile Email: mobile(a)mongeese.co.uk Tel: +44 1223 376964 Mobile: +44 7811 803377 _____________________________________________________________________ This e-mail has been scanned for viruses by Verizon Business Internet Managed Scanning Services - powered by MessageLabs. For further information visit http://www.mci.com

1 0

RE: [suse-autoinstall] Help with installing multiple machines over network
by Hans-Joachim Ehlers 07 Feb '06

07 Feb '06

Why not just using a simple post install script ? >>> "Richard Hobbs" <richard.hobbs(a)crl.toshiba.co.uk> 07/02/06 11:59:10 >>> Hello, .... This web page ( http://www.tuxmachines.org/node/4630 ) indicates that it's a known bug which has been fixed in SuSE 10.1b1, but is there any way around this when using SuSE 10.0? If not, I'll just have to modify it by hand after the install, right? Thanks again, Richard.

3 6

RE: [suse-autoinstall] Help with installing multiple machines over network
by Richard Hobbs 07 Feb '06

07 Feb '06

Hello, Thank you for all your help regarding this. For those who missed out on the solution (due to the conversation going away from the mailing list for a while), I basically had to remove the <install> tags as they have been deprecated! Everything I have tried so far is now working, except one small thing (which I think is a known bug). I have the runlevel specified in the autoyast config file, but it's being ignored. This web page ( http://www.tuxmachines.org/node/4630 ) indicates that it's a known bug which has been fixed in SuSE 10.1b1, but is there any way around this when using SuSE 10.0? If not, I'll just have to modify it by hand after the install, right? Thanks again, Richard. -- Richard Hobbs (Systems Administrator) Toshiba Research Europe Ltd. - Speech Technology Group Web: http://www.toshiba-europe.com/research/ Normal Email: richard.hobbs(a)crl.toshiba.co.uk Mobile Email: mobile(a)mongeese.co.uk Tel: +44 1223 376964 Mobile: +44 7811 803377 > -----Original Message----- > From: Uwe Gansert [mailto:ug@suse.de] > Sent: 06 February 2006 13:01 > To: Richard Hobbs > Subject: Re: [suse-autoinstall] Help with installing multiple > machines over network > > On Monday 06 February 2006 13:42, you wrote: > > > <mode> > > <confirm config:type="boolean">false</confirm> > > </mode> > > you might want to set this to "true" for the testing phase. > Autoyast stops > then before it is doing something with the harddisc. > > -- > ciao, Uwe Gansert > > Uwe Gansert, Server Technologies Team > SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nuernberg, Germany > e-mail: uwe.gansert(a)suse.de, Tel: +49-(0)911-74053-0, > Fax: +49-(0)911-74053-476, Web: http://www.suse.de > > _____________________________________________________________________ > This e-mail has been scanned for viruses by Verizon Business > Internet Managed Scanning Services - powered by MessageLabs. > For further information visit http://www.mci.com > > _____________________________________________________________________ This e-mail has been scanned for viruses by Verizon Business Internet Managed Scanning Services - powered by MessageLabs. For further information visit http://www.mci.com

1 0

RE: [suse-autoinstall] Help with installing multiple machines ove r network
by Gunreben, Peter (Peter) 03 Feb '06

03 Feb '06

Richard, Richard Hobbs wrote: [...] > I have multiple machines, all of which are identical, onto > which I would like to install SuSE 10. > > I have already installed one machine and got it setup the way > I would like it, in terms of package selections, > partitioning etc... And I would now like to replicate that > across the remaining machines if possible. > > I have read the first section of the SuSE 10 manual, entitled > "Advanced Deployment Scenarios", but this only seems to document > how to boot the system into the manual installation routine > remotely. Ideally, I need to boot from the network and begin > a fully automated install which duplicates every single aspect > of the first system, except with a different hostname and IP > (which I don't mind entering manually during the install if > necessary). > > Can this be done? I'm sure it can, but I can't find any > guides or tutorials on how to do it, so if anyone can help, > that would be very much appreciated Yes, it can be done. Basically, you need two things: 1) The mechanism to boot from the network 2) The mechanism for the automatic installation ad 1) Regarding the boot from network, I'd recommend pxegrub: http://www.gnu.org/software/grub/manual/grub.html#Network Alternatively, you could also build a boot-CD, which contains bootloader, kernel and initrd and starts the network installation. However, this might not be your preferred way of installing the computers. ad 2) I'd recommend to use autoyast. The autoyast is the SuSE mechanism for automatic installation. Using "yast2 autoyast" you can generate an XML-File, which contains the entire configuration for the installation. To install using autoyast, you just need to boot the kernel load the Installation initrd (DVD:/boot/loader/initrd) and add the kernel-parameter install=nfs://<IP-Adressse>/<Pfad>/<XML-File> in your boot-loader configuration. Mailing-List: mailto:suse-autoinstall@suse.com Archive with search function: http://marc.theaimsgroup.com/?l=suse-autoinstall Documentation: http://www.suse.com/~ug/autoyast_doc Regards, Peter.

4 18

Problem with VGA.
by Rodrigo_Albert_Fedosi 03 Feb '06

03 Feb '06

Hi, I have a problem with the autoinstallation of the SuSE 10.0. In the end of installation the kdm isn't started, because the monitor stay out of the synchronization. The problem happens with some models of the monitor, for resolution of the problem I have that in text mode execute the command "sax2 --vesa 0:800x600@65". The models: Samsung 440b, 551v to the time. Thanks, Rodrigo Albert Fedosi Suporte TI Tel: (31) 3419-8854 Fax: (31) 3419-8803 rodrigo(a)bhz.jamef.com.br www.jamef.com.br

1 0

problem while creating partitions on 2 harddisks
by Michael D. 03 Feb '06

03 Feb '06

Hello! I found some very strange behaviour while trying to let autoyast create partitions on /dev/hda and /dev/hdb. The partitioning scheme I need is very simple: /dev/hda1 - /boot (primary, auto size, ext2) /dev/hda2 - swap (primary, auto size) /dev/hda3 - / (primary, max size, reiser) /dev/hdb1 - /home (primary, max size, reiser) Autoinstall was fine while I was using /dev/hda only. But after /dev/hdb1 was added, yast2 died while installing the RPMs - fried by the OOM-killer. I could strip down the problem to a possible bug in autoyast. The XML below contains only the partition info, it was created from scratch with autoyast from SUSE 10.0 (but SUSE 9.3 does the same). The partitioning in the first interactive install screen says only "create /dev/hdb1 with reiserfs", all info from /dev/hda ist lost. With my full autoinstall XML this screen was not shown, the installer has no real root, uses the ramdisk - and gets slayed some minutes later by the OOM-killer. Can anyone comfirm this problem, or am I misunderstanding some of the autoyast options (i.e.the "primary" or the "auto/max")? Thanks Michael ---- snip <?xml version="1.0"?> <!DOCTYPE profile SYSTEM "/usr/share/autoinstall/dtd/profile.dtd"> <profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <partitioning config:type="list"> <drive> <device>/dev/hdb</device> <initialize config:type="boolean">true</initialize> <partitions config:type="list"> <partition> <crypt>twofish256</crypt> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <fstopt>noatime,acl,user_xattr</fstopt> <label></label> <loop_fs config:type="boolean">false</loop_fs> <mount>/home</mount> <mountby config:type="symbol">device</mountby> <noauto config:type="boolean">false</noauto> <partition_id config:type="integer">131</partition_id> <partition_type>primary</partition_type> <size>auto</size> </partition> </partitions> <use>all</use> </drive> <drive> <device>/dev/hda</device> <initialize config:type="boolean">true</initialize> <partitions config:type="list"> <partition> <crypt>twofish256</crypt> <filesystem config:type="symbol">ext2</filesystem> <format config:type="boolean">true</format> <loop_fs config:type="boolean">false</loop_fs> <mount>/boot</mount> <partition_id config:type="integer">131</partition_id> <partition_type>primary</partition_type> <size>auto</size> </partition> <partition> <crypt>twofish256</crypt> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <loop_fs config:type="boolean">false</loop_fs> <mount>swap</mount> <partition_id config:type="integer">130</partition_id> <partition_type>primary</partition_type> <size>auto</size> </partition> <partition> <crypt>twofish256</crypt> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <fstopt>acl,user_xattr</fstopt> <label></label> <loop_fs config:type="boolean">false</loop_fs> <mount>/</mount> <mountby config:type="symbol">device</mountby> <noauto config:type="boolean">false</noauto> <partition_id config:type="integer">131</partition_id> <partition_type>primary</partition_type> <size>max</size> </partition> </partitions> <use>all</use> </drive> </partitioning> </profile> ---- snip __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

2 2