On Mon, 2005-11-14 at 17:37 -0500, Dale Pontius wrote: > Peter Shaw wrote: > > >On Monday 14 November 2005 02:51, Dale Pontius wrote: > > > > > >>I decided to try running BIND on the SELinux system. I get this message: > >> * Starting named ... > >>named: capset failed: Operation not permitted: please ensure that the > >>capset kernel module is loaded. see insmod(8) > >> > >>I've made sure that "commoncap" was built and loaded prior to trying to > >>start BIND. A bit > >>of google searching, and this seemed to have helped everyone else, but > >>not me. > >> > >> > >I had the same problem and googled it, and the module I found I had to put > >into /etc/modules.autoload.d/kernel-2.6 was ¨capability¨, not ¨commoncap¨. > >But perhaps you´re using a 2.4 kernel and it´s different - i just subscribed > >to the mailing list and didn´t see the original post. > > > > > I saw the "capability" stuff too, and thought that was the same as > "commoncap". So > now I have to ask... Where do you turn on "capability"? I did a "grep > CAP .config" > and got only 2 entries, the one that produced commoncap, and another > that was > completely unrelated. (sound, maybe?) I'm running 2.6, by the way. in the kernel security options: CONFIG_SECURITY_CAPABILITIES=y module name: 'capability'
Antoine -- [email protected] mailing list
