From: David Chow <davidchow@shaolinmicro.com>
To: Andries Brouwer <aebr@win.tue.nl>
Cc: Alexander Viro <viro@math.psu.edu>, linux-fsdevel@vger.kernel.org
Subject: Re: partitions
Date: Thu, 25 Jul 2002 20:09:53 +0800 [thread overview]
Message-ID: <3D3FEA91.1070507@shaolinmicro.com> (raw)
In-Reply-To: 20020724192914.GA13180@win.tue.nl
Andries Brouwer wrote:
> On Wed, Jul 24, 2002 at 03:02:50PM -0400, Alexander Viro wrote:
>
>
>>Basically, gendisks are crap. Why on the earth they were created as
>>per-major objects instead of per-disk ones is a mistery, but whatever
>>reason it had, it had acted as serious source of mess. For many years.
>>Right now I'm cleaning that mess up in 2.5 and I have nothing nice to
>>say about the bright guys responsible for its creation. Sorry.
>
>
> [amused] Good to see that you now understand that permanent
> disk data is not stored in a struct block_device and that
> the way to removal of the arrays is nearly independent of
> struct block_device and instead dependent on a replacement
> of struct gendisk.
>
> [berating] However, your annoyed words are not fair to Drew Eckhardt.
> Ten years ago, when he created struct gendisk, most of the problems
> you mention did not exist yet.
Thanks for advice, it seems there are no standard solutions right? It
depends on what sort of device we are looking for... I think I rather
concentrate on finding local partitioncs, ide or scsi. But the case of
ide-floppy is in a gray area. I certainly don't want to make use of such
slow disk.
regards,
David
prev parent reply other threads:[~2002-07-25 12:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-24 16:11 partitions David Chow
2002-07-24 16:18 ` partitions Mr. James W. Laferriere
2002-07-24 16:32 ` partitions Randy.Dunlap
2002-07-24 18:47 ` partitions Andries Brouwer
2002-07-24 19:02 ` partitions Alexander Viro
2002-07-24 19:29 ` partitions Andries Brouwer
2002-07-25 12:09 ` David Chow [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=3D3FEA91.1070507@shaolinmicro.com \
--to=davidchow@shaolinmicro.com \
--cc=aebr@win.tue.nl \
--cc=linux-fsdevel@vger.kernel.org \
--cc=viro@math.psu.edu \
/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