Help !!! I'm getting very frustrated with downloading cooker ! I've been
trying to get one for 18 hours now, and still haven't been able to.
- cooker updates are so frequent that new release is out before the
previous has been propagated to mirrors. This makes is useless to have
mirrors. I never know what is the latest release.
- I never know that I have a consistent state of install+RPMS+base/*
Problem : the best assurance that I have a self-consistent fileset is to
use the primary site (sunsite.uio.no), therefore causing a bandwidth
bottleneck. It has happened to me several times that a new release caught
me in the middle of doing rsync, so I ended up with an inconsistent state,
and so was wondering why cooker isn't working as it is supposed to !
Fixing this problem will eliminate many completely unnecessary headaches
to your beta testers, who cannot currenly reliably beta test.
Because of the reasons above, it is as if cooker didn't have any mirrors.
I cannot even get onto the rsync server "@ERROR: max connections (50)
reached - try again later", and so cannot effectively do beta testing.
Proposed actions :
1. clearly indicate the version/release of self-consistent filesets (is
this done now by Mandrake/VERSION and install/VERSION ?)
2. cause cooker releases to be promptly replicated to several sites, so
that the primary site doesn't become overloaded.
3. at each release publish the most current VERSION on a
high-availability spot (no rsync or FTP with less than 1000 users limit,
please, but rather use a web page / http access for this, do not use
mailing list, as it takes sometimes many hours to get the msgs), so that
we may know whether we are up to date or not. It can be quite futile and
useless to do beta testing on an old beta.
4. indicate to us that I've finished rsyncing the same release that we
have started rsyncing ! I.e. before a replica starts being updated, remove
the VERSION file. That way people will know that any download attempts are
futile, since they will not end up with a consistent fileset. When you are
done updating a replica, put the new VERSION file in, so people know that
it makes sense to download it again. Also, if I finish syncing and the
VERSION file is different from when I started, I know I have to resync
now.
I.e. the following command will ensure that when it is finished, I have a
complete and self-consistent cooker on my HD.
$ rsync mirror::cooker/VERSION ./VERSION.previous
$ while ! cmp VERSION VERSION.previous ;
> rsync mirror::cooker/VERSION ./VERSION.previous ;
> do rsync mirror:cooker . ;
> done
$ rm ./VERSION.previous
This will greatly help us to do effective beta test on such frequent beta
releases.
Thanks,
Jan
--
-- Gospel of Jesus is the saving power of God for all who believe --
## To some, nothing is impossible. ##
http://Honza.Vicherek.com/
