[Arjen]

svn (or another vcs) is a good option as it also gives you the opportunity to revert to a previous version of your catalogs.

I host all my catalogs and packages on a web server and also a simple script that gets all the resources from the web server and builds an image.
Converting a workstation to a buildstation is just a oneliner:

[code]curl http://mywebserver/path/to/buildscript.sh | sudo sh[/code]

I was planning to share my setup with the world but I didn’t have time to create a nice writeup.

[Arjen]

NFS Mounts that you create with Disk utility are stored in the local directory. You can view and manipulate those entries via dscl e.g.:

[code]mw-003998:~ bochoven$ dscl localhost -read “/Local/Default/NFS/file.vua.local:/usr/local/storage”
AppleMetaNodeLocation: /Local/Default
GeneratedUID: 08FF6D43-3B58-4151-BDD8-0BB3A9D1E3D5
RecordName: file.vua.local:/usr/local/storage
RecordType: dsRecTypeStandard:NFS
VFSLinkDir: /Volumes/storage
VFSOpts: resvport
VFSType: nfs
[/code]

The other way would be to modify the autofs configuration files to add NFS automounts (auto_master, autofs.conf)
See also the man pages for auto_master:

Arjen

[Arjen]

[QUOTE][u]Quote by: Kim+Young[/u][p]Can you point me too a place that will explain “checking out SVN repositories”? Thanks.[/p][/QUOTE]

[url]http://code.google.com/p/instadmg/source/checkout[/url]

Basically, open a terminal, type

[code]svn checkout http://instadmg.googlecode.com/svn/trunk/ instadmg-read-only[/code]

and hit enter..

[Arjen]

Make sure you don’t have any diskimages mounted before you run instadmg, that one bit me a couple of times… I think that is a bug, but I did not get around filing a report for that.

Arjen

[Arjen]

Hi Karl,

I was indeed building from a 10.5 machine, I did not realize that the installer had changed that much.
The only default setting I changed was the CHROOT setting in instadmg.bash. I’m glad this issue is solved, the only downside is that I have to move the Xserve that I use as buildstation to 10.6.

I realize that you have the hot breath of a lot of sysadmins in your neck, and I’m pretty occupied myself, but if you need some help, just shout.

Thanks,

Arjen

[Arjen]

/bin.rm will run fine from the sparseimage which has OSX and thus all its cmd line tools already installed on it.

In principle all pacjages should install without problems, what is the nature of your packages?

grz

Arjen

[Arjen]

I should have said:

In short, it prevents the installer or any other program to [b]read or write [/b] outside the sparseimage. This is the reason why the packages have to be copied onto the sparseimage.

This also means that if your packages depend on something that is not available within the package or on the sparseimage, the installation will fail.

hth

Arjen

[Arjen]

From the man page:

[quote]The chroot command changes its root directory to the supplied directory
newroot and exec’s command, if supplied, or an interactive copy of your
shell.[/quote]

In short, it prevents the installer or any other program to write outside the sparseimage.

hth

Arjen

[Author]

Posts