[Rule-list] Distributing the distro

[Jason Roysdon]

Somewhat on-topic with this is a work-around for using Up2Date, but
redirecting where the RPMs come from.  For instance, we nightly mirror any
changes we care about (no source, and just Intel-based RPMs) from
ftp.redhat.com/pub/redhat/linux/updates/7.2/en/os/ to
ftp.artoo.net/pub/redhat/linux/updates/7.2/en/os/.  When there is a new
update, I always use rpm manually to update from our mirror, but it would be
really nice to use Up2Date to automate watching what packages is installed
locally and dependancies in order to update.  My assumption for why RedHat
is using Up2Date to only pull from them is that eventually they're planning
to charge for the service and/or just want to keep the updates secure (but
if that was the case, just pull MD5 checksums for the updates from their
server, but allow you to pull the RPM from a local mirror).  Anyone have any 
insight to this?

-- 
Jason Roysdon
http://jason.roysdon.net/

On Mon, 18 Feb 2002, Vik Olliver wrote:

> Greetings citizens of the list,
> 
<snip>
> 
> It ocurred to me that a distro with such a small footprint would be an
> ideal candidate for peer-to-peer updating. The likes of Red Hat would
> not be happy, of course, as they make money out of distributing their
> updates fro a central location. Very nice of them to make it a free
> service and all, but they seem to have to limit access from time to
> time. A Gnutella- of freenet-like system that could find the nearest
> node(s) and aquire the latest GPG-signed updates would get around this.
> 
> Vik :v)
> 




_______________________________________________
Rule-list mailing list
Rule-list at mail.freesoftware.fsf.org
http://mail.freesoftware.fsf.org/mailman/listinfo/rule-list