Nope, i'm only using the one BSD Securelevels LSM. I'm gonna investigate further tomorrow if there isn't a simple fix but "rc" is an int returning that -22. Happen to know what thats about off the top? ;-) -- Christopher Warner On Wed, 2005-02-02 at 15:49 +0000, Jerone Young wrote: > Hmmm, > Do you have SELinux compiled into your kernel also? If so you cannot > use any other LSM with it. So to use BSD securelevels you have to > cutoff SELinux when you compile your kernel. > > On Tue, 01 Feb 2005 06:58:47 -0500, Christopher Warner > <chris@private> wrote: > > I'm having a problem with 2.6.10 on x86_64 arch. > > > > I've compiled BSD securelevel support into 2.6.10 (directly into the > > kernel and via a module) and am receiving the following error below: > > > > seclvl: seclvl_init: seclvl: Failure registering with the kernel. > > seclvl: seclvl_init: seclvl: Failure registering with primary security > > module. > > seclvl: Error during initialization: rc = [-22] > > > > However; > > Security Framework v1.0.0 initialized > > Capability LSM initialized > > > > Obviously it doesn't provide seclvl info on sys because it can't > > register. LSM has been compiled directly into the kernel and is loading > > fine so I'm at a loss as to why exactly it can't register. > > > > I haven't investigated much further, is this an int/arch problem? > > > > -- > > Christopher Warner > > > > - > > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > > the body of a message to majordomo@private > > More majordomo info at http://vger.kernel.org/majordomo-info.html > > Please read the FAQ at http://www.tux.org/lkml/ > >
This archive was generated by hypermail 2.1.3 : Tue Feb 01 2005 - 13:53:20 PST