Path: utzoo!attcan!uunet!cs.utexas.edu!rutgers!sun-barr!ames!sgi!msc@ramoth.sgi.com From: msc@ramoth.sgi.com (Mark Callow) Newsgroups: comp.sys.sgi Subject: Re: init.ps (was: Network Security Violations) Message-ID: <33516@sgi.SGI.COM> Date: 24 May 89 17:17:21 GMT References: <8905222009.AA03121@lerc08.nas.nasa.gov> <3172@watale.waterloo.edu> Sender: daemon@sgi.SGI.COM Organization: Silicon Graphics, Inc., Mountain View, CA Lines: 37 In article <3172@watale.waterloo.edu>, tom@mims-iris.uucp (Tom Haapanen) writes: > > Mark Callow 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? 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