Path: utzoo!attcan!uunet!lll-winken!lll-tis!helios.ee.lbl.gov!pasteur!ucbvax!bostic
From: bostic@ucbvax.BERKELEY.EDU (Keith Bostic)
Newsgroups: comp.bugs.4bsd
Subject: Re: Installing 4.3-Tahoe on a VAX
Keywords: tahoe vax
Message-ID: <26049@ucbvax.BERKELEY.EDU>
Date: 11 Sep 88 19:34:28 GMT
References: <4790@saturn.ucsc.edu>
Organization: University of California at Berkeley
Lines: 26

In article <4790@saturn.ucsc.edu>, haynes@saturn.ucsc.edu (Jim Haynes - Computer Center) writes:
> This is not a bug report, but rather some ideas/experiences and a plea
> for others to share experiences.  This just seemed like the best place
> to post it.

Chris covered most of your questions -- it seems to me that the easiest
way to install 4.3BSD-tahoe on a VAX is to recompile "make" with the NEW
include files, then, go into /usr/src, and do a "make clean; make depend;
make build; make installsrc".  This must be run as root, as the "make depend"
modifies the Makefiles themselves.  This will clean, build, and install
the tree (including /usr/include) for a VAX.  This works, I rdist this tree
to VAXen and install it myself.  Remaking "make" may be a bit tricky, you
might just copy the include files required into a temporary directory and
use "-I." to get them.  The real issue is that make needs to know what
kind of machine you have, and it gets that information from
/sys/machine/machparam.h.

> 5.  Being paranoid about security I've been going thru all the makefile
> and changing modes from 755 to 711 for all the programs except shell
> scripts.  Also changing the owner from bin to root - this is something
> of a philosophical issue, but I'd rather try to protect root against
> intrusion than root and bin both.

Since you can't log in as "bin" (it has no password) this shouldn't be an
issue.

--keith