mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Richard B. Johnson" <root@chaos.analogic.com>
To: "Laughlin, Joseph V" <Joseph.V.Laughlin@boeing.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Modifying kernel so that non-root users have some root capabilities
Date: Tue, 25 May 2004 07:28:35 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.53.0405250724490.2512@chaos> (raw)
In-Reply-To: <67B3A7DA6591BE439001F2736233351202B47E6F@xch-nw-28.nw.nos.boeing.com>

On Mon, 24 May 2004, Laughlin, Joseph V wrote:

> (not sure if this is a duplicate or not.. Apologies in advance.)
>
> 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
>
> Anyone got any ideas about how I could start doing this?  (I'm new to
> kernel development, btw.)
>
> Thanks,

You don't modify an operating system to do that!! You just make
a priviliged program (setuid) that does the things you want.

You can even transparently send the requests to your daemon so that
existing programs that expect to do such things don't need to
be modified (hint LD_PRELOAD).

Cheers,
Dick Johnson
Penguin : Linux version 2.4.26 on an i686 machine (5570.56 BogoMips).
            Note 96.31% of all statistics are fiction.



  parent reply	other threads:[~2004-05-25 11:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-24 22:21 Laughlin, Joseph V
2004-05-24 23:24 ` Steve Youngs
2004-05-24 23:29 ` Neale Banks
2004-05-25 11:28 ` Richard B. Johnson [this message]
2004-05-25 18:14   ` Bill Davidsen
2004-05-25 14:57 ` David T Hollis
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=Pine.LNX.4.53.0405250724490.2512@chaos \
    --to=root@chaos.analogic.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

all inboxes | Powered by JetHome®