while I realise that there would be a possible sync issue. there are ways to
minimize that.
CRC of the filenames for example. Don't get me wrong, I am not saying it
would be trivial to do, but I am sure it could save a tremendous amount of
time for people who can't get a full fileset before the next update.
Probably down to about 1 cent now ;-)
Chris
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Quel Qun
> Sent: Friday, December 15, 2000 7:13 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [RE: [Cooker] Re: iso image files]
>
>
> "Chris Young" <[EMAIL PROTECTED]> wrote:
> > I agree that it would be better that way. in fact, I thought there was
> > supposed to be a current Cooker ISO set available on linuxberg, but I
> > couldn't find it. I just took the script from the 7.2beta and
> modified it
> > to fit my needs. It would seem that the mirror could just kick off the
> same
> > script via cron then there would always be a current cooker iso set.
> >
> > just my $.02
> > Chris
> >
>
> It is actually not so easy to do since there is no guaranty that cooker is
> complete. If (e.g.) you decide to make an iso when the kernel is being
> updated, you will end up with something unusable. Even worse, you
> could end up
> with wrong versions in the index files used by the installer
> because the rpms
> have been updated after these files were created.
>
> When you do your own images, you can at least check that the
> basic stuff is
> there, and stop the mirroring. Current is a concept that has no
> real meaning
> for something like cooker.
>
> Making a total of 4 cts (maybe 3).
>
> =-=
> kk1
>
> ____________________________________________________________________
> Get free email and a permanent address at http://www.netaddress.com/?N=1
>
>
>
