Hi, The second error line implies you do in fact have another security module loaded, which is the primary. I'm guessing you have capabilities either compiled into the kernel, or loaded as a module? If not, there's a major LSM problem on x86_64 corruping security_ops, but then your machine shouldn't run at all... -serge Quoting Christopher Warner (chris@private): > 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
This archive was generated by hypermail 2.1.3 : Tue Feb 01 2005 - 16:18:54 PST