From: James Bottomley <James.Bottomley@SteelEye.com>
To: Arjan van de Ven <arjanv@redhat.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
viro@parcelfarce.linux.theplanet.co.uk, greg@kroah.com,
Rusty Russell <rusty@rustcorp.com.au>,
Linux Kernel <linux-kernel@vger.kernel.org>,
SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [RFC] put symbolic links between drivers and modules in the sysfs tree
Date: 25 Sep 2004 09:16:15 -0400 [thread overview]
Message-ID: <1096118180.1715.7.camel@mulgrave> (raw)
In-Reply-To: <1096100492.17155.3.camel@laptop.fenrus.com>
On Sat, 2004-09-25 at 04:21, Arjan van de Ven wrote:
> btw does that mkinitrd already use
> readlink /sys/block/sda/device/block/device
>
> (which gives
> ../../devices/pci0000:00/0000:00:06.0/0000:03:0b.0/host1/1:0:0:0
> as output)
>
> the pci path that gives can easily be matched to modules.pcimap to find
> the information in case of a PCI device, so at least the table in your
> mkinitrd doesn't need to contain PCI devices.....
So tell me what happens when my root device is on MCA (which is one of
my machines) or is a parisc internal device (which is another)...
Putting the modules link in relieves mkinitrd from having to understand
anything about the bus types.
James
next prev parent reply other threads:[~2004-09-25 13:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-20 17:29 [RFC] put symbolic links between drivers and modules in the sysfs tree James Bottomley
2004-09-22 23:04 ` Greg KH
2004-09-22 23:06 ` Greg KH
2004-09-22 23:40 ` Greg KH
2004-09-25 7:38 ` viro
2004-09-25 8:05 ` Herbert Xu
2004-09-25 8:21 ` Arjan van de Ven
2004-09-25 13:16 ` James Bottomley [this message]
2004-09-25 13:14 ` James Bottomley
2004-09-26 10:37 ` Herbert Xu
2004-09-26 10:37 ` Herbert Xu
2004-09-26 13:09 ` James Bottomley
2004-09-25 16:46 ` Greg KH
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=1096118180.1715.7.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=arjanv@redhat.com \
--cc=greg@kroah.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
/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.