Messages in this thread |  | | Subject | Re: Devlinks. Code. (Dcache abuse?) | Date | Fri, 16 Nov 2001 10:26:17 +0000 (GMT) | From | Alan Cox <> |
| |
> A device special file is a gateway between a user (admin) > controlled name space (the filesystem) and a kernel imposed name > space (major/minor numbers) that recognises and imposes access > control (owner/group/permissions). > > The (a) problem with this is that major/minor numbers are too limited,
Textual names have unsolved problems too 1. Who administers the namespace 2. When trademarks get entangled whats the disputes procedure
Do you want to create a situation where a future kernel is likely to be forced to change a device naming because an "official" vendor driver appears too and they demand the namespace and wave trademarks around ?
> A Devlink looks like a symlink with the "sticky" (S_ISVTX) bit set. > Indeed, that is how it is stored on a filesystem.
That seems basically sound. I'm not sure about the devfs part but that is a seperate matter.
Alan
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |