From: raingloom <raingloom@riseup.net>
To: 9front@9front.org
Subject: Re: [9front] Help wanted tracking down a bug in divergefs code
Date: Thu, 20 Feb 2020 00:50:22 +0100 [thread overview]
Message-ID: <1582156222.770.0@riseup.net> (raw)
In-Reply-To: <1581969796.5020.0@riseup.net>
Since I'm also struggling with some error, I'll put this here. Maybe
it'll be helpful to someone.
https://git.sr.ht/~raingloom/divergefs
Anyone else has patches / forks of it?
The bugs I'm working on are documented in the TODO file of
https://git.sr.ht/~raingloom/package
(sorry for the top reply, my other mailing client borked and this one
doesn't let me bottom reply)
On Mon, Feb 17, 2020 at 21:03, raingloom <raingloom@riseup.net> wrote:
> Oh dang, I've been looking for this. Also struggling with divergefs
> weirdness, but this seems so much simpler.
>
> On Mon, Feb 17, 2020 at 16:44, kvik@a-b.xyz wrote:
>> Unfortunately I can't help you with divergefs problem; I am
>> not familiar with the code and I don't feel like dissecting it
>> at the time.
>>
>> If I may instead shamelessly plug unionfs(4) for the task at hand:
>> git://code.a-b.xyz/unionfs
>> or
>> http://code.a-b.xyz/unionfs/snapshot/unionfs-master.tar.gz
>>
>> ; ramfs
>> ; bind /sys/src /mnt/src
>> ; unionfs -m /sys/src /tmp /mnt/src
>> ; @{cd /sys/src; mk install}
>
>
next prev parent reply other threads:[~2020-02-19 23:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-16 9:18 Trevor Higgins
2020-02-17 5:59 ` [9front] " ori
2020-02-20 1:08 ` [9front] Help wanted tracking down a bug in divergefs code [Demonstration code] Trevor Higgins
2020-02-17 15:44 ` [9front] Help wanted tracking down a bug in divergefs code kvik
2020-02-17 20:03 ` raingloom
2020-02-19 23:50 ` raingloom [this message]
2020-02-20 1:25 ` [9front] Help wanted tracking down a bug in divergefs code [unionfs] Trevor Higgins
2020-02-20 11:21 ` kvik
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=1582156222.770.0@riseup.net \
--to=raingloom@riseup.net \
--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).