RJ Judging from the large number of *flames* I got for suggesting it,
These weren't flames. They were fairly kind explanations.
A flame is something completely different -- you'll see if you hang
around some more ;-)
Juliusz
TR You really need some way to identify the XFree86 server as
TR trusted. In Linux today, the only mechanism for doing that is
TR suid root.
I'm sorry to repeat what I've already said, but it isn't. It could
very well be setgid xfree86, setgid hwaccess. Old SunOS had setgid
kmem for ps and
RJ An IOCTL shouldn't have any more overhead than reading or writing to a
RJ file...
Make this a hundred cycles (and you're probably flushing some caches
somewhere). That's 0.1 us on a 1GHz CPU.
The machine I'm typing this on can do 2 milllion short thin lines per
second. That's 0.5 us per
On Fri, 17 Oct 2003, David Fox wrote:
I think that the wisest approach is, instead of suggesting a kernel
module to the XFree86 folks, you do two things. First, suggest a kernel
module to the Linux folks that implements a protocol for accessing the
resource you are trying to use. Then you go
wjd wrote:
I works on redhat8,how can i get a window's name which contains a compound
text in X11 program?
I has tried:
XGetWindowProperty(Display*,Window,XA_WM_NAME,0,(long)BUFSIZ,
False,XA_STRING,actual_type,actual_format,
On Fri, 17 Oct 2003, Alexander Shopov wrote:
Hi guys,
I am tryng to update the docs about nvidia chips in XFree86.
I've checked out the sgml docs (module sgml) and the nv driver files
(directory xc/programs/Xserver/hw/xfree86/drivers/nv) (HEAD branch)
There is a man page in that directory.
On Thu, 2003-10-16 at 13:24, Mike A. Harris wrote:
Anyway, the check for /usr/X11R6/bin/X to determine wether or not
to start xfs has been removed for quite a while now, as it makes
it difficult for people to start xfs, who don't run an X server
on the same machine and just want to use xfs
Hi guys,
I checked driver man pages in xc/programs/Xserver/hw/xfree86/drivers/*/*.man
Almost every driver implements the options:
HWCursor, SWCursor however they are documented differently.
From an end user perspective I would like:
1. Them being the same throughout docs
2. Them being as explicit
Thank for your reply,i has run xwininfo directly,it told me this window has no name.I
just try xprop,i find it will export correct window name,could you tell where to get
the newest code of xprop?
Thanks
wjd wrote:
I works on redhat8,how can i get a window's name which contains a compound
On Fri, 17 Oct 2003, Alexander Shopov wrote:
Mark Vojkovich wrote:
On Fri, 17 Oct 2003, Alexander Shopov wrote:
xc/programs/Xserver/hw/xfree86/drivers/nv/nv.man is the
NVIDIA driver documentation. That's what I edit.
man page directly?
Yes.
It seems to me that this is
On Fri, Oct 17, 2003 at 11:35:12PM +0300, Alexander Shopov wrote:
Mark Vojkovich wrote:
On Fri, 17 Oct 2003, Alexander Shopov wrote:
xc/programs/Xserver/hw/xfree86/drivers/nv/nv.man is the
NVIDIA driver documentation. That's what I edit.
man page directly? It seems to me that this is
On Fri, Oct 17, 2003 at 02:15:20PM -0700, Tim Roberts wrote:
On Fri, 17 Oct 2003 23:44:57 +0300, Alexander Shopov wrote:
I checked driver man pages in xc/programs/Xserver/hw/xfree86/drivers/*/*.man
Almost every driver implements the options:
HWCursor, SWCursor however they are documented
On Fri, Oct 17, 2003 at 03:52:00PM -0400, Sheldon Lee-Wen wrote:
Pardon my evilness in cross posting this, But I need to get a discussion going
on how to resolve this problem.
One lineak user went and tested his keyboard. Here is what he got. It does
appear that for the keys that do not
13 matches
Mail list logo