From: Steve Youngs <steve@youngs.au.com>
To: Linux Kernel List <linux-kernel@vger.kernel.org>
Cc: "Laughlin, Joseph V" <Joseph.V.Laughlin@boeing.com>
Subject: Re: Modifying kernel so that non-root users have some root capabilities
Date: Tue, 25 May 2004 09:24:17 +1000 [thread overview]
Message-ID: <microsoft-free.8765alo1cu.fsf@youngs.au.com> (raw)
In-Reply-To: <67B3A7DA6591BE439001F2736233351202B47E6F@xch-nw-28.nw.nos.boeing.com> (Joseph V. Laughlin's message of "Mon, 24 May 2004 15:21:56 -0700")
* Joseph V Laughlin <Laughlin> writes:
> I've been tasked with modifying a 2.4 kernel so that a non-root user can
> do the following:
> Dynamically change the priorities of processes (up and down)
> Lock processes in memory
> Can change process cpu affinity
I'm assuming that there are user-land tools to do these things now for
root, right? So why not look into things like sudo(8) or even setuid
executables?
--
|---<Steve Youngs>---------------<GnuPG KeyID: A94B3003>---|
| Ashes to ashes, dust to dust. |
| The proof of the pudding, is under the crust. |
|----------------------------------<steve@youngs.au.com>---|
next prev parent reply other threads:[~2004-05-24 23:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-24 22:21 Modifying kernel so that non-root users have some root capabilities Laughlin, Joseph V
2004-05-24 23:24 ` Steve Youngs [this message]
2004-05-24 23:29 ` Neale Banks
2004-05-25 11:28 ` Richard B. Johnson
2004-05-25 18:14 ` Bill Davidsen
2004-05-25 14:57 ` David T Hollis
-- strict thread matches above, loose matches on Subject: below --
2004-05-24 23:41 Laughlin, Joseph V
2004-05-24 23:49 ` Chris Wright
[not found] <fa.nbdv424.kmij3i@ifi.uio.no>
2004-05-24 23:43 ` Andy Lutomirski
2004-05-25 19:06 Laughlin, Joseph V
2004-05-25 21:15 ` Bill Davidsen
2004-05-25 23:43 Roger Larsson
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=microsoft-free.8765alo1cu.fsf@youngs.au.com \
--to=steve@youngs.au.com \
--cc=Joseph.V.Laughlin@boeing.com \
--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