From: Casey Schaufler <casey@schaufler-ca.com>
To: Andi Kleen <andi@firstfloor.org>, David <david@unsolicited.net>
Cc: casey@schaufler-ca.com, Mike Galbraith <efault@gmx.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.25 Kernel - Problems with capabilities
Date: Sun, 20 Apr 2008 15:04:20 -0700 (PDT) [thread overview]
Message-ID: <898767.43890.qm@web36607.mail.mud.yahoo.com> (raw)
In-Reply-To: <87y7788hul.fsf@basil.nowhere.org>
--- Andi Kleen <andi@firstfloor.org> wrote:
> David <david@unsolicited.net> writes:
>
> > Casey Schaufler wrote:
> >> Do you have a libcap that reflects the change from 32 capabilities
> >> to 64? You'll be looking for libcap.so.2.06 or thereabouts.
> >>
> > Adding libcap-2.08 and recompiling ntpd has fixed the issue, and I'm
> > now running normally, thanks!
>
> FWIW I ran into this problem too with systemtap. It was a quite
> nasty surprise and took some time to track down.
>
> I also don't remember seeing a thread about this on l-k. Where was this
> major binary breakage discussed?
lkml and lsm.
Casey Schaufler
casey@schaufler-ca.com
next prev parent reply other threads:[~2008-04-20 22:04 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-19 18:43 2.6.25 Kernel - Problems with capabilities David
[not found] ` <1208676743.4763.10.camel@marge.simson.net>
2008-04-20 14:09 ` David
2008-04-20 17:15 ` Casey Schaufler
2008-04-20 17:29 ` David
2008-04-20 19:08 ` Andi Kleen
2008-04-20 22:04 ` Casey Schaufler [this message]
2008-04-20 22:36 ` Andi Kleen
2008-04-21 0:00 ` serge
2008-04-21 0:44 ` Andrew Morgan
2008-04-21 7:20 ` David R
2008-04-21 7:01 ` David R
2008-04-21 18:34 ` serge
2008-04-21 18:48 ` David
2008-04-21 19:01 ` serge
2008-04-21 20:28 ` David
2008-04-22 2:42 ` serge
2008-04-22 5:29 ` Andrew G. Morgan
2008-04-22 5:54 ` David R
2008-04-20 22:21 ` Andrew Morton
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=898767.43890.qm@web36607.mail.mud.yahoo.com \
--to=casey@schaufler-ca.com \
--cc=andi@firstfloor.org \
--cc=david@unsolicited.net \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
/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