[comp.sys.apollo] SR10.1.p installation messed up

e07@nikhefh.nikhef.nl (Eric Wassenaar) (12/18/89)

If you start to install SR10 from scratch from cartridge tape onto
your newly invol-ed disk using the recommended new installation
procedures (minst, install++), you may end up with a very undesired
situation. Be warned.

If you specify a 'closed' system, you end up with a system as open
as possible, with acl-s allowing full access to the world.

If you desire bsd-type inheritance rules (owner from process, group
from directory), you won't get it. Both owner and group come from
the process. (This looks like sys5 inheritance, apart from the
non-organization inheritance).

If you specify bsd as your primary environment, the /etc/environ
file will contain
	ENVIRONMENT=sysv

To get a closed system, specify as target machine not the usual
"//nodename" but instead "//nodename/topdirectory", and move
everything by hand back to the //nodename directory.
However, the installation procedure still leaves many files with world
access in the new system tree. You can trace them with appropriate
variants of the command 'find /topdirectory -perm -002 -ls'
and fix them by hand.

This is terrible.

Eric Wassenaar
-- 
Organization: NIKHEF-H, National Institute for Nuclear and High-Energy Physics
Address: Kruislaan 409, P.O. Box 41882, 1009 DB Amsterdam, the Netherlands
Phone: +31 20 592 0412, Home: +31 20 909449, Telefax: +31 20 592 5155
Internet: e07@nikhef.nl