9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Gorka guardiola" <paurea@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] replica's _* files
Date: Tue, 18 Apr 2006 15:08:01 +0200	[thread overview]
Message-ID: <599f06db0604180608o68d142bbi3acecf4077288230@mail.gmail.com> (raw)
In-Reply-To: <20060418125320.GA464@routi.local.net>

If I got it right, you didnt. This is for files which are already being executed
and loaded in demand so that, for example the rio *which is alredy running*
doesnt get broken if all the binary is not loaded yet. The file is already in
use, so the name doesnt get resolved again. As long as you dont delete
it will continue to be used even if you rename it.

On 4/18/06, Sascha Retzki <sretzki@gmx.de> wrote:
> On Tue, Apr 18, 2006 at 07:44:47PM +1000, Bruce Ellis wrote:
> > unfortunately this method does'nt solve the problem.
> > [...]
> > i'd rather them be rename in _i++.
> >
>
> Actually I reboot after an update automatically, exactly because of this
> problem; I don't see a reason for a renaming in the first place.
> Informing the user that he shall reboot should be enough.
>
>
> And, did I get it right, you rename files which may be executed, so how
> do these actually know about that? Something needs to be changed so
> that pages are loaded from _rio, else that prefixing-part is rendered
> useless.
>
>
> So it is probably just me who sees "bloat" here... my two cents
>
>


--
- curiosity sKilled the cat


  reply	other threads:[~2006-04-18 13:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-17 21:04 Lluís Batlle i Rossell
2006-04-17 22:24 ` Russ Cox
2006-04-18  9:44   ` Bruce Ellis
2006-04-18 12:53     ` Sascha Retzki
2006-04-18 13:08       ` Gorka guardiola [this message]
2006-04-19  1:02 geoff
2006-04-19 14:12 ` Ronald G Minnich

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=599f06db0604180608o68d142bbi3acecf4077288230@mail.gmail.com \
    --to=paurea@gmail.com \
    --cc=9fans@cse.psu.edu \
    /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;
as well as URLs for NNTP newsgroup(s).