From Dwayne.McGarty@huskyenergy.ca Thu Oct 27 20:08:29 2005
From: Dwayne McGarty <Dwayne.McGarty@huskyenergy.ca>
To: autoinstall@lists.opensuse.org
Subject: Rules compatibility between Novell OES1 and SLES 9 x64
Date: Thu, 27 Oct 2005 20:08:29 +0000
Message-ID: <s360df49.000@cnf008.huskyenergy.ca>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============1648189389982392210=="

--===============1648189389982392210==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit

Greetings, I presently have an autoyast set up to deliver Novell OES1
(SLES9 i386 based).  I wish to build some servers with just the SLES9
x64 distribution and was hoping to use the same rules.xml file to kick
things off.  Here is the rules.xml that is presently working for OES1:

<?xml version="1.0"?>
<!DOCTYPE autoinstall SYSTEM "/usr/share/autoinstall/dtd/rules.dtd">
<autoinstall xmlns="http://www.suse.com/1.0/yast2ns"
xmlns:config="http://www.suse.com/1.0/configns">
  <rules config:type="list">
    <rule>
       <product>
          <match>*</match>
          <match_type>exact</match_type>
       </product>
       <result>
          <profile>profiles/templates/base.xml</profile>
          <continue config:type="boolean">true</continue>
       </result>
    </rule>
    <rule>
      <mac>
        <match>*</match>
        <match_type>exact</match_type>
      </mac>
      <result>
        <profile>profiles/mac/@mac@/eth0.xml</profile>
        <continue config:type="boolean">true</continue>
      </result>
    </rule>
    <rule>
       <custom1>
          <script>
             <![CDATA[
#!/bin/sh
PATH=/bin:/sbin:/usr/bin:/usr/sbin
if [ -n "`grep build= /proc/cmdline`" ]
then
   echo -n `cat /proc/cmdline | sed -e 's/.*build=\(.*\)/\1/' -e
's/^\(.*\) BOOT.*/\1/'`
else
   echo -n "hse9-32"
fi
]]>
          </script>
          <match>*</match>
          <match_type>exact</match_type>
       </custom1>
       <result>
          <profile>profiles/software/@custom1(a).xml</profile>
          <continue config:type="boolean">false</continue>
       </result>
    </rule>
  </rules>
</autoinstall>


The SLES9 x64 autoyast attempts using the same rules.xml file but seems
to not match any of the rules and prompts for the location of a proper
rules file.  On inspecting the /var/log/YaST2/y2log file, it appears
that the bit of shell scripting being kicked off to compare the
product/mac strings to the * character are failing and returning 1
instead of 0 as they do with the OES1 installation.  ie the scripts are
treating the wildcard (*) character literally.  Does the SLES9 x64
autoyast support the use of wildcards in the match?  If not, what can I
use instead

Thanks for any help...

--===============1648189389982392210==--


From ug@suse.de Fri Oct 28 09:18:36 2005
From: Uwe Gansert <ug@suse.de>
To: autoinstall@lists.opensuse.org
Subject:
 Re: [suse-autoinstall] Rules compatibility between Novell OES1 and SLES 9 x64
Date: Fri, 28 Oct 2005 09:18:36 +0000
Message-ID: <200510281119.43333.ug@suse.de>
In-Reply-To: <s360df49.000@cnf008.huskyenergy.ca>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============6446785676969664249=="

--===============6446785676969664249==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit

On Thursday 27 October 2005 22:07, Dwayne McGarty wrote:


before I start to dig deeper we have to clear up some versioning stuff.

> Greetings, I presently have an autoyast set up to deliver Novell OES1
> (SLES9 i386 based). 

AFAIK OES1 is SLES9 SP1 based. That's an important difference (at least for 
me) :)

> I wish to build some servers with just the SLES9 
> x64 distribution 

just SLES9 or with SLES9 SPx?
If it's just SLES9, it might be that there was a fix for that in SP1 and so 
OES1 works fine, while SLES9 without any SP fails.

-- 
ciao, Uwe Gansert

Uwe Gansert, Server Technologies Team
SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nuernberg, Germany
e-mail: uwe.gansert(a)suse.de, Tel: +49-(0)911-74053-0,
Fax: +49-(0)911-74053-476, Web: http://www.suse.de      

--===============6446785676969664249==--