public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: devzero@web.de
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: Laurent.Vivier@bull.net, linux-kernel@vger.kernel.org, pavel@ucw.cz
Subject: Re: [PATCH] Allow NBD to be used locally
Date: Sat, 02 Feb 2008 18:31:48 +0100	[thread overview]
Message-ID: <141350930@web.de> (raw)

> 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.

> This still does not account for compressed disk images, for example.
unfortunately, not




> 
> 
> On Feb 2 2008 15:40, devzero@web.de wrote:
> >
> >>In fact, VMware uses local nbd today for its vmware-loop helper
> >>utility, most likely because of the above-mentioned reasons. (Though
> >>it quite often hung last time I tried.)
> >
> >seems this will go away. recent vmware versions (e.g. server 2.0
> >beta) have a fuse based replacement for that.
> 
> How will that work? Fuse makes up a filesystem - not helpful
> if you have a raw disk without a known fs to mount.
> 
> >>So what we have is non-linearity -- LBA 22 comes after LBA 40 -- loop
> >>does not deal with that.
> >
> >maybe dm-loop does? http://sources.redhat.com/lvm2/wiki/DMLoop
> 
> This still does not account for compressed disk images, for example.
> 
> 


________________________________________________________
Bis 50 MB Dateianhänge? Kein Problem!
http://www.digitaledienste.web.de/freemail/club/lp/?lp=7


             reply	other threads:[~2008-02-02 17:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-02 17:31 devzero [this message]
2008-02-03  0:54 ` [PATCH] Allow NBD to be used locally Jan Engelhardt
2008-02-03  6:02   ` Kyle Moffett
  -- 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=141350930@web.de \
    --to=devzero@web.de \
    --cc=Laurent.Vivier@bull.net \
    --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