>>Consequently it's impossible that the kernel guarantees a static name/
>>number for a specific device. devfs showed that the kernel is the wrong
>>place for name policies. Is see no other possibility than to number
>>devices dynamically and leave it to userspace to name them or did I miss
>>an important point in previous discussions?
>>Maybe you could also answer me, what exactly you need a 64bit dev_t for?
Well, I'm not Peter, or Andries or anyone else for that matter... but if a
userspace tool can be built that will enforce the user's (or distro's) desired
naming policies for completely dynamic numbered devices, I'm all for that. It
sure seems that it would greatly simplify much code in the kernel and completely
eliminate the need to move beyond 32-bit dev_t at all. (I mean really, who's
ever going to have more than 4G devices on a single Linux system image?)
However, there are significant hurdles to implementing this tool:
- defining an adequately powerful file format to define the desired naming policy
- getting the tool to run _both_ in early-userspace and real-userspace
environments, using the _same_ policy file (or copies thereof)
-
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/