From: Russ Cox <rsc@swtch.com>
To: weigelt@metux.de, Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Design of webfs and webcookies
Date: Thu, 14 Jan 2010 10:25:20 -0800 [thread overview]
Message-ID: <dd6fe68a1001141025p7a5538fbxd5266db3d8311fcb@mail.gmail.com> (raw)
In-Reply-To: <20100113162339.GA24738@nibiru.local>
> but how do you get into that situation in the first place ?
> (more to the point: who starts these multiple instances ?)
cookiefs (or upas/fs, etc.) running on multiple terminals
connected to the same shared file server. or in multiple windows.
russ
next prev parent reply other threads:[~2010-01-14 18:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<bcba51a0912220638vb1867f3me65e9e799f9b6d87@mail.gmail.com>
2009-12-22 14:55 ` erik quanstrom
2009-12-22 17:56 ` Russ Cox
2010-01-05 15:03 ` Enrico Weigelt
2010-01-05 15:23 ` erik quanstrom
2010-01-13 16:23 ` Enrico Weigelt
2010-01-14 18:25 ` Russ Cox [this message]
2010-01-25 20:14 ` Ethan Grammatikidis
2010-01-25 20:59 ` erik quanstrom
2009-12-22 14:38 Dimitry Golubovsky
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=dd6fe68a1001141025p7a5538fbxd5266db3d8311fcb@mail.gmail.com \
--to=rsc@swtch.com \
--cc=9fans@9fans.net \
--cc=weigelt@metux.de \
/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).