Path: utzoo!utgpu!utstat!jarvis.csri.toronto.edu!rutgers!apple!sun-barr!ames!lll-winken!arisia!sgi!shinobu!odin!elysium!archer
From: archer@elysium.sgi.com (Archer Sully)
Newsgroups: comp.sys.sgi
Subject: Re: init.ps (was: Network Security Violations)
Message-ID: <112@odin.SGI.COM>
Date: 24 May 89 15:43:28 GMT
References: <8905222009.AA03121@lerc08.nas.nasa.gov> <3172@watale.waterloo.edu>
Sender: news@odin.SGI.COM
Organization: Silicon Graphics, Inc., Mountain View, CA
Lines: 28

In article <3172@watale.waterloo.edu> tom@mims-iris.waterloo.edu.UUCP (Tom Haapanen) writes:
>> Mark Callow <sgi!msc%ramoth.SGI.COM@ucbvax.berkeley.edu> writes:
>>> No, no, no!  Never edit init.ps unless you really know what you are doing.
>
>fsfacca@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?
>

Yes, and you >>will<< burn forever in H-E double toothpicks for it :-).

Whenever I want to modify the behavior of something I first look in
the standard PostScript files to see how its done.  Then I copy the
code to my user.ps, and make modifications there.  This usually works,
and it preserves my changes arcross releases.  To change the console
you can just copy the code from init.ps to user.ps, and change the font,
placement, etc...  There should be an example of this particular technique
in the 4Dgifts account, by the by.


Archer Sully (archer@sgi.com)

"life is short, filled with stuff"
		-- Lux Interior