May 2004 - openSUSE Autoinstall - openSUSE Mailing Lists

RE: [suse-autoinstall] How to add customized packages in AutoYast2 in SLES9?
by You, Yongkang 31 May '04

31 May '04

Thank you very much! I installed the rpm and got the command. It works. While I have other questions of autoyast: If I want to contribute and provide an additional CD including extra RPMs packages in SLES9, how can I add the whole CD into autoyast installation process like other Core CDs? If some RPMs in this extra CD are conflicted with the former Core CDs (even if the rpm package version is lower than the SLES9), is there any way to let the auto process only install the RPMs in the extra CD but not in the Core CDs? Regards, You, Yongkang( Kangkang ) -----Original Message----- From: Martin Vidner [mailto:mvidner@suse.cz] Sent: 2004年5月28日 21:03 To: suse-autoinstall(a)suse.com Subject: Re: [suse-autoinstall] How to add customized packages in AutoYast2 in SLES9? On Fri, May 28, 2004 at 05:18:49PM +0800, You, Yongkang wrote: > I created a control file and used PXE + NFS source server to > automatically install SLES9 beta6. The basic installation can be > successful if I followed AutoYast2 document for SLES8. While I also want > to install some additional personal packages by AutoYast2. The SLES8 > document introduces a command: create_package_descr to create the new > package database for installation. But I failed to find this command in > the new SLES9 System. It doesn't locate in: /usr/lib/YaST2/bin/ or other > place. It's in autoyast2-utils.rpm, /usr/bin/create_package_descr. -- Martin Vidner, developer SuSE CR, s.r.o. e-mail: mvidner(a)suse.cz Drahobejlova 27 tel:+420-296542373 190 00 Praha 9, Czech Republic http://www.suse.cz -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

How to add customized packages in AutoYast2 in SLES9?
by You, Yongkang 28 May '04

28 May '04

Hello, I met a problem of using AutoYast2 to install SLES9 beta6. I created a control file and used PXE + NFS source server to automatically install SLES9 beta6. The basic installation can be successful if I followed AutoYast2 document for SLES8. While I also want to install some additional personal packages by AutoYast2. The SLES8 document introduces a command: create_package_descr to create the new package database for installation. But I failed to find this command in the new SLES9 System. It doesn't locate in: /usr/lib/YaST2/bin/ or other place. I don't know if there is a new way to add the extra personal packages into autoYast2 installation in SLES9. Or if there is any way to modify the package database myself? Is there any new Document for SLES9 AutoYast2? Can anyone help me please? Thanks and best Regards, You, Yongkang

2 1

SuSE 9.1 failed Setting up network after network-installation
by Hoepfner, Enrico 28 May '04

28 May '04

Hallo, i have installed SuSE 9.1 with autoyast successfully - nearly :-) After a complete installation over network, SuSE "failed Setting up network". lsmod show the right module for network-card (for example: 3c59x) ifconfig show only lo0 and sit0 the network-part of autoyast-config (which was ok for SuSE 9.0) is <networking> <dns> <dhcp_hostname config:type="boolean">true</dhcp_hostname> <dhcp_resolv config:type="boolean">true</dhcp_resolv> <domain></domain> <hostname></hostname> <nameservers config:type="list"/> <searchlist config:type="list"/> </dns> <interfaces config:type="list"> <interface> <bootproto>dhcp</bootproto> <device>eth0</device> <startmode>onboot</startmode> <wireless>no</wireless> </interface> </interfaces> <modules config:type="list"> <module_entry> <device>eth0</device> </module_entry> </modules> <routing> <ip_forward config:type="boolean">false</ip_forward> <routes config:type="list"/> </routing> </networking> can anyone help please thanks and best regards enrico

5 12

[suse-autoinstall] autoinstall (SuSE 9.1 Pro)
by Theo Gross 27 May '04

27 May '04

Hello, we discovered some problems with the autoinstall in SuSE 9.1 pro. We downloaded updates (rpms) from an ftp-server and then build a new package list as described in the documentation. Everything looked ok, but postfix and sshd did not start any more with the new package-list. The reason was, that some users and groups were missing. These users and groups could not be created (completely) with normal autoinstall-script. Since it was ok before the update, one or more of the updated rpms should be the source of the trouble. Looking at the updated packages i found yast2-users-2.9.29-0.2.i586.rpm to be the favourite candiate for the break. After removing it from the packagelist everything (in this context) worked as expected. Another issue dials with the file: /etc/opt/kde3/share/config/kdm/kdmrc Since yast-configuration does not offer all the options we need, we copied the file to this location during install using the "complete configuration files" option from autoyast. But after the installation the expected content was not in the file. It was overwritten from the installation process. I think this is a error, which shoult be fixed. A quick solution was to use a "post-install" script to put the file in its position. --- Theo Groß Sysadmin WsPool Informatik/ServiceGruppe University of Ulm theo.gross(a)informatik.uni-ulm.de James-Franck-Ring Work: 0731/50-24205 89081 Ulm Fax: 0731/50-24202 Germany

3 3

SUSE 9.1 Autoyast woes
by Peter Schwenk 25 May '04

25 May '04

Hello: I'm new to SUSE and autoyast. I've been using Red Hat for years now and automating installations with their Kickstart scheme. Since Fedora, I've been looking for a better distribution, and SUSE, once installed, seems to be very nice. Everything's there and already nicely configured for my average user. Autoyast, however, is eluding me. So far, I realize that I need a floppy disk with an 'info' file to load the right network interface modules and assign the IP address, etc. I've generated an autoinst.xml file using the 'autoyast' module of yast2, but the install seems to ignore my disk partitioning directives. I want yast to wipe the drive of existing partitions and make 4 new ones: /, swap, /boot, and /home. Here's an excerpt from my autoinst.xml file that's supposed to be doing this: <partitioning config:type="list"> <drive> <device>/dev/hda</device> <initialize config:type="boolean">true</initialize> <partitions config:type="list"> <partition> <crypt>twofish256</crypt> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <loop_fs config:type="boolean">false</loop_fs> <mount>/</mount> <partition_id config:type="integer">131</partition_id> <size>10000</size> </partition> <partition> <crypt>twofish256</crypt> <filesystem config:type="symbol">ext2</filesystem> <format config:type="boolean">true</format> <loop_fs config:type="boolean">false</loop_fs> <mount>/boot</mount> <partition_id config:type="integer">131</partition_id> <size>auto</size> </partition> <partition> <crypt>twofish256</crypt> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <loop_fs config:type="boolean">false</loop_fs> <mount>swap</mount> <partition_id config:type="integer">130</partition_id> <size>auto</size> </partition> <partition> <crypt>twofish256</crypt> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <loop_fs config:type="boolean">false</loop_fs> <mount>/home</mount> <partition_id config:type="integer">131</partition_id> <size>max</size> </partition> </partitions> <use>all</use> </drive> </partitioning> While yast is running, it looks like it is trying to partition, format, and mount the partitions, but it isn't successful. After choosing "Continue" several times, the installation proceeds, but the ramdisk (I'm assuming) is the place where stuff is getting installed. The filesystem fills up after a short time, and yast asks if I want to abort the installation, which I do. Does anyone have any ideas why my partitioning scheme isn't being accepted? A manual install from the same NFS source seems to proceed without incident. The manual install asks for confirmation of several kernel modules, mostly USB stuff but there's a couple dm_* modules loaded by yast, too. The machine is a Gateway E-1800 (Celeron 1300MHz, IDE disks, 256MB RAM, on-board Intel graphics). -- - Peter A. Schwenk | Mathematical Sciences - schwenk(a)math.udel.edu | University of Delaware - (302) 831-0437 | Newark, DE 19716-2553 USA

5 11

autoyast fails with HTTP virtual hosts
by Rajiv Aaron Manglani 25 May '04

25 May '04

i believe that there is a bug in autoyast when installing via an http server. yast does not properly support the 'Host' http header. because of this you cannot install from an http server that is setup with virtual hosts. the examples below show public suse mirrors, however i found this problem while trying to use our own in-house mirror. how to replicate the problem: boot the 9.0 install cd. pass "install=http://ftp.oregonstate.edu/suse/x86_64/9.0" to the kernel. the install ramdisk (/boot/root) is downloaded just fine. but then X starts and yast runs. yast then tries to get the list of software groups. it sends to the server: GET /x86_64/9.0/media.1/products HTTP/1.1 Host: 128.193.0.3 Pragma: no-cache Accept: [edited] notice the 'Host' field. it should read: Host: ftp.oregonstate.edu because yast sends the ip address and not the proper host name, the http request returns a 404 (not found) and the install fails. the install does work, however, if you use a server that does not host multiple virtual hosts (such as mirror.mcs.anl.gov or ftp-linux.cc.gatech.edu) i reported this via the suse 'feedback' form. is there a suse bugzilla or other tracking database to follow this issue? thanks

1 0

Virtual IP addresses and SUSE 9.1 AutoYaST
by David Carter 25 May '04

25 May '04

I used the following under 9.0 to set up a system with a real IP address (enabled by default) and a virtual IP address (disabled by default). The virtual address is shared between two systems for failover purposes: if the main system fails, we just do an "/sbin/ifup eth0:1" on the spare. <configure> <networking> . . . <interfaces config:type="list"> <interface> <device>eth0</device> <ipaddr>131.111.8.51</ipaddr> <netmask>255.255.255.0</netmask> <startmode>onboot</startmode> <bootproto>static</bootproto> </interface> <interface> <device>eth0:1</device> <ipaddr>131.111.8.59</ipaddr> <netmask>255.255.255.0</netmask> <startmode>manual</startmode> <bootproto>static</bootproto> </interface> </interfaces> . . . This doesn't work under 9.1 (autoyast appears to ignore the interface entirely). I understand that the ethX:Y notation is now deprecated, though it is referred to on page 283 of the printed manual. Is there a way of getting the same effect under 9.1? -- David Carter Email: David.Carter(a)ucs.cam.ac.uk University Computing Service, Phone: (01223) 334502 New Museums Site, Pembroke Street, Fax: (01223) 334679 Cambridge UK. CB2 3QH.

1 0

can't disable DHCP
by discip＠pjm.com 24 May '04

24 May '04

Hi, I am having a problem with suse 9.0. I have modified the boot.iso image, placing an info file in the root of the initrd. Linuxrc seems to pick up the parameters in the file, and I see them on the screen, and it says it is using them, but then it also runs dhcp on eth0. I can't seem to stop this behavior. The following is what I have in my info file: insmod: 3c59x netdevice: eth0 DHCP: 0 HostIP: 192.168.1.3 netmask: 255.255.255.0 gateway: 192.168.1.1 server: 192.168.1.5 autoyast: nfs://192.168.1.5/opt/Linux/SUSE-9/profiles/test.xml any help with this would be greatly appreciated. Thanks, Paul

1 0

Cannot mount Root Filesystem after new installation
by Juergen Pfeiffer 24 May '04

24 May '04

Hi I have a working Fileserver with Suse Linux 7.3 installed. There are 3 SCSI Hard Disks with Partitions on it (sda<i>, sdb<i> and sdc<i>). Now i want to upgrade to Suse Linux 9.0, but not as an Update (risky! If something fails, i have no working fileserver for hours or days!). Therefore i installed a 4. Harddisk, with a SCSI-Id greater than the three others (=> sdd). Then i did a new Installation of Suse Linux 9.0 to sdd1 with puting GRUB as bootmanager to sdd. All went fine until after installing from the first CD. The Reboot, necessary at this point did not work. Of course i told the BIOS to boot from the 4. SCSI Harddisk. The boot manager GRUB was found on the 4. SCSI Harddisk. A Linux system was found, but when the root Filesystem should be mounted, this was not possible! I got the Message "Cannot mount Root Filesystem". Luckily i could reboot my old 7.3 Linux from sda. But what did i do wrong? -- Juergen Pfeiffer SesKion Softwareentwicklung und System Konzeption GmbH Tel: +49-711-99058-14 Karlsruher Str. 11/1 Fax: +49-711-99058-27 D-70771 Leinfelden Echterdingen http://www.seskion.de

1 0

Lan Printer Problem
by Bob 24 May '04

24 May '04

I've installed 8.2 and can access the WWW and can ping the other PC's on my lan, but I cannot get it to identify the printers attached to usb ports on them. Some guidance will be much appreciated.<br> Bob

1 0

Modules update during auto installation.
by bigluo 24 May '04

24 May '04

How could I updated modules with additional .pcitable and .module-info files during auto installation. I would be advised to update modules during auto installation by putting modules into /..../root_for_autoyast/modules.However, seems I could not deal with modules, such as bcm5700, which need additional .pcitable and .module-info files as well as the module.As I know, this feature could be supported  by modifying modules.cgz during redhat auto installation. -- USTC Alumni Email System

1 0

Having dhclient installed and enabled instead of dhcpcd with AutoYaST.
by Hans Deragon 23 May '04

23 May '04

Greetings. We use a modified dhclient-script under RHL to get /etc/resolv.conf setup properly according to our network configuration. SuSE supports both dhcpcd and dhclient, but the default is dhcpcd. Anybody can inform me on how to setup dhclient as the default DHCP client using AutoYaST? Best regards, Hans Deragon -- Consultant en informatique/Software Consultant Deragon Informatique inc. Open source: http://www.deragon.biz http://facil.qc.ca (Promotion du libre) mailto://hans@deragon.biz http://autopoweroff.sourceforge.net (Logiciel)

2 1

Any documentation for modules's options available for yast2?
by Hans Deragon 21 May '04

21 May '04

Greetings. Newbie here with yast2. Typing "yast2 -l" shows a list of modules, and for each module, one can pass parameters. My problem: where can I find documentation about the options I can pass to a module? I have no clue what to pass to the modules. Best regards, Hans Deragon -- Consultant en informatique/Software Consultant Deragon Informatique inc. Open source: http://www.deragon.biz http://facil.qc.ca (Promotion du libre) mailto://hans@deragon.biz http://autopoweroff.sourceforge.net (Logiciel)

1 0

autoinstall problems (SuSE 9.1 Pro)
by Ivan Poddubny 20 May '04

20 May '04

Hello All, I'm trying to install SuSE 9.1 Pro onto 50+ systems and having some difficulties with the process. Any help would be appreciated. First of all, does anyone have an explanation why AutoYaST GUI and documentation (I'm using 9.0 docs as an example) creating different output then described in DTD files? Many DTDs are simply missing (like there are no definitions of samba-server), the other have different structure. Is it suppose to be so and we should correct DTD files ourselves or is this wrong? Anyway, I probably could live with this issue (at least I found some workarounds) but there are several other problems I can't resolve: (1) the documentation does not specify what users created (if any) during installation. I suspected that root is created but when I tried to login on test system after installing it using empty password for root, I got "Login incorrect". So I modified the control file and I tried to create user and assign a password for him. I got same results (Login incorrect) after installation. Is there any kind of special tricks here? BTW, I specified NIS but I suppose that users like root should be read from local files (i.e. /etc/nsswitch.conf has either "passwd: compat" or "passwd: files nis"). (2) my installation seems to be hanging at the very end. All packages installed, system rebooted and then installer is running SuSEconfig.* scripts. At the end of this process (or maybe right after it: step with copying preconfigured files onto system has been completed) I'm getting black screen (monitor stays on) and no disk activity. The only solution is reset button (which could lead to some missing configuration steps). I'm configuring X11 and suspecting that error comes from this part. Video adapter on test system supports the resolution I'm trying to use (1024x768 @ 16bpp). Is there anything I could do to debug the problem? (3) (this is sort of goes back to problem with DTDs). I was trying to use new syntax to describe LVM part when partitioning hard disk. The validation of control file goes OK. But when installing a test system, I got "lvremove cannot delete group sysdg" and after that installation fails. I tried to remove <use>all</use> tag from description of LVM partition, but it didn't help. The only solution was to go back to old syntax of LVM. However, there's a hidden (for me) problem: in the configuration I choose I have two volumes then belong to same disk group: root and home. While the size of root is always static (let's say 12GB), the size of home may vary due to different size of the harddrive. When using old syntax there's no way to specify "use maximum available space" for a volume, the size has to be defined. With new syntax it's possible to use key word "max". Is there anything could be done to either use new syntax of LVM's description or how could I specify "use all available space" with the old one? Thank you! --ivan

1 0

Large Amount Physical Memory and Automatic Swap Size
by Eric Schroeder 20 May '04

20 May '04

I have set the swap partition size to auto, which works great unless I try to install on a machine with a large amount of physical memory. The swap partition is never bigger than 1GB. Is this a limitation of autoyast, and is there any way to have the swap partition be 1.5 times the size of physical memory, regardless of the size? Thanks in advance, Eric Schroeder "Postmaster" made the following annotations. ------------------------------------------------------------------------------ This message may contain confidential information, and is intended only for the use of the individual(s) to whom it is addressed. ==============================================================================

1 0

Re: [suse-autoinstall] Broadcom NICs - tg3 WORKED
by Mouncef_Belcaid＠blm.gov 19 May '04

19 May '04

The automated installation worked using the tg3 module for the Broadcom NICs. Thank you all, especially Bjorn, you saved me a few hours of troubleshooting. Mouncef |---------+----------------------------> | | Bjorn Tore Sund | | | <bjornts(a)mi.uib.n| | | o> | | | | | | 05/19/2004 02:21 | | | AM | | | | |---------+----------------------------> >--------------------------------------------------------------------------------------------------------------| | | | To: suse-autoinstall(a)suse.com | | cc: | | Subject: Re: [suse-autoinstall] Broadcom NICs | >--------------------------------------------------------------------------------------------------------------| On Tue, 18 May 2004 Mouncef_Belcaid(a)blm.gov wrote: > I have used Autoyast successfully to install SuSE 8.2 Pro on multiple IBM > Blade servers. Each one of these servers comes with two Broadcom gigabit > cards, I used the bcm5700 module which worked fine during and after the > installation. We purchased more of these Blades, which come with the next > generation Broadcom cards, they work fine after a manual installation is > complete. > The problem is during the automated installation. After the installation > kernel loads, the card tries to get a DHCP IP from the NFS server (before > YAST starts), that's when it hangs. I checked the DHCP server logs and it > doesn't seem like the request is even reaching the server. > I tried loading 9.0 on one of the Blade servers, and it worked using > Autoyast. But I have to stick with SuSE 8.2 for now. Is there an updated > version of the SuSE 8.2 Pro loader files (initrd, linux, memtest...)? On 32bit systems I've found that the tg3 driver is a lot more stable than the bcm5700 driver. Have you tried that? Bjørn -- Bjørn Tore Sund Phone: (+47) 555-84894 Stupidity is like a System administrator Fax: (+47) 555-89672 fractal; universal and Math. Department Mobile: (+47) 918 68075 infinitely repetitive. University of Bergen VIP: 81724 Support: system(a)mi.uib.no Contact: teknisk(a)mi.uib.no Direct: bjornts(a)mi.uib.no -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

Broadcom NICs
by Mouncef_Belcaid＠blm.gov 19 May '04

19 May '04

Hi everyone, I have used Autoyast successfully to install SuSE 8.2 Pro on multiple IBM Blade servers. Each one of these servers comes with two Broadcom gigabit cards, I used the bcm5700 module which worked fine during and after the installation. We purchased more of these Blades, which come with the next generation Broadcom cards, they work fine after a manual installation is complete. The problem is during the automated installation. After the installation kernel loads, the card tries to get a DHCP IP from the NFS server (before YAST starts), that's when it hangs. I checked the DHCP server logs and it doesn't seem like the request is even reaching the server. I tried loading 9.0 on one of the Blade servers, and it worked using Autoyast. But I have to stick with SuSE 8.2 for now. Is there an updated version of the SuSE 8.2 Pro loader files (initrd, linux, memtest...)? Thanks for your time, Mouncef

3 2

Antwort: [suse-autoinstall] Broadcom NICs [FinanzIT: Viruscheck]
by Hartmut.Dunker＠finanzit.com 19 May '04

19 May '04

Hi Mouncef, we had the same Problem with SLES8 and HP Proliants. Old systems worked with an old boot kernel. After purchasing a new Proliant some weeks ago the system wasn't able to get a DHCP IP after PXE boot. After changing the boot kernel to the SLES8 SP3 kernel in the tftp directory pxe boot and autoinstallation works fine. Just try to use the boot kernel from the 9.0 CD for installation. Regards Hartmut Dunker Mouncef_Belcaid@b lm.gov An: suse-autoinstall(a)suse.com Kopie: 18.05.04 21:22 Thema: [suse-autoinstall] Broadcom NICs [FinanzIT: Viruscheck] Hi everyone, I have used Autoyast successfully to install SuSE 8.2 Pro on multiple IBM Blade servers. Each one of these servers comes with two Broadcom gigabit cards, I used the bcm5700 module which worked fine during and after the installation. We purchased more of these Blades, which come with the next generation Broadcom cards, they work fine after a manual installation is complete. The problem is during the automated installation. After the installation kernel loads, the card tries to get a DHCP IP from the NFS server (before YAST starts), that's when it hangs. I checked the DHCP server logs and it doesn't seem like the request is even reaching the server. I tried loading 9.0 on one of the Blade servers, and it worked using Autoyast. But I have to stick with SuSE 8.2 for now. Is there an updated version of the SuSE 8.2 Pro loader files (initrd, linux, memtest...)? Thanks for your time, Mouncef -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

Post script not created/executed.
by Hans Deragon 17 May '04

17 May '04

Greetings. Newbie with AutoYaST here trying to install SuSE 9.0. I have a config.xml file that works fine, except that the post script is not created (not found in var/adm/autoinstall/scripts). I cannot understand why it is not created and executed. The /var/log/y2log does show that the script's entry has been parsed. But I could not find any error messages regarding this. Following, the <scripts> section. <scripts> <post-scripts config:type="list" > <script> <filename>post.sh</filename> <interpreter>shell</interpreter> <source><![CDATA[echo "POST TEST passed."]]></source> </script> </post-scripts> </scripts> Pretty basic, huh? Can anybody point me to log files that would show me error messages related to my problem or provide me some clues? Best regards, Hans Deragon -- Consultant en informatique/Software Consultant Deragon Informatique inc. Open source: http://www.deragon.biz http://autopoweroff.sourceforge.net mailto://hans@deragon.biz (Automatically poweroff home servers)

3 3

Unable to uninstall YaST2 Installed Package (SuSE 9.0)
by Mike Blonder 14 May '04

14 May '04

Hi. I used YaST2 to install a Content Management System call midgard to a SuSE 9.0 system. Now I am denied by YaST2 when I attempt to uninstall it. It should be noted that I installed a second iteration of the package (non RPM) directly from the source group. Even worse, I cannot restart Apache. I am prompted to run SuSEconfig --module apache. When I run said command it also bombs with the following error message: No FQHOSTNAME SET! Quitting When I look at the config files httpd.SuSEconfig and suse_include.conf I notice advisories at the top of the screen to "Please don't edit these files" What do I do now? Thanks Mike

1 0

Re: installing SLES8 using autoyast and without any user interaction / problems with existing /dev/md?
by jochen.kirn＠daimlerchrysler.com 14 May '04

14 May '04

Steve, hmm, i already have these options included (see below), that's why I'm wondering <general> ... <mode> <confirm config:type="boolean">false</confirm> <forceboot config:type="boolean">false</forceboot> <interactive_boot config:type="boolean">false</interactive_boot> <reboot config:type="boolean">false</reboot> </mode> ... </general> in addition if I reinstall a previously installed system (which already has some raid devices, e.g. /dev/md0) autoyast complains that it can't create those raid devices because the autoyast installation process already detected the old raid device (of the old installation) and brings it up, thus it bugs me that it can't create a new one (with same name). A manual workaround for me is to switch to the second console (ALT+F2) and do the following 1) erase partition table manually (since putting it in a pre-installation-script doesn't helped either). $ dd if=/dev/zero bs=512 count=1 of=/dev/sda $ dd if=/dev/zero bs=512 count=1 of=/dev/sdb 2) reboot & restart autoyast installation Mit freundlichen Grüssen/best regards Jochen Kirn

2 1

Re: [suse-autoinstall] installing SLES8 using autoyast and withou tany user interaction
by Kohrs, Steven 14 May '04

14 May '04

On Fri, 2004-05-14 at 01:41, jochen.kirn(a)daimlerchrysler.com wrote: > > > > Hi everyone, > > I'm currently creating an autoyast.xml file for an unattended > installation > of SLES8 (using PXE). > so far everything went fine, except after the software rpms are > installed a > window pops up (textmode) > telling me that the boot loader was succesfully written to disc which > I > have to approve by clicking ok. > > I guess there is a way (xml-tag) to perform a complete and silent > installation without any user interaction Jochen, I believe this is what you're looking for: <general> ... <mode> <confirm config:type="boolean">false</confirm> <reboot config:type="boolean">false</reboot> </mode> ... </general> -- Sincerely, Steve Kohrs Distributed Systems 402.633.7058 This email and any files attached with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error delete this message and notify the sender at 402-341-0500. If you are not the named recipient you should not disseminate, distribute or copy this email or any attachment.

1 0

installing SLES8 using autoyast and without any user interaction
by jochen.kirn＠daimlerchrysler.com 14 May '04

14 May '04

Hi everyone, I'm currently creating an autoyast.xml file for an unattended installation of SLES8 (using PXE). so far everything went fine, except after the software rpms are installed a window pops up (textmode) telling me that the boot loader was succesfully written to disc which I have to approve by clicking ok. I guess there is a way (xml-tag) to perform a complete and silent installation without any user interaction thanks for any help Jochen Kirn

1 0

SuSE 9.1 autoinstall printer problem
by fschuett 11 May '04

11 May '04

Hallo, I use the autoinstall feature with 8.2 for our school network and it works great. I try to update to 9.1 and adapted the xml files to this. During the installation process there is an error similar to "cannot contact cups server" and the printer is not installed. The printer is attached to a printserver box D-Link DP-300 and with YaST the same printer configuration works fine. So I think the problem ist autoinstall related. Does anyone have a solution to this? I attach the installedSystem.xml file. Thank you. Bye -- Frank Schütte Gymnasium Himmelsthür fschuett(a)gymnasium-himmelsthuer.de

1 0

memo on windows
by A.L Paul 10 May '04

10 May '04

Hi all,I need to reassure someone just how unrealiable a windows platform can be especially if its used as a server of any sort and is a proxy to the internet.Also,and more importantly,I need facts and figures on the linux equivalent so that I can put things into proper perspective for them to wake up to reality. thanks Paul.

1 0

Minor problem w/ info file and custom kernel package
by Nicoya Helm 08 May '04

08 May '04

I'm just in the beginning stages of understanding SuSE's autoinstall process, which I'm implementing for an OpenMosix cluster. The scenario is that I have a server w/ the appropriate media directories, a standard SuSE boot CD, and a floppy w/ a custom autoinst.xml and info file at the root. And using SuSE 9.0 Yast 2. Problem 1: Info file not working. Because this is on a cluster, and for various reasons we don't want to run DHCP on the control node, I would like to use an info file to statically assign IP info and have the YaST look for the nfs install directory. Here's the contents of my info file: netdevice: eth0 ip: 192.168.1.200 netmask: 255.255.255.0 gateway: 192.168.1.200 install: nfs://192.168.1.1/usr/local/SuSE/current autoyast: floppy During the boot process the system searches for the info file, loads usb drivers, etc., searches for autoinstall file, then says "Sending DHCP request to eth0". I've watched, and the system reads the floppy drive both times. If I use this info file and autoinst.xml file on a network that has a DHCP server available, the network card grabs an IP, finds the nfs share, and proceeds to install according to my autoinst settings. But it fails if I use it on the cluster segment where no DHCP is available. I can do a manual installation, load the card drivers and manually enter all the IP and NFS info, and the autoinstallation proceed wonderfully. So my question is - what's wrong w/ my info file that the systems keep trying to use DHCP instead of the static info? Clearly they're getting at least some of the info from the file since the install finds the NFS shared okay. Problem 2: Not so much a problem as looking for additional tips/docu resources for how to make a custom kernel as part of the autoinstall process. I need to have the openmosix kernel installed, and am looking for the best way to accomplish this automatically. I tried to have it install as an addon package like any other RPM (like section 4.5.3 of the documentation says for general RPMS) - the install completes partially, then fails. However, I'm thinking I may be confused and should be adding it as a kernel package (is this any different than a standard RPM?) per section 4.5.4 of the documentation. If so, other than specifying the "kernel" property, is there anything different I will need to do to get the custom kernel to install automatically? Any suggestions very much appreciated! Nicoya Helm University of Kansas Medical Center nhelm2(a)kumc.edu

2 1

dhcpd.leases and SLES8 autoinstall
by Frank Samuel 07 May '04

07 May '04

Hi, I have a question regarding to autoinstall for SLES8. During the autoinstall of a node. The following two new leases are noticed in the dhcp.leases file. I feel surprised when I read the latter lease. Could someone explain what is the meaning of uid "\001\000PE\000\244\022"; Thanks a lot. lease 192.168.0.19 { starts 5 2004/05/07 10:35:48; ends 6 2004/05/08 10:35:48; binding state active; next binding state free; hardware ethernet 00:50:45:00:a4:12; } lease 192.168.0.19 { starts 5 2004/05/07 10:36:11; ends 6 2004/05/08 10:36:11; binding state active; next binding state free; hardware ethernet 00:50:45:00:a4:12; uid "\001\000PE\000\244\022"; } __________________________________ Do you Yahoo!? Win a $20,000 Career Makeover at Yahoo! HotJobs http://hotjobs.sweepstakes.yahoo.com/careermakeover

1 0

Re: [suse-autoinstall] Upgrade 9.0 -> 9.1 went totally wrong
by Wolfgang.Bauer＠schoellerbank.at 07 May '04

07 May '04

Hi Roy, no, my specs are: Athlon XP 1600, 768 MB RAM, 80 GB IDE (ATA-100), Geforce 440 MX, SB live, 2x ethernet, 1 firewire-card The funny thing was, that I was always told that the upgrade-program could not mount my root-partition but when I chose "reset options" (by not changing any options before) it recognised the root-partition... I guess, there could be a bug somewhere in the upgrade-program... I would love to track this problem down, but I fear that all logs were deleted. Yours, Gery ------------------------------------------------------------------- Dipl.-Ing. Wolfgang Gernot Bauer, Leiter Internet Schoellerbank AG, Sterneckstrasse 5, 5024 Salzburg, Austria/Europe Tel.: ++43-662-8684-364, Fax.: ++43-662-8684-44364 Email: mailto:wolfgang.bauer@schoellerbank.at, WWW: http://www.schoellerbank.at Diese Nachricht dient ausschließlich zu Informationszwecken und ist nur für den Gebrauch des Empfängers bestimmt. This message is only for informational purposes and is intended solely for the use of the addressee. Roy Butler <roy.butler@jpl. nasa.gov> An suse-autoinstall(a)suse.com 06.05.2004 22:27 Kopie Thema Re: [suse-autoinstall] Upgrade 9.0 -> 9.1 went totally wrong Gery, Is your root-partition on an SATA drive? If so, maybe the upgrade feature isn't accomodating the device file change between the 2.4 and 2.6 kernels. Roy Wolfgang.Bauer(a)schoellerbank.at wrote: > > > > > Hello everybody, > > I tried to install SuSE 9.1 yesterday by trying to Upgrade my > 9.0-installation. The nightmare was as follows: > > The first problem I encountered was that yast was not able to mount my > root-partition (reiserfs) although my 9.0-installation worked properly... > > After a few tries, I used the "Auto-Repair Installed System"-feature (if > you still use 9.0 - DONT USE THIS FEATURE!!!). First it worked very nicely > until it got to the point where it checked the installation. The > repair-function noticed that the 9.1-installation was faulty (right, as it > was a 9.0-installation) and upgraded some packages. After a reboot the > system did not come up (could not find kernel). Well, yast-installation > again - could not mount root-filesystem. Damn. > > I tried many things but when I used "Reset Options" from the menu on the > bottom YAST COULD MOUNT MY PARTITION - there were no other settings but (by > magic) now it worked (could this be a bug?!). But as the repair-system > changed my old 9.0-installation "There was an error upgrading your system". > > After I copied all my /home-data to my windowspartition via text-console > and freshly installed 9.1, I had a running linux-system again. But I really > have to say: poor upgrade-system. It used to work better with older > Suse-distributions... > > Btw. I'm not a Linux novice (I use Linux since 1994) but it seems that you > must not rely on "automatic upgrade functionalities"... > > Sad, sad. > > Gery > ------------------------------------------------------------------- > Dipl.-Ing. Wolfgang Gernot Bauer, Leiter Internet > Schoellerbank AG, Sterneckstrasse 5, 5024 Salzburg, Austria/Europe > Tel.: ++43-662-8684-364, Fax.: ++43-662-8684-44364 > Email: mailto:wolfgang.bauer@schoellerbank.at, WWW: > http://www.schoellerbank.at > > Diese Nachricht dient ausschließlich zu Informationszwecken und ist nur für > den Gebrauch des Empfängers bestimmt. > This message is only for informational purposes and is intended solely for > the use of the addressee. > > > -- > 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

SuSE SLES 8 and United Linux 1.0 autoinstall
by Frank Samuel 07 May '04

07 May '04

I have a question regarding to SLES8 autoinstall. I've done some experiments for SLES8 autoinstall without SP3. One experiment I did is copying the CDs to a dir of /usr/local/SLES8 in the order of UnitedLinux 3,2,1 and SLES8 and then removed some packages not used. After installation, Welcome to SuSE SLES8 ... will be in the file of /etc/issue. I didn't notice any problem happen during the installation. So is it a valid method? Another issue is how can I possibly install UnitedLinuxinstead of SLES8 using autoinstall? Copying three CDs of United Linux seems won't work. Thanks. __________________________________ Do you Yahoo!? Win a $20,000 Career Makeover at Yahoo! HotJobs http://hotjobs.sweepstakes.yahoo.com/careermakeover

2 2

Upgrade 9.0 -> 9.1 went totally wrong
by Wolfgang.Bauer＠schoellerbank.at 06 May '04

06 May '04

Hello everybody, I tried to install SuSE 9.1 yesterday by trying to Upgrade my 9.0-installation. The nightmare was as follows: The first problem I encountered was that yast was not able to mount my root-partition (reiserfs) although my 9.0-installation worked properly... After a few tries, I used the "Auto-Repair Installed System"-feature (if you still use 9.0 - DONT USE THIS FEATURE!!!). First it worked very nicely until it got to the point where it checked the installation. The repair-function noticed that the 9.1-installation was faulty (right, as it was a 9.0-installation) and upgraded some packages. After a reboot the system did not come up (could not find kernel). Well, yast-installation again - could not mount root-filesystem. Damn. I tried many things but when I used "Reset Options" from the menu on the bottom YAST COULD MOUNT MY PARTITION - there were no other settings but (by magic) now it worked (could this be a bug?!). But as the repair-system changed my old 9.0-installation "There was an error upgrading your system". After I copied all my /home-data to my windowspartition via text-console and freshly installed 9.1, I had a running linux-system again. But I really have to say: poor upgrade-system. It used to work better with older Suse-distributions... Btw. I'm not a Linux novice (I use Linux since 1994) but it seems that you must not rely on "automatic upgrade functionalities"... Sad, sad. Gery ------------------------------------------------------------------- Dipl.-Ing. Wolfgang Gernot Bauer, Leiter Internet Schoellerbank AG, Sterneckstrasse 5, 5024 Salzburg, Austria/Europe Tel.: ++43-662-8684-364, Fax.: ++43-662-8684-44364 Email: mailto:wolfgang.bauer@schoellerbank.at, WWW: http://www.schoellerbank.at Diese Nachricht dient ausschließlich zu Informationszwecken und ist nur für den Gebrauch des Empfängers bestimmt. This message is only for informational purposes and is intended solely for the use of the addressee.

2 1

Re: [suse-autoinstall] Upgrade 9.0 -> 9.1 went totally wrong
by Ryan Partridge 06 May '04

06 May '04

Just wanted to show the other side of the coin. Two days ago I upgraded my development workstation from 9.0 to 9.1 and the process couldn't have been smoother. I'm sorry that you had trouble, Gery. I would imagine that the majority of users will not experience the same problems you did. Just the same, if anybody else has bad experiences, please publish them so the underlying issues can be addressed. Cheers! >>> <Wolfgang.Bauer(a)schoellerbank.at> 5/6/2004 1:26:18 AM >>> Hello everybody, I tried to install SuSE 9.1 yesterday by trying to Upgrade my 9.0-installation. The nightmare was as follows: The first problem I encountered was that yast was not able to mount my root-partition (reiserfs) although my 9.0-installation worked properly... After a few tries, I used the "Auto-Repair Installed System"-feature (if you still use 9.0 - DONT USE THIS FEATURE!!!). First it worked very nicely until it got to the point where it checked the installation. The repair-function noticed that the 9.1-installation was faulty (right, as it was a 9.0-installation) and upgraded some packages. After a reboot the system did not come up (could not find kernel). Well, yast-installation again - could not mount root-filesystem. Damn. I tried many things but when I used "Reset Options" from the menu on the bottom YAST COULD MOUNT MY PARTITION - there were no other settings but (by magic) now it worked (could this be a bug?!). But as the repair-system changed my old 9.0-installation "There was an error upgrading your system". After I copied all my /home-data to my windowspartition via text-console and freshly installed 9.1, I had a running linux-system again. But I really have to say: poor upgrade-system. It used to work better with older Suse-distributions... Btw. I'm not a Linux novice (I use Linux since 1994) but it seems that you must not rely on "automatic upgrade functionalities"... Sad, sad. Gery ------------------------------------------------------------------- Dipl.-Ing. Wolfgang Gernot Bauer, Leiter Internet Schoellerbank AG, Sterneckstrasse 5, 5024 Salzburg, Austria/Europe Tel.: ++43-662-8684-364, Fax.: ++43-662-8684-44364 Email: mailto:wolfgang.bauer@schoellerbank.at, WWW: http://www.schoellerbank.at Diese Nachricht dient ausschließlich zu Informationszwecken und ist nur für den Gebrauch des Empfängers bestimmt. This message is only for informational purposes and is intended solely for the use of the addressee. -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

differences / description / experiences autoyast with suse9.1 ?
by Hella Breitkopf 06 May '04

06 May '04

Hi List, Before I dip my toes into automatic installation with suse9.1, is there a description on the way? Are there many differences from 9.0 to 9.1? Has anybody tried it, yet? With what results? (Btw: It would be nice to see a page "things what changed from version x to version x+1" in the description - and if the description is updated, date + version number would come in handy.) thanks for any information, Hella -- Top 100 things you don't want the sysadmin to say: 60. We're standardizing on AIX.

4 6

Secure Network-Based Install for SuSE 9.0...
by Roy Butler 06 May '04

06 May '04

Hi, I'd like to create a secure network-based install for SuSE 9.0 with AutoYaST using iptables. Currently, I have the following working quite well on a private network: - Server at 192.168.1.1 with SuSE 9.0 DVD contents NFS-exported and AutoYast XML control file served via TFTP. - Client connected through switch and booted from SuSE 9.0 CD1 with the following arguments: hostip=192.168.1.2 netmask=255.255.255.0 gateway=192.168.1.1 install=nfs://192.168.1.1/export/i386/SuSE/9.0/DVD autoyast=tftp://192.168.1.1/test-1.xml My goal is to move the server to a semi-public network and install clients in a manner similar to the above, but prohibit any network traffic to the client from anywhere but the server during the process. I've read (most of) Anas' fine AutoYaST documentation, the Linux Bootdisk HOWTO, and the kernel's initrd.txt file, as well as some of the messages on this list. I've missed it if anyone has described how to do this before, but here is my plan of attack: - Copy SuSE 9.0 CD1 to hard drive. - Gunzip and mount the CD's /boot/loader/initrd. - Copy iptables.o to initrd's /modules directory and add an entry to the [autoload] section of initrd's /modules/module.config file. - Unmount and gzip the initrd image. - Create a template entry for the long-winded boot arguments above in the CD's /boot/loader/isolinux.cfg. - Burn a custom SuSE 9.0 CD1 from the hard drive. - Create a pre-script in my test-1.xml file which runs "iptables <some rule>". Has anyone done something similar who can offer advice/comments? I like the extended boot arguments, because I can't rely on PXE or DHCP everywhere. I'm not stuck on iptables, if there's a similar way to do it otherwise. I have the sense that I may be working with the wrong ramdisk (/boot/loader/initrd) since I found no /lib directory and an incredibly sparse /bin directory there... Much appreciated, Roy

1 0

[suse linux 9.1 prof x86] autoinstall over network failed: yast: not enough memory !!!
by Maurer, Hermann 05 May '04

05 May '04

Hello folks, I have a trouble to start the autoinstall process of SuSE Linux 9.1 over the LAN. In my grub.conf on the boot floppy I have the following entries: title SuSE Linux 9.1 Installation kernel (nd)/boot/suse-linux-9.1 insmod=e100 install=ftp://10.73.59.88/pub/suse/i386/9.1 initrd (nd)/boot/suse-linux-9.1.initrd title SuSE Linux 9.0 Installation kernel (nd)/boot/suse-linux-9.0 insmod=e100 install=ftp://10.73.59.88/pub/suse/i386/9.0 initrd (nd)/boot/suse-linux-9.0.initrd The installation comes up to the point, where the installation process loads some data (53308 kb) onto the ram disk. It draws dots and switches then in the ncurses mode with the following error: "Your computer doesn't have enough memory to run YaST. To continue, activate some swap space" Some last lines on the tty3: ... going for automatic install Loading image "/pub/suse/i386/9.1/boot/root"... cramfs "root 53308" image size: 53308 kB mount: /dev/ram2: we need a loop device mount: using /dev/loop0 Loading image "/pub/suse/i386/9.1/driverupdate"... ramdisk /dev/ram3 freed Ther is not the file driverupdate in the root dir and in the subdirecories of the distribution ! The installation over pxe + grub over the LAN failes with the same error. Here is a section of my grub.conf for pxe-boots: # SuSE Linux 9.1 Installation title SuSE Linux 9.1 Installation root (nd) kernel /boot/suse-linux-9.1 ramdisk_size=65536 insmod=e100 install=ftp://10.73.59.88/pub/suse/i386/9.1 initrd /boot/suse-linux-9.1.initrd # SuSE Linux 9.0 Installation title SuSE Linux 9.0 Installation root (nd) kernel /boot/suse-linux-9.0 ramdisk_size=65536 insmod=e100 install=ftp://10.73.59.88/pub/suse/i386/9.0 initrd /boot/suse-linux-9.0.initrd The installation of SuSE 9.0 works fine, it doesn't matter, whether over pxe + grub or with grub boot floppy. My PC has the following hardware configuration: - Intel P-III 550 MHz - 128 MB RAM - 9 GB SCSI HDD - Matrox G400 AGP card - Intel EtherExpress 10/100 NIC Any help will be appreciated ! Thank you very much ! Regards, Hermann Maurer

3 2

Full automatic installation of SLES8 with update
by Nicolas Marciniak 05 May '04

05 May '04

Here some tips to help you to install a sles8 with update. I think it will be usefull for many people. ========================================================= == 1 == Setting up install directory ========================================================= Use the script in section 6.1.3 of the autoyast documentation for sles8 You have now a repository with SLES CD and UL CD 1,2,3 I have setup my repository in /suse/install I have used UL/CD{1,2,3} and SLES/ instead of unitedlinux-i386/CD{1,2,3} and sles8-i386/CD1 directory ========================================================= == 2 == Download update ========================================================= Go to http://sdb.suse.de/download/i386/update/SuSE-SLES/8/rpm/ Download all rpms like this : foo-x.xx-xx.rpm Do NOT download foo.patch.rpm and foo.rpm files Save files in directory like this /suse/update/update/i586 /suse/update/update/i686 /suse/update/update/noarch Download SP3 CD1 iso to get driverupdate file You must have it later. ========================================================= == 3 == Creating package description for update ========================================================= Install autoyast2 rpm ### script ### cd /suse/update/update/ /usr/local/YaST2/bin/create_package_descr -d /suse/update/update -l english -l german -l french cd /suse/update mkdir media.1 touch content touch media.1/media ############### ### file : content ### PRODUCT SuSE SLES VERSION update DISTPRODUCT SuSE-Linux-SLES-i386 DISTVERSION 8.1-0 BASEPRODUCT UnitedLinux BASEVERSION 1.0 YOUTYPE business YOUPATH i386/update/SuSE-SLES/8 YOUURL http://www.suse.de/cgi-bin/suseservers.cgi VENDOR SuSE Linux AG ARCH.i686 i686 i586 i486 i386 noarch ARCH.i586 i586 i486 i386 noarch ARCH.i486 i486 i386 noarch ARCH.i386 i386 noarch DEFAULTBASE i386 REQUIRES distribution-release LINGUAS de en LABEL SuSE SLES Update LABEL.de SuSE SLES Update DESCRDIR update/setup/descr DATADIR update LANGUAGE en_US TIMEZONE America/Los_Angeles ############### ### file : media.1/media ### SuSE Linux AG 20021022191434 1 ############### You must have this in your /suse/update /suse/update |-- content |-- media.1 | `-- media `-- update |-- i586 -- *.rpm |-- i686 -- *.rpm |-- noarch -- *.rpm `-- setup `-- descr |-- packages |-- packages.DU |-- packages.en `-- packages.fr ========================================================= == 5 == setting up the final repository with update rpms ========================================================= #### script ################ mv /suse/update /suse/install/ cd /suse/install mkdir -p yast/update/update/setup/descr mkdir -p yast/update/media.1 cp -a update/content yast/update/ cp -a update/media.1/media yast/update/media.1/ cp -a update/update/setup/descr/*.* yast/update/update/setup/descr/ ############################ Your /suse/install/yast must look like this : |-- TRANS.TBL |-- order |-- sles8 | |-- content | |-- media.1 | | |-- TRANS.TBL | | |-- info.txt | | |-- media | | `-- products | `-- suse | `-- setup | `-- descr | |-- Minimal+X11.sel | |-- Minimal.sel | |-- X11.sel | |-- packages | |-- packages.DU | |-- .... |-- ul | |-- TRANS.TBL | |-- UnitedLinux | | |-- TRANS.TBL | | `-- setup | | |-- TRANS.TBL | | `-- descr | | |-- Minimal+X11.sel | | |-- Minimal.sel | | |-- X11.sel | | |-- packages | | |-- packages.DU | | |-- packages.cs | | |-- ..... | |-- content | `-- media.1 | |-- TRANS.TBL | |-- info.txt | |-- media | `-- products `-- update |-- content |-- media.1 | `-- media `-- update `-- setup `-- descr |-- packages |-- packages.DU |-- packages.en `-- packages.fr ---- /!\ Don't forget to put the driverupdate file of SP3 CD1 in /suse/install ========================================================= == 6 == Important files ========================================================= /suse/install/yast/order : -------------------------- /yast/update /update /yast/ul /UL/CD1 /yast/sles8 /SLES ========================================================= == 7 == Make a custom boot cd ========================================================= Mount and copy your SLES8 CD1 to /iso/cdboot/ You can delete all rpm in /iso/cdboot/ to reduce the size of the final cd Mount the SP3 CD to /mnt/sp3 ### script ### cp /mnt/sp3/boot/loader/linux /iso/cdboot/boot/loader/ cp /mnt/sp3/boot/loader/initrd /iso/cdboot/boot/loader/ cp /mnt/sp3/boot/loader/initrd /iso/ touch /iso/info ############### the file info is used to setup network and connect to the nfs repository to install the system ### file : /iso/info ### install: nfs://128.1.217.166/suse/install/ netdevice: eth0 hostip: 128.1.33.60 gateway: 128.1.6.23 nameserver: 128.1.6.228 netmask: 255.255.0.0 textmode: 1 forceinsmod: 1 nopcmcia: 1 ############### I have tweak the isolinux.cfg to get different autoyast control file ### file /iso/cdboot/boot/loader/isolinux.cfg #### default harddisk # hard disk label harddisk kernel linux append SLX=0x202 # ide label ide kernel linux append initrd=initrd ramdisk_size=65536 autoyast=nfs://128.1.217.166/suse/autoyast/ide.xml # scsi label scsi kernel linux append initrd=initrd ramdisk_size=65536 autoyast=nfs://128.1.217.166/suse/autoyast/scsi.xml # custom1 label custom1 kernel linux append initrd=initrd ramdisk_size=65536 autoyast=nfs://128.1.217.166/suse/autoyast/custom1.xml # custom2 label custom2 kernel linux append initrd=initrd ramdisk_size=65536 autoyast=nfs://128.1.217.166/suse/autoyast/custom2.xml # custom3 label custom3 kernel linux append initrd=initrd ramdisk_size=65536 autoyast=nfs://128.1.217.166/suse/autoyast/custom3.xml failsafe label failsafe kernel linux append initrd=initrd ramdisk_size=65536 ide=nodma apm=off acpi=off # apic #label apic # kernel linux # append initrd=initrd ramdisk_size=65536 apic # manual #label manual # kernel linux # append initrd=initrd ramdisk_size=65536 manual=1 memory test label memtest kernel memtest implicit 0 gfxboot bootlogo display message prompt 1 timeout 100 readinfo 2 framebuffer 1 ####################### Here my script to create a cdboot with sp3 kernel and info file ##### script makeiso.sh ####### #!/bin/bash INITRD=/iso/initrd INITRD_GUNZIP=/iso/initrd_gunzip INITRD_MOUNT=/iso/temp/initrd INFO=$1 CDBOOT=/iso/cdboot ISO=$2 INITRD_FINAL=$CDBOOT/boot/loader/initrd if [ "$#" -lt 2 ] then echo "Usage: makeiso file_info image.iso" exit 1 fi mkdir -p $INITRD_MOUNT gunzip -q < $INITRD > $INITRD_GUNZIP mount -o loop -t minix $INITRD_GUNZIP $INITRD_MOUNT cp $INFO $INITRD_MOUNT umount $INITRD_MOUNT gzip < $INITRD_GUNZIP > $INITRD_FINAL mkisofs -R -l -J -o $ISO -b boot/loader/isolinux.bin -c boot.catalog \ -no-emul-boot -boot-load-size 4 -boot-info-table \ $CDBOOT rm -f $INITRD_GUNZIP ############################### in /iso simply use : ./makeiso.sh info slescustom.iso :) ========================================================= == 7 == Creating a good control file with nfs postinstall script and LVM stuff :) ========================================================= Here my ide.xml control file --------------------- <?xml version="1.0"?> <!DOCTYPE profile SYSTEM "/usr/share/YaST2/include/autoinstall/profile.dtd"> <profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <configure> <scripts> <chroot-scripts config:type="list"/> <post-scripts config:type="list" > <script> <filename>postinstall.sh</filename> <interpreter>shell</interpreter> <source> <![CDATA[ #!/bin/sh UPDATE_SRV=128.1.217.166 UPDATE_DIR=/suse/postinstall eject echo "Mounting update server" mkdir -p /tmp/postinstall mount -t nfs $UPDATE_SRV:$UPDATE_DIR /tmp/postinstall sh /tmp/postinstall/update_rpm.sh ]]> </source> </script> </post-scripts> <pre-scripts config:type="list"/> </scripts> </configure> <install> <bootloader> <location>mbr</location> </bootloader> <report> <messages> <show>false</show> <timeout>5</timeout> <log>true</log> </messages> <errors> <show>true</show> <timeout>5</timeout> <log>true</log> </errors> <warnings> <show>true</show> <timeout>5</timeout> <log>true</log> </warnings> </report> <general> <clock> <hwclock>GMT</hwclock> <timezone>Europe/Paris</timezone> </clock> <keyboard> <keymap>french</keymap> </keyboard> <language>fr_FR</language> <mouse> <id>20_imps2</id> </mouse> </general> <lvm config:type="list"> <lvm_group> <logical_volumes config:type="list"> <lv> <lv_fs config:type="symbol">reiser</lv_fs> <lv_mount>/</lv_mount> <lv_name>lvroot</lv_name> <lv_size>2147483648</lv_size> </lv> <lv> <lv_fs config:type="symbol">reiser</lv_fs> <lv_mount>/tmp</lv_mount> <lv_name>lvtmp</lv_name> <lv_size>536870912</lv_size> </lv> <lv> <lv_fs config:type="symbol">reiser</lv_fs> <lv_mount>/var</lv_mount> <lv_name>lvvar</lv_name> <lv_size>536870912</lv_size> </lv> </logical_volumes> <lvm_name>vgroot</lvm_name> <pesize>8M</pesize> </lvm_group> </lvm> <partitioning config:type="list"> <drive> <device>/dev/hda</device> <partitions config:type="list"> <partition> <filesystem config:type="symbol">ext2</filesystem> <mount>/boot</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">1</partition_nr> <size>49348609</size> </partition> <partition> <mount>swap</mount> <partition_id config:type="integer">130</partition_id> <partition_nr config:type="integer">2</partition_nr> <size>1069219841</size> </partition> <partition> <lvm_group>vgroot</lvm_group> <partition_id config:type="integer">142</partition_id> <partition_nr config:type="integer">3</partition_nr> <size>auto</size> </partition> </partitions> <use>all</use> </drive> </partitioning> <software> <base>Minimal+X11</base> </software> </install> </profile> -------------- Note : report directive doesn't work, whatever the timeout value , it's always 10s and is always show A Postinstall script on the nfs repository is executed. ========================================================= == 8 == postinstall script and nfs setting ========================================================= My setup is like this /suse/install : repository used to install /suse/autoyast : store .xml control file /suse/update : store homemade and update rpms which are not in /suse/install /suse/postinstall : store postinstall scripts ### file : /suse/postinstall/update_rpm.sh #### #!/bin/sh SERV_UPDATE=128.1.217.166 PATH_UPDATE=/suse/update PATH_SLES=/suse/install mkdir -p /tmp/nfs mount -t nfs $SERV_UPDATE:$PATH_UPDATE /tmp/nfs ### useless since update rpms are in install repository #rpm -Fvh /tmp/nfs/update/i686/*.rpm #rpm -Fvh /tmp/nfs/update/i586/*.rpm #rpm -Fvh /tmp/nfs/update/noarch/*.rpm ### ###### Install homemade rpms (cfengine etc...) ######### rpm -Uvh --nodeps /tmp/nfs/update/add/*.rpm umount /tmp/nfs ##### install sles8 banner ###### mount -t nfs $SERV_UPDATE:$PATH_SLES /tmp/nfs rpm -e --nodeps unitedlinux-release rpm -Uvh /tmp/nfs/SLES/suse/i586/sles-release*.rpm rpm -e --nodeps yast2-theme-UnitedLinux rpm -Uvh /tmp/nfs/SLES/suse/noarch/yast2-theme-SuSE*.rpm umount /tmp/nfs ######## SOURCE UPDATE ########### PATH_UPDATE=/suse/install/update PATH_SLES=/suse/install/SLES PATH_UL=/suse/install/UL/CD1 echo "Deleting old sources" rm -rf /var/adm/YaST/InstSrcManager/* echo "Adding new sources" installation_sources -ea nfs://$SERV_UPDATE:$PATH_UPDATE installation_sources -ea nfs://$SERV_UPDATE:$PATH_SLES installation_sources -ea nfs://$SERV_UPDATE:$PATH_UL #################################### --------------------------------------------------------- ### file : /etc/exports #### /suse/autoyast *(sync,ro) /suse/update *(sync,ro) /suse/install *(sync,ro) /suse/postinstall *(sync,ro) ################# ========================================================= == 9 == Conclusion ========================================================= A sles8 installation is made within 5-10 minutes depending the install machine. No human intervention is needed after the boot (all you must do is to choose the right .xml at the lilo cd screen) After installation the machine reboots on harddrive (in fact it reboot on cd but the cd boots by default on harddrive :p) Update is done at install time : you can say goodbye to smp/bcm5700 driver bug in kernel 2.4.19 Postinstall script on nfs provide easy way to install homemade rpms I hope this set of tips will be on Anas Nashif autoyast Homepage :) Regards, Nicolas Marciniak

1 0

Full automatic installation of SLES8 with update
by Nicolas Marciniak 05 May '04

05 May '04

Here some tips to help you to install a sles8 with update. I think it will be usefull for many people. ========================================================= == 1 == Setting up install directory ========================================================= Use the script in section 6.1.3 of the autoyast documentation for sles8 You have now a repository with SLES CD and UL CD 1,2,3 I have setup my repository in /suse/install I have used UL/CD{1,2,3} and SLES/ instead of unitedlinux-i386/CD{1,2,3} and sles8-i386/CD1 directory ========================================================= == 2 == Download update ========================================================= Go to http://sdb.suse.de/download/i386/update/SuSE-SLES/8/rpm/ Download all rpms like this : foo-x.xx-xx.rpm Do NOT download foo.patch.rpm and foo.rpm files Save files in directory like this /suse/update/update/i586 /suse/update/update/i686 /suse/update/update/noarch Download SP3 CD1 iso to get driverupdate file You must have it later. ========================================================= == 3 == Creating package description for update ========================================================= Install autoyast2 rpm ### script ### cd /suse/update/update/ /usr/local/YaST2/bin/create_package_descr -d /suse/update/update -l english -l german -l french cd /suse/update mkdir media.1 touch content touch media.1/media ############### ### file : content ### PRODUCT SuSE SLES VERSION update DISTPRODUCT SuSE-Linux-SLES-i386 DISTVERSION 8.1-0 BASEPRODUCT UnitedLinux BASEVERSION 1.0 YOUTYPE business YOUPATH i386/update/SuSE-SLES/8 YOUURL http://www.suse.de/cgi-bin/suseservers.cgi VENDOR SuSE Linux AG ARCH.i686 i686 i586 i486 i386 noarch ARCH.i586 i586 i486 i386 noarch ARCH.i486 i486 i386 noarch ARCH.i386 i386 noarch DEFAULTBASE i386 REQUIRES distribution-release LINGUAS de en LABEL SuSE SLES Update LABEL.de SuSE SLES Update DESCRDIR update/setup/descr DATADIR update LANGUAGE en_US TIMEZONE America/Los_Angeles ############### ### file : media.1/media ### SuSE Linux AG 20021022191434 1 ############### You must have this in your /suse/update /suse/update |-- content |-- media.1 | `-- media `-- update |-- i586 -- *.rpm |-- i686 -- *.rpm |-- noarch -- *.rpm `-- setup `-- descr |-- packages |-- packages.DU |-- packages.en `-- packages.fr ========================================================= == 5 == setting up the final repository with update rpms ========================================================= #### script ################ mv /suse/update /suse/install/ cd /suse/install mkdir -p yast/update/update/setup/descr mkdir -p yast/update/media.1 cp -a update/content yast/update/ cp -a update/media.1/media yast/update/media.1/ cp -a update/update/setup/descr/*.* yast/update/update/setup/descr/ ############################ Your /suse/install/yast must look like this : |-- TRANS.TBL |-- order |-- sles8 | |-- content | |-- media.1 | | |-- TRANS.TBL | | |-- info.txt | | |-- media | | `-- products | `-- suse | `-- setup | `-- descr | |-- Minimal+X11.sel | |-- Minimal.sel | |-- X11.sel | |-- packages | |-- packages.DU | |-- .... |-- ul | |-- TRANS.TBL | |-- UnitedLinux | | |-- TRANS.TBL | | `-- setup | | |-- TRANS.TBL | | `-- descr | | |-- Minimal+X11.sel | | |-- Minimal.sel | | |-- X11.sel | | |-- packages | | |-- packages.DU | | |-- packages.cs | | |-- ..... | |-- content | `-- media.1 | |-- TRANS.TBL | |-- info.txt | |-- media | `-- products `-- update |-- content |-- media.1 | `-- media `-- update `-- setup `-- descr |-- packages |-- packages.DU |-- packages.en `-- packages.fr ---- /!\ Don't forget to put the driverupdate file of SP3 CD1 in /suse/install ========================================================= == 6 == Important files ========================================================= /suse/install/yast/order : -------------------------- /yast/update /update /yast/ul /UL/CD1 /yast/sles8 /SLES ========================================================= == 7 == Make a custom boot cd ========================================================= Mount and copy your SLES8 CD1 to /iso/cdboot/ You can delete all rpm in /iso/cdboot/ to reduce the size of the final cd Mount the SP3 CD to /mnt/sp3 ### script ### cp /mnt/sp3/boot/loader/linux /iso/cdboot/boot/loader/ cp /mnt/sp3/boot/loader/initrd /iso/cdboot/boot/loader/ cp /mnt/sp3/boot/loader/initrd /iso/ touch /iso/info ############### the file info is used to setup network and connect to the nfs repository to install the system ### file : /iso/info ### install: nfs://128.1.217.166/suse/install/ netdevice: eth0 hostip: 128.1.33.60 gateway: 128.1.6.23 nameserver: 128.1.6.228 netmask: 255.255.0.0 textmode: 1 forceinsmod: 1 nopcmcia: 1 ############### I have tweak the isolinux.cfg to get different autoyast control file ### file /iso/cdboot/boot/loader/isolinux.cfg #### default harddisk # hard disk label harddisk kernel linux append SLX=0x202 # ide label ide kernel linux append initrd=initrd ramdisk_size=65536 autoyast=nfs://128.1.217.166/suse/autoyast/ide.xml # scsi label scsi kernel linux append initrd=initrd ramdisk_size=65536 autoyast=nfs://128.1.217.166/suse/autoyast/scsi.xml # custom1 label custom1 kernel linux append initrd=initrd ramdisk_size=65536 autoyast=nfs://128.1.217.166/suse/autoyast/custom1.xml # custom2 label custom2 kernel linux append initrd=initrd ramdisk_size=65536 autoyast=nfs://128.1.217.166/suse/autoyast/custom2.xml # custom3 label custom3 kernel linux append initrd=initrd ramdisk_size=65536 autoyast=nfs://128.1.217.166/suse/autoyast/custom3.xml failsafe label failsafe kernel linux append initrd=initrd ramdisk_size=65536 ide=nodma apm=off acpi=off # apic #label apic # kernel linux # append initrd=initrd ramdisk_size=65536 apic # manual #label manual # kernel linux # append initrd=initrd ramdisk_size=65536 manual=1 memory test label memtest kernel memtest implicit 0 gfxboot bootlogo display message prompt 1 timeout 100 readinfo 2 framebuffer 1 ####################### Here my script to create a cdboot with sp3 kernel and info file ##### script makeiso.sh ####### #!/bin/bash INITRD=/iso/initrd INITRD_GUNZIP=/iso/initrd_gunzip INITRD_MOUNT=/iso/temp/initrd INFO=$1 CDBOOT=/iso/cdboot ISO=$2 INITRD_FINAL=$CDBOOT/boot/loader/initrd if [ "$#" -lt 2 ] then echo "Usage: makeiso file_info image.iso" exit 1 fi mkdir -p $INITRD_MOUNT gunzip -q < $INITRD > $INITRD_GUNZIP mount -o loop -t minix $INITRD_GUNZIP $INITRD_MOUNT cp $INFO $INITRD_MOUNT umount $INITRD_MOUNT gzip < $INITRD_GUNZIP > $INITRD_FINAL mkisofs -R -l -J -o $ISO -b boot/loader/isolinux.bin -c boot.catalog \ -no-emul-boot -boot-load-size 4 -boot-info-table \ $CDBOOT rm -f $INITRD_GUNZIP ############################### in /iso simply use : ./makeiso.sh info slescustom.iso :) ========================================================= == 7 == Creating a good control file with nfs postinstall script and LVM stuff :) ========================================================= Here my ide.xml control file --------------------- <?xml version="1.0"?> <!DOCTYPE profile SYSTEM "/usr/share/YaST2/include/autoinstall/profile.dtd"> <profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <configure> <scripts> <chroot-scripts config:type="list"/> <post-scripts config:type="list" > <script> <filename>postinstall.sh</filename> <interpreter>shell</interpreter> <source> <![CDATA[ #!/bin/sh UPDATE_SRV=128.1.217.166 UPDATE_DIR=/suse/postinstall eject echo "Mounting update server" mkdir -p /tmp/postinstall mount -t nfs $UPDATE_SRV:$UPDATE_DIR /tmp/postinstall sh /tmp/postinstall/update_rpm.sh ]]> </source> </script> </post-scripts> <pre-scripts config:type="list"/> </scripts> </configure> <install> <bootloader> <location>mbr</location> </bootloader> <report> <messages> <show>false</show> <timeout>5</timeout> <log>true</log> </messages> <errors> <show>true</show> <timeout>5</timeout> <log>true</log> </errors> <warnings> <show>true</show> <timeout>5</timeout> <log>true</log> </warnings> </report> <general> <clock> <hwclock>GMT</hwclock> <timezone>Europe/Paris</timezone> </clock> <keyboard> <keymap>french</keymap> </keyboard> <language>fr_FR</language> <mouse> <id>20_imps2</id> </mouse> </general> <lvm config:type="list"> <lvm_group> <logical_volumes config:type="list"> <lv> <lv_fs config:type="symbol">reiser</lv_fs> <lv_mount>/</lv_mount> <lv_name>lvroot</lv_name> <lv_size>2147483648</lv_size> </lv> <lv> <lv_fs config:type="symbol">reiser</lv_fs> <lv_mount>/tmp</lv_mount> <lv_name>lvtmp</lv_name> <lv_size>536870912</lv_size> </lv> <lv> <lv_fs config:type="symbol">reiser</lv_fs> <lv_mount>/var</lv_mount> <lv_name>lvvar</lv_name> <lv_size>536870912</lv_size> </lv> </logical_volumes> <lvm_name>vgroot</lvm_name> <pesize>8M</pesize> </lvm_group> </lvm> <partitioning config:type="list"> <drive> <device>/dev/hda</device> <partitions config:type="list"> <partition> <filesystem config:type="symbol">ext2</filesystem> <mount>/boot</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">1</partition_nr> <size>49348609</size> </partition> <partition> <mount>swap</mount> <partition_id config:type="integer">130</partition_id> <partition_nr config:type="integer">2</partition_nr> <size>1069219841</size> </partition> <partition> <lvm_group>vgroot</lvm_group> <partition_id config:type="integer">142</partition_id> <partition_nr config:type="integer">3</partition_nr> <size>auto</size> </partition> </partitions> <use>all</use> </drive> </partitioning> <software> <base>Minimal+X11</base> </software> </install> </profile> -------------- Note : report directive doesn't work, whatever the timeout value , it's always 10s and is always show A Postinstall script on the nfs repository is executed. ========================================================= == 8 == postinstall script and nfs setting ========================================================= My setup is like this /suse/install : repository used to install /suse/autoyast : store .xml control file /suse/update : store homemade and update rpms which are not in /suse/install /suse/postinstall : store postinstall scripts ### file : /suse/postinstall/update_rpm.sh #### #!/bin/sh SERV_UPDATE=128.1.217.166 PATH_UPDATE=/suse/update PATH_SLES=/suse/install mkdir -p /tmp/nfs mount -t nfs $SERV_UPDATE:$PATH_UPDATE /tmp/nfs ### useless since update rpms are in install repository #rpm -Fvh /tmp/nfs/update/i686/*.rpm #rpm -Fvh /tmp/nfs/update/i586/*.rpm #rpm -Fvh /tmp/nfs/update/noarch/*.rpm ### ###### Install homemade rpms (cfengine etc...) ######### rpm -Uvh --nodeps /tmp/nfs/update/add/*.rpm umount /tmp/nfs ##### install sles8 banner ###### mount -t nfs $SERV_UPDATE:$PATH_SLES /tmp/nfs rpm -e --nodeps unitedlinux-release rpm -Uvh /tmp/nfs/SLES/suse/i586/sles-release*.rpm rpm -e --nodeps yast2-theme-UnitedLinux rpm -Uvh /tmp/nfs/SLES/suse/noarch/yast2-theme-SuSE*.rpm umount /tmp/nfs ######## SOURCE UPDATE ########### PATH_UPDATE=/suse/install/update PATH_SLES=/suse/install/SLES PATH_UL=/suse/install/UL/CD1 echo "Deleting old sources" rm -rf /var/adm/YaST/InstSrcManager/* echo "Adding new sources" installation_sources -ea nfs://$SERV_UPDATE:$PATH_UPDATE installation_sources -ea nfs://$SERV_UPDATE:$PATH_SLES installation_sources -ea nfs://$SERV_UPDATE:$PATH_UL #################################### --------------------------------------------------------- ### file : /etc/exports #### /suse/autoyast *(sync,ro) /suse/update *(sync,ro) /suse/install *(sync,ro) /suse/postinstall *(sync,ro) ################# ========================================================= == 9 == Conclusion ========================================================= A sles8 installation is made within 5-10 minutes depending the install machine. No human intervention is needed after the boot (all you must do is to choose the right .xml at the lilo cd screen) After installation the machine reboots on harddrive (in fact it reboot on cd but the cd boots by default on harddrive :p) Update is done at install time : you can say goodbye to smp/bcm5700 driver bug in kernel 2.4.19 Postinstall script on nfs provide easy way to install homemade rpms I hope this set of tips will be on Anas Nashif autoyast Homepage :) Regards, Nicolas Marciniak

1 0

SMB parameters for username, password, & workgroup?
by Kohrs, Steven 04 May '04

04 May '04

Where can I find a definition for the "init" element under "install"? I'm trying to include a username, password, & workgroup for a SMB share. I tried the following with no success: ... <init> <domain></domain> <gateway></gateway> <info_file> <![CDATA[ # # Don't remove the following line: # start_linuxrc_conf # install: smb://192.168.0.23/suse8 workdomain: WORKGROUP username: skohrs password: passw0rd Usedhcp: 1 Textmode: 1 # end_linuxrc_conf # Do not remove the above comment #]]> </init> ... Can I place these values in-line, like with FTP? smb://WORKGROUP\skohrs:passw0rd@192.168.0.23/suse8

1 0