Re: Mac OS X 10.5: X11 Documentation/Release Notes
Re: Mac OS X 10.5: X11 Documentation/Release Notes
- Subject: Re: Mac OS X 10.5: X11 Documentation/Release Notes
- From: Mike Beattie <email@hidden>
- Date: Sun, 11 Nov 2007 19:49:02 +1300
- Thread-topic: Mac OS X 10.5: X11 Documentation/Release Notes
On 11/11/07 6:01 PM, "Bill Janssen" <email@hidden> wrote:
> Ben, that's a nice theory, but the "client" I want to run is my
> .xinitrc file. (Where *did* xinit disapppear to?)
While not in exact agreement, the concept that X startup, either by
/A/U/X11.app or by launchd, should set up the environment for the user in
its entirety before the first application is displayed is a good one.
Ben, I take it the X server starts accepting connections via the launchd
socket before it starts initialising itself (with things like resources)? Is
this the general description of the race condition?
If that is the case, then a very ugly interim 'hack' for /A/U/X11.app which
equates to 'xhost;sleep 5;xterm' could work? The correct solution could be
to have some way to stop X clients from being able to access the server via
the launchd socket until the X server is completely initialised.
> I think I've come to terms with having launchd run the server, but it
> shouldn't start up X11.app. That's an app, and should be started by
> the user, whether they do in their Login Items, or explicitly by
> clicking on it.
By that theory, you'd not like double clicking documents to start the
application associated with them either.. :) - Think of an X client (xterm,
etc) just being a "document" that needs X11.app to display it.
Mike.
--
Mike Beattie <email@hidden>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
This email sent to email@hidden