Re: Darwin-kernel Digest, Vol 4, Issue 283
Re: Darwin-kernel Digest, Vol 4, Issue 283
- Subject: Re: Darwin-kernel Digest, Vol 4, Issue 283
- From: Sam Vaughan <email@hidden>
- Date: Fri, 14 Dec 2007 15:41:02 +1100
On 14/12/2007, at 7:05 AM, Terry Lambert <email@hidden> wrote:
Or you can choose to not try creating subdirectores in /dev, and put
the information into node names themselves instead.
For example, a SCSI disc device on controller 0 with unit 3 and lun 8
with three partitions on it, where you wanted the second one could be
named something like "sdc0u3l8s3".
UNIX systems have used this type of convention forever. Think of the
letters other than the initial "sd" as path component separators, if
it helps you sleep.
Given that subdirectories in /dev are not supported, and may be
removed, if we end up needing to do that for some technical reason,
it's probably better to just go that route on both 10.4 and 10.5
instead.
This is probably the approach we will end up taking... just have to
actually do it :)
Oi! That's my code you'd be ripping out! ;o)
The reason for the subdirectories in the first place was to allow
LUNs to be identified by the port and node WWNs on the host and RAID
controller that uniquely described their path on the fibre channel
network. The WWNs are too long to include in the one devfs node
name, so the only option is to use a hierarchy.
If you ask me, even if the required information could be squashed
into one name, it's a hell of a lot neater and less cryptic to break
it up into a hierarchy. Why punish yourself with things like
"sdc0u3l8s3"? Not to mention the sorting problems once any of those
numbers goes double-digits...
Sam
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-kernel mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden