is it possible to set the url of the installation source in the autoyast
I use kernel parameters like install=http://IP/sles9
autoyast=http://IP/sles9.xml for installation at the moment.
The only use of autoyast=http://IP/sles9.xml would be nice.
The automatic generation of the xml file didn't succeed. When I tried to
generate a reference profile and
activated the partitioning resource (I installed on LVM) no Partition
configs were actually written.
My solution was to copy the data from a former generated SuSE 9.3 xml
Additionally i couldn't find a possibility to set the root password in the
dialog. The username root is not permitted in the
"Security and users" -> "edit and create" tab. So I also took the values
from the 9.3 file, too.
I installed recent patches yesterday:
I've been autoinstalling for a long time, but haven't been using the
rules system. I would like to start, but am having trouble understanding
how you write a rules file which has multiple rules that will match and
return different class files, based on things like hardware specs and
hostid netmask, and merge to a profile at the end.
Can someone send me example rules file(s) which are at least somewhat
similar? I'm having a hard time finding example files online that do
similar to what I want. If I see enough example files I can figure it out.
Basically, I want to do things like these:
If hard drive is smaller than x,
result class DiskSize / IDE_Small.class
If hard drive is bigger than x,
result class DiskSize / IDE_Large.class
If hostid is C0A8000*
result class Roles / Server.class
If hostid is C0A8004*
result class Roles / Workstation.class
Is this possible, or do you have to write profiles which specify
classes, and use the <profile> tag in the result? I've read all of
nashif's autoinstall page for 9.1 page but I think I just need examples
of more scenarios.
Also, am I right in thinking that as of 9.2, you don't have to have
separate profiles for 32 and 64 bit machines? Playing around with it, it
seems to just figure it out on its own...
Thanks in advance,
When creating a autoinstall file with SAMBA on SUSE 9.3, I get this errors when saving:
Can't coerce array into hash at /usr/share/YaST2/modules/SambaServer.pm line
(F) You used an array where a hash was expected, but the array has no
information on how to map from keys to array indices. You can do that
only with arrays that have a hash reference at index 0.
Uncaught exception from user code:
Can't coerce array into hash at /usr/share/YaST2/modules/SambaServer.pm line 257.
at /usr/share/YaST2/modules/SambaServer.pm line 257
SambaServer::Import('SambaServer', 'HASH(0x9ff7074)') called at -e line 0
Can't undef active subroutine during global destruction.
Command: /sbin/yast2 autoyast &
Pseudo-hashes are deprecated at /usr/share/YaST2/modules//SambaServer.pm line
(D deprecated) Pseudo-hashes were deprecated in Perl 5.8.0 and they
will be removed in Perl 5.10.0, see perl58delta for more details.
You can continue to use the fields pragma.
The autoinst.xml file has everything ok, except for samba definition. It had though a "</samba-server>" line.
Had anyone seen this error?
André Assis Guimarães
Modelo Continente Hipermercados, S.A.
Direcção de Sistemas de Informação
Suporte Especializado - Sistemas Centrais
Ext: 14850 Tel: +351 220114850
we administer a number of SuSE Professional and SLES machines. To reduce
installation time we download updates for SuSE Professional nightly,
so we have all updates available locally.
With increasing numbers of SLES machines, we'd like to do the same -
right now our installation takes approx. 35 minuts while updating takes
Is it possible to download updates for SLES on a non-SLES machine (using
usernames and passwords)? If so, how?
how do you create or edit the [resolution].spl files in the boot/loader/ area
of the install CD? or otherwise go about making a custom bootsplash for an
autoinstall? have been looking at whatever information I can find regarding
gfxboot, syslinux/isolinux, and bootsplash but I am still having trouble
getting anything to work...any how-tos you guys can point to would be
great...or if you can nudge me in the right direction I don't mind putting a
how-to together when I am done
thanks for your time!
Hi, I have one doubt, yesterday I did instaled sles9 because i need to
use cd-creator, I try to find some tutorial abaut yast-cd-creator on
the net but i doesnt have sucess, somone knows haw a can make a iso cd
Sorry my bad english, I am brasilian.
I am trying to install suse 9.2 on a pentium 4 with Microstar board. As
soon as i put the CD or DVD, and choose install/manual
installation/safe installation it hangs and show the following message:
Code: 81 fe 00 ff 75 05 8a c1 ee eb 11 66 81 fe 01 ff 75 07 66 8b c1 66
ef eb 03
8b c1 ef 66 9d 66 5a 58 f8 c3 c3 c3 66 50 66 53 b7 00 <2e> 8a 83 96 04
5b 8a d8 66 58 c3 00 01 02 03 04 05 06
<0>Kernel panic -not syncing:Attemted to kill init!
I've tried 9,3 and the same output, the suse 9.1 boots the installer ok
and install a base systems, but when it boots again the same thing.
The behavior is very similar to that posted in this list:
The bios is most likely updated, passing mem=2048M does not work. The
solution suggested about switching off the USB controller is not
Thanks for the help
I'm new to the autoyast deployment system and have to script the
install of a bunch of servers. It has been going pretty well but I'm
got a small issue that I don't understand.
I would like that autoyast sets the keyboard layout to the belgian
format. To configure this I've used the yast autoinstallation module
to create a template at it gives me this in the actual xml file :
But when I actually use this in my deployment the keyboard remains the
US. I've also checked the /etc/sysconfig/keyboard file on the deployed
system and that also has the Us keyboard configured.
So it this a bug in autoyast ? (I'm using SLES 9 SP2) Or am I using
the wrong keymap identifier for the belgian layout ?
Anyone having the opportunity to test this and let me know if you see
this or not ?
Tim Verhoeven - dj(a)rootshell.be - 0479 / 88 11 83
/* This is total bullshit: */