Path: utzoo!attcan!uunet!cs.utexas.edu!rutgers!mcnc!duke!juliet!khera From: khera@juliet.cs.duke.edu (Vick Khera) Newsgroups: comp.windows.x Subject: what i want in R5 Keywords: xhost,fixed paths Message-ID: <20629@duke.cs.duke.edu> Date: 5 Jul 90 16:17:59 GMT Sender: news@duke.cs.duke.edu Lines: 34 I would like to see the following in the next release of X11: 1. a better mechanism than xhost for security. a per-user list would be perfect, allowing the list to be used as a kerberos access control list if kerberos was available. if not available, then it could be used similarly to the current host list. i am attempting to implement something like this presently. 2. remove the need to install X in /usr/*/X11. some of us have to keep other versions around for various reasons, and forcing the location is inconvenient at best. the directory should be completely configuration file dependent. i have had to directly modify several source files to change the location, as well as specify it in the config files. along the same lines, in the makedepend program, the gcc-include directory should not be hard-coded, but also specified in a config file. not everyone installs gcc in /usr/local (we install it in /usr/gnu.) at the very least, these changes should be documented with the installation notes, not just as an errata sheet that everyone may not get. 3. there should be some way to determine which release a particular vendor's X implementation is based on. for example, i write a client that must run on a release 4 server. how can i tell if a particular vendor's X server supports release 4 or not? i can't very well have a table of all vendor names and release numbers to check against. vick. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Vick Khera (919) 660-6528 Department of Computer Science ARPA: khera@cs.duke.edu Duke University UUCP: ..!{mcnc,decvax}!duke!khera Durham, NC 27706