home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!sdd.hp.com!network.ucsd.edu!sdcc12!sdcc14!ph600fbr
- From: ph600fbr@sdcc14.ucsd.edu (James Dehnert)
- Newsgroups: comp.sys.next.misc
- Subject: Re: fantasy style login image
- Message-ID: <42808@sdcc12.ucsd.edu>
- Date: 22 Dec 92 19:54:22 GMT
- References: <1992Dec22.101601.20122@macc.wisc.edu> <1992Dec22.135658.1340@macc.wisc.edu> <1h7gl4INNeeo@darkstar.UCSC.EDU>
- Sender: news@sdcc12.ucsd.edu
- Organization: University of California, San Diego
- Lines: 28
- Nntp-Posting-Host: sdcc14.ucsd.edu
-
- >I've not tried it under 3.0, but I think there's a better way. Replacing the
- >login panel as Jess describes seems somewhat perilous and does require messing
- >with system files. NeXT has provided a defaults variable for loginwindow that
- >points to the location of the desired login panel tiff. Setting this defaults
- >variable and leaving the system login panel where it is seems like a cleaner
- >approach (but of course, if the defaults variable is set incorrectly, problems
- >will still occur :-)
- >
- ># dwrite loginwindow ImageFile fullPathForNewLoginPanelTiff
- >
- >Then restart the window server as Jess described.
-
- The best way to go ( IMHO ) is to make the dwrite above look at a generic
- file called login.tiff, or whatever, and make this file a symbolic link to
- whatever file you would like to use. This way you dont have to remember
- the dwrite command when you get a better login screen tiff, and you can
- also be a bit creative with this. For instance, you can name all your
- login tiffs 1 through 34 ( or whatever ) and have a logout hook move the
- symbolic link at random. I havent tried this ( I like the unix daemon
- screen myself ) but it should work.
-
-
-
- --
- +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
- = James "Zeke" Dehnert zeke@mode.css.gov =
- + SAIC Geophysical Div. Eschew Obfuscation +
- =+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=
-