mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Martin Nybo Andersen <tweek@tweek.dk>
To: Tom Watson <tsw@johana.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Offset into block file for mounting?
Date: Mon, 3 Jan 2011 15:25:25 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.00.1101031518410.12757@odin.tweek.dk> (raw)
In-Reply-To: <1294060384.3030.18.camel@xytar7a>

Hi Tom,

On Mon, 3 Jan 2011, Tom Watson wrote:

> Hi...
>
> I recently got a "floppy drive emulator" that uses an USB thumb drive to
> emulate floppy images to be used as a floppy drive.  In trying out the
> software (it is a bit cryptic), I found that this model stores the
> floppy images consecutively on said thumb drive (with some padding to
> make the drives on 1.5 Mbyte borders on the thumb drive.  When plugging
> in the thumb drive, the 'vfat' module just mounts the first image (as I
> expect).  What I would like to do is mount some of the other images that
> exist (I dumped out the raw thumb drive).  I believe that a simple way
> to do this is to add an offset to the vfat mount, so that the accesses
> begin at (as in my example) 0x180000 (and multiples thereof) from the
> start of the physical drive.
>
> Is there any way to add such an offset?
> Would it be useful in any other file systems?

mount diskimage /dir -t vfat -o loop,offset=xxx,sizelimit=yyy

mount will then forward the offset and sizelimit options to losetup which 
sets up a loop device before mounting.

Have a look at the man-pages for mount and losetup. :-)

Hope that helps.

> [...]
> -- 
> Tom Watson <tsw@johana.com>
> I'm at home now

-- 
Martin

      parent reply	other threads:[~2011-01-03 14:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-03 13:13 Tom Watson
2011-01-03 14:22 ` Ted Ts'o
2011-01-03 14:25 ` Martin Nybo Andersen [this message]

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=alpine.DEB.2.00.1101031518410.12757@odin.tweek.dk \
    --to=tweek@tweek.dk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tsw@johana.com \
    /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®