Trying to add the SLES11SP1 SDK to my Installation server (which is also
SLES11 SP1), when I get to the point where it asks for Disk2, it never
accepts my second iso as valid. My Installation server is a SLES11SP1
install running on top of VMWare ESX 3.5. I have tried copying the iso’s
directly to the filesystem of my Installation server, mounting the iso’s
across the VMWare Infrastructure client from my workstation, and burning
the iso’s and mounting them via the ESX host server. Always YaST loads
the first iso’s content ok but when prompted for the second iso, it
always just comes back and continually asks for the second iso, it never
sees the iso as the valid second iso.
I have loaded many versions of SLES into my installation server without
issue, it’s just this SDK that seems to be problematic. Not sure if it’s
the fact that it’s a large (ie over 4.7GB) iso or what the issue is.
Second iso mount’s fine if I try mounting it on same machine via same
methods, so VMWare driver must support large/double layer iso’s.
Trying to add the SLES11SP1 SDK to my Installation server (which is
also SLES11 SP1), when I get to the point where it asks for Disk2, it
never accepts my second iso as valid. My Installation server is a
SLES11SP1 install running on top of VMWare ESX 3.5. I have tried
copying the iso’s directly to the filesystem of my Installation
server, mounting the iso’s across the VMWare Infrastructure client
from my workstation, and burning the iso’s and mounting them via the
ESX host server. Always YaST loads the first iso’s content ok but
when prompted for the second iso, it always just comes back and
continually asks for the second iso, it never sees the iso as the
valid second iso.
I have loaded many versions of SLES into my installation server
without issue, it’s just this SDK that seems to be problematic. Not
sure if it’s the fact that it’s a large (ie over 4.7GB) iso or what
the issue is. Second iso mount’s fine if I try mounting it on same
machine via same methods, so VMWare driver must support large/double
layer iso’s.
[/color]
Hi
Seems strange, the second is the source rpms, do you really need them?
I am adding via YaST tui interface. I do not think you can add an
install source repo via add-on products, that is for adding something
like OES to your SLES install. I am just trying to add an installation
source repo, not the SDK itself. I realize the SDK disk 2 is only source
RPM’s, and I do not currently need anything off it, but shouldn’t it
work anyway?
BTW, installing the SDK for the x86 version works fine, with similar
size iso’s. It’s only the x86_64 version that fails. Didn’t realize it
initially because I had not finished downloading the x86 SDK iso’s. I
had re-downloaded the x86_64 iso twice just to be sure it was not a
corrupt iso, and mounted it and unpacked it also, it seems fine
otherwise. I wonder, could it be that because my installation server is
running SLES11SP1-x86, not x86_64, that could be the problem?
I am adding via YaST tui interface. I do not think you can add an
install source repo via add-on products, that is for adding something
like OES to your SLES install. I am just trying to add an installation
source repo, not the SDK itself. I realize the SDK disk 2 is only
source RPM’s, and I do not currently need anything off it, but
shouldn’t it work anyway?
BTW, installing the SDK for the x86 version works fine, with similar
size iso’s. It’s only the x86_64 version that fails. Didn’t realize it
initially because I had not finished downloading the x86 SDK iso’s. I
had re-downloaded the x86_64 iso twice just to be sure it was not a
corrupt iso, and mounted it and unpacked it also, it seems fine
otherwise. I wonder, could it be that because my installation server
is running SLES11SP1-x86, not x86_64, that could be the problem?
Thanks
[/color]
Hi
No, all the SDK, SMT etc are added via ‘Add on products’, this will
then add the information to the NCC site and update repositories.