How should the files be laid out on the 
FTP / NFS / HTTP server when preping them 
for a network install?  Given that it's 
easy to simply use the loopback feature
to the ISO images, should we consider
allowing a structure of cd1 cd2 & cd3
instead of the way I understand it
where you take:

Contents of cd1
Then add RPMS2 from 2nd CD and put it 
under /Mandrake from the first CD
and the RPMS3 from the 3rd CD and 
add it also under /Mandrake from the
first CD.

I just performed a network install 
from a sight who graciously provided
loopback images of the 9.2b1 install
cds and it went about 1/3 of the way 
through the install and reported...

"There was an error installing packages indexhtml-9.1-8mdk.noarch
Go on anyway?  y/n

On the other hand, as someone suggested, I tried 
downloading straight from a mandrake-devel directory from 
a mirror which failed miserably indicating at first that 
it was Mandrake Cooker 9.2, but then many packages including
termcap could not be loaded.

Adding this ability for the network install to locate the RPMS2
and RPMS3 files in seperate file trees could significantly reduce
the job of the mirror maintainers, and provide a way to reduce
the disk space requirements for mirroring both ISOs and the
file layout.  (Maybe the disk space requirements could be handled
with some fancy symbolic links)

-Joe Baker



Reply via email to