From: Marshall Conover <marzhall.o@gmail.com>
To: "9fans@9fans.net" <9fans@9fans.net>
Subject: [9fans] The Case for Bind
Date: Thu, 14 Sep 2017 14:58:02 +0000 [thread overview]
Message-ID: <CAK0pxsHDGmk4jKV+WeOdV8u-oc4YB2sMQoz-uN67upG+utfhrA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1710 bytes --]
Hi All!
I've been exploring the Fuchsia operating system, and while they have
per-process namespaces, they don't have a utility like plan 9's bind, nor a
method of supporting it by default in their system libraries. I've made
some progress on adding it (https://imgur.com/HELWbrQ), but enthusiasm for
the concept seems lukewarm, and I'm coming to the point where I feel I'm
going to need to make a strong argument for why it should be a feature of
their per-process namespace filesystem. As someone who's neither on their
team nor an employee of google, I feel that I'm going to need to make a
damn good argument - and I'd very much like to, as it really, *really* is
something I'd like to have easily within reach in a modern OS, and it seems
like such a low-hanging fruit of a feature.
I have two scenarios currently I feel make a strong argument for the
inclusion of bind: one is running tests on an install of a product while
still being able to do development on it, by using a bind to redirect the
development dll to the install's dll in the process I'm developing in; and
the other an example of when a bind would just be convenient, such as a
certain process needing python2 instead of python3 on a system which
defaults to python 3, and have scripts that reference #/bin/python.
So, I'd like to hear the community's thoughts on other uses of bind. I
think they'd be useful both for making my case for bind, and in thinking
about my continuing implementation of the command. I also want to implement
union mounting in the future (which I can get very-close-to-being-free with
my changes for umount), but right now bind is my focus.
Thanks for your time.
Marshall
[-- Attachment #2: Type: text/html, Size: 1923 bytes --]
next reply other threads:[~2017-09-14 14:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-14 14:58 Marshall Conover [this message]
2017-09-14 15:11 ` Kurt H Maier
2017-09-14 19:55 ` Marshall Conover
2017-09-14 20:25 ` Kurt H Maier
2017-09-14 21:40 ` Marshall Conover
2017-09-14 23:46 ` Micah Stetson
2017-09-15 0:53 ` Marshall Conover
2017-09-15 1:14 ` Devon H. O'Dell
2017-09-15 2:01 ` Marshall Conover
2017-09-15 11:59 ` Marshall Conover
2017-09-17 21:06 ` Marshall Conover
2017-09-18 8:31 ` Giacomo Tesio
2017-09-18 12:15 ` Marshall Conover
2017-09-15 9:45 ` Giacomo Tesio
2017-09-14 22:22 ` Aleksandar Kuktin
[not found] <1312270110.2858999.1505498867019.ref@mail.yahoo.com>
2017-09-15 18:07 ` Brian L. Stuart
2017-09-15 19:54 ` Fran. J Ballesteros
2017-09-16 0:02 ` Chris McGee
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=CAK0pxsHDGmk4jKV+WeOdV8u-oc4YB2sMQoz-uN67upG+utfhrA@mail.gmail.com \
--to=marzhall.o@gmail.com \
--cc=9fans@9fans.net \
/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).