Around 0 o'clock on Dec 1, Boris wrote:
> What XFree *really* needs is much more data compression when sending data
> to a remote display
I'm doing some packet level analysis of this problem; at ethernet speeds,
most X applications spend a lot more time waiting for round trips than
they do wait
What XFree *really* needs is much more data compression when sending data to
a remote display. It seems XFree is being used more and more for diskless
clients and to display remote screens. The X protocol uses alot of Bandwidth
when dealing with *alot* of clients.
- Original Message -
From:
On Tue, 26 Nov 2002, David Dawes wrote:
> I'm not particularly interested in using these lists to apply social
> pressure. I'm only interested in a mechanism that provides an acceptably
> low level of spam without imposing subscriber-only posting restrictions.
Then why not simply use an email co
X11 has two kinds of windows -- InputOnly and InputOutput. InputOnly
windows receive mouse and keyboard events just like InputOutput windows
but have no graphical content so that underlying windows show through them.
InputOutput windows receive input and also occlude underlying windows.
Missing
Around 3 o'clock on Dec 1, James Hawtin wrote:
> The only problem with the fixes extension will people use it, as they
> will have to write the code twice so it supports "legancy" ie not Xfree86
> systems. (thinking of selection tracking here)
That's been the argument against such extensions over
On Sat, 30 Nov 2002, Keith Packard wrote:
> 2) Selection Tracking
>
> Applications like the KDE 'klipper' monitor selection contents to save
> them and also perform actions based on them. Right now, this happens by
> having these clients contantly polling the selection.
>
> The proposal is to hav
We've been working around various problems with the core X protocol for
about 15 years now. I think it's time to build an extension that includes
small changes that fix big problems.
Such an extension would be limited to problems with existing core
functionality that can be easily fixed in the
First, I am new to this list.
If my question goes to the wrong list, pls direct me to the right
one.
Second, I am new to building (any) XFree from source (besides
compiling
FreeBSD's ports) - so forgive, if it's simply an "RTFM"
(and point me to the right manual/document)
Third: my question(s):
I have ATI RADEON 8500, 64 MB DDR."powered by ati".
Hi, i have installed the newest snapshot R200 dri drivers, i have also
installed the extras. But when i start X, it shows screen and cursor, but
then immediately stops and shows me:
Fatal server error:
Caught signal 11. Server aborting
I am
Hi,
I have updated my Red Hat from 7.3 to Red Hat 8.0 and I have this error
ever since :
[jan@paris jan]$ xset +dpms
xset: relocation error: xset: undefined symbol: DPMSQueryExtension
Here are the XFree packages installed on my computer :
[jan@paris jan]$ rpm -qa|grep XFree
XFree86-twm-4
YT> Seems my mail got lost somehow...
No, it didn't. I did reply.
As far as I know, nobody is working on KDrive for *BSD.
Porting the accelerated KDrive servers should be a triviality.
Porting the generic server will be difficult until the FreeBSD folks
either provide a framebuffer device or el
11 matches
Mail list logo
