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
Good morning,
we are using PXE to boot into autoyast and install the packages from local
repositories via http and are having a problem since Suse released a new kernel
package in April.
Everything works fine up to the first reboot after finishing stage 1. Then grub
has two kernels to choose from: 2.6.31.12-0.1-default, which is the kernel of
the autoyast installation, and 2.6.31.12-0.2-desktop, which is the newest kernel
freshly installed from our repositories.
Grub boots the 2.6.31.12-0.1-default-kernel, complains (with good cause) 'unable
to canonicalize path
"/lib/modules/2.6.31.12-0.1-default/systemtap/preloadtrace.ko": No such file or
directory' and continues booting, but fails to load the modules for the network
card and the graphics card (and probably others). This leads to X not starting
and -worse- autoyast failing to load some configuration files via ftp,
configured like this:
<file>
<file_path>/etc/somefile</file_path>
<file_owner>root:root</file_owner>
<file_permissions>644</file_permissions>
<file_location>ftp://somehost/files/etc/somefile</file_location>
</file>
Autoyast does not complain very visibly about this failure while it's running.
The files not loaded do exist on the system afterwards, alas with a size of 0
bytes. The normal system logs do not contain that first boot, so it is kinda
hard to figure out exactly why the final system does not work like it should.
If I babysit the installation and manually choose the other kernel version
(2.6.31.12-0.2-desktop) when grub comes up after stage 1, everything continues
like it should, but I don't really want to wait to hit "down down return" at the
exact right time...
So: Why is the installation kernel still configured in grub when it is not fully
functional anymore? How do I get rid of it at this early time? Or is our error
something else entirely?
Thanks in advance,
Antje
--
Antje Bendrich (Team IT-Services), Phone +49 40 808077-642
DFN-CERT Services GmbH, https://www.dfn-cert.de/, Phone +49 40 808077-555
Sitz / Register: Hamburg, AG Hamburg, HRB 88805, Ust-IdNr.: DE 232129737
Sachsenstraße 5, 20097 Hamburg/Germany, CEO: Dr. Klaus-Peter Kossakowski
Greetings,
I'm trying to get SLED-11-SP1 installing via autoyast, but the install
(for both i686 & x86_64) fails as soon as it reaches the 'Create
partition plans' step with a pop-up error stating:
These packages could not be found in the software repositories:
autoyast2-installation
I'm rather puzzled by this, as I've got that very RPM on my
installation server under $OS/suse/noarch
Anyone have any suggestions?
thanks
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
L. Friedman netllama(a)gmail.com
LlamaLand https://netllama.linux-sxs.org
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org
Hi,
I am using autoyast to install both SLES11 and openSUSE 11.2 hosts. I
want all host to use FQDN for hostname, but for unknown reasons, some
of them do, and some others only have a short name without domain
part. The autoyast.xml file is auto generated for each node, and only
FQDN are referenced in there.
I have following sections in autoyast.xml (real host name replaced,
to protect innocent):
<host>
<hosts config:type="list">
<hosts_entry>
<host_address>127.0.0.1</host_address>
<names config:type="list">
<name>localhost </name>
</names>
</hosts_entry>
<hosts_entry>
<host_address>10.1.68.86</host_address>
<names config:type="list">
<name>myhostname,example.com</name>
</names>
</hosts_entry>
</hosts>
</host>
and
<dns>
<domain>example.com</domain>
<hostname>myhostname.example.com</hostname>
<nameservers config:type="list">
...
</nameservers>
<searchlist config:type="list">
...
</searchlist>
</dns>
I also have following line in /etc/sysctl.conf:
kernel.hostname = myhostname.example.com
Even after reboot, above sysctl.conf entry doesn't seem to do
anything, or some scripts has changed hostname after
/etc/init.d/boot.d/S13boot.sysctl script.
So my question is how should I set hostname during initial set up ?
Thanks,
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org
I'm trying to use the CheckMedia functions from within my customized
YaST module. It appears to be working fine, as I can detect
drives/start/stop/fetch progress. However, the customized media I
created fails verification. The read test finishes ok, but I get an
"md5sum not computed" error.
My question is, where is the media descriptor/MD5 stored on the media?
How do I generate it? It seems to ignore the "content" files with SHA1
checksums.
--
-- Erico
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org
Hallo,
I using autoyast only once per year.
My problems:
1)
I made a xml-file basing on a working system.
Now the network-card-detection doesn t work. In my cloned system 2 cards
are detected. The old one and the new one without any configuration.
2)
The kde-configuration:
What ist the option to configure a german keyboard-layout.
Thanks
Ralf Prengel
Manager
Customer Care
Comline AG
Hauert 8
D-44227 Dortmund/Germany
Fon +49 231 97575 904
Fax +49 231 97575 257
Mobil +49 151 10831 157
EMail Ralf.Prengel(a)comline.de
www.comline.de
Vorstand Stephan Schilling, Erwin Leonhardi
Aufsichtsrat Dr. Franz Schoser (Vorsitzender) HR Dortmund B 14570 USt.-ID-Nr. DE 124727422
Für die Erstellung unserer Dokumente benutzen wir die Produkte aus dem Microsoft Office 2007 Paket.
Sollte sich ein Anhang in der Mail befinden, der mit einer älteren Office Version nicht geöffnet werden kann,
installieren Sie bitte das Compatibility Pack für Office 2007.
http://www.microsoft.com/downloads/details.aspx?FamilyID=941b3470-3ae9-4aee…
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org