Should init and getty be shared text?

Jerry Aguirre jerry at oliveb.UUCP
Fri May 4 04:59:52 AEST 1984


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



More information about the Comp.unix.wizards mailing list