Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10 5/3/83; site oliveb.UUCP
Path: utzoo!watmath!clyde!akgua!sdcsvax!sdcrdcf!hplabs!oliveb!jerry
From: jerry@oliveb.UUCP (Jerry Aguirre)
Newsgroups: net.unix-wizards
Subject: Should init and getty be shared text?
Message-ID: <338@oliveb.UUCP>
Date: Thu, 3-May-84 14:59:52 EDT
Article-I.D.: oliveb.338
Posted: Thu May  3 14:59:52 1984
Date-Received: Wed, 9-May-84 03:19:46 EDT
Organization: Olivetti ATC, Cupertino, Ca
Lines: 20

We run 2.8 on PDP-11/70s.  In looking around our system I noticed that
/etc/getty has the sticky bit set but is neither pure executable or
split I&D.  As I understand the function of the sticky bit, setting
it on an unshared text doesn't do any good.

I recompiled getty with -n option and am using it now.  This should
save memory, swap space, and load time, right?

I notice that /etc/init is also unshared text.  As it is frequently
the program with the greatest number of processes shouldn't it be
pure executable?

I can understand why many of these programs (csh and ls) are
distributed without split I&D (-i) as some PDP-11s don't support it.
But why are common processes like init and getty not even made pure
executable?  Does any one know of any reason why I shouldn't make
init pure executable?

					    Jerry Aguirre
    {hplabs|fortune|ios|tolerant|allegra|tymix}!oliveb!jerry