public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Guillaume Boissiere" <boissiere@mediaone.net>
To: Guillaume Boissiere <boissiere@mediaone.net>,
	linux-kernel@vger.kernel.org, "Tim Pepper" <tpepper@vato.org>
Subject: Re: [STATUS 2.5]  January 17, 2001
Date: Thu, 17 Jan 2002 17:22:46 -0500	[thread overview]
Message-ID: <3C470866.5353.10126E20@localhost> (raw)
In-Reply-To: <20020117141458.A11402@vato.org>
In-Reply-To: <20020117214752.GA5085@localhost>; from jdomingo@internautas.org on Thu, Jan 17, 2002 at 10:47:53PM +0100

So are you suggesting I add the following task to my list?
o Finalize new device naming convention (Linus Torvalds)

-- Guillaume



On 17 Jan 2002 at 14:14, Tim Pepper wrote:

> I'm not sure if any of the block changes already include this or if
> this will rekindle the flamewar on devfs, but something's going to need
> to happen with device naming.
> 
> At the very least the upcoming change to the major/minor allocation
> will allow large numbers of block devices and fs/partitions/check.c's
> disk_name() will break.  I think a lot of the scsi code's ready to support
> a large number of devices.  It'd be kind of ugly to have it find them
> and disk_name() give them colliding names or names with odd extended
> characters.
> 
> There's already code out there to allow the sd to find more than 128
> devices and I've seen it in use where there are enough luns to cause
> disk_name() to call them interesting names.
> 
> Tim
> -- 
> *********************************************************
> *  tpepper@vato dot org             * Venimus, Vidimus, *
> *  http://www.vato.org/~tpepper     * Dolavimus         *
> *********************************************************


  parent reply	other threads:[~2002-01-17 22:24 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-17  7:13 [STATUS 2.5] January 17, 2001 Guillaume Boissiere
2002-01-17  9:09 ` Stefan Smietanowski
2002-01-17 10:03 ` Russell King
2002-01-17 11:21   ` Dave Jones
2002-01-17 12:40     ` Erik Mouw
2002-01-17 21:47 ` Jose Luis Domingo Lopez
2002-01-17 22:14   ` Tim Pepper
2002-01-17 22:21   ` Hans Reiser
2002-01-17 22:39     ` Tim Pepper
2002-01-17 23:02       ` James Simmons
2002-01-18  0:21         ` Hans Reiser
2002-01-18  0:38     ` Alan Cox
2002-01-18 11:36       ` Hans Reiser
2002-01-17 22:22   ` Guillaume Boissiere [this message]
2002-01-17 22:30     ` Tim Pepper
2002-01-20  1:02       ` H. Peter Anvin
2002-01-18  4:47     ` Guillaume Boissiere
2002-01-18  0:23 ` Anton Altaparmakov
2002-01-18  0:50   ` Chris Chabot
2002-01-18  4:35     ` Guillaume Boissiere
2002-01-18  2:02 ` Arnaldo Carvalho de Melo
2002-01-21 12:39 ` Pavel Machek
2002-01-24 17:40   ` James Simmons

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=3C470866.5353.10126E20@localhost \
    --to=boissiere@mediaone.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tpepper@vato.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