February 2005 - openSUSE Autoinstall - openSUSE Mailing Lists

Re: Fw: [suse-autoinstall] Re: firstboot scripts
by Anas Nashif 09 Feb '05

09 Feb '05

Anthony, Are your scripts executable? Maybe you need to chmod +x them. I have tested again, and it works for me. Anas Anthony Staples wrote: > Anas, > > I uninstalled the current version of yast-firstboot (2.9.3-0.2) and > updated the install to 2.9.4-0.1 as you requested. > The results were the same. > I created a small, simple script in /usr/share/firstboot/scripts, touched > /etc/reconfig_system, then rebooted. > Firstboot service did run, but the script did not run. > /var/log/Yast2/firstboot.log file was created, however it was empty. > > I also tested with a stock control.xml file with the same results. > > Cheers, > T > > > > ----- Forwarded by Anthony Staples/Louisville/Humana on 02/08/2005 03:26 > PM ----- > > "Anthony Staples" <awstaples(a)hotmail.com> > 02/07/2005 05:47 PM > > To > <astaples(a)humana.com> > cc > > Subject > Fw: [suse-autoinstall] Re: firstboot scripts > > > > > > > > ----- Original Message ----- > From: "Anas Nashif" <nashif(a)suse.de> > To: "Anthony Staples" <astaples(a)humana.com> > Cc: <awstaples(a)hotmail.com> > Sent: Monday, February 07, 2005 3:57 PM > Subject: Re: [suse-autoinstall] Re: firstboot scripts > > >>Anthony, >>Could you please try the attached RPM. >> >> >>Anas >> >>Anthony Staples wrote: >>>Anas, >>> >>>I sometimes have trouble recieving email from you, so please respond >>>to awstaples(a)hotmail.com, That is if you don't post to the mailing >>>list. >>> >>>Regards, >>> >>>Anthony Staples Technical Analyst Humana Inc. 502.580.2870 >>> >>> >>> >>> >>>The information transmitted is intended only for the person or entity >>>to which it is addressed and may contain CONFIDENTIAL material. If >>>you receive this material/information in error, please contact the >>>sender and delete or destroy the material/information. > > The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.

2 1

AW: [suse-autoinstall] More mysteries: LDAP
by Andreas.Matthieu＠tfa.brandenburg.de 09 Feb '05

09 Feb '05

Hi Anas, i reproduce this, and my y2log say: [YCP] clients/ldap_auto.ycp:26 Ldap auto started [agent-ldap] LdapAgent.cc(debug_exception):447 ldap error while searching for (-1): Can't contact LDAP server [ag_passwd] new plus lines in passwd: +:::::: [ag_passwd] new plus lines in group: +::: [YCP] Service.ycp:80 Der Dienst nscd existiert nicht. [YCP] clients/ldap_auto.ycp:90 Ldap auto finished That's correct, no lan interface are active. In previous step eth0 are configured, but not activated. Is this the problem? How can I activate the lan interface at configuration step? Regards, Andreas -----Ursprüngliche Nachricht----- Von: nashif(a)suse.de [SMTP:nashif@suse.de] Gesendet am: Sonntag, 6. Februar 2005 06:18 An: ole-suse-autoyast(a)gmx.net Cc: suse-autoinstall(a)suse.com Betreff: Re: [suse-autoinstall] More mysteries: LDAP Ole, I could reproduce this, but still can't find out what is the problem exactly. I am still investigating. Anas Ole Streicher wrote: > 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 > -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

Autoyast fails after integrating SLES9 SP1
by Frank Steiner 09 Feb '05

09 Feb '05

Hi, we are running autoyast for SLES9 on IBM pSeries. We install over the network with bootp. Things went fine, until we added SP1 the way Anas described it in the mails from last week. But now installation fails because it can't find the core9 sources. First I created the new "install" image from the SP1 directory with mkzimage_cmdline for booting with dhcp/bootp. Then I set up the NFS directory. It looks like: lrwxrwxrwx 1 root root 10 Jan 11 14:21 boot -> sles9/boot lrwxrwxrwx 1 root root 13 Jan 11 14:21 content -> sles9/content lrwxrwxrwx 1 root root 17 Jan 11 14:21 control.xml -> sles9/control.xml drwxr-xr-x 8 root root 360 Jan 11 11:56 core9 lrwxrwxrwx 1 root root 22 Feb 4 09:17 driverupdate -> sles9-SP1/driverupdate lrwxrwxrwx 1 root root 15 Feb 4 09:17 linux -> sles9-SP1/linux lrwxrwxrwx 1 root root 13 Jan 11 14:21 media.1 -> sles9/media.1 drwxr-xr-x 5 root root 312 Jan 11 12:36 sdk9 drwxr-xr-x 12 root root 1160 Jan 11 12:36 sles9 drwxr-xr-x 13 root root 1496 Feb 4 09:16 sles9-SP1 drwxr-xr-x 2 root root 104 Feb 4 09:12 yast The contents of the sles9/, core9/ and sdk9/ directories have not changed, we just added the sles9-SP1 directory and copied the CDs. Instead of creating subdirs CD{?} there we just put all CD contents into the subdirs which worked fine all the time. I.e., core9/ looks like babbage 9/SuSE# ls core9 . .. ARCHIVES.gz ChangeLog INDEX.gz content directory.yast ls-lR.gz media.1 media.2 media.3 media.4 media.5 suse We adjusted order and instorder: /sles9-SP1 /sles9-SP1 /sles9 /sles9 /core9 /core9 /sdk9 /sdk9 /sles9-SP1 /sles9 /core9 /sdk9 Now, when I start the installation, everything goes fine and yast starts installing the packages. here is a screenshot: http://www.bio.ifi.lmu.de/~steiner/aysles9.jpg on which you can see that it found all 4 install sources. But after a few packages from the SP1, it says it can't find the packet "sles_admin_de" on the installation source, then some more packages, and when I click " ignore", it complains it can't find the core version 9 CD. The differing numbers that are shown are from the media.1/media files from the sles9/ and the core9/ subdir. When I manually add the core9/ subdir in the error window, that it continues to install and flip flops between installing packages from core9 and SP1 etc. But initially it seems to be unable to find the core9 sources in the core9/ subdir. This problem did not occur before we added SP1, so it must be caused by it somehow. Just like the additional SP1 dir make yast forget that the core sources are in a subdir, so it is just considering the link media.1 in the main dir instead of looking at core9/media.1... Any ideas how to fix this? cu, Frank -- Dipl.-Inform. Frank Steiner Web: http://www.bio.ifi.lmu.de/~steiner/ Lehrstuhl f. Bioinformatik Mail: http://www.bio.ifi.lmu.de/~steiner/m/ LMU, Amalienstr. 17 Phone: +49 89 2180-4049 80333 Muenchen, Germany Fax: +49 89 2180-99-4049 * Rekursion kann man erst verstehen, wenn man Rekursion verstanden hat. *

1 0

KDE default skeleton
by suse_list 09 Feb '05

09 Feb '05

Hi, I was woundering where does SuSE store the kde skeleton files and how best to create a new skeleton and have it replicated with the autoinstall, so that when new users are created, that they get the customized skeleton for kde. Please let me know Thanks S.

2 1

RE: [suse-autoinstall] KDE default skeleton
by Schumacher, Gordon 08 Feb '05

08 Feb '05

# From: suse_list [mailto:suse_list@infineon.net] # Sent: Tuesday, February 08, 2005 4:13 PM # To: suse-autoinstall(a)suse.com # Subject: [suse-autoinstall] KDE default skeleton # # Hi, # # I was woundering where does SuSE store the kde skeleton files # and how best to create a new skeleton and have it replicated # with the autoinstall, so that when new users are created, # that they get the customized skeleton for kde. Not sure on the first half, but the way I'd go about replicating it is by an init-script that fetches down a tarball of the default skeleton, and then unpacking it into the destination directory: wget -q http://myserver/my-kde-skel.tgz tar xvfz --directory /path/to/default/kde/skeleton my-kde-skel.tgz That should do it, I think!

1 0

Fw: [suse-autoinstall] Re: firstboot scripts
by Anthony Staples 08 Feb '05

08 Feb '05

Anas, I un-installed the current version of yast-firstboot (2.9.3-0.2) and updated the install to 2.9.4-0.1 as you requested. The results were the same. I created a small, simple script in /usr/share/firstboot/scripts, touched /etc/reconfig_system, then rebooted. Firstboot service did run, but the script did not run. /var/log/Yast2/firstboot.log file was created, however it was empty. I also tested with a stock control.xml file with the same results. Cheers, T The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.

1 0

Sysconfig section mystery
by Ole Streicher 08 Feb '05

08 Feb '05

Hi, I have a mysterious problem with the sysconfig section:when I use the following section <sysconfig config:type="list"> <sysconfig_entry> <sysconfig_key>DISPLAYMANAGER_REMOTE_ACCESS</sysconfig_key> <sysconfig_path>/etc/sysconfig/displaymanager</sysconfig_path> <sysconfig_value>yes</sysconfig_value> </sysconfig_entry> <sysconfig_entry> <sysconfig_key>DISPLAYMANAGER_STARTS_XSERVER</sysconfig_key> <sysconfig_path>/etc/sysconfig/displaymanager</sysconfig_path> <sysconfig_value>no</sysconfig_value> </sysconfig_entry> <sysconfig_entry> <sysconfig_key>DISPLAYMANAGER_XSERVER_TCP_PORT_6000_OPEN</sysconfig_key> <sysconfig_path>/etc/sysconfig/displaymanager</sysconfig_path> <sysconfig_value>yes</sysconfig_value> </sysconfig_entry> <sysconfig_entry> <sysconfig_key>YAST2_LOADFTPSERVER</sysconfig_key> <sysconfig_path>/etc/sysconfig/onlineupdate</sysconfig_path> <sysconfig_value>no</sysconfig_value> </sysconfig_entry> </sysconfig> all system variables are set except the DISPLAYMANAGER_STARTS_XSERVER which still has the default value "yes". Is the handling of this section buggy, and how could one work around this? System is SuSE-9.2. Best regards, Ole -- GMX im TV ... Die Gedanken sind frei ... Schon gesehen? Jetzt Spot online ansehen: http://www.gmx.net/de/go/tv-spot

2 2

Custom package DB generation problem
by Schumacher, Gordon 08 Feb '05

08 Feb '05

I'm trying to make myself a custom package set, by using the command: create_package_descr -o setup/descr/ -x setup/descr/EXTRA_PROV as suggested by Ole Streicher, and as contained in section 4.5.3. I do get the "not a directory" warning, and it continues, and seems to complete just fine, claiming to have processed 7233 packages. If I look in the file "packages", I can see my new packages in it. (This repository is a duplicate of the standard SuSE 9.2 Professional one, with one extra .sel file and three new packages added, as a test to start out.) But when I start YaST afterwards, pointed at this repository, many, many packages seem to be missing! I'm not quite sure what I should be looking for here. All I did was, I added a file "Maxtor-9.2-i586.sel", which has =Ord: 150 (I'm not at all sure what that is for!) and three packages in the +Ins: section, and is otherwise pretty much identical to the other .sel files. I also added Maxtor-9.2-i586.sel alphabetically in the list in both "selections" and "directory.yast". Did I miss something? I noticed that the file MD5SUMS is not updated; do I need to regenerate this?

2 1

RE: [suse-autoinstall] RPM packages fail
by Ryan Allen 07 Feb '05

07 Feb '05

thank you, this solved it. I had run the utility in the past, but for some reason, the file setup/descr/EXTRA_PROV was missing. When create_package_descr ran, it just produced a quick warning, and worked to completion anyhow. Thanks for the support! - Ryan > -----Original Message----- > From: Anas Nashif [mailto:nashif@suse.de] > Sent: Monday, February 07, 2005 12:30 PM > To: Ryan Allen > Cc: suse-autoinstall(a)suse.com > Subject: Re: [suse-autoinstall] RPM packages fail > > did you run create_package_descr with the -x option pointing to > setup/descr/EXTRA_PROV ? > > Anas > > Ryan Allen wrote: > > > > > > Hi list! > > > > > > > > I've gotten a CD to boot and launch the install process with SuSE 9.2. > > From some reason however, many important RPMs are failing with the > > following errors: > > > > > > > > > > > > Installation of package kernel-default-2.6.8-24.i586 failed > > > > > > > > ERROR(InstTarget:E_RpmDB_subprocess_failed) > > > > --- > > > > ...... <some successful rpm's> ...... > > > > rpm output: > > > > error: %pre(kernel-default-2.5.8-24) scriptlet failed, exit status 255 > > > > error: install: %pre scriptlet failed (2), skipping > > kernel-default-2.5.8-24 > > > > > > > > > > > > > > > > So, for troubleshooting I hit "ignore", and it kept on going. Seems > > that about every 10 packages or so, I get the same error but for the > > current rpm. > > > > > > > > Anybody know what this means? > > > > > > > > Thanks, > > > > Ryan > > > > > > > >

1 0

RPM packages fail
by Ryan Allen 07 Feb '05

07 Feb '05

Hi list! I've gotten a CD to boot and launch the install process with SuSE 9.2. >From some reason however, many important RPMs are failing with the following errors: Installation of package kernel-default-2.6.8-24.i586 failed ERROR(InstTarget:E_RpmDB_subprocess_failed) --- ...... <some successful rpm's> ...... rpm output: error: %pre(kernel-default-2.5.8-24) scriptlet failed, exit status 255 error: install: %pre scriptlet failed (2), skipping kernel-default-2.5.8-24 So, for troubleshooting I hit "ignore", and it kept on going. Seems that about every 10 packages or so, I get the same error but for the current rpm. Anybody know what this means? Thanks, Ryan

2 1