mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter Samuelson <peter@cadcamlab.org>
To: "Eric S. Raymond" <esr@thyrsus.com>,
	Rob Landley <landley@trommello.org>, Nicolas Pitre <nico@cam.org>,
	lkml <linux-kernel@vger.kernel.org>,
	kbuild-devel@lists.sourceforge.net
Subject: Re: CML2-2.1.3 is available
Date: Wed, 16 Jan 2002 00:29:42 -0600	[thread overview]
Message-ID: <20020116062942.GC2067@cadcamlab.org> (raw)
In-Reply-To: <Pine.LNX.4.33.0201151538340.5892-100000@xanadu.home> <20020116034137.CRFB26021.femail12.sdc1.sfba.home.com@there> <20020115224821.A4658@thyrsus.com>
In-Reply-To: <20020115224821.A4658@thyrsus.com>


[esr]
> The version I just released does exactly that.  Well, not exactly; it
> actually looks at fstab -- /proc/mounts gives you '/dev/root' rather
> than a physical device name in the root entry.

/etc/fstab is hardly guaranteed to be accurate either.  The kernel
mounts the root device based on its command line and any pivot_root()
calls you make, not based on /etc/fstab.

[In practice, I imagine most people don't lie to fstab.  The fsck init
script would get annoyed.]

But the horse's mouth, in this case, is /proc/sys/kernel/real-root-dev,
a 16-bit decimal int which represents a device number in
MAJOR*256+MINOR format.  There *may* also the 'root=' asciiz string in
/proc/cmdline, which will be a 4-digit hex number, but that is not
reliable - because of pivot_root() among other things.

On my system, real-root-dev gives 8453, which means /dev/hde5, which is
on ide2.  According to /proc/ide/ide2/config, it is a PCI device of
type 105a:4d30 [Promise Ultra100], so you can derive
CONFIG_BLK_DEV_PDC202XX as well as CONFIG_BLK_DEV_IDEDISK.

Peter

  reply	other threads:[~2002-01-16  6:30 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-15 19:53 Eric S. Raymond
2002-01-15 20:15 ` Nicolas Pitre
2002-01-15 20:18   ` Eric S. Raymond
2002-01-15 20:41     ` Nicolas Pitre
2002-01-15 19:19       ` Rob Landley
2002-01-16  3:48         ` Eric S. Raymond
2002-01-16  6:29           ` Peter Samuelson [this message]
2002-01-16  6:32             ` Eric S. Raymond
2002-01-16  7:13               ` Peter Samuelson
2002-01-16  6:36             ` Alexander Viro
2002-01-16  0:15     ` Henning P. Schmiedehausen
2002-01-15 20:16 ` Anton Altaparmakov
2002-01-15 20:24   ` Eric S. Raymond
2002-01-15 19:30     ` Rob Landley
2002-01-16  3:58       ` Eric S. Raymond
2002-01-15 20:25 ` Russell King
2002-01-15 19:37   ` Rob Landley
2002-01-17  1:18     ` Val Henson
2002-01-21 16:22     ` Daniel Phillips
2002-01-21 17:05       ` [kbuild-devel] " Giacomo Catenazzi
2002-01-21 23:11         ` Daniel Phillips
2002-01-23 21:45         ` Daniel Phillips
2002-01-22  6:29       ` Kai Henningsen
2002-01-16  0:38   ` Peter Samuelson
2002-01-15 20:26 ` Ross Vandegrift
2002-01-16  4:02   ` Eric S. Raymond
2002-01-16 16:38     ` Ross Vandegrift
2002-01-16 16:59       ` Ross Vandegrift
2002-01-16 18:29       ` Rob Landley
2002-01-18 18:32     ` Ross Vandegrift
2002-01-22  5:31       ` Eric S. Raymond
2002-01-15 20:27 ` Robert Love
2002-01-15 21:09 ` David Lang
2002-01-16 15:06 ` Horst von Brand
2002-01-16 21:31   ` Eric S. Raymond
2002-01-16 21:56     ` Horst von Brand
2002-01-16 21:47       ` Eric S. Raymond
2002-01-17  1:26       ` David Woodhouse
2002-01-17  1:43         ` Eric S. Raymond
2002-01-17  8:53         ` David Woodhouse
2002-01-17 13:37           ` Eric S. Raymond
2002-01-17 14:09           ` David Woodhouse
2002-01-17 14:29             ` Eric S. Raymond
2002-01-16 23:36     ` David Lang
2002-01-18  6:48     ` Kai Henningsen
2002-01-22  9:11 [kbuild-devel] " Giacomo Catenazzi
2002-01-22  9:20 ` Keith Owens
     [not found] <fa.d4sn1fv.b78io8@ifi.uio.no>
     [not found] ` <fa.i3p6mlv.1mg2frl@ifi.uio.no>
2002-01-22 10:09   ` Giacomo Catenazzi
2002-01-22 10:25     ` Keith Owens
2002-01-22 10:48       ` Giacomo Catenazzi
2002-01-22 10:53         ` Keith Owens

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=20020116062942.GC2067@cadcamlab.org \
    --to=peter@cadcamlab.org \
    --cc=esr@thyrsus.com \
    --cc=kbuild-devel@lists.sourceforge.net \
    --cc=landley@trommello.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nico@cam.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

all inboxes | Powered by JetHome®