On Fri, 2003-09-26 at 09:58, G. M. Bodnar wrote:
> That's great as long as you've got a similar system at both ends.
> Things can be a bit more tricky going from different unix flavours,
> though, where implementations of software might have slightly different
> configuration files. It's a little gotcha, admitedly, but something to
> keep in mind.
Yea, the different types of system can be a problem at Uni.
* Tip 1: Use a standard scripting language. Bourne Shell (sh) is
a good choice as it is standard across *nix platforms.
* Tip 2: Put all your standard configuration files in one place,
and replace the files in "/etc/" with simlinks. For example, in
Computer Science "/etc/printcap.local" points to
"/netfs/cosc/etc/printcap.client", which is on a NFS share.
--
Michael JasonSmith http://www.ldots.org/
