9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Stuart Morrow <morrow.stuart@gmail.com>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] 9Front / cwfs64x and hjfs storage
Date: Thu, 7 Jan 2021 21:28:45 +0000	[thread overview]
Message-ID: <CABB-WO-eFdk8GSp6axmyL9QvVYpNKcJE-mWr8TubfkL8SJfUaQ@mail.gmail.com> (raw)
In-Reply-To: <b60f836e-c27f-4463-b6bb-e5a2c1a25346@sirjofri.de>

On 29/12/2020, sirjofri <sirjofri+ml-9fans@sirjofri.de> wrote:
> ori's new filesystem

What's this? and why is it needed? Hjfs already fixes the worst thing
about cwfs already (needing to copy files from one partition to
another on the same disk).

Though speaking of new file servers, the Irssi /upgrade trick would be
good to have. (Save needed state to disk, exec new version in current
process, and tell it to pick up where we left off. The 'trick' is we
need not close any network connections.)

------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Tc951a224dde6dde5-Mb12f611a58a194f4bac92d97
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

  parent reply	other threads:[~2021-01-07 21:29 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-28 23:55 joey
2020-12-29  2:27 ` Ethan Gardener
2020-12-29  8:53   ` sirjofri
2020-12-29  9:15     ` Kurt H Maier
2020-12-29  9:21       ` sirjofri
2021-01-07 21:28     ` Stuart Morrow [this message]
2021-01-07 23:25       ` ori
2021-02-08  1:35   ` Ryan
2021-02-08  6:14     ` Ethan Gardener
2020-12-29 13:06 ` Alex Musolino
2020-12-29 16:14   ` Ethan Gardener
2020-12-30  8:08     ` joey
2021-02-04 23:10       ` rt9f.3141
2021-02-05  2:51         ` rt9f.3141
2021-02-05  3:06         ` Alex Musolino
2021-02-07  6:37           ` rt9f.3141
2021-02-07 22:54             ` rt9f.3141

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=CABB-WO-eFdk8GSp6axmyL9QvVYpNKcJE-mWr8TubfkL8SJfUaQ@mail.gmail.com \
    --to=morrow.stuart@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).