Subject: Re: wscons problems on macppc, was -current on PowerBook G3/400
To: None <M.Drochner@fz-juelich.de>
From: Bill Studenmund <email@example.com>
Date: 09/22/1999 14:15:03
On Wed, 22 Sep 1999, Matthias Drochner wrote:
> firstname.lastname@example.org said:
> > > diff -r220.127.116.11 wskbd.c
> > > 560c560
> > > < #if NWSMUX > 0 || NWSDISPLAY > 0
> > > ---
> > > > #if NWSMUX > 0
> That's a wsmux issue - this should be quite independent from
> the virtual screen stuff.
> (I've got some problems with wsmux too, but didn't have time
> to understand how things are supposed to work.)
Well, it's getting in the way. :-)
> > I think the problem is that the wscons code kinda assumes that X will run
> > on one of the ttyE's (typically ttyE4)
> No, wscons doesn't assume this. At least on i386, X runs
> with only the console screen (what you get with wscons
> not enabled in /etc/rc.conf).
I'll try this on macppc.
> > if (sc->nscreens > 0)
> > return (ENOMEM);
> > which seems to imply only one screen is ok. A comment below, "/* one and
> > only for now */" corroberates that.
> That's for simplicity of the display driver. X can take over the
> one and only screen -- at least wscons allows it.
wscons in general might, but I get busy errors with the mux stuff. both
wskbd1 (the real keyboard) and wskbd (the mux of it) all report EBUSY to
the x server. :-(