On Wed, Nov 24, 2010 at 03:46:05PM -0300, Davidlohr Bueso wrote:
> On Wed, 2010-11-24 at 19:14 +0100, Kay Sievers wrote:
> > On Wed, Nov 24, 2010 at 19:03, Davidlohr Bueso <dave@xxxxxxx> wrote:
> > > On Wed, 2010-11-24 at 17:26 +0100, Karel Zak wrote:
> > >> Hi,
> > >>
> > >> I have merged Milan's lsblk(8) utility. The command lists information
> > >> about all or selected block devices (from /sys).
> > >
> > > Very useful tool!
> > >
> > > We could naturally add lschr(8) for character devices, based on lsblk
> > > and devinfo (which I proposed a few months ago). Thoughts?
> >
> > Block is a rather simple subsystem regarding its interfaces, covering
> > aspects of a single domain.
>
> Agree.
>
> >
> > 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.
Please, be more specific. What data?
Note that lsblk is still not complete, I'd like to add (probably in
v2.20) support for "tree of slaves" for selected device. Now it
supports tree of holders only. Something like:
# lsblk --slaves /dev/mapper/foo
foo
`---sda5
`----sda
Karel
--
Karel Zak <kzak@xxxxxxxxxx>
http://karelzak.blogspot.com
--
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
