Andreas Girardet schrieb:
I changed the subject since it was OT
yea, I've read that before in the thread. but never done it before.
and
the stuff around "autoyast.xml" I didn't understand exactly. has that to do
with the
tool "automatic install" ( or "Automatische Installation" in german; don't know the exact name in the english version) in YAST ? is there something
in
the documentation where u can point me to (I've got the boxed pro-
version
with the books of 9.3 if its in there .... ).
http://forgeftp.novell.com/yast/doc/SLES9/autoinstall/index.html
There is a GUI tool in yast alled autoyast2-installation, that creates a core file you can then adapt following the above howto. Please install that rpm first and then go into yast --> misc autoinstallation, download my sample autoyast file from
ftp://opensuse.linux.co.nz/pub/SUPER/files/autoyast.xml
and load it in the autoyast installation tool. You could in theory just use that file, but then you can't log in. As a minimum without the gui tool you need to change ENCRYPTEDPASSWORD to for example
txzvp3z2ZKYrc
which equates to sles9 as password. I keep using that since I cannot be bothered to encrypt passwords the whole time. Change when you log in the first time. Current software selection is the default KDE system + kernel-source and gcc. Default partitioning in my xml file creates a 256 Mbyte /boot and a 3 GB / and 2048 Mb swap.
You really should look at the XML and change things with vi or use the gui tool I mentioned and not just use the xml file alone.
I turn this into a wiki entry or add it to the network install wiki entry ..... probably best in the next day or two.
Regards,
Andreas
openSUSE is SUPER: To help in the SUSE Performance Enhanced Release project visit http://www.opensuse.org/index.php/SUPER
--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-help@opensuse.org
Andreas,
I have to say thanks again !! this will make my (testing)time realy
easier the next days !! but also a BIG THANKS to all others here,
on the list and the wiki, who worked out so mutch things in that short
time !!
some words when you edit the wiki for the network install:
first of all, I've tested the steps as you've written - they are both
working,
for the beta1 as also beta2 (and I think, beta3 will be ).
there is only one thing that need a short correction: when SLP wasn't
started
before, the service has to be started with "rcslpd start", esp. when openslp
was installed just before the first step.
and maybe some short hints for the ones who setup this stuff the first time:
- when SLP doen't work, the network install service can be reached on the
client by /