All of lore.kernel.org
 help / color / mirror / Atom feed
From: AJ Lewis <lewis@sistina.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: devfs and /proc/ide/hda
Date: Thu, 1 Mar 2001 08:41:33 -0600	[thread overview]
Message-ID: <20010301084133.C16667@sistina.com> (raw)
In-Reply-To: <3A9CCA76.3E6AB93A@optushome.com.au> <20010228161023.A19929@win.tue.nl>
In-Reply-To: <20010228161023.A19929@win.tue.nl>; from dwguest@win.tue.nl on Wed, Feb 28, 2001 at 04:10:23PM +0100

[-- Attachment #1: Type: text/plain, Size: 1959 bytes --]

On Wed, Feb 28, 2001 at 04:10:23PM +0100, Guest section DW wrote:
> On Wed, Feb 28, 2001 at 08:52:54PM +1100, Glenn McGrath wrote:
> 
> > Im running kernel 2.4.1, I have entries like /proc/ide/hda,
> > /proc/ide/ide0/hda etc irrespective of wether im using devfs or
> > traditional device names.
> > 
> > Is always using traditional device names for /proc/ide intentional, or
> > is it something nobody has gotten around to fixing yet?
> 
> If only humans look at /proc, and they like typing long names,
> then there is no objection against changing /proc.
> As it is, however, quite a few programs look at /proc for
> information about devices. I don't think it would be a good
> idea to "fix" /proc and simultaneously break all these programs.

What it should do is change based on whether devfs is mounted or not.  It
doesn't make *any* sense to have /dev/ide/host0/foo/bar in your
/proc/partitions entries if you aren't mounting devfs.  The /proc/partitions
entry is the only way I know of for something like LVM to determine which
devices to scan for Volume Groups.  If you can't read /proc/partitions, it
has to attempt to scan all block devices it recognizes, regardless of
whether they are actually on the system or not.  This can take several
minutes.

-- 
AJ Lewis
Sistina Software Inc.                  Voice:  612-379-3951
1313 5th St SE, Suite 111              Fax:    612-379-3952
Minneapolis, MN 55414                  E-Mail: lewis@sistina.com
http://www.sistina.com

Current GPG fingerprint = 3B5F 6011 5216 76A5 2F6B  52A0 941E 1261 0029 2648
Get my key at: http://www.sistina.com/~lewis/gpgkey
 (Unfortunately, the PKS-type keyservers do not work with multiple sub-keys)

-----Begin Obligatory Humorous Quote----------------------------------------
Choose a job you love, and you will never have to work a day in your life.
-----End Obligatory Humorous Quote------------------------------------------

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

  reply	other threads:[~2001-03-01 14:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-28  9:52 devfs and /proc/ide/hda Glenn McGrath
2001-02-28 10:29 ` Helge Hafting
2001-02-28 10:29   ` Glenn McGrath
2001-02-28 11:58     ` Pierre Rousselet
2001-02-28 15:15     ` Guest section DW
2001-02-28 15:10 ` Guest section DW
2001-03-01 14:41   ` AJ Lewis [this message]
2001-03-08 12:32     ` Goswin Brederlow
2001-04-27 16:09       ` AJ Lewis
2001-04-27 16:22         ` Richard Gooch

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=20010301084133.C16667@sistina.com \
    --to=lewis@sistina.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.