public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: James Cassidy <jcassidy@cs.kent.edu>
To: ebuddington@wesleyan.edu
Cc: linux-kernel@vger.kernel.org
Subject: Re: Dissociating process from bin's filesystem
Date: Wed, 24 Apr 2002 23:42:28 -0400	[thread overview]
Message-ID: <20020425034227.GA445@qfire.net> (raw)
In-Reply-To: <20020424224714.B19073@ma-northadams1b-46.bur.adelphia.net>

[-- Attachment #1: Type: text/plain, Size: 873 bytes --]


    You could always copy the process to a RAM filesystem like tmpfs
or a ramdisk. 

On Wed, Apr 24, 2002 at 10:47:14PM -0400, Eric Buddington wrote:
> Is there any way to dissociate a process from its on-disk binary?  In
> other words, I want to start 'foo_daemon', then unmount the filesystem
> it started from. It seems to me this would be reasonably accomplished
> by loading the binary completely into memory first ro eliminate the
> dependence.
> 
> Is this possible, or planned? Are there intractable problems with it
> that I don't see?
> 
> Eric Buddington
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
						-- James Cassidy (QFire)

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

  reply	other threads:[~2002-04-25  3:42 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 [this message]
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

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=20020425034227.GA445@qfire.net \
    --to=jcassidy@cs.kent.edu \
    --cc=ebuddington@wesleyan.edu \
    --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