public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Friesen <cfriesen@nortelnetworks.com>
To: Rob Landley <landley@trommello.org>
Cc: ebuddington@wesleyan.edu,
	Eric Buddington <eric@ma-northadams1b-46.bur.adelphia.net>,
	linux-kernel@vger.kernel.org
Subject: Re: Dissociating process from bin's filesystem
Date: Thu, 25 Apr 2002 13:52:46 -0400	[thread overview]
Message-ID: <3CC8426E.B2DBDCE@nortelnetworks.com> (raw)
In-Reply-To: <20020424224714.B19073@ma-northadams1b-46.bur.adelphia.net> <20020425184801.60BDC742@merlin.webofficenow.com>

Rob Landley wrote:
> 
> On Wednesday 24 April 2002 10:47 pm, Eric Buddington wrote:
> > Is there any way to dissociate a process from its on-disk binary?
> 
> Sure.  Fire up an instance of ramfs, copy the file there (and its associated
> libraries), chroot and exec the copy on ramfs.  Sort of like initrd in
> reverse. :)

If you're writing the binary in question, you could use mlockall() which ensures
that you won't need to page in bits of the binary from disk.  I don't know if
the filesystem considers this totally dissociated though, but it might be good
enough for what you want.

Chris

-- 
Chris Friesen                    | MailStop: 043/33/F10  
Nortel Networks                  | work: (613) 765-0557
3500 Carling Avenue              | fax:  (613) 765-2986
Nepean, ON K2H 8E9 Canada        | email: cfriesen@nortelnetworks.com

      reply	other threads:[~2002-04-25 18:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-25  2:47 Dissociating process from bin's filesystem Eric Buddington
2002-04-25  3:42 ` James Cassidy
2002-04-25  8:52 ` john slee
2002-04-25  9:22   ` johan.adolfsson
2002-04-25 11:42 ` Padraig Brady
2002-04-27 19:03   ` Eric W. Biederman
2002-04-25 12:28 ` Rob Landley
2002-04-25 17:52   ` Chris Friesen [this message]

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=3CC8426E.B2DBDCE@nortelnetworks.com \
    --to=cfriesen@nortelnetworks.com \
    --cc=ebuddington@wesleyan.edu \
    --cc=eric@ma-northadams1b-46.bur.adelphia.net \
    --cc=landley@trommello.org \
    --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