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