Mailinglist Archive: opensuse-autoinstall (192 mails)
| < Previous | Next > |
Autoyast fails after integrating SLES9 SP1
- From: Frank Steiner <fsteiner-mail@xxxxxxxxxxxxxx>
- Date: Wed, 9 Feb 2005 11:32:23 +0000 (UTC)
- Message-id: <4209F4C2.3040604@xxxxxxxxxxxxxx>
Hi,
we are running autoyast for SLES9 on IBM pSeries. We install
over the network with bootp. Things went fine, until we added
SP1 the way Anas described it in the mails from last week.
But now installation fails because it can't find the core9
sources.
First I created the new "install" image from the SP1 directory
with mkzimage_cmdline for booting with dhcp/bootp.
Then I set up the NFS directory. It looks like:
lrwxrwxrwx 1 root root 10 Jan 11 14:21 boot -> sles9/boot
lrwxrwxrwx 1 root root 13 Jan 11 14:21 content -> sles9/content
lrwxrwxrwx 1 root root 17 Jan 11 14:21 control.xml -> sles9/control.xml
drwxr-xr-x 8 root root 360 Jan 11 11:56 core9
lrwxrwxrwx 1 root root 22 Feb 4 09:17 driverupdate ->
sles9-SP1/driverupdate
lrwxrwxrwx 1 root root 15 Feb 4 09:17 linux -> sles9-SP1/linux
lrwxrwxrwx 1 root root 13 Jan 11 14:21 media.1 -> sles9/media.1
drwxr-xr-x 5 root root 312 Jan 11 12:36 sdk9
drwxr-xr-x 12 root root 1160 Jan 11 12:36 sles9
drwxr-xr-x 13 root root 1496 Feb 4 09:16 sles9-SP1
drwxr-xr-x 2 root root 104 Feb 4 09:12 yast
The contents of the sles9/, core9/ and sdk9/ directories have not changed,
we just added the sles9-SP1 directory and copied the CDs. Instead of
creating subdirs CD{?} there we just put all CD contents into the
subdirs which worked fine all the time. I.e., core9/ looks like
babbage 9/SuSE# ls core9
. .. ARCHIVES.gz ChangeLog INDEX.gz content directory.yast ls-lR.gz media.1
media.2 media.3 media.4 media.5 suse
We adjusted order and instorder:
/sles9-SP1 /sles9-SP1
/sles9 /sles9
/core9 /core9
/sdk9 /sdk9
/sles9-SP1
/sles9
/core9
/sdk9
Now, when I start the installation, everything goes fine and yast starts
installing the packages. here is a screenshot:
http://www.bio.ifi.lmu.de/~steiner/aysles9.jpg
on which you can see that it found all 4 install sources. But after a
few packages from the SP1, it says it can't find the packet "sles_admin_de"
on the installation source, then some more packages, and when I click "
ignore", it complains it can't find the core version 9 CD.
The differing numbers that are shown are from the media.1/media files
from the sles9/ and the core9/ subdir. When I manually add the core9/
subdir in the error window, that it continues to install and flip
flops between installing packages from core9 and SP1 etc. But initially
it seems to be unable to find the core9 sources in the core9/ subdir.
This problem did not occur before we added SP1, so it must be caused
by it somehow. Just like the additional SP1 dir make yast forget that
the core sources are in a subdir, so it is just considering the link
media.1 in the main dir instead of looking at core9/media.1...
Any ideas how to fix this?
cu,
Frank
--
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. *
we are running autoyast for SLES9 on IBM pSeries. We install
over the network with bootp. Things went fine, until we added
SP1 the way Anas described it in the mails from last week.
But now installation fails because it can't find the core9
sources.
First I created the new "install" image from the SP1 directory
with mkzimage_cmdline for booting with dhcp/bootp.
Then I set up the NFS directory. It looks like:
lrwxrwxrwx 1 root root 10 Jan 11 14:21 boot -> sles9/boot
lrwxrwxrwx 1 root root 13 Jan 11 14:21 content -> sles9/content
lrwxrwxrwx 1 root root 17 Jan 11 14:21 control.xml -> sles9/control.xml
drwxr-xr-x 8 root root 360 Jan 11 11:56 core9
lrwxrwxrwx 1 root root 22 Feb 4 09:17 driverupdate ->
sles9-SP1/driverupdate
lrwxrwxrwx 1 root root 15 Feb 4 09:17 linux -> sles9-SP1/linux
lrwxrwxrwx 1 root root 13 Jan 11 14:21 media.1 -> sles9/media.1
drwxr-xr-x 5 root root 312 Jan 11 12:36 sdk9
drwxr-xr-x 12 root root 1160 Jan 11 12:36 sles9
drwxr-xr-x 13 root root 1496 Feb 4 09:16 sles9-SP1
drwxr-xr-x 2 root root 104 Feb 4 09:12 yast
The contents of the sles9/, core9/ and sdk9/ directories have not changed,
we just added the sles9-SP1 directory and copied the CDs. Instead of
creating subdirs CD{?} there we just put all CD contents into the
subdirs which worked fine all the time. I.e., core9/ looks like
babbage 9/SuSE# ls core9
. .. ARCHIVES.gz ChangeLog INDEX.gz content directory.yast ls-lR.gz media.1
media.2 media.3 media.4 media.5 suse
We adjusted order and instorder:
/sles9-SP1 /sles9-SP1
/sles9 /sles9
/core9 /core9
/sdk9 /sdk9
/sles9-SP1
/sles9
/core9
/sdk9
Now, when I start the installation, everything goes fine and yast starts
installing the packages. here is a screenshot:
http://www.bio.ifi.lmu.de/~steiner/aysles9.jpg
on which you can see that it found all 4 install sources. But after a
few packages from the SP1, it says it can't find the packet "sles_admin_de"
on the installation source, then some more packages, and when I click "
ignore", it complains it can't find the core version 9 CD.
The differing numbers that are shown are from the media.1/media files
from the sles9/ and the core9/ subdir. When I manually add the core9/
subdir in the error window, that it continues to install and flip
flops between installing packages from core9 and SP1 etc. But initially
it seems to be unable to find the core9 sources in the core9/ subdir.
This problem did not occur before we added SP1, so it must be caused
by it somehow. Just like the additional SP1 dir make yast forget that
the core sources are in a subdir, so it is just considering the link
media.1 in the main dir instead of looking at core9/media.1...
Any ideas how to fix this?
cu,
Frank
--
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. *
| < Previous | Next > |