From: "Ethan Gardener" <eekee57@fastmail.fm>
To: 9front@9front.org
Subject: Re: [9front] rio wishlists
Date: Tue, 21 Jan 2020 08:54:27 +0000 [thread overview]
Message-ID: <39c448c0-c50d-4db8-b3d6-6c7960bfe688@www.fastmail.com> (raw)
In-Reply-To: <CAFSF3XPHOhVuSgyv2MtCbaP_4DV3KDRZ+xB0K+LbYrXE1CVBag@mail.gmail.com>
On Sat, Jan 18, 2020, at 8:19 AM, hiro wrote:
> i like the idea of having only one layer of namespace separation in rio, i.e.
> windows inside a subrio could all just share the same parent ns. would be
> useful for me not to have to post every window's ns ressources in a
> /srv. and the top-level rio would still allow separation (and by
> default).
> not sure i need a window manager for that :)
>
> the main problem is that right now rio terminals have their own ns so
> that they can have their own /dev/* files per window, bound there for
> them by rio.
> but there should be a way to allow partial sharing of namespaces, i.e.
> all other files.
If all programs prefixed an environment variable to their /dev files, rio wouldn't need to namespace at all, just fork the environment for each window (rfork e). Most of the prefixing cases could be handled by small changes to existing libraries.
next prev parent reply other threads:[~2020-01-21 8:54 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <134490038A9377D966659F986F257F34@ewsd.inri.net>
2020-01-17 14:43 ` [9front] Bounties Ethan Gardener
2020-01-17 16:05 ` kvik
2020-01-17 21:55 ` Silas McCroskey
2020-01-18 0:23 ` rio wishlists Lyndon Nerenberg
2020-01-18 0:40 ` [9front] " Stanley Lieber
[not found] ` <CAFSF3XNfdhb+ViOBmVMQ+5+PnSjCeD+9a9p9e4Ug0EX9==aZvw@mail.gmail.com>
2020-01-18 8:19 ` hiro
2020-01-18 9:53 ` Steve Simon
2020-01-18 10:19 ` hiro
2020-01-21 8:54 ` Ethan Gardener [this message]
2020-01-21 8:57 ` Ethan Gardener
2020-01-21 9:49 ` hiro
2020-01-22 16:30 ` Ethan Gardener
2020-01-22 16:47 ` hiro
2020-01-23 15:09 ` Ethan Gardener
[not found] ` <CAK0pxsHVpyae1+teTSOAFp=nBoq_r7-aKexh_X=hEDe7hUcReA@mail.gmail.com>
[not found] ` <CAK0pxsFDk=C_+37tKzU=U-TMQLTPcW6MOQ1sgKNBrYhWrj4Bwg@mail.gmail.com>
2020-01-23 18:12 ` Marshall Conover
2020-01-23 21:23 ` hiro
2020-01-23 22:42 ` Julius Schmidt
2020-01-24 0:39 ` Ethan Gardener
2020-01-24 0:44 ` Ethan Gardener
2020-01-23 23:50 ` Ethan Gardener
2020-01-24 0:59 ` Jeremy Jackins
2020-01-24 10:04 ` hiro
2020-01-21 8:37 ` [9front] Bounties Ethan Gardener
2020-01-22 17:04 ` Ori Bernstein
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=39c448c0-c50d-4db8-b3d6-6c7960bfe688@www.fastmail.com \
--to=eekee57@fastmail.fm \
--cc=9front@9front.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;
as well as URLs for NNTP newsgroup(s).