All of lore.kernel.org
 help / color / mirror / Atom feed
From: AJ Lewis <lewis@sistina.com>
To: Goswin Brederlow <goswin.brederlow@student.uni-tuebingen.de>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: devfs and /proc/ide/hda
Date: Fri, 27 Apr 2001 11:09:36 -0500	[thread overview]
Message-ID: <20010427110935.C1632@sistina.com> (raw)
In-Reply-To: <3A9CCA76.3E6AB93A@optushome.com.au> <20010228161023.A19929@win.tue.nl> <20010301084133.C16667@sistina.com> <87snkov3uk.fsf@mose.informatik.uni-tuebingen.de>
In-Reply-To: <87snkov3uk.fsf@mose.informatik.uni-tuebingen.de>; from goswin.brederlow@student.uni-tuebingen.de on Thu, Mar 08, 2001 at 01:32:03PM +0100

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

On Thu, Mar 08, 2001 at 01:32:03PM +0100, Goswin Brederlow wrote:
>      > 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.
> 
> First:
> 
> % cat /proc/partitions 
> major minor  #blocks  name
> 
>    3     0   20010816 ide/host0/bus0/target0/lun0/disc
>    3     1     192748 ide/host0/bus0/target0/lun0/part1
>    3     2     249007 ide/host0/bus0/target0/lun0/part2
>    3     3          1 ide/host0/bus0/target0/lun0/part3
>    3     5     289138 ide/host0/bus0/target0/lun0/part5
>    3     6    1951866 ide/host0/bus0/target0/lun0/part6
>    3     7     979933 ide/host0/bus0/target0/lun0/part7
>    3     8   16346106 ide/host0/bus0/target0/lun0/part8
>   33     0   80043264 ide/host2/bus0/target0/lun0/disc
>   33     1   80035798 ide/host2/bus0/target0/lun0/part1
> 
> So its already right.

Only if devfs is mounted.  That's my point.  Maybe it's an corner case to
have devfs compiled into the kernel, but not mounted, and so we can just
ignore this, but it seems to me that /proc/partitions should reflect which
/dev system is currently running.

> Secondly with devfs, why not just scan all /dev/discs/?
> 
> % ls -l /dev/discs 
> total 0
> lr-xr-xr-x    1 root     root           30 Jan  1  1970 disc0 -> ../ide/host0/bus0/target0/lun0/
> lr-xr-xr-x    1 root     root           30 Jan  1  1970 disc1 -> ../ide/host2/bus0/target0/lun0/
> 
> Also if lvm opens all known devices by way of /dev/whatever while
> scanning, it will only find existing devices there with devfs.

Yeah, as long as devfs is running, that makes sense.

-- 
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----------------------------------------
A computer without a Microsoft operating system is like a dog without bricks
tied to its head.
-----End Obligatory Humorous Quote------------------------------------------

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

  reply	other threads:[~2001-04-27 16:11 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
2001-03-08 12:32     ` Goswin Brederlow
2001-04-27 16:09       ` AJ Lewis [this message]
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=20010427110935.C1632@sistina.com \
    --to=lewis@sistina.com \
    --cc=goswin.brederlow@student.uni-tuebingen.de \
    --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.