Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!uunet!super!rminnich From: rminnich@super.ORG (Ronald G Minnich) Newsgroups: comp.windows.x Subject: Re: xterm, xload, and X libraries in non-standard locations Message-ID: <22078@metropolis.super.ORG> Date: 8 Mar 90 20:11:08 GMT References: <9003061606.AA17990@nswc-wo.arpa> Sender: news@super.ORG Reply-To: rminnich@metropolis.UUCP (Ronald G Minnich) Organization: Supercomputing Research Center, Bowie, Md. Lines: 15 In article tale@cs.rpi.edu (David C Lawrence) writes: >In <9003061606.AA17990@nswc-wo.arpa> cwarsaw@NSWC-WO.ARPA (Warsaw): >> According to the ERRATA, xterm and xload must be linked statically. >Only if you make them setuid to root. You don't have to do that at >all with xload to get full functionality and you (well, I) can live no, if you make them sgid kmem it fails too. How do you get full functionality out of xload if you can't read kmem? Or do you make kmem world-readable? I don't get it. ron -- ------------------------------------------------------------------------------ "If the future of CD-ROM is pinned to the | rminnich@super.org imaginations of IBM, Microsoft, and Intel, | uunet!super!rminnich we're in real trouble". - author unknown |