On Fri, Dec 12, 2008 at 12:00:21AM -0500, Ted Unangst wrote: > wondering why things stopped working after an upgrade, it took me a > little while to remember that lpr was overwritten. but then it took a > while longer to find cups-enable, even after I remembered that I > needed to run it, because it's not cupsenable, which is the only one > that shows up when I type cups[tab]. I spent a good amount of time > trying to find a program with a name just like cupsenable but that > wasn't cupsenable.
pkg_info -L cups | grep enable > Why is cups-enable installed only runnable by root? It's harder to > find this way. And why can't a normal user even read it? It already > checks that you're root before doing anything, and we have tons of > things that aren't useful to users but are still runnable. good point. > It's also not mentioned by pkg_info as something of interest. It > should be, right? pkg_info -M cups this message is also displayed when cups is installed. > While on the subject, the lpd.pre-cups test is a little broken. I had > my old lpd backed up (pre-upgrade). Now the 4.4 tools are gone, and > the backups are from 4.3 or whenever. well, it's been like that for close to 4 years now. anyway, how will the script know if the backed-up files are from a previous release? should the backups use `uname -r` in their names? or if it finds a backed-up file, should it ask again if you're sure you want to continue? -- [email protected] SDF Public Access UNIX System - http://sdf.lonestar.org
