Jeroen van Meeuwen wrote:
John Summerfield wrote:
Jeroen van Meeuwen wrote:
So, you would want the DVD holding the CD ISO images to replace both
the DVD ISO image and the CD ISO images? That is going to be very
nasty in terms of distribution as one would need a double loop mount
for each CD
Is that difficult? I'd not have thought so. I'm sure I've nested loop
mounts before.
I'm not saying it is difficult but we're not Joe Average are we?
I was referring to the coding; I'm sure the jigdo hackers are up to it.
ISO image to be able to use the installation media as a resource for
additional package installation, not to mention the inability of
Jigdo to cope with this -which at this point is just a Release
Feature I'm the owner of.
I am sure that when I learned to use jigdo some years ago, that it
didn't actually care how the file's structured, and that it actually
works with tarballs. See http://atterer.net/jigdo/
[...snip...]
Richard Atterer might be interested on working with you on this;
surely Debian has the same problem.
Debian hasn't got that problem; I've spoken to Richard Atterer and he
feels Jigdo is at it's best as it is right now; enough features for what
it's supposed to do and still maintainable. Looking at the code I
couldn't agree with him more.
The first CDROM though would need to contain another set of metadata
which makes opening up the actual repository a pain in the ass -you
have mediaid's there, again.
I don't understand.
If you have packages spread over multiple locations, you will need to
have repository metadata that also lists the exact location of the
package (ergo in this case CD #1, #2, and so on).
It makes little difference whether the 650 Mbyte ISOs are imbedded in a
4.5 Gbite ISO, or it's Linux is being installed from those same ISOs
accessible my NFS or from a local hard disk. Both have been working
since RHL 7.2 or thereabouts.
It might be a little different with the advent of yum-in-anaconda.
Say we built a slightly-modified boot.iso.
Say this boot.iso contains all that's needed to install
Fedora/RHEL/whatever. Just not the repos.
Say it has a root directory, /images.
Say this directory _might_ have a collection of ISOs.
If this directory has a collection of .ISOs, then it offers the user
the possibility of installing from it. If the collection is
incomplete, then it allows changing media during the install process,
as it does now for CD installations.
I'm not sure how this differs in having both DVD ISO images (just as we
have them now), and CD ISO images available with the releases. I do know
having ISO's inside ISO's makes HTTP/FTP installations more difficult as
one would now just extract or loop mount the DVD ISO image whereas in
this new situation one would have to merge the different CD ISO image's
(that you get when loop mounting the DVD ISO image) contents into one
large repository.
http installs would be little different whether from 650 Mbyte ISOs
imbedded in a 3.5 Gbyte ISO or downloaded separately. Historically (but
not with the first yum-based Acondas) there's been a README explain how
to make a repo from the CD ISO.
autofs _can_ do loop mounts, I've used it for that purpose. I don't know
whether it can do two on one user access, as it would need to to access
internal ISOs.
--
Cheers
John
-- spambait
1aaaaaaa@xxxxxxxxxxxxxxxx Z1aaaaaaa@xxxxxxxxxxxxxxxx
-- Advice
http://webfoot.com/advice/email.top.php
http://www.catb.org/~esr/faqs/smart-questions.html
http://support.microsoft.com/kb/555375
You cannot reply off-list:-)
_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list
