From: "Kyle Moffett" <kyle@moffetthome.net>
To: "Jan Engelhardt" <jengelh@computergmbh.de>
Cc: devzero@web.de, Laurent.Vivier@bull.net,
linux-kernel@vger.kernel.org, pavel@ucw.cz
Subject: Re: [PATCH] Allow NBD to be used locally
Date: Sun, 3 Feb 2008 01:02:18 -0500 [thread overview]
Message-ID: <f73f7ab80802022202s2c695a8fjea20e5092e9c5dcc@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0802021834380.18790@fbirervta.pbzchgretzou.qr>
Whoops, only hit "Reply" on the first email, sorry Jan.
On Feb 2, 2008 7:54 PM, Jan Engelhardt <jengelh@computergmbh.de> wrote:
> On Feb 2 2008 18:31, devzero@web.de wrote:
> >
> >> How will that work? Fuse makes up a filesystem - not helpful
> >> if you have a raw disk without a known fs to mount.
> >
> >take zfs-fuse or ntfs-3g for example.
> >you have a blockdevice or backing-file containing data structures and fuse makes those show up as a filesystem.
> >i think vmware-mount is not different here.
>
> vmware-mount IS different, it provides the _block_ device,
> which is then mounted through the usual mount(2) mechanism
> (if there is a filesystem driver for it).
As far as I can tell, vmware-mount should be re-implemented as a
little perl script around "dmsetup" and/or "losetup", possibly with
"dm-userspace" patched into the kernel to allow you to handle
non-mapped blocks in your userspace daemon when somebody tries to
access them. If you don't need that ability then straight dm-loop and
dm-linear will work.
Cheers,
Kyle Moffett
next prev parent reply other threads:[~2008-02-03 6:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-02 17:31 devzero
2008-02-03 0:54 ` Jan Engelhardt
2008-02-03 6:02 ` Kyle Moffett [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-02-02 14:40 devzero
2008-02-02 16:57 ` Jan Engelhardt
2008-02-01 13:25 Laurent Vivier
2008-02-02 11:23 ` Pavel Machek
2008-02-02 11:52 ` Jan Engelhardt
2008-02-02 15:26 ` Laurent Vivier
2008-02-02 16:13 ` Miklos Szeredi
2008-02-02 20:54 ` Pavel Machek
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=f73f7ab80802022202s2c695a8fjea20e5092e9c5dcc@mail.gmail.com \
--to=kyle@moffetthome.net \
--cc=Laurent.Vivier@bull.net \
--cc=devzero@web.de \
--cc=jengelh@computergmbh.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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
all inboxes | Powered by JetHome®