Re: [RFC] New Driver Model for 2.5

[Padraig Brady]

Kai Henningsen wrote:

>[e-mail] (Mike Fedyk)  wrote on 19.10.01 in <[e-mail]>:
>
>>On Fri, Oct 19, 2001 at 09:02:09PM +0200, Tim Jansen wrote:
>>
>>>On Friday 19 October 2001 20:26, Patrick Mochel wrote:
>>>
>>>>There are equivalents in USB. But, neither of them are globally unique
>>>>identifiers for the device. That doesn't necessarily mean that one
>>>>couldn't be ascertained from the device; ethernet cards do have MAC
>>>>addresses. But, I don't think that many will have a ID/serial number.
>>>>[...]
>>>>Which leads me to the question: what real benefit does this have? Why
>>>>would you ever want to do a global search in kernel space for a
>>>>particular device?
>>>>
>>>For example for harddisks. You usually want them to be mounted in the same
>>>directory.
>>>
>>When is /etc/fstab going to support this?
>>
>
>Know your tools.
>
>/etc/fstab:
>UUID=eba05cbf-55ff-44d7-846a-7846c6010843 /usr ext2 defaults,nocheck 0 2
>
>I have this mounted right now, on 2.2.19:
>
>/dev/sdb7              3936400   3597588    138852  97% /usr
>
>That's an ext2 partition ID, so even if repartitioning renumbers the  
>partition, mount will still find it - only mkfs forces me to use a new ID.  
>Changing the controller and SCSI id obviously makes no difference  
>whatsoever. I could use labels, too, but they tend to be less unique.
>
>/proc/partitions is necessary to know what partitions to look at, of  
>course.
>
>>>Or for ethernet adapters:
>>>because each is connected to a different network, so you need to assign
>>>different IP addresses to them.
>>>
>>I haven't seen anything assign ethX assign a certain order, except for
>>ordered module loading, and then if there are multiple devices with the same
>>driver, the order is chosen by bus scanning order, or module option.
>>
>
>Exactly. So you can't use the order if there's any possibility of this, so  
>you need to use the MAC address.
>
Yes this (MAC address) is the only general way of doing it.
For ethernet cards (or anything else) on the PCI bus you can use
the following to specify an order:
ftp://platan.vc.cvut.cz/pub/linux/pciorder.patch-2.4.12-ac1.gz
This allows you to pass the following parameter to the kernel:
pciorder=Bus:Node.Fn,Bus:Node.Fn,... e.g.
pciorder=0:0d.0,0:0b.0,0:0a.0

Padraig.