LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "BuraphaLinux Server" <buraphalinuxserver@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: at program breaks with kernel 2.6.24
Date: Wed, 27 Feb 2008 19:27:44 +0700 [thread overview]
Message-ID: <5d75f4610802270427y789ffae9ie2682059206eed51@mail.gmail.com> (raw)
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=463669
I have the same problem - it is not debian specific. Did the
semantics of kill() change with the new kernel? I thought as long as
something is setuid, even with capability stuff around the setuid
programs just get _all_ capabilities and would keep working.
I did a good search and found many people with the problem, but no
solutions except going back to 2.6.23.x kernels. I guess you'll flame
me, but at least include a link to the solution too.
next reply other threads:[~2008-02-27 12:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-27 12:27 BuraphaLinux Server [this message]
2008-02-27 13:41 ` Jiri Kosina
2008-02-27 18:17 ` serge
2008-02-27 19:36 ` Frans Pop
2008-02-27 19:47 ` BuraphaLinux Server
2008-02-28 3:00 ` serge
2008-02-28 5:23 ` BuraphaLinux Server
2008-02-28 14:54 ` serge
2008-02-28 17:19 ` serge
2008-02-28 17:51 ` BuraphaLinux Server
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=5d75f4610802270427y789ffae9ie2682059206eed51@mail.gmail.com \
--to=buraphalinuxserver@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--subject='Re: at program breaks with kernel 2.6.24' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).