I'm looking for any pointers on automating the installation of SLES 8 w/
SP3 to IBM HS20 blade servers via PXE booting.
First, I have a question about creating my network share.
http://portal.suse.com/sdb/en/2003/03/rschmid_slesnfs.html states to
copy all 4 CDs, in reverse order, to a common directory. How does the
SP3 CD fit into this puzzle? Can I substitute the SP3 CD for CD 1,
since you can boot from SP3?
Second, I'm going to try and follow the instructions from
http://portal.suse.com/sdb/en/2003/06/tsieden_pxe-install.html. This is
where any (HS20 | Blade Center Chassis | RDM) specific hints would be
great.
Thank you.
--
Sincerely,
Steve Kohrs
Distributed Systems
402.633.7058
This email and any files attached with it are confidential and intended
solely for the use of the individual or entity to whom they are addressed.
If you have received this email in error delete this message and notify the
sender at 402-341-0500. If you are not the named recipient you should not
disseminate, distribute or copy this email or any attachment.
I'm looking for any pointers on automating the installation of SLES 8 w/
SP3 to IBM HS20 blade servers via PXE booting.
First, I have a question about creating my SMB share.
http://portal.suse.com/sdb/en/2003/03/rschmid_slesnfs.html states to
copy all 4 CDs, in reverse order, to a common directory. How does the
SP3 CD fit into this puzzle? Can I substitute the SP3 CD with CD 1,
since you can boot from SP3?
Second, I'm going to try and follow the instructions from
http://portal.suse.com/sdb/en/2003/06/tsieden_pxe-install.html. This is
where any (HS20 | Blade Center Chassis | RDM) specific hints would be
great.
Thank you.
--
Sincerely,
Steve Kohrs
Distributed Systems
402.633.7058
This email and any files attached with it are confidential and intended
solely for the use of the individual or entity to whom they are addressed.
If you have received this email in error delete this message and notify the
sender at 402-341-0500. If you are not the named recipient you should not
disseminate, distribute or copy this email or any attachment.
Hi,
I am trying to do a disk-to-disk installation using SLES 8 and autoyast.
Now I have two questions:
1) Is it possible to keep disk partitions? And if yes, how? I figured it out
for SuSE 9.0 but it does not work this way for SLES 8.
2) I prepared a source repository as described in 6.1.3 in
http://www.suse.de/~nashif/autoinstall/sles8/html/advanced.html#AEN1321 on
partition /dev/hda7 (the last one on the disk). The info file for linuxrc
seems to work but linuxrc always says "/dev/hda7 is not a SuSE Linux
installation media". After trying DHCP on the NICs it runs into the textual
UI of linuxrc. When I select installation from harddisk and then /dev/hda7
as source, everything works fine.
Any ideas?
Regards,
i. A. Moritz Wenk
Software Developer
Produkt Management International
PLATINUM Server
MAXDATA Computer GmbH&Co.KG
Elbestraße 12 - 16
D-45768 Marl
Telefon: +49 2365 952-2715
Telefax: +49 2365 952-2279
http://www.maxdata.com
Hallo,
ich möchte per AutoYast2 unter SLES8 logische Laufwerke anlegen. Das letzte
logische Laufwerk soll dabei den restlichen zur Verfügung stehenden
Plattenplatz belegen. Ist dieses Möglich und wenn ja wie sieht die Syntax
dafür aus? Ich konnte leider keine Referenz finden, in der die Syntax mit
möglichen Parametern beschrieben ist. Gibt es eine solche?
Folgendes habe ich versucht:
<partitioning config:type="list">
<drive>
<device>/dev/cciss/c0d0</device>
<reuse>all</reuse>
<initialize config:type="boolean">true</initialize>
<partitions config:type="list">
[...]
<partition>
<size>max</size>
<lvm_group>datavg</lvm_group>
</partition>
</partitions>
</drive>
</partitioning>
<lvm config:type="list">
<lvm_group>
<lvm_name>datavg</lvm_name>
<pesize>4M</pesize>
<logical_volumes config:type="list">
[...]
<lv>
<lv_name>datalv</lv_name>
<lv_size>max</lv_size>
<lv_fs>ext3</lv_fs>
<lv_mount>/data</lv_mount>
</lv>
</logical_volumes>
</lvm_group>
</lvm>
Bei datalv bleibt AutoYast2 mit einer Fehlermeldung stehen - hier scheint
es max für lv_size nicht zu mögen...
MfG
Hartmut Dunker
Hello,
is there really no way to have the ethernet adapter detected automatically
so that there will be the entry for my ethernet interface in
/etc/modules.conf again? Since I create my CD according to Anas
instruction it won't be inserted automatically.
Thank you for you help.
Regards Manuel
----- Weitergeleitet von Manuel Lässer/TK Services/Telekurs am 17.04.2004
13:32 -----
Manuel.Laesser(a)telekurs.com
07.04.2004 21:52
An
Anas Nashif <nashif(a)suse.de>
Kopie
suse-autoinstall(a)suse.com
Thema
[suse-autoinstall] Antwort: Re: [suse-autoinstall] autoinst.xml on
self-made cd
Hello Anas
Thank you so much for this hint! It really works if you follow all your
instruction below step by step. There are a couple of things that changed
if I compare it with the installation from my repository-server.
1. at the stage when the license agreement is displayed, there is a 10
second countdown and after this the installation starts. How can I disable
this timer so you really have to press enter to continue?
2. no module will be loaded for the network interface(s) because there is
no entry in /etc/modules.conf for eth0. If I install the server from my
repository-server the ethernet interface eth0 will be discovered
automatically and I've got an alias set for my eth0 in /etc/modules.conf.
Is there a way, I can detect all ethernet interfaces and insert them all
in /etc/modules.conf even I install my server from the cd as described by
Anas below?
Thank you for your answer.
Regards Manuel
-----------------------------------------------------------
Telekurs Services
Hardturmstrasse 201, 8005 Zürich
Phone : +41 1 279 44 24
Fax : +41 1 279 34 44
mailto : manuel.laesser(a)telekurs.com
-----------------------------------------------------------
Anas Nashif <nashif(a)suse.de>
03.04.2004 02:59
An
Manuel.Laesser(a)telekurs.com
Kopie
suse-autoinstall(a)suse.com
Thema
Re: [suse-autoinstall] autoinst.xml on self-made cd
Hi,
I have just tried reproducing this, and it works for me as expected.
- unpack ISO/CD of SLES8 into a directory /tmp/SLES
- unpack ISO/CD of SP3 into a directory /tmp/SP3
- cp /tmp/SP3/driverupdate /tmp/SLES
- cp /tmp/SP3/boot/loader/linux /tmp/SLES/boot/loader
- cp /tmp/SP3/boot/loader/initrd /tmp/SLES/boot/loader
- Edit /tmp/SLES/boot/loader/isolinux.cfg and add
autoyast=default instmode=cd
- Copy autoinst.xml into /tmp/SLES
Create ISO image
Boot and it works.
Anas
Manuel.Laesser(a)telekurs.com wrote:
> Hello,
> sorry to bother you again and again. I'm using SLES8 with
> autoyast2-2.6.44-7 and autoyast2-installation-2.6.44-7. I think this is
> the latest version for SLES8 (comming with SP3). I copied autoinst.xml
to
> the root of my self-made CD-ROM and I'm using the following parameter in
> isolinux.cfg
>
> # autoyast
> label autoyast
> kernel linux
> append initrd=initrd ramdisk_size=65536 autoyast=default instmode=cd
> usedhcp=0 textmode=1
>
> If you use parameter "autoyast=default" YaST2 will look for
autoinst.xml
> in the following three places (according to Anas Nashif PDF SLES8 -
> Automatic Linux Installation and Configuration with YaST2) :
>
> 1. the root directory of the floppy disk
> 2. the root directory of the installation medium (CD-ROM in my case)
> 3. the root directory of the initial ram disk used to boot the system
>
> Cool......unfortunately it doesn't work at all in my environment. I
tried
> with "autoyast=file:/autoinst.xml", "autoyast=file://autoinst.xml",
> "autoyast=default" I always got this bloody control menu where it asks
for
> the location of the autoinst.xml! From there I could choose http,
device,
> floppy, nfs....but I didn't manage to access the cdrom. If I insert a
> floppy with my autoinst.xml in the root, the installation is proceeding.
I
> also can edit isolinux.cfg with "autoyast=floppy://autoinst.xml" and
it'll
> find autoinst.xml.
>
> Why do I get always very nice and well meant hints from the autoinstall
> mailing list telling me that the are using "...autoyast= default
> instmode=cd..." and everything is working fine. Does this have a
coherence
> that I'm using SLES8 with autoyast2-2.6.44-7 and most of people Suse x.x
> with the newest autoyast2 autoyast2-2.8.14-20 or so.....
>
> I'm really stumped....
>
> Any comment is welcome.
>
> Regards Manuel
>
> p.s. I'll send a box of the finest original swiss chocolate to the one
who
> can give me the right tip to solve this problem...... ;-))
>
> -----------------------------------------------------------
> Telekurs Services
> Hardturmstrasse 201, 8005 Zürich
> Phone : +41 1 279 44 24
> Fax : +41 1 279 34 44
> mailto : manuel.laesser(a)telekurs.com
> -----------------------------------------------------------
You can run "online_update -s"
That will update for you assuming that you have all the network access you
need.
Todd
-----Original Message-----
From: Cosmo King [mailto:cosmo@pogolinux.com]
Sent: Monday, April 26, 2004 5:39 PM
To: suse-autoinstall(a)suse.com
Subject: [suse-autoinstall] automatic updates after autoinstall
How do I force updates to be automatically run after a network
autoinstall of susepro 9/ sles8?
I have downloaded the update tree, and placed it in the update folder at
the root of the suse installation repository.
Thanks!
--
Cosmo King
Systems Engineer
Pogo Linux, Inc.
888.828.7646
cosmo(a)pogolinux.com
--
To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com
For additional commands, e-mail: suse-autoinstall-help(a)suse.com
I have used the method of "wget http://IP/somepath/somefile -O /somedest" in
a post install script.
-----Original Message-----
From: Cosmo King [mailto:cosmo@pogolinux.com]
Sent: Monday, April 26, 2004 5:34 PM
To: suse-autoinstall(a)suse.com
Subject: [suse-autoinstall] Postinstall scripts in a different file
Is there a way to have the entire postinstall script reside in a file
other than the autoinstall.xml, and circumventing the need for the
awkward <![CDATA[#!/bin/bash ]]> syntax?
Thanks!
--
Cosmo King
Systems Engineer
Pogo Linux, Inc.
888.828.7646
cosmo(a)pogolinux.com
--
To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com
For additional commands, e-mail: suse-autoinstall-help(a)suse.com
Is there a way to have the entire postinstall script reside in a file
other than the autoinstall.xml, and circumventing the need for the
awkward <![CDATA[#!/bin/bash ]]> syntax?
Thanks!
--
Cosmo King
Systems Engineer
Pogo Linux, Inc.
888.828.7646
cosmo(a)pogolinux.com
How do I force updates to be automatically run after a network
autoinstall of susepro 9/ sles8?
I have downloaded the update tree, and placed it in the update folder at
the root of the suse installation repository.
Thanks!
--
Cosmo King
Systems Engineer
Pogo Linux, Inc.
888.828.7646
cosmo(a)pogolinux.com
Hi,
I have several installations done throught autoyast and everithing works
fine,but I spend lot of time replicating all configuration variations
after installation across different machines,is it possible to use
autoyast and generate an autoinst.conf with some variations (for example
one more user or something similar ...) and pass it to another autoyast
on an other machine and make him write changes on the configuration
files (or pass it directly to yast) ? I've read that autoyast use a
format compatible with other modules of yast ,so how can I make yast
able of reading these configurations from autoyast and use them to
change my configuration files ? Is it possible ? even with some hacks
....
Thanks in advance
regards