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
* 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
"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
I dont have kinternet installed.
This is what doesnt seem to work:
In y2log it mentions that those packages should be removed, but it goes ahead and installs them anyway. I can do it manually on the command line:
# rpm -e pptp smpppd ppp wvdial mutt
and that works fine so I know I have no dependency problems.
> -----Original Message-----
> From: Uwe Gansert [mailto:firstname.lastname@example.org]
> Sent: Friday, 30 June 2006 12:50 AM
> To: suse-autoinstall(a)suse.com
> Subject: Re: [suse-autoinstall] SLES 10 RC2 remove-packages section?
> On Thursday 29 June 2006 16:45, Manfred Hollstein wrote:
> > If that fails, you have kinternet installed; add that to
> the list and it
> > should work.
> good point.
> <remove-packages> can not break dependencies and so it's very
> likely that
> there is still a package that needs those packages.
> I did a very small installation with no X - so it worked for me.
> ciao, Uwe Gansert
> Uwe Gansert, Server Technologies Team
> SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nuernberg, Germany
> Fax: +49-(0)911-74053-476, Web: http://www.suse.de/~ug
> now playing Covenant - Wasteland
> To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com
> For additional commands, e-mail: suse-autoinstall-help(a)suse.com
This email and any attachments may contain privileged and confidential information and are intended for the named addressee only. If you have received this e-mail in error, please notify the sender and delete this e-mail immediately. Any confidentiality, privilege or copyright is not waived or lost because this e-mail has been sent to you in error. It is your responsibility to check this e-mail and any attachments for viruses. No warranty is made that this material is free from computer virus or any other defect or error. Any loss/damage incurred by using this material is not the sender's responsibility. The sender's entire liability will be limited to resupplying the material.
Does anyone know if it is possible to use the 'dirinstall' from the command
For instance i would like to be able to do something like:
# yast dirinstall -d /someroot -s mypackages.sel
If i do yast -h it says:
"Usage: /sbin/yast [OPTIONS] [MODULE] [module specific parameters]"
But is there a way to find out what 'module specific parameters' are available
for a specific module?
is it possible to use a locally attached raid storage as installation
source for autoyast?
I.e., boot our NFS server (that usually serves the autoyast install
repository via NFS to the clients) from a second dhcp/tftp server,
but then let it mount it's raid locally and install from there.
So sth. like "install=local://..." or whatever. Assuming the neccessary
modules are preloaded.
Is that possible?
Dipl.-Inform. Frank Steiner Web: http://www.bio.ifi.lmu.de/~steiner/
Lehrstuhl f. Bioinformatik Mail: http://www.bio.ifi.lmu.de/~steiner/m/
LMU, Amalienstr. 17 Phone: +49 89 2180-4049
80333 Muenchen, Germany Fax: +49 89 2180-99-4049
* Rekursion kann man erst verstehen, wenn man Rekursion verstanden hat. *
I am experiencing problems while the installation of SLES 9 with the
A HTTP Repository holds the complete installation media and the autoyast
xml control files. Booting the machine which is about to be installed
works as far as it concerns reading the control file, partitioning the
harddisk and starting the installation.
The partition table looks as the following:
LVM containing /
The installation stops with this error message:
ERROR(Media:Unknown error in
If I do not use LVM the installation proceeds smoothly.
Any help is appreciated!
it's me again.
I have the following line in my autoinst.xml
But in /etc/inittab I find the following line
ca::ctrlaltdel:/sbin/shutdown -r -t 4 now
With SLES9 this was no problem. Any idea what's wrong ?
could somebody help out with the attached xml-snippet please?
I can't find the error in the partitioning section.
Any help is greatly appreciated.
Address: Duesseldorf , 40470, Germany Noerdlicher Zubringer 9-11
is it possible to setup lvm on top of raid via autoyast?
Can someone provide an example please?
Address: Duesseldorf , 40470, Germany Noerdlicher Zubringer 9-11
I still having problem using autoinstall on SuSE 10 PPC on IBM LPAR. I have tftpboot set up pointing to inst64 image and parameters passed:
mkzimage_cmdline -a 1 -c -s "insmod=ibmveth hostip=10.1.245.201 netmask=255.255.0.0 install=nfs://10.1.5.130/images/SUSE10PPC autoyast=nfs://10.1.5.130/images/SUSE10PPC/autoinst.xml" inst64
I use a very simple profile file (I've tried a few combinations):
<!DOCTYPE profile SYSTEM "/usr/share/autoinstall/dtd/profile.dtd">
<profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns">
The partition boots, and I can see in the logs that the NFS partition gets mounted and the a get the error below. Search on Google for the error didn't shed any light on the source of the problem.
[boot]0100 MM Init
[boot]0100 MM Init Done
Linux version 22.214.171.124-0.8-ppc64 (geeko@buildhost) (gcc version 4.1.0 (SUSE Linux)) #1 SMP Mon Jul 3 18:25:39 UTC 2006
[boot]0012 Setup Arch
Node 0 Memory:
Node 1 Memory:
Node 2 Memory: 0x0-0x28000000
Node 3 Memory: 0x28000000-0x40000000
EEH: PCI Enhanced I/O Error Handling Enabled
PPC64 nvram contains 7168 bytes
Using shared processor idle loop
[boot]0015 Setup Done
Built 4 zonelists
Kernel command line: insmod=ibmveth hostip=10.1.245.201 netmask=255.255.0.0 install=nfs://10.1.5.130/images/SUSE10PPC autoyast=nfs://10.1.5.130/images/SUSE10PPC/autoinst.xml
[boot]0020 XICS Init
xics: no ISA interrupt controller
[boot]0021 XICS Done
PID hash table entries: 4096 (order: 12, 131072 bytes)
time_init: decrementer frequency = 238.055000 MHz
Found a kterm terminal on /dev/console (80 columns x 24 lines).
*** Starting YaST2 ***
/usr/lib/YaST2/startup/YaST2.call: line 306: 2938 Aborted (core dumped) $OPT_FBITERM y2base "$Y2_MODULE_NAME" $Y2_MODE_FLAGS $Y2_MODULE_ARGS $Y2_MODE $Y2_UI_ARGS
*** An error occurred during the installation.
Thanks in advance,