Mailinglist Archive: opensuse-autoinstall (91 mails)
| < Previous | Next > |
SELS 10 Network Installation Directory Layout?
- From: Pete Nishimoto <peten@xxxxxxxxxxxx>
- Date: Tue, 2 May 2006 17:08:16 +0000 (UTC)
- Message-id: <7.0.1.0.2.20060502130859.04a862e0@xxxxxxxxxxxx>
Hi,
I'm trying to setup a PXE server to autoinstall SELS 10
and I'm running into a problem because I'm not sure
how to layout the installation directories for the network install.
I've setup the installation directories and links to sucessfully
network install SELS 9 and I figured it would be pretty
much the same. However, I've run into a problem.
I've created a SELS 10 (Beta 9) installation directory
much like a SLES 9 installation directory, with a sles10 directory
(containing CD 1) and a core10 direcotry (containining
the contents of CD 2-4 in the directories CD1-CD3).
I'm able to install the first CD once I get a number
of extra links (which wasn't in SELS 9), such as
content.asc, content.key.
I've found that I also need a link ./suse->sels10/CD1/suse
to get the first CD to install.
However, when the installation reboots (after installing CD1),
and it start to go through the other packages, etc., it
first looks for the media.2 file. Ok, so I put a link
for media.2 to core10/CD1/media.2. But then it turns out
that the installation procedure is trying to find the
first package that I want to install (aalib) and it traverses
the ./suse link to look for it. Since ./suse->sles10/CD1/suse,
the aalib rpm is not there (it's in ./core10/CD1/suse). Of course,
if I restart at this point and have ./suse->core01/CD1/suse, it
can't find 'setup' and then the installation fails.
So, I still need to know what's the right directory tree
layout for SELS10. Is there any script/documentation/pointer
to anything that can help me here? I'm stuck because of
the problem with the ./suse link, and the installer wanting
different contents for different times.
I was thinking, does it have to do with the ./yast/instorder
or ./yast/order files (are these still used?).
Please help. I'm really close and just need a nudge in the right
direction. I'll continue to search the mail lists, but a
shortcut would be greatly appreciated.
Pete
I'm trying to setup a PXE server to autoinstall SELS 10
and I'm running into a problem because I'm not sure
how to layout the installation directories for the network install.
I've setup the installation directories and links to sucessfully
network install SELS 9 and I figured it would be pretty
much the same. However, I've run into a problem.
I've created a SELS 10 (Beta 9) installation directory
much like a SLES 9 installation directory, with a sles10 directory
(containing CD 1) and a core10 direcotry (containining
the contents of CD 2-4 in the directories CD1-CD3).
I'm able to install the first CD once I get a number
of extra links (which wasn't in SELS 9), such as
content.asc, content.key.
I've found that I also need a link ./suse->sels10/CD1/suse
to get the first CD to install.
However, when the installation reboots (after installing CD1),
and it start to go through the other packages, etc., it
first looks for the media.2 file. Ok, so I put a link
for media.2 to core10/CD1/media.2. But then it turns out
that the installation procedure is trying to find the
first package that I want to install (aalib) and it traverses
the ./suse link to look for it. Since ./suse->sles10/CD1/suse,
the aalib rpm is not there (it's in ./core10/CD1/suse). Of course,
if I restart at this point and have ./suse->core01/CD1/suse, it
can't find 'setup' and then the installation fails.
So, I still need to know what's the right directory tree
layout for SELS10. Is there any script/documentation/pointer
to anything that can help me here? I'm stuck because of
the problem with the ./suse link, and the installer wanting
different contents for different times.
I was thinking, does it have to do with the ./yast/instorder
or ./yast/order files (are these still used?).
Please help. I'm really close and just need a nudge in the right
direction. I'll continue to search the mail lists, but a
shortcut would be greatly appreciated.
Pete
| < Previous | Next > |