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!
Hi,
I configured 2 NICs on my system with 2 static IP in 2 different subnets. Then
I used Autoinstallation to save the XML control file.
<interfaces config:type="list">
<interface>
<bootproto>static</bootproto>
<device>eth0</device>
<ipaddr>172.24.255.11</ipaddr>
<name>CK804 Ethernet Controller</name>
<netmask>255.255.0.0</netmask>
<startmode>auto</startmode>
<usercontrol>no</usercontrol>
</interface>
<interface>
<bootproto>static</bootproto>
<device>eth1</device>
<ipaddr>172.19.1.1</ipaddr>
<name>82541PI Gigabit Ethernet Controller</name>
<netmask>255.255.0.0</netmask>
<startmode>auto</startmode>
<usercontrol>no</usercontrol>
</interface>
</interfaces>
After many installations with AutoYast, most of the time the system would
detect CK804 NIC (MAC address) as eth0 and 82541PI (MAC address) as eth1.
However, it is not true all the time. So there would be the case that the
eth0 with name of CK804 is set to the MAC address of 82541PI NIC and eth1
with name of 82541PI is set to the MAC address of CK804. (CK804 is an
integrated NIC and 82541PI is a PCI NIC card).
Is there a way to make sure the network settings would be the same after every
installation using AutoYast?? (I would like to have one NIC with specific IP
setting and the other one has another specific IP setting all the time)?
If I use the XML control file to autoinstall on another system with different
2 NICs (not CK804 and 8254 PI anymore), what will happen?
By the way, the Linuxrc would always see the CK804 NIC as eth1 and 82541PI as
eth0 (at least so far).
Is it possible you could kindly point me to some directions so that I could
solve those problems. I am not sure how the NICs are detected as eth0, eth1,
etc. Why the Linuxrc always detects CK804 as eth1 but most of the time the
AutoYast would detect CK804 as eth0?
Thank you so much for your time and I look forward to hearing from you.
Sincerely,
Alan
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org
Hello,
I'm trying to use AutoYaST to install SLES10SP1. I need to make use of
chroot scripts, but found an issue with it;
This is a snippet from my AutoYaST script;
<scripts>
<chroot-scripts config:type="list">
<script>
<chrooted config:type="boolean">false</chrooted>
<location>file:///mounts/extra/chroot-1.sh</location>
</script>
<script>
<chrooted config:type="boolean">true</chrooted>
<location>file:///mounts/extra/chroot-2.sh</location>
</script>
</chroot-scripts>
</scripts>
In the example above, the chrooted=false script runs just fine, but the
chrooted=true does not. It looks like it is still trying to run it
from /mnt/var/... instead of /var/...
/mnt/var/... does not exist since we've done a chroot into / at this
stage.
This is a snippet from y2log for the chroot-2.sh script;
2008-08-19 06:13:31 <1> linux(3086) [Interpreter]
clients/autoinst_scripts2_finish.ycp:57 Calling YaST client
autoinst_scripts2_finish (arguments: ["Write"])
2008-08-19 06:13:31 <1> linux(3086) [YCP]
clients/autoinst_scripts2_finish.ycp:33 starting
autoinst_scripts2_finish
2008-08-19 06:13:31 <1> linux(3086) [YCP] AutoinstScripts.ycp:484
Writing chroot script
into /mnt/var/adm/autoinstall/scripts/chroot-scripts
2008-08-19 06:13:31 <1> linux(3086) [agent-system]
SystemAgent.cc(Execute):1098 mkdir /tmp/YaST2-03086-eyCR4s/tmp_mount
2008-08-19 06:13:31 <1> linux(3086) [YCP] autoinstall/io.ycp:119 Copy
profile:
cp /mounts/extra/config/etc/config-builder/chroot-2.sh /mnt/var/adm/autoinstall/scripts/chroot-scripts
2008-08-19 06:14:12 <1> linux(3086) [YCP] AutoinstScripts.ycp:548 Script
Execution command: /bin/sh
-x /mnt/var/adm/autoinstall/scripts/chroot-scripts
2&> /mnt/var/adm/autoinstall/logs/chroot-scripts.log
2008-08-19 06:14:12 <1> linux(3086) [YCP]
clients/autoinst_scripts2_finish.ycp:57 autoinst_scripts2_finish
finished
2008-08-19 06:14:12 <1> linux(3086) [Interpreter]
clients/autoinst_scripts2_finish.ycp:57 Called YaST client returned: nil
Any ideas on what's happening here?
Thanks,
Magnus
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org
Hi,
I get errors, when including xml files in autoyast profile. xmllint --xinclude
opensuse110-4-xincludes.xml > ausgabe.xml doesn't complain.
Autoyast doesn' t find the xml file, because it isn't in the mounted tmp
directory.
I tried several includes like:
<xi:include href="nfs://x.x.x.x/installation/classes/include/include.xml"/>
<xi:include href="http://x.x.x.x/installation/classes/include/include.xml"/>
and just file <xi:include href="classes/include/include.xml"/>
Nothing works. Any hints ?
Georg
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org
Hello,
i wan't use classes in my profile.xml, for installing additional
software and some scripts, depending on departments. But the autoyast
doesn't fetch the additional software and scripts. Where is my fault?
I have the following structur:
myStart.xml
<?xml version="1.0"?>
<!DOCTYPE profile>
<profile xmlns="http://www.suse.com/1.0/yast2ns"
xmlns:config="http://www.suse.com/1.0/configns">
<classes config:type="list">
<class>
<class_name>additionalsoftware</class_name>
<configuration>software.xml</configuration>
</class>
</classes>
<software>
<packages config:type="list">
<package>all packages</package>
<patterns config:type="list">
<pattern>all patterns</pattern>
</software>
<scripts>
<init-scripts config:type="list" >
<script>
<interpreter>shell</interpreter>
<location>nfs://192.168.0.2/installation/autoinstall/w-scripts/init_install_db2.sh</location>
<filename>init_install_db2.sh</filename>
</script>
</init-scripts>
</scripts>
</profile>
In the folder classes/additonalsotware i have the software.xml
<?xml version="1.0"?>
<!DOCTYPE profile>
<profile xmlns="http://www.suse.com/1.0/yast2ns"
xmlns:config="http://www.suse.com/1.0/configns">
<software>
<post-packages config:type="list">
<package>psw_basis</package>
<package>psw_ab1000</package>
<package>psw_fb1000</package>
<package>psw_winbasis</package>
<package>psw_winab1000</package>
<package>psw_winfb1000</package>
</post-packages>
</software>
<scripts>
<chroot-scripts config:type="list">
<script>
<chrooted config:type="boolean">true</chrooted>
<interpreter>shell</interpreter>
<filename>init-parity.sh</filename>
<source>
<![CDATA[
!#/bin/sh
mkdir /home/abfb
ln -sf /home/abfb /usr/parity
]]>
</source>
</script>
</chroot-scripts>
</scripts>
</profile>
Georg
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org
Is there a way to select the default screensaver with autoyast? By default
we'd like it to be set to blank instead of random.
Thanks for your input.
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org
Hello,
i did following in
file /installation/repository/OpenSuSE110/distribution/11.0/repo/oss/control.xml
Around line 1059 there is a line like this:
<name>rpmcopy_secondstage</name>
change that line to
<name>rpmcopy</name>
no i get the error
sorry, repository failed checksum test.
What have i to do ?
Greetings
Georg
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org
Kind of a silly question, but is there documentation anywhere that lists
all of the valid values I can specify in <pattern> and <package>
elements in the <software> section of the AutoYaST profile?
Thanks,
Michael
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org
Hallo,
i get the following error again and again. I want add certain rpm
Pakets to an add_on folder and the autoinstaller complains about
Invalid URL. I could create the add_on part with the autoyast wizard.
The error:
Yast2 Fehler: Zusatzprodukt konnte nich hinzugefügt werden
less /var/log/Yast2/y2log
[..]Source_Create.cc(SourceCreateEx):593 Invalid URL: Das URL-Schema
ist eine erforderliche Komponente [...]
/etc/exports:
/installation/repository *(rw,no_root_squash,sync,no_subtree_check)
/installation/autoinstall *(ro,no_root_squash,sync,no_subtree_check)
/installation/repository/OpenSuSE110/CD1
*(rw,no_root_squash,sync,no_subtree_check)
/installation/repository/OpenSuSE110/CD1/updates
*(rw,no_root_squash,sync,no_subtree_check)
/installation/repository/OpenSuSE110/distribution/11.0/repo/non-oss
*(rw,no_root_squash,sync,no_subtree_check)
/installation/repository/OpenSuSE110/distribution/11.0/repo/oss
*(rw,no_root_squash,sync,no_subtree_check)
/installation/repository/OpenSuSE110/update/11.0
*(rw,no_root_squash,sync,no_subtree_check)
The Folder /installation/repository/OpenSuSE110/CD1/updates was
created like on the homepage http://www.suse.com/~ug/
create_update_source.sh /installation/repository/OpenSuSE110/CD1
cd /installation/repository/OpenSuSE110/CD1
cp -a
/installation/packages/vmware-server-1.06/VMware-server-1.0.6-91891.i386.rpm
updates/suse/i386
cd updates/suse
create_package_descr -x setup/descr/EXTRA_PROV
cd setup/descr
ls > directory.yast
# the following two steps are required since openSUSE 11.0
cd ../../..
create_sha1sums -x -n ./
The /installation/repository/OpenSuSE110/CD1/updates/content file
looks like this:
PRODUCT openSUSE Updates
VERSION 11.0
DISTPRODUCT SuSE-Linux-Updates
TYPE base
VENDOR SUSE LINUX Products GmbH, Nuernberg, Germany
RELNOTESURL
http://www.suse.com/relnotes/i386/openSUSE/11.0/release-notes-openSUSE.rpm
ARCH.x86_64 x86_64 i686 i586 i486 i386 noarch
ARCH.i686 i686 i586 i486 i386 noarch
ARCH.i586 i586 i486 i386 noarch
ARCH.i486 i486 i386 noarch
ARCH.i386 i386 noarch
DEFAULTBASE i586
REQUIRES openSUSE-release = 11.0 pattern:basesystem
PROVIDES product:openSUSE = 11.0
OBSOLETES product:SUSE_LINUX product:openSUSE < 11.0 package:openSUSE < 11.0
LINGUAS cs da de en en_GB en_US es fi fr hu it ja nb nl pl pt pt_BR ru
sv zh zh_CN zh_TW
SHORTLABEL oS 11.0
LABEL openSUSE 11.0
LABEL.de openSUSE 11.0
DESCRDIR suse/setup/descr
DATADIR suse
FLAGS update
LANGUAGE en_US
Following the autoyast.xml part
<add-on>
<add_on_products config:type="list" >
<signature-handling >
<accept_file_without_checksum config:type="boolean"
>true</accept_file_without_checksum>
<accept_non_trusted_gpg_key config:type="boolean"
>true</accept_non_trusted_gpg_key>
<accept_unknown_gpg_key config:type="boolean"
>true</accept_unknown_gpg_key>
<accept_unsigned_file config:type="boolean" >true</accept_unsigned_file>
<accept_verification_failed config:type="boolean"
>true</accept_verification_failed>
<import_gpg_key config:type="boolean" >true</import_gpg_key>
</signature-handling>
<listentry >
<media_url>nfs://192.168.0.2/installation/repository/OpenSuSE110/CD1/updates</media_url>
<product>SuSE-Linux-Updates</product>
<product_dir>/</product_dir>
</listentry>
</add_on_products>
</add-on>
<software >
<packages config:type="list" >
<package >autoyast2-installation</package>
<package >autoyast2</package>
<package >VMware-server</package>
</packages>
<patterns config:type="list" >
<pattern >base</pattern>
<pattern >enhanced_base</pattern>
<pattern >enhanced_base_opt</pattern>
<pattern >fonts</pattern>
<pattern >fonts_opt</pattern>
<pattern >sw_management</pattern>
<pattern >x11</pattern>
<pattern >x11_opt</pattern>
<pattern >x11_yast</pattern>
<pattern >xfce</pattern>
<pattern >yast2_basis</pattern>
<pattern >yast2_install_wf</pattern>
</patterns>
</software>
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org