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
Dear all,
I am trying to solve a strange networking problem with PXE boot and
SUSE.
Here follows a description with the strange ARP broadcast noted at the end:
1) PXE boot the 10.205.8.253 (new server to install)
2) DHCPOFFER to 10.205.8.253 and this then sends a DHCPACK.
3) 10.205.8.253 then TFTP downloads the linux and initrd and executes
it successfully.
4) Afterwards 10.205.8.253 looses all the network information.
5) The final messages (Xensourc) shown in Ethereal are ARP requests
that come from 10.205.8.253. This is the autoyast server ARPing for the
MAC of 10.205.8.253 because it has disappeared from the network.
No. Time Source
Destination Protocol Info
15120 22.480085 Xensourc_33:3f:cc d8:d3:85:5a:00:b0 ARP
Who has 10.205.8.253? Tell 10.205.8.145
At this point the PXE booted system 10.205.8.253 then reverts to the
screen for starting a manual set-up programme.
"Could not find ... the Installation Source. Activating manual setup
program." When I use this to display the network interfaces then it
only displays the loopback.
This problem is not specific to one server. It happens on all servers.
The servers consist of existing HP c-class blades, and some newer G6
blades. I tried a CD installation on the former blades and this works,
but Suse does not see the NIC on the newer G6 blades. I do know that
the firmware for the OA on the HP c7000 was upgraded this week, it all
worked last week, but this is process of elimination because, as ever,
one has to prove to others that this is or is not a cause because
otherwise the firmware won't be rolled back.
Does anyone know where I would start? Perhaps, I could load modules
during the PXE boot for the server NIC? Unsure how or whether this is
the right path to start down.
Yours sincerely, s.
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org
Dear folks,
Is there a programme I can run that will verify that the packages in
a customised autoinst.xml file are correct and won't fail the package
resolver?
Best wishes, S.
--
Simon Loewenthal/Tele2
GSM: +31 6 2000 5427
******** IMPORTANT NOTICE ********
Please repect the X-Reply to klunky.co.uk. PGP available 0xD86A5A17.
S/MIME PKCS12 key available for Lotus Notes: Please ask me for it.
This e-mail (including any attachments) may contain information that is confidential or otherwise protected from disclosure and it is intended only for the addressees. If you are not the intended recipient, please note that any copying, distribution or other use of information contained in this e-mail (and its attachments) is not allowed. If you have received this e-mail in error, kindly notify us immediately by telephone or e-mail and delete the message (including any attachments) from your system.
Please note that e-mail messages may contain computer viruses or other defects, may not be accurately replicated on other systems, or may be subject of unauthorized interception or other interference without the knowledge of sender or recipient. Tele2 only send and receive e-mails on the basis that Tele2 is not responsible for any such computer viruses, corruption or other interference or any consequences thereof. It ought to be obvious that my views do not represent my employer's views.
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org
There are usually two NICs on each server, but only one NIC [eth0] is
required when jumpstarting it from autoyast.
If I remove the entry, and there are two NICs, will it default to the
first NIC it finds, which hopefully with be eth0.
S
Uwe Gansert wrote:
> on Monday 25 January 2010 Simon Loewenthal/NL/Tele2 wrote:
>
>
>> <net-udev config:type="list">
>> <rule>
>> <name>eth0</name>
>> <rule>ATTR{address}</rule>
>> <value>00:1c:c4:a8:27:42</value>
>> </rule>
>> </net-udev>
>>
>> i) Can I remove the lines referencing n-etudev and let autoyast use the
>> first interface it happens upon or,
>>
>
> if you only have one interface, then you can remove the complete net-udev part
> from the profile.
>
>
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org
Dear all,
The autoinst.xml has this line in it and this is normal.
<net-udev config:type="list">
<rule>
<name>eth0</name>
<rule>ATTR{address}</rule>
<value>00:1c:c4:a8:27:42</value>
</rule>
</net-udev>
This profile is being modified so that it can be used as a genericone
for many systems, but all systems have different MAC addresses, so the
line would not be useful in a generic profile.
i) Can I remove the lines referencing n-etudev and let autoyast use the
first interface it happens upon or,
ii) have the newly build machine automatically add the MAC address with
a line similar to:
<value>auto</value> ?
I have searched a little this morning and could not come up with a lot
of ideas.
Yours faithfully, SL
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org