🚀 go-pugleaf

In article <BxtDwG.4L7@mentor.cc.purdue.edu> ab@nova.cc.purdue.edu (Allen  
B) writes:
> In article <BxLvqp.B5o@newcastle.ac.uk> S.A.McIntyre@durham.ac.uk  
writes:
> > 
> > Is there any way of launching a FileViewer with setuid root privs?
> > 
> > If it doesn't exist, maybe it should.
> 
> It certainly should. 

O.K. I'm going to throw a little TNT onto this fire:

Disclaimer:  I am not responsible for anything you type into your machine.

Try this (PLEASE do not do this as root):

Type into a terminal window:

/usr/lib/NextStep/Workspace.app/WM.app/WM -NXAutoLaunch YES &

I clipped this from a "ps ax" and added the "&" so that I could keep my  
terminal window useful.

This creates a new workspace on top of the old one (move it and see).
Except for moving or copying from the old workspace to the new one,  
everything seems to work fine (you can still create multiple viewers,  
etc.).

So far, I can get out of it by choosing "logout" from either WorkSpace's  
menu, which generates an error and logs you off ungracefully, or by doing  
a "kill PID" which generates an error and logs you off ungracefully.
Neither is satisfactory.

I checked the online docs with DL and found no mention of command-line  
arguments for WM.  Maybe there's some argument which will make it exit  
gracefully when you hit logout without killing everything in sight.

Maybe now that I've got people around the planet crashing their  
Workspaces, someone who really knows will pipe up.  :-)

Anyone?


------------------------------------------------------------------------
Robert Lutwak                                  robert@amo.mit.edu
Atomic Resonance and Spectroscopy Laboratory
MIT                                            Workspace Error 1000