You can build a headless VM today and run without X.
If you use David Lewis's OSProcess plugin, you can
start in X, and then fork an identical copy without
X and continue from there (at least in theory - I
haven't tried this one).
As for me, I like the ability of being able to
reconnect to my VNC/X session and have full access to
the development environment. My code is solid
enough that I never need this, but its nice to know
its there if I do :>) Oops, there comes the lightning
bolt again...
-david
> -----Original Message-----
> From: Bijan Parsia [mailto:[EMAIL PROTECTED]]
> Sent: Friday, May 26, 2000 8:56 AM
> To: [EMAIL PROTECTED]
> Subject: Re: [pws]status comswiki10 and safety risks?
>
>
> On Fri, 26 May 2000, Bert Freudenberg wrote:
>
> > On Thu, 25 May 2000, Bijan Parsia wrote:
> >
> > > Writing files and opening sockets may be sufficient for a
> variety of
> > > secondary attacks (as well as the obvious direct
> attacks). For example, if
> > > you can write out a pre-compiled AppleScript to the
> "startup" folder, it
> > > will get executed next startup.
> >
> > The latest (not yet official) Unix VM has a -secure option
> that restricts
> > file prims to be able to read and write only in the image
> directory and
> > subdirs (the so-called "file sandbox").
>
> Cool! I suspected that this would be fairly straightforward.
>
> Now, as soon as we can kill the need to run X even if Squeak
> is running
> headless, I know several folks who will be delighted to adopt
> Squeak as
> their server.
>
> (This complaint---the need for X even if you aren't going to use
> it---cropped up on comp.lang.smalltalk. From Tim's rumblings,
> however, I
> suspect that's on the way.)
>
> Cheers,
> Bijan.
>
