From: Benjamin Riefenstahl <b.riefenstahl@turtle-trading.net>
To: Steve Simon <steve@quintile.net>
Cc: 9front@9front.org
Subject: Re: [9front] Invers of partfs
Date: Fri, 11 Feb 2022 12:44:34 +0100 [thread overview]
Message-ID: <87iltlmxul.fsf@turtle-trading.net> (raw)
In-Reply-To: <2B66F3F0-47FA-4FC4-B6CD-ECDDC16A514D@quintile.net> (Steve Simon's message of "Thu, 10 Feb 2022 19:07:03 +0000")
Hi Steve,
Steve Simon writes:
> unmount?
I tried that, but although the name in /dev is called a "mountpoint" in
the man page, unmount claims it doesn't know anything about it.
> probably the easiest would be to put your tests in a script with
> “rfork ne” at the top.
>
> this will ensure that when your script ends the namespace and
> environment will evaporate. partfs will also close as its input is
> closed as part of the namspace going.
Ah, thinking in namespaces, nice! Yes, a subprocess like that should
work fine, thank you.
so long, benny
next prev parent reply other threads:[~2022-02-11 11:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-10 17:42 Benjamin Riefenstahl
2022-02-10 19:07 ` Steve Simon
2022-02-11 11:44 ` Benjamin Riefenstahl [this message]
2022-02-14 19:06 ` Benjamin Riefenstahl
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=87iltlmxul.fsf@turtle-trading.net \
--to=b.riefenstahl@turtle-trading.net \
--cc=9front@9front.org \
--cc=steve@quintile.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).