🚀 go-pugleaf

In article <16813@umd5.umd.edu> matthews@oberon.umd.edu (Mike Matthews) writes:
> I'm thinking about having an account set up so that when they log in, a
> custom app autolaunches, fires off the PS code so you can't get to NeXTstep
> essentially, waits until that's done, then fires up another application
> (coXist in this case), waits 'til coXist quits, then logs the user out.  In
> short, I want the NeXT to be an X terminal with no interaction with NeXTstep.

The best way of doing this is to replace the Workspace Manager with your own  
application (CoXist).  This can be done on a per-user basis by writing into the  
user's defaults database (dwrite loginwindow Workspace <your app>).
(I've hunted all through NeXTanswers and the tech docs for where I found this  
out, but I can't find it.  It is alluded to in workspace.500.)

I used this together with a Shutdown application (which is just a front-end
to /etc/shutdown) and the PowerOffDisabled feature (see NeXTanswers  
workspace.333) to implement an elegant way of controlling power-off of our NeXT  
which has a network of 6 TCP/IP connected terminals.  Users can only power off  
by logging in as "power", which launches my Shutdown Application instead of the  
Workspace Manager.   Shutdown encourages folks to use a fair (3-minute) warning  
with broadcast messages to all users that the system will be going down.  By  
changing the default shell for that user (passwd -s), you can also prevent  
remote logins as well.

Chris Roehrig
University of British Columbia