-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Jan 13, 2005, at 10:25 AM, Kurt Schwehr wrote:
Hey all in the fink world,
This is something that I am not directly involved, but I would be interested in hearing what other think. One of the departments at my school is looking to deploy fink across about 120 machines which is about 1/2 desktops that are aways on the network and 1/2 laptops that will come and go from the wired and wireless networks along with going to sleep. The admins feel they need to maintain a global fink that they maintain that all of the users can count on. They also want to let laptop users have their own fink tree in say /sw.
So the questions are:
* Has any group done this before and what lessons are you willing to share?
I haven't done it with quite that many machines, but I've got fink set up to use a local apt source.
* How would you go about this if you had the freedom to do it anyway you want?
I have one of our G5s set up to be the apt repository for the machines at my day job. It's running 10.3 client, so I added a file, /etc/httpd/users/fink with the following contents:
- -- cut --
Alias /fink /sw/fink
<Directory /sw/fink>
Options Indexes FollowSymLinks
</Directory>
- -- cut --I did this as a separate user file rather than edit /etc/httpd/httpd.conf to prevent future OS updates from breaking my apt repository. If you're running the repository on OS X Server, I believe you need to put the file in /etc/httpd/sites, and the file name may need to be tweaked to avoid confusing the GUI tools.
To get client machines to use the repository, I added the following lines at the beginning of /sw/etc/apt/sources.list (change finkmachine to the machine name of your repository):
- -- cut -- deb http://finkmachine.local./fink stable main crypto deb http://finkmachine.local./fink unstable main crypto - -- cut --
It was cool to discover that apt would deal with rendezvous names painlessly.
Now all you have to do is remember to do "fink scanpackages" after you build anything new on the repository, and your clients can just "apt-get update;apt-get upgrade" periodically to stay up to date.
* Would you just have machines periodically rsync in the debs and list of packages from a machine and have only local fink installs?
I only run local fink installs to prevent locking issues on the shared tree. Disk is cheap, it isn't worth my time to monkey with coercing the various packages to deal with not having exclusive access to their files.
If your admins want to ensure that all the machines in the labs have identical fink environments, the easiest solution is to create a dummy package that depends on all the packages that they want to be on the lab machines, and add it to their repository. I've got one that in addition to requiring a bunch of other things that I want installed on my production machines, installs a bunch of my personal scripts that I've accumulated over the years. When I add a new script or edit an old one, I have a Makefile that rebuilds the fink package and transfers the deb file to the repository box.
jpb
- -- Joe Block <[EMAIL PROTECTED]>
Making machines do more so that man may do less. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (Darwin)
iD8DBQFB7WVFyEXo8W2M9hsRAnrNAKC0P5MeN2uZvfmnsbpkfe6uNNyXOACfQlY2 ulJVmSGHujva0oxJY/6Xsyc= =8ldI -----END PGP SIGNATURE-----
------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Fink-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fink-users
