init.ps (was: Network Security Violations)

[Mark Callow]

In article <3172 at watale.waterloo.edu>, tom at mims-iris.uucp (Tom Haapanen) writes:
> > Mark Callow <sgi!msc%ramoth.SGI.COM at ucbvax.berkeley.edu> writes:
> >> No, no, no!  Never edit init.ps unless you really know what you are doing.
> 
> fsfacca at LERC08.NAS.NASA.GOV (Tony Facca) writes:
> > I agree that init.ps is not a file which should be modified.
> 
> OK, so I suppose you could figure out a way to modify the size and font
> of the default window using PostScript in user.ps, but for me, it was a
> lot easier looking it up in init.ps, and changing the window to be 40x80
> in font ScreenBold.  Have I committed a deadly sin?

Here's the appropriate PostScript from my user.ps

%
% Customize console
%
/RunConsole {
    (/etc/gl/startconsole -r1000 -s24x68 -m60x80 -fScreen.8) forkunix
} store
(console) 10 12 preforigin

Now I don't have to worry if init.ps changes from release to release.  My
window configuration still comes up the way I"m used to.

There are 2 issues with modifying init.ps:

	you are not protected against mistakes; you could disable 4Sight.

	you have to keep making your changes with each new release.
> 
> (The default window size/placement is very annoying, as the pointer is
> initially outside the window, so the window isn't active & you can't type).

This is a bug.  It is fixed in Release 3.2.
--
	-Mark