I've got a server set up to serve out the various SuSE distros and
patches locally. One virtual host for installation, one for patching,
one for packman, etc. Worked like a charm until SuSE 9.3 came along.
As far as I can see Yast resolves the hostname and substitutes in the
IP address before it tries to install from there - which obviously
fails.
Is there a way around this on the client or do I need to change my
server setup?
Bjørn
--
Bjørn Tore Sund Phone: (+47) 555-84894 Stupidity is like a
System administrator Fax: (+47) 555-89672 fractal; universal and
Math. Department Mobile: (+47) 918 68075 infinitely repetitive.
University of Bergen VIP: 81724
Support: system(a)mi.uib.no Contact: teknisk(a)mi.uib.no Direct: bjornts(a)mi.uib.no
Dear Everybody,
we are testing different Blade Systems.
In our environment PXE boot is not allowed, though all the deployment
tools can't work. That's why we use autoyast with custom CDs.
The IBM Blade Center has an USB CDROM and an USB floppy.
On blades with local disks the installation works fine, but on blades
without local disks there is a problem with the USB floppy.
When the system boots from CDROM the floppy shows up as /dev/sda and the
first SAN disk as /dev/sdb. After the installation the device probing
order changes an the first SAN disk shows up as /dev/sda.
There is no problem if I do a manual installation with the original SLES9
CDs.
Any idea ?
Details on install media:
I created the CD with Yast CD Creator from SLES9 RC5 isos and SLES9 SP1
isos. There is no autoyast.xml but a rules/rules.xml which calls other XML
files depending on disk device, cpu architecture and memory.
Sincerely
Bernhard
On 1 Jul, Harald Milz wrote:
> On a SLES9 SP1 I'm trying to add a webwasher RPM to the install repository
> created with the Yast installation server function.
> I put the RPM into SUSE-CORE-9-CD1/suse/i586, and ran
Personal preference, but I like to leave the default directories untouched and
make a custom/update path with any new rpms. That way you still have an
untouched default setup and don't have to figure out what you added.
I put all our updates/custom packages in a SUSE-Updates path (at the same
level as your SUSE-CORE-9 path).
> create_package_descr -x suse/setup/descr/EXTRA_PROV -d SUSE-CORE-9-CD1/suse
> Now if this were understandably documented. What the heck is EXTRA_PROV,
> and are the paths right?
EXTRA_PROV is short for extra provides.. lists short names and the full path
to the executable, it's a text file, just look at it.
That should work for you though. Unless they expect that new rpms are put
into a seperate path like I do.
--
Mike Marion-Unix SysAdmin/Staff Engineer-http://www.qualcomm.com
Marge: Homer, the plant called. They said if you don't show up tomorrow don't
bother showing up on Monday.
Homer: Woo-hoo! Four-day weekend!
==> Simpsons
I have a bit of a problem installing SuSE 9.3 Pro
on a HP Proliant DL380 with six SCSI disks defined
in two RAID arrays using the hardware RAID controller.
Everything seems to work fine when autoinstalling.
The problem is that the boot loader wont install
properly, rendering the machine useless after an
autoinstall.
I left the bootloader section mostly empty, to allow
autoyast to fill in the proper values. I even tried
without the bootloader section in the autoyast file.
Does anyone have any experience from autoinstalling
a HP Proliant DL380?
R
/LarS
I am using AutoYaST and an Installation Server for SLES 9. I want to offer SLES9 and SLES9SP1.
What is the best way to make SP1?
Install SLES9 again and then add CDs?
Copy SLES9 to new directory and configure it and then add CDs
Start w/ SLES9SP1 CD1 for first CD and go through all 9 CDs?
Thanks
Hi ,
I 'm trying to setup Network install using CIFS for 9.3 and 9.2 and they
both fail for my cluster setup .
Though I have got the network install to work using NFS, But same install FAILS
while using samba.
The server hosting the repository is an Netapp FAS 980 .
While using Suse 9.3 the system boots up fine and I can see my repository too .
but it fails with an message cant find sources.
While using Suse 9.2 I get a very different message . I get a message cant find
images and the installation aborts. Any help to solve the problem
Cheers
yogesh
Dear all,
as a systemadministrator for a research group at a university,I'd like
to use autoyast to install version 9.3 on all the computers. While
trying my autoyast file on a test system, I get this error while
partitioning:
"Error while configuring partitions. Try again."
When I look at the partitioning after this, it looks like yast is
determining it's own partitioning scheme, since it partitions a swap
partition first and then a / partition.
my configuration file looks like this (for partitioning):
<partitioning>
<drive>
<device>/dev/hda</device>
<partitions>
<partition>
<mount>/</mount>
<size>3gb</size>
</partition>
<partition>
<mount>swap</mount>
<size>auto</size>
</partition>
</partitions>
<use>all</use>
</drive>
</partitioning>
after checking y2log I found the following error:
2005-07-01 07:24:22 <3> linux(2771) [Interpreter]
clients/inst_autosetup.ycp:118 Can't convert value
'$["drive":$["device":"/dev/hda",
"partitions":$["partition":$["mount":"swap", "size":"auto"]],
"use":"all"]]' to type 'list'
2005-07-01 07:24:22 <3> linux(2771) [Interpreter]
clients/inst_autosetup.ycp:118 Parameter eval failed (/* any -> list
*/Profile::Flat["partitioning"]:[])
2005-07-01 07:24:22 <1> linux(2771) [YCP] AutoinstStorage.ycp:300 Target
map: $["/dev/hda":$["bios_id":"0x80", "bus":"IDE", "cyl_count":13328,
"cyl_size":483328, "label":"msdos", "max_logical":63, "max_primary":4,
"model":"MPD3064AT", "name":"1. IDE, 5.9 GB, /dev/hda,
FUJITSU-MPD3064AT", "partitions":[], "scrpath":."hda",
"unique":"l_yX.aATOdNRb6qD"]]
2005-07-01 07:24:22 <1> linux(2771) [YCP] AutoinstStorage.ycp:306 disk
with bios_id 0x80: /dev/hda
2005-07-01 07:24:22 <1> linux(2771) [YCP] AutoinstStorage.ycp:311 mbr
disk: /dev/hda
2005-07-01 07:24:22 <1> linux(2771) [YCP] AutoinstStorage.ycp:164
processed autoyast partition plan: $[]
TIA,
Maarten Hilgenga
--
-------------------------------------------------------
M.L.Hilgenga
University of Groningen
Department of Applied Physics
Nijenborgh 4, 9747 AG Groningen
The Netherlands
tel: +31-50-3638045
fax: +31-50-3634886
email : m.l.hilgenga(a)rug.nl
-------------------------------------------------------
Hi Harald,
I did that a few days ago for a 9.3 Pro. The
purpose was to have dhcpd, bind and squid on CD1.
I copied the CD-Content to sl93cd1/
cd sl93cd1/suse/
/opt/kde3/share/apps/krpmview/create_package_descr \
-x ./setup/descr/EXTRA_PROV -l en -l de -p ./setup/descr/
worked for me. I have no idea why I found create_package_descr
only in this directory. It also had a minor bug with
the parameter order for find.
>From the docu:
Change starting from SUSE Linux 9.1/SLES 9
To provide extra dependencies which can not be extracted
from the rpm files, an extra file with missing dependencies
is available in the directory suse/setup/descr. The file
EXTRA_PROV can be used when recreating the package database
using the -x option.
I admit that the documentation leaves many question for
R&D or this mailinglist...
Maybe a AutoYaST-Wiki would be a good idea? Or is it
already in existence?
Regards,
Goetz
> -----Ursprüngliche Nachricht-----
> Von: Harald Milz [mailto:hm@seneca.muc.de]
> Gesendet: Freitag, 1. Juli 2005 08:19
> An: suse-autoinstall(a)suse.com
> Betreff: Re: [suse-autoinstall] Additional Package & Silent install
>
>
> Michael Marion <mmarion(a)qualcomm.com> wrote:
>
> > I should document my setup when I have a chance.. this
> comes up so often.
>
> I wish everything were documented more clearly to begin with.
>
> On a SLES9 SP1 I'm trying to add a webwasher RPM to the
> install repository
> created with the Yast installation server function.
> I put the RPM into SUSE-CORE-9-CD1/suse/i586, and ran
>
> create_package_descr -x suse/setup/descr/EXTRA_PROV -d
> SUSE-CORE-9-CD1/suse
>
> Now if this were understandably documented. What the heck is
> EXTRA_PROV,
> and are the paths right?
>
> --
> Great minds run in great circles.
>
> --
> To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com
> For additional commands, e-mail: suse-autoinstall-help(a)suse.com
>
On 30 Jun, Jan Kalcic wrote:
> 1) I'm looking for a clear way to add additional packages to the installation server. I found a solution using the post script (wget && rpm) but it would really better and more handy to have them direclty into the AutoYaST software package database.
Sort of difficult to get working.. but once you do, easy to keep updated and
very slick integration.
>From a previous answer I posted to the same question before:
Look in the archives of this list for many threads on this,
i.e. subjs:
[suse-autoinstall] Custom install source for yast in SLES9
[suse-autoinstall] How can I regularly update the install repository?
I should document my setup when I have a chance.. this comes up so often.
--
Mike Marion-Unix SysAdmin/Staff Engineer-http://www.qualcomm.com
Joe: "I don't know, one minute we're spanking each other with meat, the next
minute it got weird." --Wings
