Subject: Re: Distributing supp'ed files inside a network
To: Xavier HUMBERT <firstname.lastname@example.org>
From: Hubert Feyrer <email@example.com>
Date: 10/23/2001 23:07:47
On Tue, 23 Oct 2001, Xavier HUMBERT wrote:
> > * Setup your own SUP Server - of course this means scanning the full disk
> > once after SUP.
> Mmmh... basically, there's little difference between supserv and mirror,
> precisely because it means scanning the whole tree(s), and for each client.
SUP does *not* scan the whole tree for each client!
The client says when it did it's last update, and the server has a
database about which file was touched when. It then sends any files that
are newer than the client's timestamp. You only need to scan the tree once
after updating your SUP server.
> > Updating the SUP database from an existing SUP output
> > would be nice, i guess.
> Well, lets's think about some perl-ish thing for that :-)
Updating the SUP database on demand (e.g. CVS commit mails, or SUP
output) would indeed be nice. Shouldn't be too hard to hack. :)
(Says he who has never looked inside the SUP database :-)
Want to get a clue on IPv6 but don't know where to start? Try this:
* Basics -> http://www.onlamp.com/pub/a/onlamp/2001/05/24/ipv6_tutorial.html
* Setup -> http://www.onlamp.com/pub/a/onlamp/2001/06/01/ipv6_tutorial.html
Of course with your #1 IPv6 ready operating system -> http://www.NetBSD.org/