Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

I just *had* to comment.

Derek Atkins writes:
| ~/.* is not sufficient to deal with "global settings".  However a
| registry isn't sufficient, either.  Think distributed systems (i.e.,
| I've got 1000 machines and the software is installed on a central file
| server (not on each machine) and run out of the network file system).
| Registries of all forms fall flat in the face of distributed file
| systems, unless there is some standard way to read the global registry
| info out of the file system.

Now if the registry were handled by a server that used TCP or UDP for
access, it would be straightforward to have a shared net registry.  I
wonder if the sourceforge registry project is considering  this.   If
not, maybe you should send them a suggestion.

This could get complicated, since such a central registry could  well
be a bottleneck. Then you'd want to add mirroring and a way to find a
server with good response time.

BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!

Boston Linux & Unix /