On Wed, 2010-11-24 at 20:03 +0100, Kay Sievers wrote: > On Wed, Nov 24, 2010 at 19:46, Davidlohr Bueso <dave@xxxxxxx> wrote: > > On Wed, 2010-11-24 at 19:14 +0100, Kay Sievers wrote: > > >> I doubt anything like this can be done for character devices in > >> general. They are just a tiny detail of all the many domains that use > >> chardevs. For most domains, the devices are not interesting at all. > >> So, I don't think anything like this makes much sense, and it should > >> be left to the individual subsystems. > > > > lsblk simply lists the block devices, showing some (general) details > > about the dev(s), which are common to all block devices. We could also > > do this with char devs, and show specific data, which is common to all > > char devices. IMHO, as a user, if I have a lsblk I will also expect an > > lschr. ls-like tools are very useful because I can quickly and > > intuitively get some information. More complex stuff can be handled by > > other tools, like, as you know, udev. > > Nah, there is no useful common information for chardevs in general. > Look at alsa: > > $ ls -1 /dev/snd/ > controlC0 > controlC29 > pcmC0D0c > pcmC0D0p > seq > timer > > These devices mean absolutely nothing. The interface is libalsa, and > that a card shows up as 3 devices is just a detail never to expose to > anything but things like libalsa. > > That's the thing for many non-trivial subsystems. It still does not > make sense to even try that, I think. I see your point now and was going through my system I have to agree. In fact, I looked at the code of devinfo, and for chardevs I am only using basic things the name and major/minor. Thanks, Davidlohr -- To unsubscribe from this list: send the line "unsubscribe util-linux-ng" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
