From: Lars Marowsky-Bree <lmb@suse.de>
To: "Dimitry V. Ketov" <Dimitry.Ketov@avalon.ru>,
Kevin Corry <kevcorry@us.ibm.com>,
linux-kernel@vger.kernel.org
Subject: Re: Partitioned loop device..
Date: Tue, 15 Jul 2003 23:15:37 +0200 [thread overview]
Message-ID: <20030715211537.GQ29748@marowsky-bree.de> (raw)
In-Reply-To: <E1B7C89B8DCB084C809A22D7FEB90B3840AB@frodo.avalon.ru>
[-- Attachment #1: Type: text/plain, Size: 823 bytes --]
On 2003-07-15T22:32:11,
"Dimitry V. Ketov" <Dimitry.Ketov@avalon.ru> said:
> > You can already use Device-Mapper to create "partitions" on
> > your loop devices,
> You're right but I want _partitions_ but not "partitions" ;)
> It should appears like a real hardware disk, not virtual one.
There is no difference. What makes /dev/loop1a worse than /dev/hda1?
It's just block devices, that's it.
I have hopes that the entire partitioning code etc will be ripped out in
2.7 in favour of full userspace discovery + DM, and that MD will hit the
same fate...
Sincerely,
Lars Marowsky-Brée <lmb@suse.de>
--
SuSE Labs - Research & Development, SuSE Linux AG
"If anything can go wrong, it will." "Chance favors the prepared (mind)."
-- Capt. Edward A. Murphy -- Louis Pasteur
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-07-15 21:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-15 18:32 Dimitry V. Ketov
2003-07-15 21:15 ` Lars Marowsky-Bree [this message]
2003-07-18 14:20 ` Christophe Saout
2003-07-18 19:10 ` Mr. James W. Laferriere
2003-07-18 23:57 ` Christophe Saout
-- strict thread matches above, loose matches on Subject: below --
2003-07-16 8:59 Dimitry V. Ketov
2003-07-16 13:51 ` Kevin Corry
2003-07-15 8:46 Dimitry V. Ketov
2003-07-15 15:01 ` Kevin Corry
2003-07-15 15:53 ` Josh Litherland
2003-07-15 16:04 ` Kevin Corry
2003-07-15 16:05 ` Herbert Pötzl
2003-07-17 2:44 ` kernel
2003-07-15 7:10 Dimitry V. Ketov
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=20030715211537.GQ29748@marowsky-bree.de \
--to=lmb@suse.de \
--cc=Dimitry.Ketov@avalon.ru \
--cc=kevcorry@us.ibm.com \
--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®