From: Andries Brouwer <aebr@win.tue.nl>
To: Steven Dake <sdake@mvista.com>
Cc: Bryan Henderson <hbryan@us.ibm.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Douglas Gilbert <dougg@torque.net>,
Christoph Hellwig <hch@infradead.org>,
Joel Becker <Joel.Becker@oracle.com>,
Kurt Garloff <kurt@garloff.de>,
linux-kernel@kernel.vger.org,
Linux SCSI list <linux-scsi@vger.kernel.org>
Subject: Re: New model for managing dev_t's for partitionable block devices
Date: Wed, 29 Jan 2003 18:38:37 +0100 [thread overview]
Message-ID: <20030129173837.GA3979@win.tue.nl> (raw)
In-Reply-To: <3E380532.2010900@mvista.com>
On Wed, Jan 29, 2003 at 09:45:38AM -0700, Steven Dake wrote:
> What is needed is a compromise, described above, limiting the number of
> partitions to some sane amount, but allowing significantly more disks
> for the power user.
Always this discussion, over and over again.
Changing dev_t to be 32-bit is something many people that take part
in this discussion could do in a few hours. The subsequent kernel
audit takes a weekend.
Is there a reason everybody prefers to discuss ugly hacks?
Andries
next prev parent reply other threads:[~2003-01-29 17:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-21 21:56 Fwd: 32bit dev_t Douglas Gilbert
2003-01-22 17:18 ` Patrick Mansfield
2003-01-22 23:55 ` Tim Pepper
2003-01-23 0:51 ` Joel Becker
2003-01-23 18:31 ` Kurt Garloff
2003-01-23 22:18 ` Christoph Hellwig
2003-01-24 8:20 ` Kurt Garloff
2003-01-24 18:29 ` Joel Becker
2003-01-27 22:51 ` Christoph Hellwig
2003-01-28 11:21 ` Alan Cox
2003-01-28 11:28 ` Christoph Hellwig
2003-01-28 15:19 ` Kurt Garloff
2003-01-28 16:33 ` Bryan Henderson
2003-01-28 18:22 ` Alan Cox
2003-01-28 17:09 ` New model for managing dev_t's for partitionable block devices Steven Dake
2003-01-29 1:41 ` Bryan Henderson
2003-01-29 16:45 ` Steven Dake
2003-01-29 17:38 ` Andries Brouwer [this message]
2003-01-29 18:00 ` Kurt Garloff
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=20030129173837.GA3979@win.tue.nl \
--to=aebr@win.tue.nl \
--cc=Joel.Becker@oracle.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dougg@torque.net \
--cc=hbryan@us.ibm.com \
--cc=hch@infradead.org \
--cc=kurt@garloff.de \
--cc=linux-kernel@kernel.vger.org \
--cc=linux-scsi@vger.kernel.org \
--cc=sdake@mvista.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