From: Tim Riker <Tim@Rikers.org>
To: linux-kernel@vger.kernel.org
Subject: loop device length
Date: Thu, 14 Dec 2000 20:20:42 -0700 [thread overview]
Message-ID: <3A398E0A.A12F973E@Rikers.org> (raw)
losetup allows for setting a starting offset within a file for the loop
block device. There however is no length parameter to permit setting the
length. Adding a length parameter would allow for multiple fs images in
a single file (or device) and would correctly handle programs like
resize2fs.
What do you think? We could add a lo_length to struct loop_device and
return that if it was non-zero and less than the physical length
calculated normally by figure_loop_size().
While I'm at it why are loop_sizes[] and loop_blksizes[] not part of
struct loop_device now?
--
Tim Riker - http://rikers.org/ - short SIGs! <g>
All I need to know I could have learned in Kindergarten
... if I'd just been paying attention.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2000-12-15 3:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-15 3:20 Tim Riker [this message]
2000-12-17 10:38 ` loop device length Peter Samuelson
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=3A398E0A.A12F973E@Rikers.org \
--to=tim@rikers.org \
--cc=linux-kernel@vger.kernel.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