From: "Remy Bohmer" <l.pinguin@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Fwd: [OOPS] on 2.6.20-rc5-rt10
Date: Tue, 30 Jan 2007 16:50:22 +0100 [thread overview]
Message-ID: <3efb10970701300750m22519ab1w30f2e6f468468431@mail.gmail.com> (raw)
In-Reply-To: <3efb10970701300749h68f868eew37b115ad2719c9f@mail.gmail.com>
---------- Forwarded message ----------
From: Remy Bohmer <l.pinguin@gmail.com>
Date: 30 jan 2007 16:49
Subject: Re: [OOPS] on 2.6.20-rc5-rt10
To: Michal Schmidt <xschmi00@stud.feec.vutbr.cz>
Hello Michal,
This cap_over driver is a capability driver to give certain processes
extra capabilities, this makes it possible to run them under a normal
user account. It is an inheritance from the time we used a
distribution that did not have support for SE-Linux.
You can find it at: http://www.randombit.net/projects/cap_over/
But, I do not think it is a nice solution, and I will replace it soon
by the default SELinux implementation of FC6.
Kind Regards,
Remy Bohmer
2007/1/30, Michal Schmidt <xschmi00@stud.feec.vutbr.cz>:
> Remy Bohmer wrote:
> > Hello All,
> >
> > Once in a while we see the following stacktrace.
> > We do not know yet the exact condition that generates this, but is
> > there anyone that recognises this oops?
> >
> > Kind Regards,
> >
> > Remy Bohmer
> >
> > [...]
> > Jan 30 14:09:20 localhost kernel: Modules linked in: cap_over
> > commoncap i2c_dev uhci_hcd i2c_i801 i2c_core ehci_hcd
>
> What's the cap_over module? I can't find it in my kernel anywhere.
> Michal
>
>
next prev parent reply other threads:[~2007-01-30 15:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-30 14:30 Remy Bohmer
2007-01-30 14:45 ` Michal Schmidt
[not found] ` <3efb10970701300749h68f868eew37b115ad2719c9f@mail.gmail.com>
2007-01-30 15:50 ` Remy Bohmer [this message]
2007-01-30 15:02 ` Karsten Wiese
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3efb10970701300750m22519ab1w30f2e6f468468431@mail.gmail.com \
--to=l.pinguin@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@bohmer.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®