openSUSE Autoinstall February 2005

autoinstall@lists.opensuse.org

50 participants
108 discussions

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

25 May '05

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

3 2

multiple raid and autoyast
by Jeremy Sanders 02 Mar '05

02 Mar '05

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

1 3

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

02 Mar '05

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

2 1

More mysteries: LDAP
by Ole Streicher 01 Mar '05

01 Mar '05

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

3 2

SLES8: GRUB as default boot loader?
by Oliver Schwabedissen 28 Feb '05

28 Feb '05

Hello, we are installing SLES8 with SP3 through HTTP. Although we specified grub as the boot loader we still get lilo installed by default and have to replace it with grub in our post install script. <bootloader> <location>mbr</location> <loader_type>grub</loader_type> <loader_device>/dev/cciss/c0d0</loader_device> <kernel_parameters>acpi=off 3</kernel_parameters> <initrd_modules config:type="list"> <module></module> </initrd_modules> </bootloader> Hardware are HP server with /, /boot and /var mounted on normal partitions (HW RAID 1) and /home, /tmp and /usr mounted to LVM volumes (same RAID 1). All file systems are XFS. Kernel and initrd in tftp directory are from SP3, we have the driverupdate file from SP3 CD1 linked to our SLES8 installation root (/autoyast/SLES8), in yast/order the paths to SP3 CD1 and CD2 are listed as the first entries. Regards, Oliver Schwabedissen -- DSL Komplett von GMX +++ Superg�nstig und stressfrei einsteigen! AKTION "Kein Einrichtungspreis" nutzen: http://www.gmx.net/de/go/dsl

3 4

Autoinstall problems on SLES-9...Please help...
by Sasikumar R 28 Feb '05

28 Feb '05

Hi List, Greetings,and sorry for the earlier mail, without subject and body. It was a mischief by the browser. I am trying to setup autoinstall for 64 IBM OpenPower 720 (PPC) systems with Autoyast control file and NFS repository. I am using SLES 9 for PPC. Everyting goes smoothly, but after the first phase of install, just before the first reboot, the system gives me an error - "Installation of suse-build-key RPM failed", and waits for an acknoledgment. Once the error is acknowledged, system reboots, and continues the configuration. I checked the y2logRPM file in /var/log/Yast2 directory on the target server, and found the following errors: ----snipped-----------------------------snipped----------- 1970-01-06 01:25:27 samba-client-3.0.4-1.22.ppc.rpm installed ok 1970-01-06 01:25:29 sax2-4.8-103.7.ppc.rpm installed ok Additional rpm output: Updating etc/sysconfig/sax... 1970-01-06 01:25:30 at-3.1.8-898.1.ppc.rpm installed ok 1970-01-06 01:25:30 suse-build-key-1.0-662.4.noarch.rpm install failed rpm output: importing SuSE build key to rpm keyring... gpg: key 9C800ACA has been created 971524343 seconds in future (time warp or clock problem) gpg: key 9C800ACA has been created 971524343 seconds in future (time warp or clock problem) gpg: key 9C800ACA has been created 971524343 seconds in future (time warp or clock problem) gpg: key 9C800ACA has been created 971524343 seconds in future (time warp or clock problem) gpg: key 9C800ACA: no valid user IDs gpg: key 3D25D3D9 has been created 920289658 seconds in future (time warp or clock problem) gpg: key 3D25D3D9 has been created 920289658 seconds in future (time warp or clock problem) gpg: key 3D25D3D9: no valid user IDs importing the key from the file usr/lib/rpm/gnupg/suse-build-key.gpg returned an error. This should not happen. It may not be possible to properly verify the authenticity of rpm packages from SuSE sources.The keyring containing the SuSE rpm package signing key can be found in the root directory of the first CD (DVD) of your SuSE product. error: %post(suse-build-key-1.0-662.4) scriptlet failed, exit status 255 1970-01-06 01:25:31 apache2-2.0.49-27.8.ppc.rpm installed ok Additional rpm output: Updating etc/sysconfig/apache2... 1970-01-06 01:25:32 cups-1.1.20-108.3.ppc.rpm installed ok Additional rpm output: Updating etc/sysconfig/cups... 1970-01-06 01:25:32 gpgme-0.3.16-51.1.ppc.rpm installed ok 1970-01-06 01:25:32 kdebase3-nsplugin-3.2.1-68.16.ppc.rpm installed ok ----snipped-----------------------------snipped----------- It will be a pain to acknowledge on all 64 systems, since these systems are without graphics card / monitor. I have observed that the system date is being set as January 6th, 1970. Could someone please guide me on how to set the correct date using autoinstall script?? My control file (install.xml) reads as: --------------------------------------- <?xml version="1.0"?> <!DOCTYPE profile SYSTEM "/usr/share/autoinstall/dtd/profile.dtd"> <profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <configure> <inetd> <last_created config:type="integer">0</last_created> <netd_conf config:type="list"> <conf> <protocol>udp</protocol> <script>amanda</script> <server>/usr/lib/amanda/amandad</server> <service>amanda</service> </conf> <conf> <protocol>tcp</protocol> <script>amandaidx</script> <server>/usr/lib/amanda/amindexd</server> <service>amandaidx</service> </conf> <conf> <protocol>tcp</protocol> <script>amidxtape</script> <server>/usr/lib/amanda/amidxtaped</server> <service>amidxtape</service> </conf> <conf> <protocol>tcp</protocol> <script>bitlbee</script> <server>/usr/sbin/bitlbee</server> <service>ircd</service> </conf> <conf> <protocol>udp</protocol> <script>bootp-DD2</script> <server>/usr/sbin/bootpd</server> <service>bootps</service> </conf> <conf> <protocol>tcp</protocol> <script>chargen</script> <service>chargen</service> </conf> <conf> <protocol>udp</protocol> <script>chargen-udp</script> <service>chargen</service> </conf> <conf> <protocol>tcp</protocol> <script>cups-lpd</script> <server>/usr/lib/cups/daemon/cups-lpd</server> <service>printer</service> </conf> <conf> <protocol>tcp</protocol> <script>cvs</script> <server>/usr/bin/cvs</server> <service>cvspserver</service> </conf> <conf> <protocol>tcp</protocol> <script>daytime</script> <service>daytime</service> </conf> <conf> <protocol>udp</protocol> <script>daytime-udp</script> <service>daytime</service> </conf> <conf> <protocol>tcp</protocol> <script>echo</script> <service>echo</service> </conf> <conf> <protocol>udp</protocol> <script>echo-udp</script> <service>echo</service> </conf> <conf> <protocol>tcp</protocol> <script>fam</script> <server>/usr/sbin/fam</server> <service>fam</service> </conf> <conf> <protocol>tcp</protocol> <script>finger</script> <server>/usr/sbin/in.fingerd</server> <service>finger</service> </conf> <conf> <protocol>tcp</protocol> <script>i4l-vbox</script> <server>/usr/sbin/vboxd</server> <service>vboxd</service> </conf> <conf> <protocol>tcp</protocol> <script>imap</script> <server>/usr/sbin/ipop2d</server> <service>pop2</service> </conf> <conf> <protocol>tcp</protocol> <script>imap</script> <server>/usr/sbin/ipop3d</server> <service>pop3</service> </conf> <conf> <protocol>tcp</protocol> <script>imap</script> <server>/usr/sbin/ipop3d</server> <service>pop3s</service> </conf> <conf> <protocol>tcp</protocol> <script>imap</script> <server>/usr/sbin/imapd</server> <service>imap</service> </conf> <conf> <protocol>tcp</protocol> <script>imap</script> <server>/usr/sbin/imapd</server> <service>imaps</service> </conf> <conf> <protocol>tcp</protocol> <script>leafnode</script> <server>/usr/sbin/leafnode</server> <service>nntp</service> </conf> <conf> <script>nagios-nrpe</script> <server>/usr/bin/nrpe</server> <service>9991</service> </conf> <conf> <protocol>tcp</protocol> <script>netstat</script> <server>/bin/netstat</server> <service>netstat</service> </conf> <conf> <protocol>udp</protocol> <script>ntalk</script> <server>/usr/sbin/in.talkd</server> <service>ntalk</service> </conf> <conf> <protocol>tcp</protocol> <script>pidentd</script> <server>/usr/sbin/in.identd</server> <service>ident</service> </conf> <conf> <protocol>tcp</protocol> <script>pure-ftpd</script> <server>/usr/sbin/pure-ftpd</server> <service>ftp</service> </conf> <conf> <protocol>tcp</protocol> <script>qpopper</script> <server>/usr/sbin/popper</server> <service>pop3</service> </conf> <conf> <protocol>tcp</protocol> <script>rexec</script> <server>/usr/sbin/in.rexecd</server> <service>exec</service> </conf> <conf> <protocol>tcp</protocol> <script>rlogin</script> <server>/usr/sbin/in.rlogind</server> <service>login</service> </conf> <conf> <protocol>tcp</protocol> <script>rman</script> <server>/usr/sbin/http-rman</server> <service>http-rman</service> </conf> <conf> <protocol>tcp</protocol> <script>rsh</script> <server>/usr/sbin/in.rshd</server> <service>shell</service> </conf> <conf> <protocol>udp</protocol> <script>rstatd</script> <server>/usr/sbin/rpc.rstatd</server> <service>rstatd</service> </conf> <conf> <protocol>tcp</protocol> <script>rsync</script> <server>/usr/sbin/rsyncd</server> <service>rsync</service> </conf> <conf> <protocol>udp</protocol> <script>rusersd</script> <server>/usr/sbin/rpc.rusersd</server> <service>rusersd</service> </conf> <conf> <protocol>udp</protocol> <script>rwalld</script> <server>/usr/sbin/rpc.rwalld</server> <service>rwall</service> </conf> <conf> <protocol>tcp</protocol> <script>samba</script> <server>/usr/sbin/swat</server> <service>swat</service> </conf> <conf> <protocol>tcp</protocol> <script>servers</script> <service>servers</service> </conf> <conf> <protocol>tcp</protocol> <script>services</script> <service>services</service> </conf> <conf> <protocol>tcp</protocol> <script>smtpd</script> <server>/usr/sbin/smtpd</server> <service>smtpd</service> </conf> <conf> <protocol>tcp</protocol> <script>systat</script> <server>/bin/ps</server> <service>systat</service> </conf> <conf> <protocol>udp</protocol> <script>talk</script> <server>/usr/sbin/in.talkd</server> <service>talk</service> </conf> <conf> <protocol>tcp</protocol> <script>telnet</script> <server>/usr/sbin/in.telnetd</server> <service>telnet</service> </conf> <conf> <protocol>udp</protocol> <script>tftp</script> <server>/usr/sbin/in.tftpd</server> <service>tftp</service> </conf> <conf> <protocol>tcp</protocol> <script>time</script> <service>time</service> </conf> <conf> <protocol>udp</protocol> <script>time-udp</script> <service>time</service> </conf> <conf> <protocol>tcp</protocol> <script>uucp</script> <server>/usr/lib/uucp/uucico</server> <service>uucp</service> </conf> <conf> <protocol>tcp</protocol> <script>vnc</script> <server>/usr/X11R6/bin/Xvnc</server> <service>vnc1</service> </conf> <conf> <protocol>tcp</protocol> <script>vnc</script> <server>/usr/X11R6/bin/Xvnc</server> <service>vnc2</service> </conf> <conf> <protocol>tcp</protocol> <script>vnc</script> <server>/usr/X11R6/bin/Xvnc</server> <service>vnc3</service> </conf> <conf> <protocol>tcp</protocol> <script>vnc</script> <server>/usr/X11R6/bin/vnc_inetd_httpd</server> <service>vnchttpd1</service> </conf> <conf> <protocol>tcp</protocol> <script>vnc</script> <server>/usr/X11R6/bin/vnc_inetd_httpd</server> <service>vnchttpd2</service> </conf> <conf> <protocol>tcp</protocol> <script>vnc</script> <server>/usr/X11R6/bin/vnc_inetd_httpd</server> <service>vnchttpd3</service> </conf> <conf> <protocol>tcp</protocol> <script>vsftpd</script> <server>/usr/sbin/vsftpd</server> <service>ftp</service> </conf> </netd_conf> <netd_service config:type="symbol">xinetd</netd_service> <netd_status config:type="integer">0</netd_status> </inetd> <networking> <dns> <dhcp_hostname config:type="boolean">false</dhcp_hostname> <dhcp_resolv config:type="boolean">false</dhcp_resolv> </dns> <interfaces config:type="list"> <interface> <bootproto>dhcp</bootproto> <device>eth0</device> <startmode>onboot</startmode> </interface> <interface> <bootproto>dhcp</bootproto> <device>eth1</device> <startmode>onboot</startmode> </interface> </interfaces> <modules config:type="list"> <module_entry> <device>static-0</device> <module>e1000</module> </module_entry> <module_entry> <device>static-1</device> <module>e1000</module> </module_entry> </modules> <routing> <ip_forward config:type="boolean">false</ip_forward> </routing> </networking> <nfs_server> <start_nfsserver config:type="boolean">true</start_nfsserver> </nfs_server> <tftp-server> <start_tftpd config:type="boolean">true</start_tftpd> <tftp_directory>/tftpboot/</tftp_directory> </tftp-server> </configure> <install> <general> <clock> <hwclock>UTC</hwclock> <timezone>Asia/Calcutta</timezone> </clock> <keyboard> <keymap>english-us</keymap> </keyboard> <language>en_US</language> <mode> <confirm config:type="boolean">false</confirm> <forceboot config:type="boolean">false</forceboot> </mode> <mouse> <id>none</id> </mouse> </general> <pre-scripts config:type="list"> <script> <filename>/vgremove.sh</filename> <interpreter>shell</interpreter> <source><![CDATA[ insmod lvm-mod vgscan # Adjust the list of VGs to be removed vgs=`echo /dev/rootvg` for vg in $vgs do if [ -d $vg ] then vgchange -a y $vg lvs=`ls $vg` for lv in $lvs do i=`basename $lv` if [ $i != "group" ] then lvremove -f $vg/$i fi done vgchange -a n $vg vgremove $vg fi done ]]></source> </script> </pre-scripts> <partitioning config:type="list"> <drive> <device>/dev/sda</device> <initialize config:type="boolean">false</initialize> <partitions config:type="list"> <partition> <crypt>twofish256</crypt> <format config:type="boolean">false</format> <loop_fs config:type="boolean">false</loop_fs> <partition_id config:type="integer">65</partition_id> <partition_type>primary</partition_type> <size>50M</size> </partition> <partition> <format config:type="boolean">false</format> <loop_fs config:type="boolean">false</loop_fs> <partition_type>primary</partition_type> <mount/> <size>8GB</size> </partition> <partition> <lvm_group>rootvg</lvm_group> <partition_type>primary</partition_type> <size>60GB</size> </partition> </partitions> <use>all</use> </drive> <drive> <device>/dev/rootvg</device> <is_lvm_vg config:type="boolean">true</is_lvm_vg> <partitions config:type="list"> <partition> <filesystem config:type="symbol">reiser</filesystem> <lv_name>rootlv</lv_name> <mount>/</mount> <size>6GB</size> </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <lv_name>optlv</lv_name> <mount>/opt</mount> <size>4GB</size> </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <lv_name>varlv</lv_name> <mount>/var</mount> <size>1GB</size> </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <lv_name>tmplv</lv_name> <mount>/tmp</mount> <size>1GB</size> </partition> </partitions> <pesize>4M</pesize> <use>all</use> </drive> </partitioning> <software> <addons config:type="list"> <addon>Base-System</addon> <addon>Basis-Devel</addon> <addon>Basis-Sound</addon> <addon>File-Server</addon> <addon>Gnome</addon> <addon>HA</addon> <addon>Kde-Desktop</addon> <addon>LAMP</addon> <addon>LSB</addon> <addon>Linux-Tools</addon> <addon>Mail_News-Server</addon> <addon>Print-Server</addon> <addon>SuSE-Documentation</addon> <addon>Various-Tools</addon> <addon>WBEM</addon> <addon>X11</addon> <addon>YaST2</addon> <addon>analyze</addon> <addon>auth</addon> <addon>dhcp_DNS-Server</addon> </addons> <base>Full-Installation</base> </software> </install> </profile> Please help. Thank you for your time in advance, and sorry for this long mail. Regards, Sasi ___________________________________________________ Build your own website, it's easy and fun. http://www.homemaster.net - Homemaster. Come Together. Online.

1 0

no subject
by Sasikumar R 28 Feb '05

28 Feb '05

___________________________________________________ Have your own email and web address for life. http://www.homemaster.net - Homemaster. Come Together. Online.

1 0

Re: [suse-autoinstall] SLES8: GRUB as default boot loader?
by Oliver Schwabedissen 26 Feb '05

26 Feb '05

> > we are installing SLES8 with SP3 through HTTP. Although we specified > grub > > as the boot loader we still get lilo installed by default and have to > > replace it with grub in our post install script. > > > > <bootloader> > > <location>mbr</location> > > <loader_type>grub</loader_type> > > <loader_device>/dev/cciss/c0d0</loader_device> > > <kernel_parameters>acpi=off 3</kernel_parameters> > > <initrd_modules config:type="list"> > > <module></module> > > </initrd_modules> > > </bootloader> > Try "tabooing" LILO and selecting GRUB in the package selection, it should > help. The package list only contains GRUB, no LILO at all... Oliver -- DSL Komplett von GMX +++ Superg�nstig und stressfrei einsteigen! AKTION "Kein Einrichtungspreis" nutzen: http://www.gmx.net/de/go/dsl

1 0

How do I disable auto accept of the SUSE End User License Agreement?
by John George 25 Feb '05

25 Feb '05

I have a control file to automate a SLES9 SP1 installation using autoyast. However, I want yast to wait for the user to accept the end user license agreement before proceeding. Waiting 10 seconds and then automatically accepting the license seems to be the default behavior. Is there a way to disable this? --John --------------------------------- Do you Yahoo!? Yahoo! Mail - 250MB free storage. Do more. Manage less.

1 0

installing a lot of perl modules
by Ryan Allen 25 Feb '05

25 Feb '05

Hi List, Does anybody have recommendations for installing a bunch of perl modules that aren't in RPM? We have a few that require some custom compile settings. Currently, I'm doing a painful process of installing on a clean machine, compiling and installing, then making a tar ball from the output of "make install". Then during post-install, copying and un-tarring them onto the new system. This gets us by for now, but is horribly non-maintainable for future upgrades. What's the "best practice" for installing custom-compiled perl modules, or modules that are not pre-packaged in RPM's. Thanks! -- Ryan

3 2

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

openSUSE Autoinstall February 2005