[1530] in NetBSD-Development
sipb-mkserv
daemon@ATHENA.MIT.EDU (Nathan J. Williams)
Sun Jan 11 21:40:26 1998
To: sipb-athena@MIT.EDU
From: "Nathan J. Williams" <nathanw@MIT.EDU>
Date: Sun, 11 Jan 1998 21:40:12 EST
I'm getting ready to start writing some mkserv scripts for
NetBSD-Athena. I'm pretty sure we want a new locker for our mkserv
stuff to live in. Here are the reasons:
- While mkserv scripts are in theory vaguely
architecture-independent, in reality many of the things that they
fiddle with are extremely system-dependent, such as the location of
alias files, how to set up NFS filesystems, and so on. Thus, a lot of
what's in the mkserv locker doesn't apply to us at the moment.
- The administration would be a pain in the butt. The set of
athena mkserv people and SIPB mkserv people doesn't overlap very well,
and isn't something we want to count on. Plus, integrating our changes
into existing scripts requires some level of testing on the normal
Athena platforms, and would slow down development even more. As the
developers of the SIPB-Athena system, we want to be the ones in
control of system software for it, and mkserv falls in that category.
- The attach-and-run model we have makes using a sipb-mkserv
locker instead of the mkserv locker easy. The alternative would be
leaving attach-and-run pointed at mkserv, and having users run "mkserv
sipb-mkserv:service", which seems silly, and also requires that we
get the mkserv locker populated with binaries for SIPB-Athena
platforms.
I'll set this up soon if no one objects.
- Nathan
