Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!ames!haven!mimsy!chris
From: chris@mimsy.UUCP (Chris Torek)
Newsgroups: comp.bugs.4bsd
Subject: Re: Installing 4.3-Tahoe on a VAX
Message-ID: <13563@mimsy.UUCP>
Date: 15 Sep 88 00:24:44 GMT
References: <5415@zodiac.UUCP> <10477@ncc.Nexus.CA> <5432@zodiac.UUCP> <624@mace.cc.purdue.edu>
Organization: U of Maryland, Dept. of Computer Science, Coll. Pk., MD 20742
Lines: 27

In article <624@mace.cc.purdue.edu> dls@mace.cc.purdue.edu
(David L Stevens) notes:
>	You clearly have to protect "bin" as much as "root", so why even
>have them be separate?

We already answered that.  And, as I pointed out, if you do NOT want them
to be separate, under the current scheme, you need only change one line in
/etc/passwd:

	bin:*:3:3:Brain In Neutral:/bin:/bin/csh

(I see someone has been adjusting the user names again :-) .  Your uids
will differ) to

	bin:*:0:0:Brain In Neutral:/bin:/bin/csh

whereas, if you *do* want them to be separate, and they are not already,
you must change every Makefile.

We are thinking of fixing the `-m' value duplication (and anything
else that comes up) by adding an `include' mechanism to make, a la
SunOS 3.5 (which, I believe, got it from SysV).  It would be nicer if
make simply used m4 on makefiles, but that would break old ones, whereas
adding `include' as a magic word should not.
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7163)
Domain:	chris@mimsy.umd.edu	Path:	uunet!mimsy!chris