mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: BlaisorBlade <blaisorblade_spam@yahoo.it>
To: linux-kernel@vger.kernel.org
Subject: Re: [NEW FEATURE]Partitions on loop device for 2.6
Date: Wed, 24 Dec 2003 20:04:14 +0100	[thread overview]
Message-ID: <200312242004.14750.blaisorblade_spam@yahoo.it> (raw)
In-Reply-To: <200312241341.23523.blaisorblade_spam@yahoo.it>

Answering to Sean Estabrooks:

1st, I asked to be CC'ed on replies, as I'm not subscribed. In fact I'm sorry 
your mail is not properly quoted, as I did this by hand.

On Wed, 24 Dec 2003 18:20:22 +0100
BlaisorBlade <blaisorblade_spam@yahoo.it> wrote:
>> NEED:
>> I have the need to loop mount files containing not plain filesystems,
>> but whole disk images.
>> 
>
>What does your proposed feature
Note that I propose also beta-code(not actually ready due to the BLKRRPART 
problem).
> add to the kernel that can't be
>accomplished with the "losetup" command and its offset parameter?
If you read my mail, I already noted the existance of the offset parameter, 
but do you prefer:
1) to run fdisk, shoot some commands and get the offset and then put that 
offset into losetup or mount, saving some code but losing a lot of 
time(remember computers are all about saving time for humans); this could 
actually be scripted, and if you post a script to do this I could even use 
it.
2) or use existing code in the kernel to automate all this, with minimal 
intrusiveness?
I know that moving things to userspace is useful if it helps reduce kernel 
bloating(and this patch will not bloat anything); yet we could move partition 
handling to the userspace by adding an offset param for general mounts, but 
this doesn't happen.
However for this it's matter of taste.

Good bye and merry Christmas!
-- 
Paolo Giarrusso, aka Blaisorblade


  parent reply	other threads:[~2003-12-24 19:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-24 17:20 BlaisorBlade
2003-12-24 18:39 ` Sean Estabrooks
2003-12-24 19:04 ` BlaisorBlade [this message]
2003-12-24 21:03   ` Sean Estabrooks
2003-12-25 21:03     ` Jan-Benedict Glaw
2003-12-30  7:26 ` Tomas Szepe
2004-01-02 21:04 ` Bill Davidsen
2004-01-03 10:56   ` Maciej Zenczykowski
2004-01-03 18:05   ` BlaisorBlade
2004-01-07 22:15     ` bill davidsen
     [not found] <010a01c415a4$26fc1110$d100000a@sbs2003.local>
2004-03-30 21:37 ` Bill Davidsen

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=200312242004.14750.blaisorblade_spam@yahoo.it \
    --to=blaisorblade_spam@yahoo.it \
    --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

all inboxes | Powered by JetHome®