Hmm, good point.  I guess it's not x11 specific, just that x11 is the
most common use.  So it probably makes sense to keep it in the sysutils
category with x11 referenced.  Sorry for the noise...

Simon.
--
"Johnny C. Lam" wrote:

> I'm not sure.  The code was unrelated to the X11 code, except that it
> could be used by a setuid-root process to access memory (from what I
> understand), so I stuck it under 'sysutils'.  Feel free to move it if
> you think it's more appropriately classified under 'x11'.
> 
>      -- Johnny C. Lam <lamj@stat.cmu.edu>
>         Department of Statistics, Carnegie Mellon University
>         http://www.stat.cmu.edu/~lamj/
> 
> Simon Burge <simonb@netbsd.org> writes:
> > > XFree86 Framebuffer "aperture" driver for NetBSD
> > 
> > Wouldn't this make more sense on the x11 category (where things like
> > XF86Setup already exist)?  I know that the package has x11 in the
> > CATEGORIES list, but if I were looking quickly for this I'd check the
> > x11 directory first...
> > 
> > Simon.
>