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
Hi,
openSUSE beta1 has a broken initrd. A signing key is missing.
I have uploaded fixed initrd files for openSUSE beta1 for i586 and x86_64 to:
http://www.suse.de/~ug/download
Thanx for testing AutoYaST on openSUSE.
--
ciao, Uwe Gansert
Uwe Gansert, Server Technologies Team
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
Business: http://www.suse.de/~ug
listening to: "Freiheit" by Unheilig
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org
Hi Uwe,
I didn't know to store the id in xml file.
The keys where used to sign individual packages.
And also content.asc of CD1 and so on.
As I learned I have to put the public keys into initial initrd which
is used during boot to prevent installer error messages about unknown
signed packages.
The idea is to retrieve the public key which signed our addon product
from somewhere (web) during pre installation and present it somehow the installer. Such I don't have
to put it into the initrd.
Will this work or did I miss something.
Thanks,
Jochen
>>> Uwe Gansert <ug(a)suse.de> 09/18/08 2:48 PM >>>
On Friday 12 September 2008, Jochen Schaefer wrote:
> But the question is if it is possible to retrieve and use gpg-keys to
> validate self signed installation sources
> from a web source during the preinstallation phase?
I'm not sure if I understand. The keys are already on the installation
source? What exactly do you want to achieve?
> Since it is a little overhead to change the initrds of different SUSE
> Versions in different projects.
you don't have to put them in the initrd. You can specify the key id's in
the XML file too. You just have to store them in the initrd if you don't
want to put anything in your XML.
--
ciao, Uwe Gansert
Uwe Gansert, Server Technologies Team
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
Business: http://www.suse.de/~ug
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org
Hi Frank,
>> I cannot believe it ... these daemons crash at boot as soon as I have
>> activated LDAP on the system. Has nothing to do with Autoyast setup or
>> manual setup. What have these daemons to do with LDAP? I'm going to
>> file a bug report ...
>
> Just a guess: Do you have apparmor running? With SuSE 10.1/SLES10,
> sendmail used to crashed after default installation when apparmor was
> running.
>
>
Nope. Neither installed nor started at boot time:
adnws005:~ # rpm -qa |grep app
libapparmor1-2.3-16.1
device-mapper-1.02.24-27.1
fast-user-switch-applet-2.22.0-42.1
gnome-applets-2.22.1-29.1
fast-user-switch-applet-lang-2.22.0-42.1
deskbar-applet-2.22.1-27.1
libapparmor-devel-2.3-16.1
adnws005:~ # chkconfig --list |grep app
I can reproduce crashing/noncrashing dbus-daemon at startup by editing
/etc/nsswitch.conf and enabling/disabling ldap for passwd and group:
# dbus-daemon starts at boot
passwd: files
group: files
# dbus-daemon segfault at boot
passwd: files ldap
group: files ldap
# dbus-daemon segfault at boot
passwd: compat
group: compat
passwd_compat: ldap
group_compat: ldap
adnws005:~ # ps -ef |grep dbus
100 1521 1 0 12:18 ? 00:00:00 /bin/dbus-daemon --system
root 2939 2900 0 12:19 pts/0 00:00:00 grep dbus
UID appears with 100 although messagebus is defined in /etc/passwd and
/etc/group.
Bye
Bernd
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org
Hi,
I've created an autoyast profile to install an OES2 server into our
existing eDirectory tree that works fine.
However, when performing a manual server install we occasionally
experience problems during the eDirectory section whereby an LDAP error
message is displayed, followed by the choice of F1 to re-enter the
eDirectory details, F2 to retry or Abort to call it a day.
This error now also occasionally appears when using Autoyast, but
whereas during a manual install it's possible to get around this by
doing some stuff from the console and then hitting F2, when using
Autoyast the F1/F2 keys don't seem to be responded to correctly (F1 the
install just continues regardless, F2 doesn't appear to retry), so it's
impossible to complete the install successfully.
The error that we get during the eDirectory install is not going to be
easily resolved, so I was therefore wondering if there was anything that
could be done to make Autoyast either respond correctly to the F1/F2
keys, or to stop the automatic nature of the install, so that the
eDirectory problems can be resolved and the installation completed
manually?
Many thanks for any assistance you can provide.
David Froggatt
IMPORTANT NOTICE: This message is intended for the addressee only. The content
may be confidential, legally privileged and protected by law. Unauthorised
use, copying or disclosure of any of it may be unlawful. If you are not the
intended recipient please notify the sender and remove it from your system.
Internet emails are not necessarily secure. Although we have taken steps to
ensure this email and attachments are free from any virus, we advise that in
keeping with good computing practice you should ensure they are actually virus
free. The right to monitor email communications through our network is
reserved by us.
Sopra Group Limited (Registered in England, No. 1588948) with Registered
Offices at: Middlesex House, Meadway Technology Park, Rutherford Close,
Stevenage, Hertfordshire, SG1 2EF. VAT No. 366 9784 84.
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org
Hi list,
we use some self signed packages in our autoyast environment.
Uwe describes in it's docu how to insert them into initrd of the boot media.
That works very well.
But the question is if it is possible to retrieve and use gpg-keys to
validate self signed installation sources
from a web source during the preinstallation phase?
And when they are retrieved to the local device where should they be
located?
Since it is a little overhead to change the initrds of different SUSE Versions in different
projects.
Thanks,
Jochen
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org
Hi,
I'm trying to deploy Opensuse 11.0 on our ca 200 company workstations
which runs on Dell Precision hardware. Currently we have Opensuse 10.1.
I know how Autoyast works and use it since Suse 9.0. Basically we use
Autoyast for the hardware autoconfiguration and package selection and do
network setup and customization in later init scripts.
There are some differences how the system gets configured when I install
Opensuse 11.0 manually from DVD and with Autoyast from NFS server.
Problems when configured with Autoyast on Dell Precision 670 (both 32bit
and 64bit OS installation):
- Automounter core files at every boot
- Boot process freezes when entering runlevel 5 during autoyast
installation - even with acpi=off as boot parameter. Disabling
acpid in runlevel 5 helped a bit.
- Messagebus Daemon crashes on startup (req. for USB mounts)
Starting D-Bus daemon/etc/init.d/dbus: line 45: 1401 segmentation
fault $DBUS_DAEMON_BIN $DBUS_DAEMON_PARAMETER
- Powerd crashes at startup
- Smard crashes at startup
exit status of parent of /usr/sbin/smardtd: 17
- VMware Workstation 6.0.5 modules compile but vmware hangs forever
on GUI startup (strace ends at FUTEX_WAIT_PRIVATE)
All this does not happen, when I perform a manual installation. I have
no idea what's going wrong. Similar issues we have with Opensuse 10.1.
Except for automounter they don't produce a core file. Is there a
pendant for Solaris coreadm on Linux?
Does someone use Autoyast for installing Opensuse 11.0 on Dell hardware
(Precision 650, 670, 490, T5400)?
Why doesn't use Autoyast and manual Yast the same code base and
algorithm for configuring hardware and software?
Bye
Bernd
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org
On Thu, 11 Sep 2008, Uwe Gansert wrote:
> On Wednesday 10 September 2008, Andreas Vetter wrote:
>
> > is it possible to use images (as opposed to installing every rpm) in a
> > 11.0 autoyast installation? Is there something I have to write into my
> > autoyast.xml file?
>
> what kind of images do you mean? The pre defined ones that were invented in
> openSUSE 11.0 or self created generic images?
My intention was to use the SUSE provided ones.
> The SUSE provided images can be used by autoyast with openSUSE 11.1 / SLES11
> but not with openSUSE 11.0
> Documentation will come soon with the next alpha of openSUSE were that
> feature will be activated.
I see. By the way, when is SLES11 expected?
> About generic images, since openSUSE 10.2 there is an experimental feature
> for generic images:
> http://www.suse.de/~ug/autoyast_changes_10_1-10_2.html
> but it's not tested very well ... that's why I call it experimental and not
> really officially supported. If you want to test that, I would really
> appreciate feedback.
So I'll try that for 11.0
--
Thanks a lot,
Andreas Vetter
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org