9front - general discussion about 9front
 help / color / mirror / Atom feed
From: sirjofri <sirjofri+ml-9front@sirjofri.de>
To: 9front@9front.org
Subject: Re: [9front] mycroftiv's zrv and rfork V, patch for current 9front
Date: Wed, 6 Jan 2021 20:02:40 +0000 (UTC)	[thread overview]
Message-ID: <2258e85e-0fe5-4c8d-9376-f044aaf732bd@sirjofri.de> (raw)
In-Reply-To: <3352C30E7FABA4B1547D228A5403FC9B@eigenstate.org>

Hello again,

the included patch is indeed mycroftiv's work without many adjustments. 
We just made it work in current 9front code.

Also I did forget to attach the devzrv.c. devzrv btw is the same as srv 
but doesn't fork. It is possible to srvfs the forked srvs in zrv.

Sure, there are much cleaner solutions. Using #s/clone as ori suggested 
would be a nice kernel-based solution (instead of a fully userspace 
implementation I can also imagine).

Another idea I can think of would be similar to #σ. Imagine mkdir 
'#s/newsrv' && bind -c '#/newsrv' /srv or even like some mntgen without 
the mkdir. This would break compatibility!

More compatible would be something like echo newsrv > '#sc' && bind '#s' 
/srv. This would be more compatible to current implementation.

In both ideas the newsrv is just an arbitrary name.

sirjofri

  reply	other threads:[~2021-01-06 20:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-06 10:17 sirjofri+ml-9front
2021-01-06 19:05 ` cinap_lenrek
2021-01-06 19:11   ` ori
2021-01-06 20:02     ` sirjofri [this message]
2021-01-06 22:28       ` cinap_lenrek
2021-01-07 20:55         ` Stuart Morrow
2021-01-07 14:04       ` sirjofri+ml-9front
2021-01-07  1:12     ` [9front] happy new year cinap_lenrek

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=2258e85e-0fe5-4c8d-9376-f044aaf732bd@sirjofri.de \
    --to=sirjofri+ml-9front@sirjofri.de \
    --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).