March 2005 - openSUSE Autoinstall - openSUSE Mailing Lists

Interactive option checked BEFORE scripts?
by Jesse Keating 25 May '05

25 May '05

I'm using the modified.xml method of dynamic autoinstall control files. One of the things I wanted dynamic was the interactive or not choice, controlled by: <mode> <confirm config:type="boolean">false</confirm> If this was set to true, it should be interactive. I have this being set in modified.xml, however it does not take effect. Is this option checked BEFORE the pre-scripts run? -- Jesse Keating RHCE Pogo Linux -- Linux Systems Engineer tel: (888) 828-7646 ex: 436

3 2

SLES9 Installation Tree
by Radzai, Bridgette A. 01 Apr '05

01 Apr '05

I have integrated SP1 into my current sles9 MS directory structure as outlined in Anas' 2/05/05 posting to Egan. I have updated my boot cd with the "linux" and "initrd" from the sp1 CD1. Modified the linuxrc.config. I believe something is incorrect with my directory structure, the installation server is found, loads the SUSE SLES CD1 successfully, but when it tries to find SUSE CORE CD1 I get: Insert 'SUSE LINUX Enterprise Server 9 CD2' URL http://...../sles9_x86/SUSE-SLES-Version-9/CD1 SuSE Linux = SuSE Linux AG 2000040702202411 ! = 20040702201519 Did my media.1 folders not get copied correctly? Thanks in advance for the assistance! Bridgette

2 1

Yast, autoyast, LDAP and home/small company networking
by Birger Kollstrand 28 Mar '05

28 Mar '05

Hi, I have looked around on the SuSE web nad searched the lists to find information on Yast and home/small company network setup. I have com up short on a couple of areas and would very much appreciate som help and guidance. Please redirect me to other mailing lists if this is not the right place. Here is what I want to accomplish on my 8 machine home network first. 1. Authenticate users towards OpenLDAP (or eDirectory) 2. Automount the home directories 3. Add roming possibility so the users can log on while not beeing able to contact the LDAP server. For this I have been thinking of using the http://www.padl.com/OSS/nss_updatedb.html . 4. I want to do this to new machines via autoyast. All machines are different so generating an immage is not good. 5. I want to be able to add necesary SW/Config already configured machines automagically. Now I have accomplished to set up the OpenLDAP server ( although there was no YAST module for that) and I have via YAST set up a client to successfully authenticate towards the OpenLDAP server. In the YAST module I have ticked of the "Start Automounter", but the home directory is not mounted upon login. I can mount the home directory manually without any problems. So the questions are : 1. What does the "Start Automounter" setting actually mean? 2. Is the nss_updatedb the right way to go to achieve the possibility for local login? 3. Can autoyast be used to achieve point 4 and 5 above? (What is the best documentation for autoyast? http://www.novell.com/documentation/nld/index.html?page=/documentation/nld/… ?) 4. There is no mailinglist for Yast. Is it possible to get in contact with the maintainer to discuss enhancements? I'm willing to test and (with my limited c++/qt skills) develop aditions in this area. regards Birger Kollstrand

1 0

Adding patches to Online Update Server
by suse_list 26 Mar '05

26 Mar '05

Hi, We have setup a local update server and are trying to figure out how to add our own patches to the patch server. I was looking through the autoinstall docs and can´t find anything to do with the Online Updates. I can find in the Updates that there are some of the <package_name>.info file and a patch file, but nothing specific as per explanation or quick way for us to add packages/patches to the server. Also we are still trying to configure the server so that it rsync´s with one of the other official online update servers out there like the cs.utah one, but it seems that none of them have the capability to talk to rsync (aka are not running a rsync server deamon). Anyone out there know one that works against a online update server supporting the SuSE 9.2 Professional build. Also what commands are you using to rsync with it. We would like to set it up as a cron job to check daily. If anyone has any info, it would be greatly appreciated Sascha

1 0

Rules.XML and nested rules
by suse_list 26 Mar '05

26 Mar '05

Hi, We currently have a PXE based build environment setup here with SuSE and autoyast for our 32bit workstations and it works great. Though now we are also adding 64bit workstations and need to fix the rules.xml file to support this. This is where our dilemma comes in. We basically would like to be able to setup the rules file with nested rules if that is possible so that we could basically have the following effect: if (workstation = 64bit) do if (hd size = a) profile = 64bit_a if (hd size = b) profile = 64bit_b .... etc ... else (workstation = 32bit) do if (hd size = a) profile = 32bit_a if (hd size = b) profile = 32bit_b ... etc ... Thus was messing around with the rules file and disovered this seems to be having issues. Here is the basic file: <?xml version="1.0"?> <!DOCTYPE autoinstall SYSTEM "/usr/share/autoinstall/dtd/rules.dtd"> <autoinstall xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <rules config:type="list"> <rule> <arch> <match>x86_64</match> <match_type>exact</match_type> <rule> <disksize> <match>/dev/sda 100000</match> <match_type>lower</match_type> </disksize> <result> <profile>software_64bit_80GB_sda.xml</profile> <continue config:type="boolean">false</continue> </result> </rule> <rule> <disksize> <match>/dev/sda 200000</match> <match_type>lower</match_type> </disksize> <result> <profile>software_64bit_200GB_sda.xml</profile> <continue config:type="boolean">false</continue> </result> </rule> </arch> </rule> <rule> <arch> <match>i686</match> <match_type>exact</match_type> <rule> <disksize> <match>/dev/sda 100000</match> <match_type>lower</match_type> </disksize> <result> <profile>software_32bit_80GB_sda.xml</profile> <continue config:type="boolean">false</continue> </result> </rule> <rule> <disksize> <match>/dev/sda 200000</match> <match_type>lower</match_type> </disksize> <result> <profile>software_32bit_200GB_sda.xml</profile> <continue config:type="boolean">false</continue> </result> </rule> </arch> </rule> </rules> </autoinstall> If anyone has any idea, or even a better way for loading profiles, please let me know. Thanks Sascha

1 0

autoyast missing packages when creating iso
by Martyn Iles 25 Mar '05

25 Mar '05

I'm having a problem when trying to create an automatic install of SuSE to put on CDROM. This is SuSE 9.0, if that makes any difference. I go through AutoYaST, tell it to clone my config and then select the Create ISO option, but then I get: Missing Packages ./suse/i586/3ddiag-0.703-172.i586.rpm ./suse/i586/BASS-20030801-55.i586.rpm Plus loads of others Now, I've got the entire SuSE 9.0 (all 7Gb) on an FTP server of mine and if I go into YaST and install extra packages, they install fine. Note that this was NOT where I installed from - I used a remote ftp mirror for the install as my local copy hadn't finished downloading so I've been into Yast and changed the installation source (could autoyast be picking up the path to the original RPMS from somewhere?). If I ftp to the machine and cd to the directories listed above its fine: ftp> cd ./suse 250 CWD command successful. ftp> ls 200 PORT command successful. 150 Opening ASCII mode data connection for file list. i586 i686 noarch nosrc setup src 226 Transfer complete. ftp: 39 bytes received in 0.00Seconds 39000.00Kbytes/sec. ftp> cd i586 250 CWD command successful. ftp> ls 3dd* 200 PORT command successful. 150 Opening ASCII mode data connection for file list. 3ddiag-0.703-172.i586.rpm 226 Transfer complete. ftp: 27 bytes received in 2.12Seconds 0.01Kbytes/sec. ftp> So, any suggestions for what I've done wrong? I've spent over a day on this, had the SuSE available on multiptle FTP/HTTP sites and I just cannot get it to work! Does AutoYaST actually work (I've tried this on two different SuSE 9.0 machines)? If not, how else can I clone a SuSE 9.0 install so that it can be installed (without much user intervention) on multiple machines from a CDROM?

1 0

How do you define "Final Scripts"
by Wayne Gilmore 24 Mar '05

24 Mar '05

I was wondering where you would define the "Final Scripts" in the Autoyast control file? I see tags for pre-scripts, post-scripts, and chroot-scripts but no examples for "final scripts" It says it's new in SLES9. Thanks. Wayne

1 0

RE: [suse-autoinstall] Network Ports and /etc/sysconfig/network
by Suffin, Charles 23 Mar '05

23 Mar '05

Anas, Looks good now!!! You've really helped me out. The latest batch of RPMs create the files in /etc/sysconfig/network and they contain all the correct information, including the "UNIQUE=" data. Thank you so much for your assistance in getting this resolved. -- Charlie -----Original Message----- From: Anas Nashif [mailto:nashif@suse.de] Sent: Friday, March 18, 2005 12:28 PM To: Suffin, Charles Cc: suse-autoinstall(a)suse.com Subject: Re: [suse-autoinstall] Network Ports and /etc/sysconfig/network Hi, There is an update pending you might want to try which fixes some issues with network and autoyast. See http://www.suse.de/~nashif/autoyast2/rpms/sles9/sles9-i386/ You will need all rpms. Create a new source with those updates using the script: http://www.suse.de/~nashif/autoyast2/scripts/create_update_source.sh and put all the above rpms in there. Dont forget to run create_package_descr after you have copied the rpms. then, you will need something like that: <interfaces config:type="list"> <interface> <bootproto>dhcp</bootproto> <device>eth0</device> <startmode>onboot</startmode> </interface> <interface> <bootproto>dhcp</bootproto> <device>eth1</device> <startmode>onboot</startmode> </interface> </interfaces> <modules config:type="list"> <module_entry> <device>eth0</device> <module>e1000</module> </module_entry> <module_entry> <device>eth1</device> <module>e100</module> </module_entry> </modules> Please report if that works for you. Anas Suffin, Charles wrote: > Hi folks, > > It seems that the auto-installation of network ports (which are described in > the XML control file) doesn't create files in /etc/sysconfig/network. > However, if you run YaST2 Network Devices (left) Network Card (right) and > add a network port, a file in /etc/sysconfig/network like > ifcfg-eth-id-AA:BB:CC:DD:EE:FF is created -- the name corresponds to the MAC > address of the card. > > Here's a snippet from my XML. Anyone know why auto-install isn't creating > the file(s) in /etc/sysconfig/network? Or, do you know what source code I > should look at to figure this out? : > > <interfaces config:type="list"> > <interface> > <bootproto>dhcp</bootproto> > <device>eth0</device> > <startmode>onboot</startmode> > </interface> > <interface> > <bootproto>dhcp</bootproto> > <device>eth1</device> > <startmode>onboot</startmode> > </interface> > </interfaces> > <modules config:type="list"> > <module_entry> > <device>bus-pci-0000:01:03.0</device> > <module>e1000</module> > </module_entry> > <module_entry> > <device>bus-pci-0000:01:06.0</device> > <module>e100</module> > </module_entry> > </modules> > > -- Charlie > > p.s./ I'm talking about auto-installation of SLES9 and SLES9-SP1. > > ----- > A. Charles Suffin > Senior Software Engineer > Stratus Technologies, Inc. (http://www.stratus.com) > 111 Powdermill Road > Maynard, MA 01754-3409 > US (978)461-7590 > > > -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

Adding SLES9 SDK to Yast-installsource for autoyast
by suselist＠nlsn.nu 23 Mar '05

23 Mar '05

Hi, Is it possible to add the SLES9 SDK CDs to the install repository to make it possible to select the package-sections in the xml-file? (Both source/binary and eclipse CDs). Regards Daniel

1 0

Configuring sudo
by Mitko Haralanov 22 Mar '05

22 Mar '05

Is there a way to configure the sudoer file (in the style of sysconfig) or do I have to do it in the post-install scripts? Thanx -- Mitko Haralanov mitko(a)pathscale.com http://www.pathscale.com ========================================== Build a system that even a fool can use and only a fool will want to use it.

1 0

RE: [suse-autoinstall] Question on Yast online update "YOU"
by Marlier, Ian 22 Mar '05

22 Mar '05

What version of SuSE? -----Original Message----- From: John Ciccone [mailto:cagspy@yahoo.com] Sent: Tuesday, March 22, 2005 2:46 PM To: suse-autoinstall(a)suse.com Subject: [suse-autoinstall] Question on Yast online update "YOU" Hello All, I am trying to use the Yast online Update for automatic patch update. I am getting the following error when attempting to set this up: Under Location I have: http://ftp.ale.org/pub/suse When I click on next I get the following error: error HTTP return code: 404 (URL: http://ftp.ale.org/pub/suse/i386/update/Novell-Linux-Desktop/9/patches/d irectory.3) When I use an FTP site such as: ftp.suse.com I get this error: "error Couldn't cd to Novell-Linux-Desktop" I'm not sure why it is looking for a dir called "Novell-Linux-Desktop" I haven't seen this dir on any server. Any help would be greatly appricated. Caggie. __________________________________ Do you Yahoo!? Make Yahoo! your home page http://www.yahoo.com/r/hs -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

Question on Yast online update "YOU"
by John Ciccone 22 Mar '05

22 Mar '05

Hello All, I am trying to use the Yast online Update for automatic patch update. I am getting the following error when attempting to set this up: Under Location I have: http://ftp.ale.org/pub/suse When I click on next I get the following error: error HTTP return code: 404 (URL: http://ftp.ale.org/pub/suse/i386/update/Novell-Linux-Desktop/9/patches/dire…) When I use an FTP site such as: ftp.suse.com I get this error: "error Couldn't cd to Novell-Linux-Desktop" I'm not sure why it is looking for a dir called "Novell-Linux-Desktop" I haven't seen this dir on any server. Any help would be greatly appricated. Caggie. __________________________________ Do you Yahoo!? Make Yahoo! your home page http://www.yahoo.com/r/hs

1 0

Installing 32-bit software on 64-bit computer
by Bis Kanungo 22 Mar '05

22 Mar '05

I have used autoyast SUSE Pro 9.2 on a variety of 32-bit machines without problems. I want to install on an HP xw6200 machine and it gives be a message - "Cool computer, but you are about to install 32-bit software on a 64-bit computer". Now it requires manual intervention right at the start and after first reboot. I think this message is from the boot loader. Is there any way to suppress this so that the installation can proceed automated. Thanks! Bis.

2 3

Installing SLES 8 SP3 using Driver Update disk fails at the end of installation!!!
by Ravi Anand 22 Mar '05

22 Mar '05

> Hi List, > > We are using Driver Update Disk for one of our HBA to do "BOOT From SAN" testing on AMD Opteron - IWILL motheroard using SLES 8 SP3. Interestingly enough what > happens that it recognizes the update media , loads the driver and completes the installation. But at the end of the Installation it never asks for SP3 CD again and it fails > complaining about the scsi_mod for 2.4.19-64G kernel does not exist. In other words it thinks it doing SLES 8 base istallation and not SP3 ? > > We ran into the same issue on SunFireWire (which has AMD Opteron ) using "Automatic Installation" but we were able to work it around > using the Manaul Installation -Add driver update disk. But even this mechanism fails on IWILL Motherboard + AMD Opteron + SP3 combination? > > Any ideas or input whats going on ? > > Any help in this regard would be greatly appreciated > > Thanx > Ravi Anand

1 0

SuSE 9.2 Online Updates Mirror
by suse_list 19 Mar '05

19 Mar '05

Hi, I am woundering is there anyway to rsync the SuSE 9.2 Online updates mirror. We run a shop of more then 50 Suse workstations and would like to have a local mirror of the SuSE patches. Is there a rsync mirror we can latch onto, from where we can download to our local patch server? Also we would like to have it setup in the autoinstall (autoyast) portion. We can install all workstations just fine, via PXE, but would like that it would also setup the online updates link to our server and update from there nightly (at like 2am). What do i need to put into the XML file for the online updates, that it does it automatically. Thanks for any advice S.

3 2

Network Ports and /etc/sysconfig/network
by Suffin, Charles 18 Mar '05

18 Mar '05

Hi folks, It seems that the auto-installation of network ports (which are described in the XML control file) doesn't create files in /etc/sysconfig/network. However, if you run YaST2 Network Devices (left) Network Card (right) and add a network port, a file in /etc/sysconfig/network like ifcfg-eth-id-AA:BB:CC:DD:EE:FF is created -- the name corresponds to the MAC address of the card. Here's a snippet from my XML. Anyone know why auto-install isn't creating the file(s) in /etc/sysconfig/network? Or, do you know what source code I should look at to figure this out? : <interfaces config:type="list"> <interface> <bootproto>dhcp</bootproto> <device>eth0</device> <startmode>onboot</startmode> </interface> <interface> <bootproto>dhcp</bootproto> <device>eth1</device> <startmode>onboot</startmode> </interface> </interfaces> <modules config:type="list"> <module_entry> <device>bus-pci-0000:01:03.0</device> <module>e1000</module> </module_entry> <module_entry> <device>bus-pci-0000:01:06.0</device> <module>e100</module> </module_entry> </modules> -- Charlie p.s./ I'm talking about auto-installation of SLES9 and SLES9-SP1. ----- A. Charles Suffin Senior Software Engineer Stratus Technologies, Inc. (http://www.stratus.com) 111 Powdermill Road Maynard, MA 01754-3409 US (978)461-7590

2 1

RE: [suse-autoinstall] SuSE 9.2 Online Updates Mirror
by Schumacher, Gordon 18 Mar '05

18 Mar '05

Well, except... ftp/http are a lot more intensive on bandwidth than rync: The rsync remote-update protocol allows rsync to transfer just the dif- ferences between two sets of files across the network connection, using an efficient checksum-search algorithm described in the technical report that accompanies this package. (Also, rsync has a more robust and less machine-intensive way to get the entire tree's directory listing than "ls -lAR".) And, rsync supports rate limiting too, with the --bwlimit switch. -----Original Message----- From: Marlier, Ian [mailto:ian.marlier@studentuniverse.com] Sent: Friday, March 18, 2005 5:35 AM To: suse-autoinstall(a)suse.com Subject: RE: [suse-autoinstall] SuSE 9.2 Online Updates Mirror Remember that wget was originally written for this purpose...I haven't set this up yet, so I don't know what the command line would be, but wget will allow you to mirror from any http/ftp repository (and can do things like bandwidth limits, which tends to make the sysadmins at the other end of the connection happier). -----Original Message----- From: suse_list [mailto:suse_list@infineon.net] Sent: Thu 3/17/2005 7:07 PM To: suse-autoinstall(a)suse.com Subject: [suse-autoinstall] SuSE 9.2 Online Updates Mirror Hi, I am woundering is there anyway to rsync the SuSE 9.2 Online updates mirror. We run a shop of more then 50 Suse workstations and would like to have a local mirror of the SuSE patches. Is there a rsync mirror we can latch onto, from where we can download to our local patch server? Also we would like to have it setup in the autoinstall (autoyast) portion. We can install all workstations just fine, via PXE, but would like that it would also setup the online updates link to our server and update from there nightly (at like 2am). What do i need to put into the XML file for the online updates, that it does it automatically. Thanks for any advice S. -- 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] SuSE 9.2 Online Updates Mirror
by Marlier, Ian 18 Mar '05

18 Mar '05

Remember that wget was originally written for this purpose...I haven't set this up yet, so I don't know what the command line would be, but wget will allow you to mirror from any http/ftp repository (and can do things like bandwidth limits, which tends to make the sysadmins at the other end of the connection happier). -----Original Message----- From: suse_list [mailto:suse_list@infineon.net] Sent: Thu 3/17/2005 7:07 PM To: suse-autoinstall(a)suse.com Subject: [suse-autoinstall] SuSE 9.2 Online Updates Mirror Hi, I am woundering is there anyway to rsync the SuSE 9.2 Online updates mirror. We run a shop of more then 50 Suse workstations and would like to have a local mirror of the SuSE patches. Is there a rsync mirror we can latch onto, from where we can download to our local patch server? Also we would like to have it setup in the autoinstall (autoyast) portion. We can install all workstations just fine, via PXE, but would like that it would also setup the online updates link to our server and update from there nightly (at like 2am). What do i need to put into the XML file for the online updates, that it does it automatically. Thanks for any advice S. -- 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] SuSE 9.2 Online Updates Mirror
by Schumacher, Gordon 18 Mar '05

18 Mar '05

I know of at least one at suse.cs.utah.edu. You might try connecting to other mirrors and read their policy statement; that's how I found that one (also because it's one of the closest to me). -----Original Message----- From: suse_list [mailto:suse_list@infineon.net] Sent: Thursday, March 17, 2005 5:08 PM To: suse-autoinstall(a)suse.com Subject: [suse-autoinstall] SuSE 9.2 Online Updates Mirror Hi, I am woundering is there anyway to rsync the SuSE 9.2 Online updates mirror. We run a shop of more then 50 Suse workstations and would like to have a local mirror of the SuSE patches. Is there a rsync mirror we can latch onto, from where we can download to our local patch server? Also we would like to have it setup in the autoinstall (autoyast) portion. We can install all workstations just fine, via PXE, but would like that it would also setup the online updates link to our server and update from there nightly (at like 2am). What do i need to put into the XML file for the online updates, that it does it automatically. Thanks for any advice S. -- 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] Yast Unattended Install - annoying network problem - the results so far....
by Colin Topliss 17 Mar '05

17 Mar '05

Hi all, Here's a quick update (on account of my web-mail client not doing a 'reply-all' so my responses never made it to the mailing list).... 1) DHCP related answers... I am not using DHCP. I have supplied the network details on the command line, and my final NIC configuration details are in the XML configuration file. I decided not to use DHCP because of the network topology. 2) instmode=http I hadn't thought about using this option. I sort of assumed that the install=http option was enough to tell YaST what I was up to. I also can't see what effect that would have on the timeout problem. Gave it a go though (couldn't wait until tomorrow) - and it did not help. Worse still, the initrd command line is now so long it gets truncated! :-( 3) Spanning tree option on the switch. Although not using DHCP, this has raised the question about timeouts on bringing the switch port on-line in a timely fashion. I have noticed in the past that, when 'plugging in' a new cable, the port took some time to initialise. Now this may not be *exactly* the same scenario now (I'm not un-plugging/plugging in the server), but maybe the switch is doing something funky. Unfortunately I will have to wait until tomorrow to take a look at it to see what its up to. Thanks for all the responses so far. Col. ________________________________________________________________________ This e-mail message (including any attachment) is intended only for the personal use of the recipient(s) named above. This message is confidential and may be legally privileged. If you are not an intended recipient, you may not review, copy or distribute this message. If you have received this communication in error, please notify us immediately by e-mail and delete the original message. Any views or opinions expressed in this message are those of the author only. Furthermore, this message (including any attachment) does not create any legally binding rights or obligations whatsoever, which may only be created by the exchange of hard copy documents signed by a duly authorised representative of Hutchison 3G UK Limited. ________________________________________________________________________

2 1

RE: [suse-autoinstall] Yast Unattended Install - annoying network problem.
by Schumacher, Gordon 17 Mar '05

17 Mar '05

I have not had to do this (and I'm using HTTP, as I need to be able to traverse filesystems.) -----Original Message----- From: Mitko Haralanov [mailto:mitko@pathscale.com] Sent: Thursday, March 17, 2005 1:01 PM To: suse-autoinstall(a)suse.com Subject: Re: [suse-autoinstall] Yast Unattended Install - annoying network problem. On Thu, 17 Mar 2005 16:11:25 -0000 Colin Topliss <Colin.Topliss(a)three.co.uk> wrote: > The problem starts during the 'initializing hardware' section. It stops at > this point complaining that it can't find the SUSE Linux installation > source. Now some might think that I'd made a mistake - but this is certainly > not the case. I was getting the same thing until I put 'instmode=nfs' in the kernel boot line (I am installing over nfs). You might try appending 'instmode=http' to your append line... -- Mitko Haralanov mitko(a)pathscale.com http://www.pathscale.com ========================================== I cannot conceive that anybody will require multiplications at the rate of 40,000 or even 4,000 per hour ... -- F. H. Wales (1936) -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

2 1

FW: [suse-autoinstall] Dhcp Problems?
by Schumacher, Gordon 17 Mar '05

17 Mar '05

Sounds very much like Colin's problem ("Yast Unattended Install - annoying network problem") also, I suspect! -----Original Message----- From: Brad Hudson [mailto:brad.hudson@gmail.com] Sent: Thursday, March 17, 2005 1:03 PM To: Matt Poepping Cc: suse-autoinstall(a)suse.com Subject: Re: [suse-autoinstall] Dhcp Problems? Mitko is correct on that one. I battled that same issue and the spanning-tree option on the switch needed to be enabled for the ports we were plugged into. to dhcp boot correctly. On Fri, 4 Mar 2005 15:16:42 -0700, Matt Poepping <matt.poepping(a)xilinx.com> wrote: > Is there a way to tell dhcp to try again if it fails the first time. > > > -----Original Message----- > From: Matt Poepping [mailto:matt.poepping@xilinx.com] > Sent: Thursday, March 03, 2005 9:14 > To: suse-autoinstall(a)suse.com > Subject: [suse-autoinstall] Dhcp Problems? > > I am trying to autoyast a machine, and when it is plugged directly into > another machine it works fine, but when I plug it into the network, the > dhcp servers do not seem to be responding fast enough for it and then > install will fail to manual mode. In manual mode, it can then go out and > get a dhcp address. > > I have tried editing the linuxrc.config file within the initrd file, to > up the timeout, but that doesn't seem to work. I've also tried to point > to an info file with the same info, and that seems to be ignored also. > > Thanks, > Matt > > -- > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > For additional commands, e-mail: suse-autoinstall-help(a)suse.com > > -- 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] Dhcp Problems?
by Matt Poepping 17 Mar '05

17 Mar '05

Is there a way to tell dhcp to try again if it fails the first time. -----Original Message----- From: Matt Poepping [mailto:matt.poepping@xilinx.com] Sent: Thursday, March 03, 2005 9:14 To: suse-autoinstall(a)suse.com Subject: [suse-autoinstall] Dhcp Problems? I am trying to autoyast a machine, and when it is plugged directly into another machine it works fine, but when I plug it into the network, the dhcp servers do not seem to be responding fast enough for it and then install will fail to manual mode. In manual mode, it can then go out and get a dhcp address. I have tried editing the linuxrc.config file within the initrd file, to up the timeout, but that doesn't seem to work. I've also tried to point to an info file with the same info, and that seems to be ignored also. Thanks, Matt

2 1

Yast Unattended Install - annoying network problem.
by Colin Topliss 17 Mar '05

17 Mar '05

Hi all, I have an odd problem which is causing me some grief, and I was wondering if anyone else has seen it. The problem (I think) leads to others in the process. Not as unattended as I would like! I am remotely installing SuSE 9.2 a Compaq DL380-G4. When I come to start the install, I am using (IPs changed to protect the guilty): initrd netdevice=eth0 HostIP=10.10.5.9 netmask=255.255.255.0 gateway=10.10.5.1 install=http://10.10.5.50/9.2 autoyast=http://10.10.5.50/conf/system.xml The problem starts during the 'initializing hardware' section. It stops at this point complaining that it can't find the SUSE Linux installation source. Now some might think that I'd made a mistake - but this is certainly not the case. If I now go through the steps: Select the language Choose a keyboard map Start Installation Or System Start Installation Or Update Network HTTP Your network is already configured. Keep this configuration (YES) Enter the IP address of the HTTP server (10.10.5.50) Use a HTTP proxy? (NO) I then get another error saying: connect: No route to host If I try again too quickly, I get the same error. If I wait 30 seconds or and it comes back and prompts for the installation directory (9.2) I'm not sure what causes the initial fault, but the subsequent one suggests a timeout period before the NIC comes on-line, and/or YaST is not waiting for the NIC to initialise before continuing. Now I can crack on with the install (though now its not exactly unattended anymore)! The third problem is that now I have to acknowledge a number of prompts (I think as a result of dropping out to manual mode earlier? - I think I saw that mentioned on the mailing list somewhere). The fourth problem comes after the first CD is finished with. The system reboots, and then goes on to CD2 - and here the system prompts me to load the second CD (a bit annoying as its all under HTTP control). Again, wait for 30 seconds and the install continues OK. Finally, once the system comes up, the network settings are incorrect (I override the one supplied on the command line with a new one in the xml). A reboot cures this, but the option to autoreboot (according to the manual, and bourne out by the fact I couldn't get it to work) appears to have been obsoleted. Has anyone seen this elsewhere, and any ideas on how to prevent the problem(s)? Thanks! Colin Topliss Senior UNIX Sys Admin Noli habere bovis, vir! ________________________________________________________________________ This e-mail message (including any attachment) is intended only for the personal use of the recipient(s) named above. This message is confidential and may be legally privileged. If you are not an intended recipient, you may not review, copy or distribute this message. If you have received this communication in error, please notify us immediately by e-mail and delete the original message. Any views or opinions expressed in this message are those of the author only. Furthermore, this message (including any attachment) does not create any legally binding rights or obligations whatsoever, which may only be created by the exchange of hard copy documents signed by a duly authorised representative of Hutchison 3G UK Limited. ________________________________________________________________________

3 2

RE: [suse-autoinstall] Yast Unattended Install - annoying network problem.
by Schumacher, Gordon 17 Mar '05

17 Mar '05

Sounds to me like your DHCP server is being slow to hand it an address, perhaps. Check your logs? (You might try setting up the remote logging option as described here: http://www.tcm.phy.cam.ac.uk/~mr349/suse/autoyast.html) -----Original Message----- From: Colin Topliss [mailto:Colin.Topliss@three.co.uk] Sent: Thursday, March 17, 2005 9:11 AM To: 'suse-autoinstall(a)suse.com' Subject: [suse-autoinstall] Yast Unattended Install - annoying network problem. Hi all, I have an odd problem which is causing me some grief, and I was wondering if anyone else has seen it. The problem (I think) leads to others in the process. Not as unattended as I would like! I am remotely installing SuSE 9.2 a Compaq DL380-G4. When I come to start the install, I am using (IPs changed to protect the guilty): initrd netdevice=eth0 HostIP=10.10.5.9 netmask=255.255.255.0 gateway=10.10.5.1 install=http://10.10.5.50/9.2 autoyast=http://10.10.5.50/conf/system.xml The problem starts during the 'initializing hardware' section. It stops at this point complaining that it can't find the SUSE Linux installation source. Now some might think that I'd made a mistake - but this is certainly not the case. If I now go through the steps: Select the language Choose a keyboard map Start Installation Or System Start Installation Or Update Network HTTP Your network is already configured. Keep this configuration (YES) Enter the IP address of the HTTP server (10.10.5.50) Use a HTTP proxy? (NO) I then get another error saying: connect: No route to host If I try again too quickly, I get the same error. If I wait 30 seconds or and it comes back and prompts for the installation directory (9.2) I'm not sure what causes the initial fault, but the subsequent one suggests a timeout period before the NIC comes on-line, and/or YaST is not waiting for the NIC to initialise before continuing. Now I can crack on with the install (though now its not exactly unattended anymore)! The third problem is that now I have to acknowledge a number of prompts (I think as a result of dropping out to manual mode earlier? - I think I saw that mentioned on the mailing list somewhere). The fourth problem comes after the first CD is finished with. The system reboots, and then goes on to CD2 - and here the system prompts me to load the second CD (a bit annoying as its all under HTTP control). Again, wait for 30 seconds and the install continues OK. Finally, once the system comes up, the network settings are incorrect (I override the one supplied on the command line with a new one in the xml). A reboot cures this, but the option to autoreboot (according to the manual, and bourne out by the fact I couldn't get it to work) appears to have been obsoleted. Has anyone seen this elsewhere, and any ideas on how to prevent the problem(s)? Thanks! Colin Topliss Senior UNIX Sys Admin Noli habere bovis, vir! ________________________________________________________________________ This e-mail message (including any attachment) is intended only for the personal use of the recipient(s) named above. This message is confidential and may be legally privileged. If you are not an intended recipient, you may not review, copy or distribute this message. If you have received this communication in error, please notify us immediately by e-mail and delete the original message. Any views or opinions expressed in this message are those of the author only. Furthermore, this message (including any attachment) does not create any legally binding rights or obligations whatsoever, which may only be created by the exchange of hard copy documents signed by a duly authorised representative of Hutchison 3G UK Limited. ________________________________________________________________________ -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

No Floppy option?
by Brian Corriveau 17 Mar '05

17 Mar '05

Hi, is there some way to specify in the xml control file that the system does not have a floppy or pcmcia? I've run into a problem where sometimes the probe is getting the wrong result. Tracking that down looks like a lot of work so I'm wondering if there is an xml solution. thanks brian

1 0

Root Password...SuSE 9.1
by Jeffrey Andrews 16 Mar '05

16 Mar '05

Below, I've included a portion of my autoinst.xml that sets up the password stuff. Why doesn't my root user get his password set? Am I missing something or specifying something incorrectly? <security> <console_shutdown>reboot</console_shutdown> <cwd_in_root_path>no</cwd_in_root_path> <cwd_in_user_path>no</cwd_in_user_path> <displaymanager_remote_access>no</displaymanager_remote_access> <enable_sysrq>no</enable_sysrq> <fail_delay>3</fail_delay> <faillog_enab>yes</faillog_enab> <gid_max>60000</gid_max> <gid_min>500</gid_min> <kdm_shutdown>root</kdm_shutdown> <lastlog_enab>yes</lastlog_enab> <obscure_checks_enab>no</obscure_checks_enab> <pass_max_days>99999</pass_max_days> <pass_max_len>16</pass_max_len> <pass_min_days>1</pass_min_days> <pass_min_len>6</pass_min_len> <pass_warn_age>14</pass_warn_age> <passwd_encryption>md5</passwd_encryption> <passwd_use_cracklib>yes</passwd_use_cracklib> <permission_security>secure</permission_security> <run_updatedb_as>nobody</run_updatedb_as> <system_gid_max>499</system_gid_max> <system_gid_min>100</system_gid_min> <system_uid_max>499</system_uid_max> <system_uid_min>100</system_uid_min> <uid_max>60000</uid_max> <uid_min>500</uid_min> </security> <users config:type="list"> <user> <username>root</username> <user_password>EE8863733EF4355A37D566F3DF2AD016</user_password> <encrypted config:type="boolean">true</encrypted> </user> -- Jeffrey Andrews <jandrews(a)lancope.com>

5 5

Full AutoYast tag list
by Mitko Haralanov 15 Mar '05

15 Mar '05

Is there some place where all the tags in the different sections are shown *and* described? The documentation contains only a few of them (as I am starting to notice) and the DTD is hardly the place to provide any insight into what the tags mean. Thanx -- Mitko Haralanov mitko(a)pathscale.com http://www.pathscale.com ========================================== IOT trap -- core dumped

1 0

RE: [suse-autoinstall] auto-installing with patched OS
by Suffin, Charles 15 Mar '05

15 Mar '05

Outstanding, Anas!!! Thank you so much for the rapid response and the correct fix for the problem. I'm sorry I wasn't able to try your new version of the script on Friday night when you published it, but I have had the opportunity today. Now, after rebuilding the update/ directory with your script, when installation runs, the additional CD shows up correctly as "SUSE SLES Updates" and it lists "CD 1: 00:10" (rdesktop is small). After the install is completed, the rdesktop application is automatically installed (I added it with <package> to my XML file. Apparently the incorrect permission of the content file created by the original script was indeed preventing the install source from being correctly utilized. I very much doubt I could've figured out how to set this up without the script (and your help), Anas. Folks, one thing to note... If you want to supply a source package along with a binary package, you need to create an updates/suse/src/ directory and put the source RPM in that (*not* in the iX86/ or noarch/ directories). I consulted the /var/log/YaST2/y2log file to figure out why my source RPM was failing (my little contribution to this effort). With the source located in src/ YaST2 can find it! Thanks! -- Charlie -----Original Message----- From: Anas Nashif [mailto:nashif@suse.de] Sent: Friday, March 11, 2005 5:49 PM To: Suffin, Charles Cc: suse-autoinstall(a)suse.com Subject: Re: [suse-autoinstall] auto-installing with patched OS Hi, I just found out that the permission of the content file under updates/ is wrong, it should be world readable. (chmod a+r content) I will update the script. Anas Suffin, Charles wrote: > Hi folks, > > I used Anas' create_update_source.sh on my SLES9 installation source. It > created an updates/ directory in that source, resulting in a directory > structure that looks like this: > > SLES9/ > SUSE-CORE-Version-9/ > SUSE-SLES-Version-9/ > boot > content > control.xml > media.1 > updates/ <-- this was newly-created by the script, as expected > yast/ > > After this, I followed the instructions in the script: > > 1. I moved my packages into SLES9/updates/suse/<arch> directories. > 2. I cd into SLES9/updates/suse. > 3. I ran /usr/bin/create_package_descr -x setup/descr/EXTRA_PROV > > OK, so then I do an autoinstall from this source on a targe machine. > > After the reboot, there is no sign of my package on the installed machine, > and if I search for the package using YaST2 "Install and Remove Software" it > is not found by its name. > > I think I'm missing a step somewhere to cause the installation to actually > install my package. What am I missing? Do I need to add a <package> line > to the XML file? Do I need to do some more mucking with the installation > source? > > -- Charlie > > -----Original Message----- > From: Anas Nashif [mailto:nashif@suse.de] > Sent: Tuesday, March 01, 2005 10:53 PM > To: Mark Acosta > Cc: suse-autoinstall(a)suse.com > Subject: Re: [suse-autoinstall] auto-installing with patched OS > > Hi, > I have a script for doing this you might want to try, see > > http://www.suse.de/~nashif/autoyast2/scripts/create_update_source.sh > > The script itself has some additional info on how to use it. > > The script uses the multiple source feature known from SLES, it will > register multiple sources and the latest version of packages available > in the original source and the new source will be installed. > > Give it a try and let me know if it works for you. any feedback is welcome. > > Anas > > > Mark Acosta wrote: >>I need to autoinstall a patched 2.6.8-24.11-default kernel (including >>patched utils) for Suse 9.2. The stock kernel is 2.6.8-24.10-default, >>but I can't find out how to patch/update to 2.6.8-24.11-default. How is >>the best accomplished? >> >>thanks, >>Mark >> >> >

2 1

RE: [suse-autoinstall] auto-installing with patched OS
by Suffin, Charles 14 Mar '05

14 Mar '05

Ooooh, one other bug I should tell you about. The script doesn't create a directory.yast file in the update/ directory itself. This causes the autoinstall to take an error (download failed, media: file not found) right when it's loading the new packages. I made a one line addition to your script, Anas... You might want to do this in your version on the web: Add the following line after line 140: create_dy . Put this between the "cd $UPDATES" and the for loop. -- Charlie -----Original Message----- From: Suffin, Charles [mailto:Charles.Suffin@stratus.com] Sent: Monday, March 14, 2005 3:27 PM To: suse-autoinstall(a)suse.com Subject: RE: [suse-autoinstall] auto-installing with patched OS Outstanding, Anas!!! Thank you so much for the rapid response and the correct fix for the problem. I'm sorry I wasn't able to try your new version of the script on Friday night when you published it, but I have had the opportunity today. Now, after rebuilding the update/ directory with your script, when installation runs, the additional CD shows up correctly as "SUSE SLES Updates" and it lists "CD 1: 00:10" (rdesktop is small). After the install is completed, the rdesktop application is automatically installed (I added it with <package> to my XML file. Apparently the incorrect permission of the content file created by the original script was indeed preventing the install source from being correctly utilized. I very much doubt I could've figured out how to set this up without the script (and your help), Anas. Folks, one thing to note... If you want to supply a source package along with a binary package, you need to create an updates/suse/src/ directory and put the source RPM in that (*not* in the iX86/ or noarch/ directories). I consulted the /var/log/YaST2/y2log file to figure out why my source RPM was failing (my little contribution to this effort). With the source located in src/ YaST2 can find it! Thanks! -- Charlie -----Original Message----- From: Anas Nashif [mailto:nashif@suse.de] Sent: Friday, March 11, 2005 5:49 PM To: Suffin, Charles Cc: suse-autoinstall(a)suse.com Subject: Re: [suse-autoinstall] auto-installing with patched OS Hi, I just found out that the permission of the content file under updates/ is wrong, it should be world readable. (chmod a+r content) I will update the script. Anas Suffin, Charles wrote: > Hi folks, > > I used Anas' create_update_source.sh on my SLES9 installation source. It > created an updates/ directory in that source, resulting in a directory > structure that looks like this: > > SLES9/ > SUSE-CORE-Version-9/ > SUSE-SLES-Version-9/ > boot > content > control.xml > media.1 > updates/ <-- this was newly-created by the script, as expected > yast/ > > After this, I followed the instructions in the script: > > 1. I moved my packages into SLES9/updates/suse/<arch> directories. > 2. I cd into SLES9/updates/suse. > 3. I ran /usr/bin/create_package_descr -x setup/descr/EXTRA_PROV > > OK, so then I do an autoinstall from this source on a targe machine. > > After the reboot, there is no sign of my package on the installed machine, > and if I search for the package using YaST2 "Install and Remove Software" it > is not found by its name. > > I think I'm missing a step somewhere to cause the installation to actually > install my package. What am I missing? Do I need to add a <package> line > to the XML file? Do I need to do some more mucking with the installation > source? > > -- Charlie > > -----Original Message----- > From: Anas Nashif [mailto:nashif@suse.de] > Sent: Tuesday, March 01, 2005 10:53 PM > To: Mark Acosta > Cc: suse-autoinstall(a)suse.com > Subject: Re: [suse-autoinstall] auto-installing with patched OS > > Hi, > I have a script for doing this you might want to try, see > > http://www.suse.de/~nashif/autoyast2/scripts/create_update_source.sh > > The script itself has some additional info on how to use it. > > The script uses the multiple source feature known from SLES, it will > register multiple sources and the latest version of packages available > in the original source and the new source will be installed. > > Give it a try and let me know if it works for you. any feedback is welcome. > > Anas > > > Mark Acosta wrote: >>I need to autoinstall a patched 2.6.8-24.11-default kernel (including >>patched utils) for Suse 9.2. The stock kernel is 2.6.8-24.10-default, >>but I can't find out how to patch/update to 2.6.8-24.11-default. How is >>the best accomplished? >> >>thanks, >>Mark >> >> > -- 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] auto-installing with patched OS
by Suffin, Charles 14 Mar '05

14 Mar '05

Hi folks, I used Anas' create_update_source.sh on my SLES9 installation source. It created an updates/ directory in that source, resulting in a directory structure that looks like this: SLES9/ SUSE-CORE-Version-9/ SUSE-SLES-Version-9/ boot content control.xml media.1 updates/ <-- this was newly-created by the script, as expected yast/ After this, I followed the instructions in the script: 1. I moved my packages into SLES9/updates/suse/<arch> directories. 2. I cd into SLES9/updates/suse. 3. I ran /usr/bin/create_package_descr -x setup/descr/EXTRA_PROV OK, so then I do an autoinstall from this source on a targe machine. After the reboot, there is no sign of my package on the installed machine, and if I search for the package using YaST2 "Install and Remove Software" it is not found by its name. I think I'm missing a step somewhere to cause the installation to actually install my package. What am I missing? Do I need to add a <package> line to the XML file? Do I need to do some more mucking with the installation source? -- Charlie -----Original Message----- From: Anas Nashif [mailto:nashif@suse.de] Sent: Tuesday, March 01, 2005 10:53 PM To: Mark Acosta Cc: suse-autoinstall(a)suse.com Subject: Re: [suse-autoinstall] auto-installing with patched OS Hi, I have a script for doing this you might want to try, see http://www.suse.de/~nashif/autoyast2/scripts/create_update_source.sh The script itself has some additional info on how to use it. The script uses the multiple source feature known from SLES, it will register multiple sources and the latest version of packages available in the original source and the new source will be installed. Give it a try and let me know if it works for you. any feedback is welcome. Anas Mark Acosta wrote: > I need to autoinstall a patched 2.6.8-24.11-default kernel (including > patched utils) for Suse 9.2. The stock kernel is 2.6.8-24.10-default, > but I can't find out how to patch/update to 2.6.8-24.11-default. How is > the best accomplished? > > thanks, > Mark > > -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

3 3

self installing DVD
by jan terje tønnessen 13 Mar '05

13 Mar '05

Hi ! I have a working autoyast for Suse9.1. I would now like to make a "self-installing-DVD" which should be 100% automated. I am thinking of two methods: 1) A bootable DVD which starts autoyast (with repository on the same DVD). 2) A bootable DVD which partitions the HD and then 'dd' form the DVD to the HD. Has anybody done something similar ? Br / Jan Terje

1 0

Advice to Incorporate UDEV into auto-install?
by Suffin, Charles 11 Mar '05

11 Mar '05

Hi guys, Have any of you incorporated UDEV device naming into your auto-install? I'm looking for XML examples, docs, howtos... whatever. We need to do this here at Stratus, and about all I know how to do with the autoinstall at this point is to start the boot.udev service at runlevel B. I don't think this will be enough, as configuration work is needed as well. For example, does anyone know how to muck with udev.conf via autoyast/YaST2, or will I have to write a script for this? FYI, our objective is to get fixed device naming for our disks, which is required for our hardware architecture. We might use UDEV for other device naming as well. Forgive the ignorant question(s). Any help is appreciated. -- charlie ----- A. Charles Suffin Senior Software Engineer Stratus Technologies, Inc. (http://www.stratus.com) 111 Powdermill Road Maynard, MA 01754-3409 US (978)461-7590

1 0

RE: [suse-autoinstall] YaST2 Doesn't Search for Source Packages
by Suffin, Charles 11 Mar '05

11 Mar '05

In my example, yes, both of the k3b packages are listed in the packages file, Todd. For the binary package, there's: =Pkg: k3b 0.11.7 23.1 i586 < ... stuff ... > =Src: k3b 0.11.7 23.1 src =Tim: 1088641834 =Loc: 1 k3b-0.11.7-23.1.i586.rpm < ... stuff ... > And then for the source package, there's: =Pkg: k3b 0.11.7 23.1 src =Loc: 3 k3b-0.11.7-23.1.src.rpm src < ... stuff ... > =Shr: k3b 0.11.7 23.1 i586 These two descriptions clearly relate the packages to each other. Does the "src" token in the "=Pkg:" statement inform YaST2 not to show it in a search?? -- Charlie -----Original Message----- From: Ness, Todd [mailto:todd.ness@eds.com] Sent: Wednesday, March 09, 2005 4:43 PM To: suse-autoinstall(a)suse.com Subject: RE: [suse-autoinstall] YaST2 Doesn't Search for Source Packages Try to grep src out of the CD1/suse/setup/descr/packages if it is in there I think the yast sw_single module should be able to see it. You can create packages files with /usr/lib/YaST2/bin/create_package_descr -----Original Message----- From: Suffin, Charles [mailto:Charles.Suffin@stratus.com] Sent: Wednesday, March 09, 2005 1:27 PM To: suse-autoinstall(a)suse.com Subject: [suse-autoinstall] YaST2 Doesn't Search for Source Packages Hi guys, This isn't an autoyast question, but it involves an installation server, and I'll bet someone here will know the answer... More to the point, I'm adding packages for my company's software, and I want to do it right! :) With YaST2 pointing at an SLES9 installation server, I find that "Install and Remove Software" does not find the source packages for a given name when you do a search on it (with the filter in search mode). The sources are part of the distro though, and sometimes someone in my dept. wants to study them... For example, the k3b binary package is found if you search for it, but not the source package. The two packages are in the CD1 and CD3 directories, respectively, on the server: ./SUSE-CORE-Version-9/CD1/suse/i586/k3b-0.11.7-23.1.i586.rpm ./SUSE-CORE-Version-9/CD3/suse/src/k3b-0.11.7-23.1.src.rpm The package database on the server (./SUSE-CORE-Version-9/CD1/suse/setup/descr/packages) is standard SLES9, and I see that both the binary and source packages for k3b are listed there. Why doesn't YaST2 find it? Is there something in the syntax of the packages file that indicates whether it should be found by the YaST2 search? Thanks. -- Charlie ----- A. Charles Suffin Senior Software Engineer Stratus Technologies, Inc. (http://www.stratus.com) 111 Powdermill Road Maynard, MA 01754-3409 US (978)461-7590 -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

3 9

Multiple RAID Types with SLES9/SP1 and autoyast
by Brad Hudson 11 Mar '05

11 Mar '05

I need some assistance with getting multiple RAID types to work across disks using autoyast. The formatting of all drives works properly, but the software RAID does not configure properly. I have raid1 for my /boot partition and raid5 for all other /dev/md partitions. The disks (/dev/cciss/c0d*) configure properly, but the software partitions (/dev/md*) all configure as raid1, eventhough raid5 is specified. The pertinent sections of the profile are pasted below. FYI: Each disk is exactly the same simply incremented (c0d0, c0d1, etc.). <partitioning config:type="list"> <drive> <device>/dev/cciss/c0d0</device> <partitions config:type="list"> <partition> <format config:type="boolean">false</format> <partition_id config:type="integer">0xFD</partition_id> <partition_type>primary</partition_type> <raid_name>/dev/md0</raid_name> <raid_type>raid</raid_type> <size>136436KB</size> </partition> <partition> <format config:type="boolean">false</format> <partition_id config:type="integer">0xFD</partition_id> <partition_type>primary</partition_type> <raid_name>/dev/md1</raid_name> <raid_type>raid</raid_type> <size>421545KB</size> </partition> <partition> <format config:type="boolean">false</format> <partition_id config:type="integer">0xFD</partition_id> <partition_type>primary</partition_type> <raid_name>/dev/md2</raid_name> <raid_type>raid</raid_type> <size>1633016KB</size> </partition> <partition> <format config:type="boolean">false</format> <partition_id config:type="integer">0xFD</partition_id> <raid_name>/dev/md3</raid_name> <raid_type>raid</raid_type> <size>823014KB</size> </partition> <partition> <format config:type="boolean">false</format> <partition_id config:type="integer">0xFD</partition_id> <raid_name>/dev/md4</raid_name> <raid_type>raid</raid_type> <size>1633016KB</size> </partition> <partition> <format config:type="boolean">false</format> <partition_id config:type="integer">0xFD</partition_id> <raid_name>/dev/md5</raid_name> <raid_type>raid</raid_type> <size>2449630KB</size> </partition> <partition> <format config:type="boolean">false</format> <partition_id config:type="integer">0xFD</partition_id> <raid_name>/dev/md6</raid_name> <raid_type>raid</raid_type> <size>4886036KB</size> </partition> <partition> <format config:type="boolean">false</format> <partition_id config:type="integer">0xFD</partition_id> <raid_name>/dev/md7</raid_name> <raid_type>raid</raid_type> <size>1633016KB</size> </partition> <partition> <format config:type="boolean">false</format> <partition_id config:type="integer">0xFD</partition_id> <raid_name>/dev/md8</raid_name> <raid_type>raid</raid_type> <size>max</size> </partition> </partitions> <use>all</use> </drive> more drives like above here, then... <drive> <device>/dev/md</device> <partitions config:type="list"> <partition> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <fstopt>data=journal,noacl</fstopt> <mount>/boot</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">0</partition_nr> <raid_type>raid1</raid_type> </partition> <partition> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <fstopt>pri=42</fstopt> <mount>swap</mount> <partition_id config:type="integer">130</partition_id> <partition_nr config:type="integer">1</partition_nr> <raid_type>raid5</raid_type> </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <fstopt>data=journal,noacl</fstopt> <mount>/</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">2</partition_nr> <raid_type>raid5</raid_type> </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <fstopt>data=journal,noacl</fstopt> <mount>/opt/emageon</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">3</partition_nr> <raid_type>raid5</raid_type> </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <fstopt>data=journal,noacl</fstopt> <mount>/opt/emageon/var</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">4</partition_nr> <raid_type>raid5</raid_type> </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <fstopt>data=journal,noacl</fstopt> <mount>/opt/emageon/log</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">5</partition_nr> <raid_type>raid5</raid_type> </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <fstopt>data=journal,notail,noacl</fstopt> <mount>/opt/emageon/oradb/online</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">6</partition_nr> <raid_type>raid5</raid_type> </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <fstopt>data=journal,notail,noacl</fstopt> <mount>/opt/emageon/oradb/backup</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">7</partition_nr> <raid_type>raid5</raid_type> </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <fstopt>data=ordered,noacl</fstopt> <mount>/opt/emageon/archive</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">8</partition_nr> <raid_type>raid5</raid_type> </partition> </partitions> <use>all</use> </drive> </partitioning> Brad

1 0

pxe boot, timeout on initrd tftp transfert
by Marc Sauton 10 Mar '05

10 Mar '05

Hi all, I have this 9.2 (eval, and SLES soon) network install on a Dell System PowerEdge 2850 (on its second net interface, eth1) running from a 9.0 server, and failing on a timeout when there is an attempt from the tftp server to send the ramdisk, or may be when the booting client seem to have lost its network config (crashed?), please see a trace and some details below, specially the last lines (some addresses removed for this text). Thanks for any suggestions, Marc. >From the booting client console: Intel(R) Boot Agent GE v1.2.16P6 Copyright (C) 1997-2004, Intel Corporation Intel(R) Boot Agent PXE Base Code (BA1216BD) Copyright (C) 1997-2003, Intel Corporation CLIENT MAC ADDR: xx xx xx xx xx xx GUID: ... CLIENT IP: 10.x.x.x MASK: 255.255.255.0 DHCP IP: 10.x.x.x GATEWAY IP: 10.x.x.x PXELINUX 2.06 0x3fc70fbd Copyright (C) 1994-2003 H. Peter Anvin UNDI data segment at: 000969A0 UNDI data segment size: 6240 UNDI code segment at: 0009CBE0 UNDI code segment size: 28D0 PXE entry point found (we hope) at 9CBE:0106 My IP address seems to be xxxxxxxx 10.x.x.x ip=10.x.x.x:10.x.x.x:10.x.x.x:255.255.255.0 TFTP prefix: Trying to load: pxelinux.cfg/01-xx-xx-xx-xx-xx-xx Trying to load: pxelinux.cfg/xxxxxxxx Loading 9.2.eval.dvd/boot/loader/linux64............................. Loading 9.2.eval.dvd/boot/loader/initrd64... and then time out. On the install server: ls -l /tftpboot/ total 17 drwxr-xr-x 4 root root 176 2005-03-09 18:17 . drwxr-xr-x 23 root root 536 2005-03-04 11:49 .. drwxr-xr-x 7 root root 792 2005-03-07 11:23 9.2.eval.dvd -rw-r--r-- 1 root root 188 2005-03-09 15:47 test.xml -rw-r--r-- 1 root root 11308 2003-11-28 01:05 pxelinux.0 drwxr-xr-x 2 root root 184 2005-03-10 12:52 pxelinux.cfg /tftpboot/pxelinux.cfg/default default linux serial 0,115200n8 label linux kernel 9.2.eval.dvd/boot/loader/linux64 append textmode=1 console=ttyS0,115200n8 initrd=9.2.eval.dvd/boot/loader/initrd64 autoyast=tftp://install.server.ip/test.xml A tcpdump and /var/log/messages on the tftp server show this: Mar 10 13:14:18 hostname dhcpd: DHCPDISCOVER from booting.client.mac.addr via eth1 Mar 10 13:14:18 hostname dhcpd: DHCPOFFER on booting.client.ip to booting.client.mac.addr via eth1 Mar 10 13:14:22 hostname dhcpd: DHCPREQUEST for booting.client.ip (install.server.ip) from booting.client.mac.addr via eth1 Mar 10 13:14:22 hostname tftpd[10243]: Serving pxelinux.0 to booting.client.ip:2070 Mar 10 13:14:22 hostname tftpd[10243]: Serving pxelinux.0 to booting.client.ip:2071 13:14:22.948925 IP booting.client.ip.57089 > install.server.ip.69: 63 RRQ "pxelinux.cfg/booting.client.mac.addr" octet tsize 0 blks 13:14:22.949348 IP install.server.ip.32796 > booting.client.ip.57089: UDP, length: 18 13:14:22.953048 IP booting.client.ip.56834 > install.server.ip.69: 51 RRQ "pxelinux.cfg/0A0A1426" octet tsize 0 blksize 1440 13:14:22.953503 IP install.server.ip.32796 > booting.client.ip.56834: UDP, length: 25 13:14:22.953676 IP booting.client.ip.56834 > install.server.ip.32796: UDP, length: 4 13:14:22.953816 IP install.server.ip.32796 > booting.client.ip.56834: UDP, length: 453 13:14:22.953925 IP booting.client.ip.56834 > install.server.ip.32796: UDP, length: 4 13:14:22.957419 IP booting.client.ip.56835 > install.server.ip.69: 62 RRQ "9.2.eval.dvd/boot/loader/linux64" octet tsize 0 blksi 13:14:22.957876 IP install.server.ip.32796 > booting.client.ip.56835: UDP, length: 29 13:14:22.958049 IP booting.client.ip.56835 > install.server.ip.32796: UDP, length: 4 13:14:22.958163 IP install.server.ip.32796 > booting.client.ip.56835: UDP, length: 1444 .....snip........ 13:14:23.245002 IP booting.client.ip.56835 > install.server.ip.32796: UDP, length: 4 13:14:23.415832 IP install.server.ip.32796 > booting.client.ip.56836: UDP, length: 29 Mar 10 13:14:22 hostname tftpd[10243]: Serving pxelinux.cfg/booting.client.mac.addr to booting.client.ip:57089 Mar 10 13:14:22 hostname tftpd[10243]: Serving pxelinux.cfg/0A0A1426 to booting.client.ip:56834 Mar 10 13:14:22 hostname tftpd[10243]: Serving 9.2.eval.dvd/boot/loader/linux64 to booting.client.ip:56835 Mar 10 13:14:23 hostname tftpd[10243]: Serving 9.2.eval.dvd/boot/loader/initrd64 to booting.client.ip:56836 13:14:28.585856 IP install.server.ip.32796 > booting.client.ip.56836: UDP, length: 29 Mar 10 13:14:28 hostname tftpd[10243]: timeout: retrying... 13:14:33.585049 IP install.server.ip.32796 > booting.client.ip.56836: UDP, length: 29 13:14:38.584206 IP install.server.ip.32796 > booting.client.ip8.56836: UDP, length: 29 13:14:43.583383 IP install.server.ip.32796 > booting.client.ip8.56836: UDP, length: 29 13:14:48.582561 IP install.server.ip.32796 > booting.client.ip.56836: UDP, length: 29 Mar 10 13:14:48 hostname last message repeated 4 times

1 0

RE: [suse-autoinstall] Updating an existing NLD repository with N LD sp1.
by Suffin, Charles 10 Mar '05

10 Mar '05

Anas, Isn't that missing a link to linux, as per your email from last month?: linux -> SUSE-SLES-9-Service-Pack-Version-1/CD1/linux/ (just checking) -- Charlie -----Original Message----- From: Anas Nashif [mailto:nashif@suse.de] Sent: Thursday, March 10, 2005 10:23 AM To: Anthony Staples Cc: suse-autoinstall(a)suse.com Subject: Re: [suse-autoinstall] Updating an existing NLD repository with NLD sp1. Anthony, The easiest way to integerate the service pack: in your current repository (<rep_dir>) create CD directories: mkdir -p <rep_dir>/SP1/{CD1,CD2,CD3....} mkdir <rep_dir>/yast ln -sf SP1/CD1/driverupdate echo "/SP1 /SP1" > yast/order echo "/" >> yast/order echo "/SP1" > yast/instorder echo "/" >> yast/instorder Anas Anthony Staples wrote: > I am downloading sp1 cd's for Novell Linux Desktop. What is the best, > easiest way to integrate these new packages into my existing > repository? Is there a script available to do it, or do I have to > start with a new repository? > > I see that there is a checkbox in the autoyast repository "Source > Configuration" window to "prompt for additional cds..." But when > trying to edit the existing repository this is greyed out. I don't > remember if it was greyed out when i created the repository. > > Cheers, Tony Staples astaples(a)humana.com > > > > The information transmitted is intended only for the person or entity > to which it is addressed and may contain CONFIDENTIAL material. If > you receive this material/information in error, please contact the > sender and delete or destroy the material/information. > -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

2 1

SLES 8 - Removing of packages during Installation failed
by Diener, Stefan 10 Mar '05

10 Mar '05

Hi group, i´m having a little problem with the software package configuration using autoyast installation. I want to uninstall some packages automatically during the autoyast installation. Here is the software section from my xml file: ------------------------------------------------------------------------ <software> <addons config:type="list"/> <base>default</base> <packages config:type="list"> <package>kernel-source</package> </packages> <remove-packages config:type="list"> <package>capi4linux</package> <package>i4l-isdnlog</package> <package>i4lfirm</package> <package>i4l-base</package> </remove-packages> </software> ------------------------------------------------------------------------ The installation of the additonal package "kernel-source" is okay, but the uninstallation of the i4l package doesn´t work. A manual removing with the rpm -e command in the order shown above works fine. Any ideas? Best regards, Stefan

4 4

RE: [suse-autoinstall] YaST2 Doesn't Search for Source Packages
by Ness, Todd 09 Mar '05

09 Mar '05

Good question, I always add source packages from the command line. So, I had not run into that problem, hopefully Anas or somebody "more in the know" will respond -----Original Message----- From: Suffin, Charles [mailto:Charles.Suffin@stratus.com] Sent: Wednesday, March 09, 2005 3:04 PM To: suse-autoinstall(a)suse.com Subject: RE: [suse-autoinstall] YaST2 Doesn't Search for Source Packages In my example, yes, both of the k3b packages are listed in the packages file, Todd. For the binary package, there's: =Pkg: k3b 0.11.7 23.1 i586 < ... stuff ... > =Src: k3b 0.11.7 23.1 src =Tim: 1088641834 =Loc: 1 k3b-0.11.7-23.1.i586.rpm < ... stuff ... > And then for the source package, there's: =Pkg: k3b 0.11.7 23.1 src =Loc: 3 k3b-0.11.7-23.1.src.rpm src < ... stuff ... > =Shr: k3b 0.11.7 23.1 i586 These two descriptions clearly relate the packages to each other. Does the "src" token in the "=Pkg:" statement inform YaST2 not to show it in a search?? -- Charlie -----Original Message----- From: Ness, Todd [mailto:todd.ness@eds.com] Sent: Wednesday, March 09, 2005 4:43 PM To: suse-autoinstall(a)suse.com Subject: RE: [suse-autoinstall] YaST2 Doesn't Search for Source Packages Try to grep src out of the CD1/suse/setup/descr/packages if it is in there I think the yast sw_single module should be able to see it. You can create packages files with /usr/lib/YaST2/bin/create_package_descr -----Original Message----- From: Suffin, Charles [mailto:Charles.Suffin@stratus.com] Sent: Wednesday, March 09, 2005 1:27 PM To: suse-autoinstall(a)suse.com Subject: [suse-autoinstall] YaST2 Doesn't Search for Source Packages Hi guys, This isn't an autoyast question, but it involves an installation server, and I'll bet someone here will know the answer... More to the point, I'm adding packages for my company's software, and I want to do it right! :) With YaST2 pointing at an SLES9 installation server, I find that "Install and Remove Software" does not find the source packages for a given name when you do a search on it (with the filter in search mode). The sources are part of the distro though, and sometimes someone in my dept. wants to study them... For example, the k3b binary package is found if you search for it, but not the source package. The two packages are in the CD1 and CD3 directories, respectively, on the server: ./SUSE-CORE-Version-9/CD1/suse/i586/k3b-0.11.7-23.1.i586.rpm ./SUSE-CORE-Version-9/CD3/suse/src/k3b-0.11.7-23.1.src.rpm The package database on the server (./SUSE-CORE-Version-9/CD1/suse/setup/descr/packages) is standard SLES9, and I see that both the binary and source packages for k3b are listed there. Why doesn't YaST2 find it? Is there something in the syntax of the packages file that indicates whether it should be found by the YaST2 search? Thanks. -- Charlie ----- A. Charles Suffin Senior Software Engineer Stratus Technologies, Inc. (http://www.stratus.com) 111 Powdermill Road Maynard, MA 01754-3409 US (978)461-7590 -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com -- 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] user dialog during post install/config
by Schumacher, Gordon 09 Mar '05

09 Mar '05

I'm doing it like this: <init-scripts config:type="list"> <script> <filename>1-get_username_launch.sh</filename> <interpreter>shell</interpreter> <source><![CDATA[ #!/bin/sh wget http://toolsgrp.corp.mxtr.net/autoinstall/scripts/get_username.sh chmod +x get_username.sh exec ./get_username.sh ]]> </source> </script> I've attached my get_username script (with some site-specific stuff edited out). It's been working pretty well for me, with the caveat that you can't see the text output of the "passwd" command (for whatever reason, it ignores the previous "exec" command. I've been contemplating writing a replacement for the sole purpose of autoinstallation, that will output to stdout. (I'm assuming that there's a good security reason for it to ignore stdout, but for this purpose it would be acceptible to me not to.) -----Original Message----- From: Mark Acosta [mailto:mark@auditude.com] Sent: Tuesday, March 08, 2005 12:32 PM To: suse-autoinstall(a)suse.com Subject: [suse-autoinstall] user dialog during post install/config Is there a mechanism/(set of xml tags) to enable user dialogs during post install/config? We need some of our auto-installs to have a user manually enter hostname and network details,etc. thanks, Mark -- 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] YaST2 Doesn't Search for Source Packages
by Ness, Todd 09 Mar '05

09 Mar '05

Try to grep src out of the CD1/suse/setup/descr/packages if it is in there I think the yast sw_single module should be able to see it. You can create packages files with /usr/lib/YaST2/bin/create_package_descr -----Original Message----- From: Suffin, Charles [mailto:Charles.Suffin@stratus.com] Sent: Wednesday, March 09, 2005 1:27 PM To: suse-autoinstall(a)suse.com Subject: [suse-autoinstall] YaST2 Doesn't Search for Source Packages Hi guys, This isn't an autoyast question, but it involves an installation server, and I'll bet someone here will know the answer... More to the point, I'm adding packages for my company's software, and I want to do it right! :) With YaST2 pointing at an SLES9 installation server, I find that "Install and Remove Software" does not find the source packages for a given name when you do a search on it (with the filter in search mode). The sources are part of the distro though, and sometimes someone in my dept. wants to study them... For example, the k3b binary package is found if you search for it, but not the source package. The two packages are in the CD1 and CD3 directories, respectively, on the server: ./SUSE-CORE-Version-9/CD1/suse/i586/k3b-0.11.7-23.1.i586.rpm ./SUSE-CORE-Version-9/CD3/suse/src/k3b-0.11.7-23.1.src.rpm The package database on the server (./SUSE-CORE-Version-9/CD1/suse/setup/descr/packages) is standard SLES9, and I see that both the binary and source packages for k3b are listed there. Why doesn't YaST2 find it? Is there something in the syntax of the packages file that indicates whether it should be found by the YaST2 search? Thanks. -- Charlie ----- A. Charles Suffin Senior Software Engineer Stratus Technologies, Inc. (http://www.stratus.com) 111 Powdermill Road Maynard, MA 01754-3409 US (978)461-7590 -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

YaST2 Doesn't Search for Source Packages
by Suffin, Charles 09 Mar '05

09 Mar '05

Hi guys, This isn't an autoyast question, but it involves an installation server, and I'll bet someone here will know the answer... More to the point, I'm adding packages for my company's software, and I want to do it right! :) With YaST2 pointing at an SLES9 installation server, I find that "Install and Remove Software" does not find the source packages for a given name when you do a search on it (with the filter in search mode). The sources are part of the distro though, and sometimes someone in my dept. wants to study them... For example, the k3b binary package is found if you search for it, but not the source package. The two packages are in the CD1 and CD3 directories, respectively, on the server: ./SUSE-CORE-Version-9/CD1/suse/i586/k3b-0.11.7-23.1.i586.rpm ./SUSE-CORE-Version-9/CD3/suse/src/k3b-0.11.7-23.1.src.rpm The package database on the server (./SUSE-CORE-Version-9/CD1/suse/setup/descr/packages) is standard SLES9, and I see that both the binary and source packages for k3b are listed there. Why doesn't YaST2 find it? Is there something in the syntax of the packages file that indicates whether it should be found by the YaST2 search? Thanks. -- Charlie ----- A. Charles Suffin Senior Software Engineer Stratus Technologies, Inc. (http://www.stratus.com) 111 Powdermill Road Maynard, MA 01754-3409 US (978)461-7590

1 0

AW: AW: [suse-autoinstall] SLES 8 - Removing of packages during Installation failed[Auf Viren geprüft]
by Diener, Stefan 09 Mar '05

09 Mar '05

Anas, i´ve got it from the autoyast2-sles8.pdf available at your homepage at this moment. section 5.5 example 4.24 Stefan ________________________________ Von: Anas Nashif [mailto:nashif@suse.de] Gesendet: Di 08.03.2005 20:46 An: skarsch(a)s1.karsch-net.de Cc: 'Hubertus A. Haniel'; Diener, Stefan; suse-autoinstall(a)suse.com Betreff: Re: AW: [suse-autoinstall] SLES 8 - Removing of packages during Installation failed[Auf Viren geprüft] Frank, Where exactly is this documented? Anas Frank Hollmann wrote: > Hi, > > the <remove-packages> Tag was dokumented for SLES8, but appearently > never worked. I'd call that a bug. > > > Frank > > -----Ursprüngliche Nachricht----- Von: Hubertus A. Haniel > [mailto:hubba@unixcook.com] Gesendet: Dienstag, 8. März 2005 16:24 > An: Diener, Stefan Cc: suse-autoinstall(a)suse.com Betreff: Re: > [suse-autoinstall] SLES 8 - Removing of packages during Installation > failed[Auf Viren geprüft] > > On Tue, 8 Mar 2005, Diener, Stefan wrote: > >> Date: Tue, 8 Mar 2005 14:49:21 +0100 From: "Diener, Stefan" >> <Stefan.Diener(a)isoft.de> To: suse-autoinstall(a)suse.com Subject: >> [suse-autoinstall] SLES 8 - Removing of packages during > Installation >> failed >> >> Hi group, >> >> i´m having a little problem with the software package configuration >> using > autoyast installation. I want to uninstall some packages > automatically during the autoyast installation. Here is the software > section from my xml file: >> >> ------------------------------------------------------------------------ >> <software> <addons config:type="list"/> <base>default</base> >> <packages config:type="list"> <package>kernel-source</package> >> </packages> <remove-packages config:type="list"> >> <package>capi4linux</package> <package>i4l-isdnlog</package> >> <package>i4lfirm</package> <package>i4l-base</package> >> </remove-packages> </software> >> ---------------------------------------------------------------------- >> -- >> >> The installation of the additonal package "kernel-source" is okay, >> but the > uninstallation of the i4l package doesn´t work. A manual removing > with the rpm -e command in the order shown above works fine. >> >> Any ideas? >> > > > I belive the remove-packages syntax was not supported in SLES8 and is > a SLES9 feature - you will have to edit the selection files instead > or create your own. > > Best regards Hubba > > -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

2 1

user dialog during post install/config
by Mark Acosta 08 Mar '05

08 Mar '05

Is there a mechanism/(set of xml tags) to enable user dialogs during post install/config? We need some of our auto-installs to have a user manually enter hostname and network details,etc. thanks, Mark

1 0

Bonding in Suse 9 - Need setup info
by Dana Jaeger 07 Mar '05

07 Mar '05

Hi, I am running Suse 9 (Kernel 2.6.5-7.147-bigsmp). I would like to set up bonding for dual nic failover. Can someone please tell me if this is possible and provide setup inforamation (what packages are needed, where and what files need to be created, along with samples if possible.) Also I can't seem to find much documention on this. Would anyone know where I might find some? Thanks very much, Dana Jaeger Hartford Hospital jaeger(a)harthosp.org

1 0

Wondering about grafting my own packages on SuSE pro 9.2 for autoinstall....
by Marlier, Ian 05 Mar '05

05 Mar '05

I've got a couple of RPMs that I maintain for local install -- apps with non-standard configurations, or apps specific to my network. I'm wondering what the recommended method is for adding them to a SuSE 9.2 distribution for autoinstall... Is there an option other than copying them into the distribution directory and then rebuilding the distro? Some way to tell autoyast to go somewhere else to find some packages?

2 1

autoyast tries to install into memory disk
by Jeremy Sanders 04 Mar '05

04 Mar '05

I've finally solved my raid partitioning problem (though autoyast does try to use the separate swap devices in the swap raid for swap, sigh). However, now yast tries to install the distribution into memory disk (or at least somewhere with not enough room). It fails a couple of minutes in with a ERROR(InstTarget:E_RpmDB_subprocess_failed). I have /dev/md0 specified as /, so I have no idea why it's not installing the distribution there. <drive> <device>/dev/md</device> <partitions config:type="list"> <partition> <filesystem config:type="symbol">xfs</filesystem> <format config:type="boolean">true</format> <create config:type="boolean">false</create> <mount>/</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">0</partition_nr> <raid_options> <raid_type>raid1</raid_type> </raid_options> <partition_type>primary</partition_type> </partition>  <partition> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <create config:type="boolean">false</create> <mount>swap</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">1</partition_nr> <raid_options> <raid_type>raid1</raid_type> </raid_options> </partition>  <partition> <filesystem config:type="symbol">xfs</filesystem> <format config:type="boolean">false</format> <create config:type="boolean">false</create> <mount>/soft3</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">2</partition_nr> <raid_options> <raid_type>raid1</raid_type> </raid_options> </partition> </partitions> <use>none</use> </drive> Maybe it's the use directive, but I can't see the possible values documented anywhere. I suppose autoyast may not like partitions with a partition_id of 0 or something... Thanks Jeremy -- Jeremy Sanders <jss(a)ast.cam.ac.uk> http://www-xray.ast.cam.ac.uk/~jss/ X-Ray Group, Institute of Astronomy, University of Cambridge, UK. Public Key Server PGP Key ID: E1AAE053

2 2

RE: [suse-autoinstall] CDROM Based Load With Network Access Confirmation
by Francois, Jean (J.L.) 04 Mar '05

04 Mar '05

>-----Original Message----- >From: Anas Nashif [mailto:nashif@suse.de] >Sent: Thursday, March 03, 2005 11:01 PM >To: Francois, Jean (J.L.) >Cc: suse-autoinstall(a)suse.com >Subject: Re: [suse-autoinstall] CDROM Based Load With Network >Access Confirmation > > > > >Francois, Jean (J.L.) wrote: >> I have an interesting problem I am trying to solve. > >(...) > >> Is there a way to trigger an AutoYaST install that : >> >> 1. does a complete install from the CDROM >> 2. reads the autoinst.xml control file from the floppy drive >3. grabs >> some content from a web server and does not get a 404 >> >> without having to write a <PRE> script or modify the install root >> image on the CDROM image? > >Why not use a pre-script? What is the problem with that? >How do you want to tell yast to contact a web server and do something >without using a script? > >Anas > >> >> If I do end up using lwp or wget, is there a smart way to integrate >> this so it can interrupt the install process if a file cannot be >> retrieved from a web server? >> >> -- >> Jean L. Francois Sends... >> - Enterprise Platform Engineering & Certification ( LINUX ) >> - Linux Counter Registered User #8863 1994-12-13 06:39:24 >> http://www.novell.com/linux/truth/ >> - Torquemada Linux - For the Inquisitive... >> > Hi Anas: I was just checking to see if anyone knew of another way before I went forward. Today, for network installs we use an ACL in the webserver so if the IP is not in the ACL the load fails. This is not as easy to do with a pure CDROM based install for license tracking. Since the AutoYaST control file is on a floppy I don't have control over it. In this case, I will just have to trust no one comes along with VI or notepad and changes anything :) My plan now is to use a <PRE> script to check /proc/cmdline for what type of CDROM based install is being done and use the result of the HTTP check as the trigger for whether or not to continue with the install. Thanks. -- Jean L. Francois - Enterprise Platform Engineering & Certification ( LINUX ) - Linux Counter Registered User #8863 1994-12-13 06:39:24 http://www.novell.com/linux/truth/ Torquemada Linux - For the Inquisitive...

1 0

RE: [suse-autoinstall] Integrating 3ware drivers into autoyast?
by Marlier, Ian 04 Mar '05

04 Mar '05

I've successfully autoyast'ed SuSE Pro 9.2 onto a number of machines with 3ware 9500-series RAID controllers without difficulty...it's recognized by the kernel, the correct modules (3w_9xxx.ko, which requires scsi_mod and maybe another) are loaded, etc. If the problem lies in installing the bootloader onto the controller card, well, that's one that I don't know how to solve. -----Original Message----- From: Phong Nguyen [mailto:phongn@gmail.com] Sent: Fri 3/4/2005 8:34 AM To: suse-autoinstall(a)suse.com Subject: [suse-autoinstall] Integrating 3ware drivers into autoyast? I will shortly be deploying SuSE Linux to a bunch of computers that use 3Ware 9500-series RAID controllers. For a variety of reasons we don't have an independant boot disks so we must boot off the RAID controller. Is there are way to integrate the drivers from 3ware into our autoyast system? Furthermore, 3ware claims that due to a bug in YaST a script (or series of scripts) must be run before YaST completes in the standard GUI install. Is anyone familiar with doing this? I see that there are sections on how to include shell scripts in the Auto Installer website but not on how I might include various drivers. Thanks, Phong. -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

Integrating 3ware drivers into autoyast?
by Phong Nguyen 04 Mar '05

04 Mar '05

I will shortly be deploying SuSE Linux to a bunch of computers that use 3Ware 9500-series RAID controllers. For a variety of reasons we don't have an independant boot disks so we must boot off the RAID controller. Is there are way to integrate the drivers from 3ware into our autoyast system? Furthermore, 3ware claims that due to a bug in YaST a script (or series of scripts) must be run before YaST completes in the standard GUI install. Is anyone familiar with doing this? I see that there are sections on how to include shell scripts in the Auto Installer website but not on how I might include various drivers. Thanks, Phong.

1 0

Manual Parititioning with autoyast .
by Yogesh Bhanu 04 Mar '05

04 Mar '05

Hi , I have just started using autoyast and have met with some success . We have plethora of systems with different disks types and sizes . Is it possible that while running autoyast I can choose my partitioning schema. I mean while running my autoconf.xml I can choose which disks I want to use and with which partition . Thanks in advance yogesh

1 0

CDROM Based Load With Network Access Confirmation
by Francois, Jean (J.L.) 04 Mar '05

04 Mar '05

I have an interesting problem I am trying to solve. Due to the nature of where I am doing the install, I have dialup speeds and can't do effective network installs so I have to do a SLES8 and SLES9 Load from CDROM with the control file in the floppy drive. I want to be able to make sure the server that is doing the install has its IP address in the ACL at a tracking web server that would normally get used for AutoYaST installs. Is there a way to trigger an AutoYaST install that : 1. does a complete install from the CDROM 2. reads the autoinst.xml control file from the floppy drive 3. grabs some content from a web server and does not get a 404 without having to write a <PRE> script or modify the install root image on the CDROM image? If I do end up using lwp or wget, is there a smart way to integrate this so it can interrupt the install process if a file cannot be retrieved from a web server? -- Jean L. Francois Sends... - Enterprise Platform Engineering & Certification ( LINUX ) - Linux Counter Registered User #8863 1994-12-13 06:39:24 http://www.novell.com/linux/truth/ - Torquemada Linux - For the Inquisitive...

2 1

RE: [suse-autoinstall] autoyast2 and LVM creation
by Marlier, Ian 03 Mar '05

03 Mar '05

And now I'll answer my own question, because I figured it out about 10 seconds after sending this e-mail. The problem was this parameter: <size>max</size> Which I used when defining the size of the Logical Volume. Unfortunately, this isn't a supported behavior. You have to specify a size in the standard <size>XXXgb</size> format. Which makes sense, but it would be nice to be able to do a <size>max</size> (if anyone out there who's reading this happens to feel like making that happen :-) - Ian -----Original Message----- From: Marlier, Ian [mailto:ian.marlier@studentuniverse.com] Sent: Thursday, March 03, 2005 1:37 PM To: suse-autoinstall(a)suse.com Subject: [suse-autoinstall] autoyast2 and LVM creation I found a message about this exact problem from way back (7 April 2004 -- http://lists.suse.com/archive/suse-autoinstall/2004-Apr/0026.html) but there wasn't an answer to it. I'm hoping that there might be one now... When running an autoinstall using a control file that has an LVM group configured in it, I consistently get an error that the Logical Volume needs more space during the software selection configuration section. =20 After that message times out, the setup process continues, then halts with an error when it tries to create the Logical Volume. The error in that case is "lvm create_lv invalid parameter". Once the second error comes up, I can manually create the Logical Volume with the standard `lvcreate -n space vg_name` command. I'm using autoyast2, and installing SuSE pro 9.2. The relevant section of the configuration file is this: <drive> <device>/dev/sdc</device> <partitions config:type=3D"list"> <partition> <lvm_group>suvg</lvm_group> <partition_type>primary</partition_type> <size>max</size> </partition> </partitions> <use>all</use> </drive> <drive> <device>/dev/suvg</device> <is_lvm_vg config:type=3D"boolean">true</is_lvm_vg> <partitions config:type=3D"list"> <partition> <filesystem config:type=3D"symbol">jfs</filesystem> <lv_name>space_lv</lv_name> <mount>/space</mount> <size>max</size> </partition> </partitions> <use>all</use> </drive> -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

autoyast2 and LVM creation
by Marlier, Ian 03 Mar '05

03 Mar '05

I found a message about this exact problem from way back (7 April 2004 -- http://lists.suse.com/archive/suse-autoinstall/2004-Apr/0026.html) but there wasn't an answer to it. I'm hoping that there might be one now... When running an autoinstall using a control file that has an LVM group configured in it, I consistently get an error that the Logical Volume needs more space during the software selection configuration section. =20 After that message times out, the setup process continues, then halts with an error when it tries to create the Logical Volume. The error in that case is "lvm create_lv invalid parameter". Once the second error comes up, I can manually create the Logical Volume with the standard `lvcreate -n space vg_name` command. I'm using autoyast2, and installing SuSE pro 9.2. The relevant section of the configuration file is this: <drive> <device>/dev/sdc</device> <partitions config:type=3D"list"> <partition> <lvm_group>suvg</lvm_group> <partition_type>primary</partition_type> <size>max</size> </partition> </partitions> <use>all</use> </drive> <drive> <device>/dev/suvg</device> <is_lvm_vg config:type=3D"boolean">true</is_lvm_vg> <partitions config:type=3D"list"> <partition> <filesystem config:type=3D"symbol">jfs</filesystem> <lv_name>space_lv</lv_name> <mount>/space</mount> <size>max</size> </partition> </partitions> <use>all</use> </drive>

1 0

Dhcp Problems?
by Matt Poepping 03 Mar '05

03 Mar '05

I am trying to autoyast a machine, and when it is plugged directly into another machine it works fine, but when I plug it into the network, the dhcp servers do not seem to be responding fast enough for it and then install will fail to manual mode. In manual mode, it can then go out and get a dhcp address. I have tried editing the linuxrc.config file within the initrd file, to up the timeout, but that doesn't seem to work. I've also tried to point to an info file with the same info, and that seems to be ignored also. Thanks, Matt

2 1

Script length issue?
by Schumacher, Gordon 02 Mar '05

02 Mar '05

I'm doing an autoinstall under SuSE 9.2, and I have one reasonably long script (~100 or so lines). I'm finding that under the autoinstaller, it is terminating after line 68 (no matter what that line is). If I run the very same script in a normal BASH shell, it runs fine. Is there perhaps a bug in the autoinstaller that could cause this? Or have I run into something else?

1 0

Re: WELCOME to suse-autoinstall@suse.com
by Luca Pacor 02 Mar '05

02 Mar '05

Hello everybody, I am asking myself whether it would be possible to online_update the autoinstall repository: it would be nice to be able to install new machines using an up-to-date repository reducing this way the install time ... Any hint would be greatly appreciated. Many thanks in advance Luca

1 1

SLES9 SP1 Multisource
by Lee Mayes 02 Mar '05

02 Mar '05

We recently downloaded SLES9 SP1 iso's and I integrated them into our HTTP installation tree as outlined by Anas in a previous memo. However, when I went to install from them, the actual RPMS were not in the path the client was looking for them. My setup: /sles9/CD1/ /core9/CD[1-5]/ /SLES9-SP1/CD[1-3]/ Symlinks as directed # cat yast/instorder /SLES9-SP1/CD1 /sles9/CD1 /core9/CD1 # cat yast/order /SLES9-SP1/CD1 /SLES9-SP1/CD1 /sles9/CD1 /sles9/CD1 /core9/CD1 /core9/CD1 Looking at the errors in apache's logfile, the clients are attempting to find the SP1 RPMS at /SLES9-SP1/CD1/suse/i586/ (and i686 or noarch). However, on my isos the RPMS are actually at the path: /SLES9-SP1/CD1/i386/update/SUSE-CORE/9/rpm/i586 Creating symlinks to i586/i686/noarch under /suse to ../i386/update/SUSE-CORE/9/rpm allowed my installations to work, but I'm wondering if I have something setup incorrectly, or perhaps we downloaded the wrong SLES9 SP1 iso images from Novell? Here's what we have: # cat SLES-9-SP-1.MD5SUM 3282ab591c3bf1d50053e837026d15e0 SLES-9-SP-1-i386-RC5-CD1.iso 320b3c795f9732a7f45ec6323dab9240 SLES-9-SP-1-i386-RC5-CD2.iso 36e798f4868aece793b592c3d0f05e62 SLES-9-SP-1-i386-RC5-CD3.iso Thanks and Best Regards, Lee

1 0

RE: [suse-autoinstall] post-install scripts
by Suffin, Charles 02 Mar '05

02 Mar '05

Todd, Thanks for the reply. I think what's going on is that you're installing 9.2 or something other than SLES9, and this was the source of my confusion... After discussing this last week, I think some of us concluded that your script simply wouldn't work on SLES9... I have noted that the network is not yet operational during the post-install scripting execution environment of SLES9 when I was working with it a couple of months ago. I think it is necessary to either bring up the network in the script via ifconfig ethX up (Andreas suggested this, I have not tried it myself), or you can simply wget the files that you need during a chroot-script instead and store them on the disk for when you need it (in /mnt, that is, which becomes root during post-install). Best wishes. -----Original Message----- From: Ness, Todd [mailto:todd.ness@eds.com] Sent: Wednesday, March 02, 2005 9:38 AM To: suse-autoinstall(a)lists.suse.com Subject: RE: [suse-autoinstall] post-install scripts I am doing http installs i.e. install=http://1.1.1.1/directory/CD1 autoyast=http://1.1.1.1/install/autoinstall.xml Either in the info file or on the boot cd command line. -----Original Message----- From: Suffin, Charles [mailto:Charles.Suffin@stratus.com] Sent: Thursday, February 24, 2005 9:26 AM To: 'Andreas.Matthieu(a)tfa.brandenburg.de'; Suffin, Charles; suse-autoinstall(a)lists.suse.com Subject: RE: [suse-autoinstall] post-install scripts What you're saying is great, guys (thanks!), but Todd's post-install script in his XML fragment does not do network initialization (I think) before executing wget. I do not understand why his script works... Thanks! -- Charlie p.s./ I didn't mean to rathole Mitko's original email! I am shutting up now! :) -----Original Message----- From: Andreas.Matthieu(a)tfa.brandenburg.de [mailto:Andreas.Matthieu@tfa.brandenburg.de] Sent: Thursday, February 24, 2005 11:21 AM To: Charles.Suffin(a)stratus.com; suse-autoinstall(a)lists.suse.com Subject: AW: [suse-autoinstall] post-install scripts Hi Charles, at postinstall step network are not running [SLES9: AY boot, setup network, install packages (second step), stop network, configure network (but let it down), start postscripts, continue boot with startup network]. Try "ifconfig ethX up" in postscript before use network. Regards, Andreas -----Ursprüngliche Nachricht----- Von: Charles.Suffin(a)stratus.com [SMTP:Charles.Suffin@stratus.com] Gesendet am: Donnerstag, 24. Februar 2005 16:41 An: todd.ness(a)eds.com; suse-autoinstall(a)lists.suse.com Betreff: RE: [suse-autoinstall] post-install scripts Hmm... OK, I'd swear I was unable to use http: during my post-install scripts (when I did my testing), but maybe I goofed. Thanks! -----Original Message----- From: Ness, Todd [mailto:todd.ness@eds.com] Sent: Thursday, February 24, 2005 10:36 AM To: suse-autoinstall(a)lists.suse.com Subject: RE: [suse-autoinstall] post-install scripts This happens during the post-scripts section of the auto install process. Also, I am doing network builds so the networking has to be up and running. So, I download one script that downloads and executes the rest of the scripts. <scripts> <pre-scripts config:type="list"> </pre-scripts> <post-scripts config:type="list"> <script> <filename>cleanup</filename> <interpreter>shell</interpreter> <source> <![CDATA[ echo writing profile echo "d-default" > /etc/MSDprofile echo getting scripts /usr/bin/wget http://1.2.3.4/install/postinst.sh -O /tmp/postinst.sh chmod 555 /tmp/postinst.sh /tmp/postinst.sh exit 0]]> </source> </script> </post-scripts> </scripts> -----Original Message----- From: Suffin, Charles [mailto:Charles.Suffin@stratus.com] Sent: Thursday, February 24, 2005 7:38 AM To: Ness, Todd; suse-autoinstall(a)lists.suse.com Subject: RE: [suse-autoinstall] post-install scripts Guys, quick question... I found that the post-install scripting environment -- which runs after the reboot -- didn't have networking set up yet (whereas chroot scripts run before the reboot and have the network running). Do you guys (Todd) do some magic to enable the network for the operation of post-install scripts so you could use wget? What I do is use wget during chroot scripts and store the files in /mnt/... (which gets mounted as root after the reboot). -- Charlie -----Original Message----- From: Ness, Todd [mailto:todd.ness@eds.com] Sent: Thursday, February 24, 2005 9:31 AM To: suse-autoinstall(a)lists.suse.com Subject: RE: [suse-autoinstall] post-install scripts Just a thought, I wrote a post-install wrapper that gets scripts via wget and those scripts are S01name.. S20name and then executes them serially similar to rc startup scripts. -----Original Message----- From: Anas Nashif [mailto:nashif@suse.de] Sent: Thursday, February 24, 2005 7:15 AM To: Mitko Haralanov Cc: suse-autoinstall(a)lists.suse.com Subject: Re: [suse-autoinstall] post-install scripts They are executed in the order they appear in the XMl file. Anas Mitko Haralanov wrote: > I have recently started working on a autoyast configuration file for > SuSE9.1. In the process of generating the file, I have created several > post-install scripts which configure different parts of the system. > The question that I have is: what is the order in which the scripts > are going to be executed? Currently some of the post-install scripts > depend on others and I need to be sure in what order they will be > executed. > > Thanx > -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

2 1

multiple raid and autoyast
by Jeremy Sanders 02 Mar '05

02 Mar '05

Hi - I'm trying to make a autoyast configuration file which will install a machine with 3 software raid 1 devices (root, swap, and a data partition) using SLES 9. The partitions will already exist on the drives. Unfortunately this doesn't seem to work. yast seems to want to mount the individual component partitions as /data1 ... /data6. It only seems to want to use the /dev/md2 device, and ignores md0-md1. Can anyone see the problem, or does someone have a similar working file I can look at?  <partitioning config:type="list"> <drive> <device>/dev/hda</device> <partitions config:type="list">  <partition> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">1</partition_nr> <format config:type="boolean">false</format> <create config:type="boolean">false</create> <raid_name>/dev/md0</raid_name> <raid_type>raid</raid_type> </partition>  <partition> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">2</partition_nr> <format config:type="boolean">false</format> <create config:type="boolean">false</create> <raid_name>/dev/md1</raid_name> <raid_type>raid</raid_type> </partition>  <partition> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">3</partition_nr> <format config:type="boolean">false</format> <create config:type="boolean">false</create> <raid_name>/dev/md2</raid_name> <raid_type>raid</raid_type> </partition> </partitions> </drive> <drive> <device>/dev/hdb</device> <partitions config:type="list">  <partition> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">1</partition_nr> <format config:type="boolean">false</format> <create config:type="boolean">false</create> <raid_name>/dev/md0</raid_name> <raid_type>raid</raid_type> </partition>  <partition> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">2</partition_nr> <format config:type="boolean">false</format> <create config:type="boolean">false</create> <raid_name>/dev/md1</raid_name> <raid_type>raid</raid_type> </partition>  <partition> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">3</partition_nr> <format config:type="boolean">false</format> <create config:type="boolean">false</create> <raid_name>/dev/md2</raid_name> <raid_type>raid</raid_type> </partition> </partitions> </drive>  <drive> <device>/dev/md</device> <partitions config:type="list"> <partition> <filesystem config:type="symbol">xfs</filesystem> <format config:type="boolean">true</format> <mount>/</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">0</partition_nr> <raid_options> <raid_type>raid1</raid_type> </raid_options> </partition> </partitions> </drive>  <drive> <device>/dev/md</device> <partitions config:type="list"> <partition> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <mount>swap</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">1</partition_nr> <raid_options> <raid_type>raid1</raid_type> </raid_options> </partition> </partitions> </drive>  <drive> <device>/dev/md</device> <partitions config:type="list"> <partition> <filesystem config:type="symbol">xfs</filesystem> <format config:type="boolean">false</format> <mount>/soft3</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">2</partition_nr> <raid_options> <raid_type>raid1</raid_type> </raid_options> </partition> </partitions> </drive> </partitioning> Thanks Jeremy -- Jeremy Sanders <jss(a)ast.cam.ac.uk> http://www-xray.ast.cam.ac.uk/~jss/ X-Ray Group, Institute of Astronomy, University of Cambridge, UK. Public Key Server PGP Key ID: E1AAE053

1 3

RE: [suse-autoinstall] post-install scripts
by Ness, Todd 02 Mar '05

02 Mar '05

I am doing http installs i.e. install=http://1.1.1.1/directory/CD1 autoyast=http://1.1.1.1/install/autoinstall.xml Either in the info file or on the boot cd command line. -----Original Message----- From: Suffin, Charles [mailto:Charles.Suffin@stratus.com] Sent: Thursday, February 24, 2005 9:26 AM To: 'Andreas.Matthieu(a)tfa.brandenburg.de'; Suffin, Charles; suse-autoinstall(a)lists.suse.com Subject: RE: [suse-autoinstall] post-install scripts What you're saying is great, guys (thanks!), but Todd's post-install script in his XML fragment does not do network initialization (I think) before executing wget. I do not understand why his script works... Thanks! -- Charlie p.s./ I didn't mean to rathole Mitko's original email! I am shutting up now! :) -----Original Message----- From: Andreas.Matthieu(a)tfa.brandenburg.de [mailto:Andreas.Matthieu@tfa.brandenburg.de] Sent: Thursday, February 24, 2005 11:21 AM To: Charles.Suffin(a)stratus.com; suse-autoinstall(a)lists.suse.com Subject: AW: [suse-autoinstall] post-install scripts Hi Charles, at postinstall step network are not running [SLES9: AY boot, setup network, install packages (second step), stop network, configure network (but let it down), start postscripts, continue boot with startup network]. Try "ifconfig ethX up" in postscript before use network. Regards, Andreas -----Ursprüngliche Nachricht----- Von: Charles.Suffin(a)stratus.com [SMTP:Charles.Suffin@stratus.com] Gesendet am: Donnerstag, 24. Februar 2005 16:41 An: todd.ness(a)eds.com; suse-autoinstall(a)lists.suse.com Betreff: RE: [suse-autoinstall] post-install scripts Hmm... OK, I'd swear I was unable to use http: during my post-install scripts (when I did my testing), but maybe I goofed. Thanks! -----Original Message----- From: Ness, Todd [mailto:todd.ness@eds.com] Sent: Thursday, February 24, 2005 10:36 AM To: suse-autoinstall(a)lists.suse.com Subject: RE: [suse-autoinstall] post-install scripts This happens during the post-scripts section of the auto install process. Also, I am doing network builds so the networking has to be up and running. So, I download one script that downloads and executes the rest of the scripts. <scripts> <pre-scripts config:type="list"> </pre-scripts> <post-scripts config:type="list"> <script> <filename>cleanup</filename> <interpreter>shell</interpreter> <source> <![CDATA[ echo writing profile echo "d-default" > /etc/MSDprofile echo getting scripts /usr/bin/wget http://1.2.3.4/install/postinst.sh -O /tmp/postinst.sh chmod 555 /tmp/postinst.sh /tmp/postinst.sh exit 0]]> </source> </script> </post-scripts> </scripts> -----Original Message----- From: Suffin, Charles [mailto:Charles.Suffin@stratus.com] Sent: Thursday, February 24, 2005 7:38 AM To: Ness, Todd; suse-autoinstall(a)lists.suse.com Subject: RE: [suse-autoinstall] post-install scripts Guys, quick question... I found that the post-install scripting environment -- which runs after the reboot -- didn't have networking set up yet (whereas chroot scripts run before the reboot and have the network running). Do you guys (Todd) do some magic to enable the network for the operation of post-install scripts so you could use wget? What I do is use wget during chroot scripts and store the files in /mnt/... (which gets mounted as root after the reboot). -- Charlie -----Original Message----- From: Ness, Todd [mailto:todd.ness@eds.com] Sent: Thursday, February 24, 2005 9:31 AM To: suse-autoinstall(a)lists.suse.com Subject: RE: [suse-autoinstall] post-install scripts Just a thought, I wrote a post-install wrapper that gets scripts via wget and those scripts are S01name.. S20name and then executes them serially similar to rc startup scripts. -----Original Message----- From: Anas Nashif [mailto:nashif@suse.de] Sent: Thursday, February 24, 2005 7:15 AM To: Mitko Haralanov Cc: suse-autoinstall(a)lists.suse.com Subject: Re: [suse-autoinstall] post-install scripts They are executed in the order they appear in the XMl file. Anas Mitko Haralanov wrote: > I have recently started working on a autoyast configuration file for > SuSE9.1. In the process of generating the file, I have created several > post-install scripts which configure different parts of the system. > The question that I have is: what is the order in which the scripts > are going to be executed? Currently some of the post-install scripts > depend on others and I need to be sure in what order they will be > executed. > > Thanx > -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

Creation of ISO in one minute ;)
by Pierre Allix 02 Mar '05

02 Mar '05

Hello, I wrote some scripts for easily creating AutoYaST ISOs. With few modifications in the configuration you can use them too. There is a cache system and others tips, so it is really fast (less than one minute on a good machine). You can customize your installation with pre and post scripts. You can also add any files, binaries that are not RPMS for instance, they'll be available in the final root system. It only creates ISOs for the equivalent of 'Minimal' installation but you can change this by modifying one file. You can find the scripts here : http://kototama.free.fr/perl/suse/suse3.tgz They are released under the GPL license version 2. You'll also need these files : http://kototama.free.fr/perl/suse/root http://kototama.free.fr/perl/suse/rescue Installation instructions : $ export HTTP_PROXY=proxy:3128 $ wget http://kototama.free.fr/perl/suse/root (set HTTP_PROXY according to your network) $ wget http://kototama.free.fr/perl/suse/rescue $ wget http://kototama.free.fr/perl/suse/suse3.tgz $ tar xzf suse3.tgz $ mv root rescue suse3/autoyast/suse_data/iso_tree/boot/ $ cd suse3/autoyast $ less README Sorry for not just making one archive but I can't upload big files on this ftp. It is usefull for me, I hope it'll be usefull for you. Feedback is welcome. Pierre

1 0

specify install-server in the xml-file?
by suselist＠nlsn.nu 02 Mar '05

02 Mar '05

Hi, Im a novice with autoyast, but have used kickstart for several years. I have install-server (http) for installing NLD9 clients. I boot the machine with CD1 of NLD9 and enter "autoyast=http://server/profiles/profile1.xml install=http://server/image/NLD9/i386" and everything works. But, I want to embed the "install=" in the xml, is that possible? ( kickstart has url of image in the kickstart-profile ) I have tried with linuxrc but it doesnt work. Any pointers? Regards Daniel

2 2

dual boot problems
by mspark 02 Mar '05

02 Mar '05

I'm getting ready to install SUSE 9.2 I am doing a dual boot system with XP on the first primary partition and SUSE on the second primary partition. What do I need to know about before installation as far as partition problems. Currently I have 9.1 and my XP isn't accessable and I understand it is from "hidden NTFS' partitions. A problem that Yast causes in the boot partition table or something. Is this problem corrected in 9.2 or is there more fixes?? Thanks! __________________________________ Do you Yahoo!? Read only the mail you want - Yahoo! Mail SpamGuard. http://promotions.yahoo.com/new_mail

2 1

SSH access during automated install?
by Daniel 02 Mar '05

02 Mar '05

Hi list, I successfully installed my suse 9.2 servers via PXE boot, autoyast and an XML file. Now one of the machines seems to have trouble during the install - it just hangs (perhaps a bug in my test xml file). To avoid this in situations where I have no physical access to the machine I tried: usessh=1 and sshpassword=password as kernel parameters. (just to have a "backdoor" to reset the machine if it hangs...) When I now start an automated install the machine boots but WAITS for the ssh user to log on and start yast by hand, which isn´t quite practically during automated install ;-) How do I get access via SSH during install and still have fully automatic install? Thanks for your help! Daniel

2 1

auto-installing with patched OS
by Mark Acosta 02 Mar '05

02 Mar '05

I need to autoinstall a patched 2.6.8-24.11-default kernel (including patched utils) for Suse 9.2. The stock kernel is 2.6.8-24.10-default, but I can't find out how to patch/update to 2.6.8-24.11-default. How is the best accomplished? thanks, Mark

3 2

RE: [suse-autoinstall] chroot-scripts not running
by Schumacher, Gordon 01 Mar '05

01 Mar '05

Take a look at "isolinux.cfg" on the standard SuSE CD (or DVD) 1. That should show you how it needs to look. -----Original Message----- From: Suffin, Charles [mailto:Charles.Suffin@stratus.com] Sent: Thursday, February 24, 2005 8:22 PM To: suse-autoinstall(a)lists.suse.com Subject: RE: [suse-autoinstall] chroot-scripts not running Actually, I solved the problem by removing the isolinux timeout so that nothing proceeds beyond the "boot:" prompt until someone manually types a valid install target (or just <enter> to get the default). So, if someone leaves the CD in the drive and goes out for lunch, the machine will just be sitting at the prompt when they return. They can just pop out the CD and ctl-alt-del... I like your suggestion Fraser, although I don't quite understand how to specify boot from disk in isolinux.cfg -- the targets that you specify seem to be from the boot medium, in this case the CD. Anyway, thanks! -----Original Message----- From: Campbell, Fraser [mailto:Fraser.Campbell@tdsecurities.com] Sent: Thursday, February 24, 2005 9:17 PM To: suse-autoinstall(a)lists.suse.com Subject: RE: [suse-autoinstall] chroot-scripts not running Charles Suffin wrote: > The only problem is that if a target PC has the CD drive above the hard disk > (in BIOS boot list), you can get into an infinite loop of reinstalling the > machine on each reboot. Even when I added an "eject" command into my chroot > or pre-install script, these darn drives pull the CD back into the machine > when it resets/reboots! Have the default isolinux option be "boot from harddisk" that way unless someone is there to manually select the desired install method no reinstall can happen ... this is what we do and I agree CD is infinitely less hassle than PXE. Boot from harddisk is the default option on standard SuSE CDs (at least for Enterprise server) so you should be good just copying that config onto your customized install CDs. Fraser -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com -- 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] netsetup
by Schumacher, Gordon 01 Mar '05

01 Mar '05

I've had good luck with using this for user interaction (this is a fragment of a script which constructs a user account according to the user's input): #!/bin/sh /bin/chvt 9 exec < /dev/tty9 > /dev/tty9 ### BEGIN USER INTERACTION HERE ### ans="n" while [ 1 ] do echo Please enter your first and last name. You may enter a middle name echo or initial if you wish. read fullname while [ 0 ] do echo Is "$fullname" right $Y/N$?\ read ans if [[ "$ans" == "y" || "$ans" == "n" || "$ans" == "Y" || "$ans" == "N" ]] then break fi done if [[ "$ans" == "y" || "$ans" == "Y" ]] then break fi done ### END USER INTERACTION HERE ### /bin/chvt 7 -----Original Message----- From: Pierre Allix [mailto:pierre.allix@idealx.com] Sent: Wednesday, February 23, 2005 9:34 AM To: suse-autoinstall(a)suse.com Subject: Re: [suse-autoinstall] netsetup >That parameter only affects the very first setup of networking that >is used for installing packages. You have to set up the rest in >(auto)yast. > > > Ok, thanks. I suppose autoyast can't ask the user for this information (and only for these) or not ? I think I have to create a rc script. -- 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] Installing Additional Software
by Schumacher, Gordon 01 Mar '05

01 Mar '05

Try looking at section 4.5 in the AutoYaST manual; hopefully this will help. -----Original Message----- From: Daniel Spannbauer [mailto:ds@marco.de] Sent: Wednesday, February 23, 2005 8:45 AM To: suse-autoinstall(a)lists.suse.com Subject: [suse-autoinstall] Installing Additional Software Hello, i'm working under SuSE 9.2. I've made a Config-File with Yast2, started an DHCP-Server, NFS-Server und TFTP-Server. I run Autoyast with PXE-Boot and it works very well. But now I wan't to install a Not-SuSE-Package auomaticaly after the SuSE-Installation is done. The rpm-File is at the same Path as the Suse-RPMs are (on a NFS-Share) How do I setup up this? Can I do this in Yast too? I'm not good in XML so a graphical Solution would be nice. Thanks Daniel -- Daniel Spannbauer EDV Systembetreuung marco Systemanalyse und Entwicklung GmbH Tel +49 8333 9233-66 Auf der Wies 8, D 87727 Babenhausen Fax +49 8333 9233-11 http://www.marco.de/ Email ds(a)marco.de -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

More mysteries: LDAP
by Ole Streicher 01 Mar '05

01 Mar '05

Hi group again, my fiddling with the autoyast configuration options continues. I have the following entry in my xml file: <ldap> <base_config_dn>dc=mydomain,dc=de</base_config_dn> <create_ldap config:type="boolean">true</create_ldap> <file_server config:type="boolean">false</file_server> <ldap_domain>dc=mydomain,dc=de</ldap_domain> <ldap_server>ldap</ldap_server> <ldap_tls config:type="boolean">false</ldap_tls> <ldap_v2 config:type="boolean">false</ldap_v2> <member_attribute>member</member_attribute> <pam_password>crypt</pam_password> <start_ldap config:type="boolean">true</start_ldap> </ldap> The server "ldap" is resolvable via our DNS server. Autoyast triggers the "ldap" authentication (/etc/nsswitch.conf contains a "passwd_compat: ldap" line), but the ldap configuration itself is done just half-way. The file /etc/ldap.conf is created with follwing contents (comment lines removed): host 127.0.0.1 base dc=example,dc=com ldap_version 3 pam_password crypt ssl start_tls pam_filter objectclass=posixAccount nss_base_passwd dc=mydomain,dc=de nss_base_shadow dc=mydomain,dc=de nss_base_group dc=mydomain,dc=de >From the last three lines I can see that there is "something" configured in the file, but why are the "host" and "base" lines kept unusable? They are clearly defined in my XML config. Is this something I did wrong or is it just one more bug of autoyast? Best regards Ole -- DSL Komplett von GMX +++ Superg�nstig und stressfrei einsteigen! AKTION "Kein Einrichtungspreis" nutzen: http://www.gmx.net/de/go/dsl

3 2