March 2008 - openSUSE Autoinstall - openSUSE Mailing Lists

[opensuse-autoinstall] Organizational software repository
by LDB 19 Mar '08

19 Mar '08

Sometimes some of my servers do not pick up all of the package contents in my local software repositories of SLES 9sp4 and 10sp1, while using "rug". I created the software repositories by copying the whole DVD ISOs under a directory within web root. Then I point the servers to the repositories via HTTP. Was this the correct protocol? Do I need to use Yast tool: Miscellaneous -> Installation Server to create the above? Is there an easy way to create an organization ONLY repository? I have done this in the past, but not sure of the current process. Thanks, LDB -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 0

[opensuse-autoinstall] root partition in LVM not mounting during 2nd phase of auto-installation process
by LDB 18 Mar '08

18 Mar '08

After the autoyast installation process and during the 1st boot, it stops and spews the the following ... Attempting manual resume Waiting for device /dev/rootvg/root to appear: .................. not found -- exiting to /bin/sh $ but then when I boot into rescue mode it mounts just fine ... <partitioning config:type="list"> <drive> <device>/dev/cciss/c0d0</device> <partitions config:type="list"> <partition> <create config:type="boolean">true</create> <filesystem config:type="symbol">ext3</filesystem> <filesystem_id config:type="integer">131</filesystem_id> <format config:type="boolean">true</format> <mount>/boot</mount> <mountby config:type="symbol">device</mountby> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">1</partition_nr> <partition_type>primary</partition_type> <size>534610432</size> </partition> <partition> <create config:type="boolean">true</create> <filesystem config:type="symbol">swap</filesystem> <filesystem_id config:type="integer">130</filesystem_id> <format config:type="boolean">true</format> <mount>swap</mount> <mountby config:type="symbol">device</mountby> <partition_id config:type="integer">130</partition_id> <partition_nr config:type="integer">2</partition_nr> <partition_type>primary</partition_type> <size>2293595648</size> </partition> <partition> <create config:type="boolean">true</create> <filesystem_id config:type="integer">142</filesystem_id> <lvm_group>rootvg</lvm_group> <partition_id config:type="integer">142</partition_id> <partition_nr config:type="integer">3</partition_nr> <partition_type>primary</partition_type> <size>max</size> </partition> </partitions>  <use>all</use> </drive> <drive> <device>/dev/rootvg</device> <lvm2 config:type="boolean">true</lvm2> <partitions config:type="list"> <partition> <create config:type="boolean">true</create> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <lv_name>root</lv_name> <mount>/</mount> <mountby config:type="symbol">device</mountby> <size>5368709120</size> </partition> <partition> <create config:type="boolean">true</create> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <lv_name>home</lv_name> <mount>/home</mount> <mountby config:type="symbol">device</mountby> <size>5368709120</size> </partition> <partition> <create config:type="boolean">true</create> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <lv_name>tmp</lv_name> <mount>/tmp</mount> <mountby config:type="symbol">device</mountby> <size>4368709120</size> </partition> <partition> <create config:type="boolean">true</create> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <lv_name>var</lv_name> <mount>/var</mount> <mountby config:type="symbol">device</mountby> <size>2368709120</size> </partition> <partition> <create config:type="boolean">true</create> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <lv_name>var_log</lv_name> <mount>/var/log</mount> <mountby config:type="symbol">device</mountby> <size>5368709120</size> </partition> </partitions> <pesize>4M</pesize> <type config:type="symbol">CT_LVM</type> <use>all</use> </drive> </partitioning> Any ideas?? LDB -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

3 7

[opensuse-autoinstall] "info" file section
by LDB 18 Mar '08

18 Mar '08

I have this section in my autoinst.xml file and called it "info". It is called like the following: autoyast=http://192.168.101.66/profiles/booger/info ... <install> <init> <info_file> <![CDATA[ # # Don't remove the following line: # start_linuxrc_conf # autoyast: file:///info install: http://192.168.101.66/suse/x86/10sp1/base netdevice: eth0 hostip: 192.168.101.17 netmask: 255.255.255.0 gateway: 192.168.101.254 nameserver: 192.168.101.11 textmode: 1 vnc: 1 vncpassword: super # end_linuxrc_conf # Do not remove the above comment # ]]> </info_file> </init> </install> .... but it does not work as expected. Does anyone know what I am missing? Does this only work with PXE booting? http://www.novell.com/documentation/sles10/sles_admin/index.html?page=/docu… Thank you, LDB -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

5 30

[opensuse-autoinstall] <system_gid_min> applied too late
by Michael.Leu＠mgb.ch 17 Mar '08

17 Mar '08

Hello Using SLES10 SP1. I need to prevent the creation of UIDs and GIDs in the range of 100-149, so I added this to the profile. <security> <system_uid_min>150</system_uid_min> <system_gid_min>150</system_gid_min> </security> It gets added to /etc/login.defs but too late; some rpms have already added users and groups (hal, dbus and others). A pre-install script is too early as no filesystems have been created. Any ideas? Regards, Michael Leu -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 1

[opensuse-autoinstall] Autoyast cannot install rpm files - exit status 255
by Wayman Smith 12 Mar '08

12 Mar '08

Hello, I am attempting instal SLES-10 using autoyast. I generated my autoinst.xml file from a manual install on the same hardware. My installation is over the network using an NFS share. I am able to create my partitions correctly, however when the rpm installations begin, I receive the following error Subprocess failed. Error: RPM failed: error: %post (/rpm_name/) scriptlet failed exit status 255 Even when I hit ignore, the same message appears for the next rpm as well. I haven't changed any NFS information or modified any of the rpm files. I'm not sure what is causing this. Has anyone experienced this sort of error? Regards, Wayman Smith -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 1

[opensuse-autoinstall] Error in autoyast install process
by Wayman Smith 10 Mar '08

10 Mar '08

Hello, I am attempting to perform an autoinstall process with SuSE 10.1 sp1 using autoyast and a custom autoinst.xml file. The install process reads the autoinst.xml correctly, and performs all steps up until the Install boot manager process. Here, I receive the error /sbin/mkinitrd: line 3297: /etc/fstab: No such file or directory No '/' mountpoint spceified in /etc/fstab It should also be noted that my autoinst.xml file fails RNG validation (https://bugzilla.novell.com/show_bug.cgi?id=211014#c21) I have attached my autoinst.xml file also. Might these two problems be related? --W. Smith

8 11

[opensuse-autoinstall] Routes, openSUSE and SLES
by Dan Stromberg 07 Mar '08

07 Mar '08

We want to define a multicast route. I put it in ifroute-eth0, but that seemed to work on one of openSUSE or SLES but not the other - I don't recall which unfortunately. So I took the line that I thought should work in ifroute-eth0, and put it in /etc/sysconfig/network/routes, and that worked. Temporarily. On reboots, my routes file was getting renamed to routes.YaST2save and the prior content was stuffed back in (with just a default gateway). I'd prefer to be able to set the routes file content (or ifroute-eth*) via a shell script, but if I must use the .xml method, so be it. So I stuck the following into my autoyast.xml: <routing> <ip_forward config:type="boolean">false</ip_forward>   <routes config:type="list"> <route> <destination>228.0.0.0/8</destination> <gateway>0.0.0.0</gateway> <netmask>255.0.0.0</netmask> <device>eth0</device> <extrapara>multicast</extrapara> </route> </routes> </routing> ...and that seems to handle the multicast route pretty well. It even threw in the "multicast" part at the end of my routes line for the multicast route. But. Now all seems fine on openSUSE, but on SLES, I'm not getting a default route anymore, even when I set up both of a test machine's ethernet interfaces for DHCP. I'm thinking that if I try to stick a default route into the routes file, I'm going to run into the same problem - the content will disappear on reboots. What do I need to do to get good routing? I'd like the following: 1) A consistent method across openSUSE 10.3 and SLES 10.1 - this part isn't absolutely important though 2) A good default route on DHCP or static that survives reboots and can be changed in the field without reinstalling 3) A good multicast route that survives reboots and can be changed in the field without reinstalling Thanks! -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 0

RE: [suse-autoinstall] SLES 10 RC2 remove-packages section?
by Matt Gillard 05 Mar '08

05 Mar '08

I dont have kinternet installed. This is what doesnt seem to work: <software> <patterns config:type="list"> <pattern>default</pattern> <pattern>Basis-Devel</pattern> <pattern>x11</pattern> </patterns> <packages config:type="list"> <packages>perl-libwww-perl</packages> <packages>net-snmp</packages> <packages>kernel-source</packages> </packages> <remove-packages config:type="list"> <packages>pptp</packages> <packages>smpppd</packages> <packages>ppp</packages> <packages>wvdial</packages> <packages>mutt</packages> </remove-packages> </software> In y2log it mentions that those packages should be removed, but it goes ahead and installs them anyway. I can do it manually on the command line: # rpm -e pptp smpppd ppp wvdial mutt and that works fine so I know I have no dependency problems. matt > -----Original Message----- > From: Uwe Gansert [mailto:ug@suse.de] > Sent: Friday, 30 June 2006 12:50 AM > To: suse-autoinstall(a)suse.com > Subject: Re: [suse-autoinstall] SLES 10 RC2 remove-packages section? > > > On Thursday 29 June 2006 16:45, Manfred Hollstein wrote: > > > If that fails, you have kinternet installed; add that to > the list and it > > should work. > > good point. > <remove-packages> can not break dependencies and so it's very > likely that > there is still a package that needs those packages. > I did a very small installation with no X - so it worked for me. > > -- > ciao, Uwe Gansert > > Uwe Gansert, Server Technologies Team > SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nuernberg, Germany > Fax: +49-(0)911-74053-476, Web: http://www.suse.de/~ug > now playing Covenant - Wasteland > > -- > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > For additional commands, e-mail: suse-autoinstall-help(a)suse.com > > This email and any attachments may contain privileged and confidential information and are intended for the named addressee only. If you have received this e-mail in error, please notify the sender and delete this e-mail immediately. Any confidentiality, privilege or copyright is not waived or lost because this e-mail has been sent to you in error. It is your responsibility to check this e-mail and any attachments for viruses. No warranty is made that this material is free from computer virus or any other defect or error. Any loss/damage incurred by using this material is not the sender's responsibility. The sender's entire liability will be limited to resupplying the material.

4 6