Does anyone know if any of the SLES releases 9 or 10 support passing the
linuxrc option netdevice=<hardware mac address> ?
I noticed Red Hat has had this for sometime and it seems totally missing
in SuSE which seems really odd.
I'm still scratching my head if we really are still passing only by
kernel interface name.
I read in the change log for linuxrc-1.8.6-3 a change that "sounds" like
this feature.
* Mon Mar 14 2005 - snwint(a)suse.de
- s390: fix segfault in net_list_s390_devs()
- extra root image was sometimes not used
- allow netdevices to be specified by hwaddress
But it looks like linuxrc-1.8.6-3 is only available in SuSE Professional
9.3.
"any" commentary would be sincerely appreciated
the feature also seems to be fairly minor since any delimiter seperating
the octets in the hwaddr string could be used to identify the difference
between an interface name and interface hw address
if i could figure out a generic method of overriding the linuxrc with a
custom script and daisy chain it back into linuxrc after setting up the
interface name, I would.. and have a slight idea on how to do that.. but
i'd rather find out i'm just missing something and the feature is
already there
Thanks!
Repository Priority is obviously a useful thing to be able to
manipulate. Yast lets me set it and zypper lets me set it.
Yet, if I have multiple repositories defined at the beginning
of my autoyast (including update repos so I get an up to date
system built out of the box), I don't seem to have any control
over the respective repository priorities - they're all defaulted.
Or did I miss a subtle option somewhere?
Tim
--
Tim Kirby 651-605-9074
trk(a)cray.com Cray Inc. Information Systems
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org
Hello,
someone may start to laugh now for my (OT) question, but I can't find a
satisfying solution :-/
How do you manage patches, updates, etc. for your running opensuse
clients (not enterprise linux, just the "regular" opensuse distribution)?
Is there a way like known from M$-World (WSUS)? As I know "Zend
Management Server" is not open source (and not supported any more?!).
Or can the complete management only be handled with self written scripts?
Thanks!
Regards,
Ivan
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org
Hi,
I try to install sles 11 via autoyast. I did an installation from dvd,
and pulled an autoyast profile. This profile works, and can be installed
via pxe.
Now I want to add the following packages:
findutils-locate, dhcp-server, bind, apache2, vsftpd, nfs-kernel-server
I do this via the gui. I have also tried to do it with an editor, as the
gui messed up profiles in sles10sp2.
In both cases, after the first reboot, I get the errormessage:
"The package resolver run failed. Please check your software section in
the aut" [oyast profile] (last part invisible, I guess it should be the
software section in my autoyast profile :-))
This a real problem, as I have to confirm this message, thus it stops
the autoinstall process.
After confirming, the autoinstall process continues. Right bevor I can
log in, I get
"Could not update ICEauthority file /var/lib/gdm/.ICEauthority"
I confirm, and get:
"There is a problem with the configuration server.
(/usr/lib/GConf/2/gconf-sanity-check-2 exited with status 256)"
I confirm, and can log in. Theses messages are presistend after reboot.
Its annoying, but not a stopper like the first problem.
Why is this? Can I avoid this?
Isaac
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org
I have a working autoyast install for 11.1 without using rules. Right
now I would like to introduce rules but I do not seem to understand
exactly how to make this work.
The current install is done by supplying information for a linuxrc info
file on the kernel command line
info=nfs://<ip-address>/<path>/1055_init.linuxrc
The info file has several parameters defined for network access, the
install and the autoyast variable
autoyast: nfs://<ip-address>/<path>/1055_init.autoyast <- this is
my autoinst profile
below the path I have created the rules directory which includes a rules
.xml file with following content
<?xml version="1.0"?>
<!DOCTYPE autoinstall SYSTEM "/usr/share/autoinstall/dtd/rules.dtd">
<!-- comments -->
<autoinstall xmlns="http://www.suse.com/1.0/yast2ns"
xmlns:config="http://www.suse.com/1.0/configns">
<rules config:type="list">
<rule>
<custom1>
<script>
# CPU_TYPE on vm's is giving same result for CPU as on real hardware we
have to extend to video to understand the difference between virtual and
real
CPU_TYPE=`cat /proc/cpuinfo|grep 'model name'|uniq|awk 'BEGIN
{FS=":"};{print $2}'`
VIDEO_TYPE=`/sbin/lspci | grep "VGA compatible controller"|awk 'BEGIN
{FS=":"};{print $3}'`
if [ "$CPU_TYPE" == " AMD Athlon(tm) 64 X2 Dual Core Processor 4400+" ];
then
if [ "$VIDEO_TYPE" == " nVidia Corporation G70 [GeForce 7300 GT] (rev
a1)" ]; then
echo -n "host1.xml"
elif [ "$VIDEO_TYPE" == " InnoTek Systemberatung GmbH VirtualBox
Graphics Adapter" ]; then
echo -n "host1-virtualbox.xml"
fi
# information for scan64-3200
elif [ "$CPU_TYPE" == " AMD Athlon(tm) 64 Processor 3200+" ]; then
if [ "$VIDEO_TYPE" == " nVidia Corporation G70 [GeForce 7300 GT] (rev
a1)" ]; then
echo -n "host2.xml"
elif [ "$VIDEO_TYPE" == " InnoTek Systemberatung GmbH VirtualBox
Graphics Adapter" ]; then
echo -n "host2-virtualbox.xml"
fi
fi
</script>
<match>*</match>
<match_type>exact</match_type>
</custom1>
<result>
<profile>@custom1@</profile>
<continue config:type="boolean">true</continue>
</result>
</rule>
<rule>
<custom>
<script>
</script>
<match>*</match>
<match_type>exact</match_type>
</custom>
<result>
<profile>1055_init.autoyast</profile>
<continue config:type="boolean">false</continue>
</result>
</rule>
</rules>
</autoinstall>
I have tried to change the autoyast parameter in the info file with the
following values
autoyast: nfs://<ip-address>/<path>/ <-- question about profile
location
autoyast: nfs://<ip-address>/<path>/rules/ <-- question about
profile location
autoyast: nfs://<ip-address>/<path>/rules/rules.xml
Above direct reference to rules file seems to work but not as expected.
When I check the box I can see that in /tmp/profile/autoinst.xml I find
a copy of my rules.xml file where I'm expecting a merged profile from my
1055_init.autoyast and host2.xml information
I'm not sure exactly what I'm doing wrong and even after extensive check
via google haven't found the right references. I've used
http://forgeftp.novell.com/yast/doc/SL11.1/autoinstall/ for
documentation but it is not giving me enough detail to solve above issue.
Any input would be welcomed.
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org
Hello List,
I hope I can ask my question about ayast_setup here .....
I found this littel sweet looking tool on Uwe Gansert hp at suse.de ...
Now I have some questions:
1. Can the filename argument be are URL too ?
2. What if I just bring eg. a packetlist into the XML file - would it
leave the rest of the installation untouched ?
- Would it install all missing packages and delete all packages
which are not in the XML file but at the System ?
3. Can I use it in a Cronjob ?
Thanks for helping.
greetings
Alex
--
Alexander Luedtke
Systemadministrator
Adresse: TUM - Garching Boltzmannstr. 3 85748 Garching b. Muenchen
Lehrstuhl: I20 - Frau Prof. Eckert
Zimmer: 01.08.036
Tel: ++49 (89) 289 - 18039
Fax: ++49 (89) 289 - 18579
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org
Hello,
I tried to install openSUSE 11.2 (milestone7) via autoyast for testing
purpose.
I am using the rules feature to create a profile dynamically.
I have no problems within former openSUSE releases. But in openSUSE 11.2
it fails.
'xsltproc' is missing here (for merging the profiles) !
Is this problem already known? autoyast is not working yet.
Is there a bugfix available or even a workaround to solve this problem?
This will be great.
At the moment I can not test autoinstallation in release 11.2.
Regards,
Werner Hack
--
I have an autoYast xml file with the following section as part of my
overall partition plan
<partition>
<create config:type="boolean">false</create>
<crypt_fs config:type="boolean">false</crypt_fs>
<filesystem config:type="symbol">ext3</filesystem>
<format config:type="boolean">true</format>
<loop_fs config:type="boolean">false</loop_fs>
<lv_name>lv51root</lv_name>
<mount>/</mount>
<mountby config:type="symbol">device</mountby>
<partition_id config:type="integer">131</partition_id>
<resize config:type="boolean">false</resize>
</partition>
The disk is formatted as part of the install but not with the ext3
filesystem as I defined in the above section, but rather with the
default filesystem for that particular openSUSE version. It gives
Reiserfs with 11.1 and Ext4 with 11.2. From several examples found on
the net I can not find what I'm doing wrong here.
Can someone please indicate what I'm doing wrong here since I do not
see any obvious errors in the logfiles as well.
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org
Hi all,
I'm adding two profiles in rules.xml. Both contain <patterns>,
<packages> and <remove-packages> entries.
When merging the two xml files manually according to Uwe Gansert's blog with
/usr/bin/xsltproc --novalid --param replace "'false'" \
--param dontmerge1 "'package'" \
--param with "'server.xml'" --output out.xml \
/usr/share/autoinstall/xslt/merge.xslt COMMON.xml
then out.xml contains all patterns and packages added from both profiles.
Everything is as expected.
Within autoinstallation only the <packages> and <remove-packages> are
merged in the right way. <patterns> merging fails. Patterns added from
the second profile are totally ignored.
I'm adding the second profile as:
<rule>
...
<result>
<profile>classes/software/server.xml</profile>
<continue config:type="boolean">true</continue>
<dont_merge config:type="list">
<element>package</element>
</dont_merge>
</result>
</rule>
as described in http://www.suse.de/~ug/autoyast_doc/merging.html
But the patterns are not merged. Only packages.
In y2log I see the same 'xsltproc' command as written above.
Am I doing something wrong? Why does it only work if processed manually?
Any ideas?
Regards,
Werner Hack
--
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org