From mboxrd@z Thu Jan 1 00:00:00 1970 From: James Bottomley Subject: Re: [RFC] put symbolic links between drivers and modules in the sysfs tree Date: 25 Sep 2004 09:16:15 -0400 Sender: linux-scsi-owner@vger.kernel.org Message-ID: <1096118180.1715.7.camel@mulgrave> References: <1096100492.17155.3.camel@laptop.fenrus.com> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: Received: from stat16.steeleye.com ([209.192.50.48]:14306 "EHLO hancock.sc.steeleye.com") by vger.kernel.org with ESMTP id S269323AbUIYNRr (ORCPT ); Sat, 25 Sep 2004 09:17:47 -0400 In-Reply-To: <1096100492.17155.3.camel@laptop.fenrus.com> List-Id: linux-scsi@vger.kernel.org To: Arjan van de Ven Cc: Herbert Xu , viro@parcelfarce.linux.theplanet.co.uk, greg@kroah.com, Rusty Russell , Linux Kernel , SCSI Mailing List 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