[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LFD.2.00.1012101852460.2813@dhcp-lab-213.englab.brq.redhat.com>
Date: Fri, 10 Dec 2010 18:54:47 +0100 (CET)
From: Lukas Czerner <lczerner@...hat.com>
To: Kay Sievers <kay.sievers@...y.org>
cc: Lukas Czerner <lczerner@...hat.com>,
Andreas Dilger <adilger.kernel@...ger.ca>,
Greg KH <gregkh@...e.de>, linux-fsdevel@...r.kernel.org,
linux-kernel@...r.kernel.org, tytso@....edu, sandeen@...hat.com,
hch@...radead.org, axboe@...nel.dk
Subject: Re: [RFC PATCH 0/2 v1] Ioctl for reading block queue information
On Fri, 10 Dec 2010, Kay Sievers wrote:
> On Fri, Dec 10, 2010 at 15:07, Lukas Czerner <lczerner@...hat.com> wrote:
> > On Thu, 9 Dec 2010, Andreas Dilger wrote:
> >
> >> On 2010-12-09, at 12:20, Greg KH wrote:
> >> > On Thu, Dec 09, 2010 at 04:25:35PM +0100, Lukas Czerner wrote:
> >> >> For a long time it has been pretty painful to retrieve informations from
> >> >> /sys/block/*/queue for particular block device. Not only it is painful
> >> >> to retrieve informations within C tool, parsing strings, etc, but one
> >> >> have to run into problem even finding the proper path in sysfs.
> >> >
> >> > What's wrong with using libudev? That should give you all of this
> >> > information easily using a .c program without any need to change the
> >> > kernel at all.
> >
> > What's wrong with using libudev ? Well, fist of all I have never heard
> > about it:), one can argue this is kind of my fault, and second of all
> > the documentation is kind of non-existent (almost).
>
> What else do you need?
> http://www.kernel.org/pub/linux/utils/kernel/hotplug/libudev/
>
> Let me know, we can add it.
>
> Thanks,
> Kay
>
Well, this is not really documentation right, but rather reference
manual. But I found this
http://www.signal11.us/oss/udev/
as a good way to start with.
Thanks!
-Lukas
Powered by blists - more mailing lists