From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [patch] first stupid try for a rule compose gui
Date: Tue, 23 Mar 2004 18:46:31 +0000 [thread overview]
Message-ID: <20040323184631.GC5694@kroah.com> (raw)
In-Reply-To: <20040315202817.GA5653@vrfy.org>
On Thu, Mar 18, 2004 at 03:55:23AM +0100, Kay Sievers wrote:
> On Mon, Mar 15, 2004 at 09:28:17PM +0100, Kay Sievers wrote:
> > Here is a first simple and pretty stupid try to make a simple tool for
> > composing of a udev rule.
> >
> > It reads the udevdb to get all currently handled devices and presents a
> > list, where you can choose the device to compose the rule for.
> >
> > The composed rule is just printed out in a window, nothing else by now.
> >
> > Do we want something like this?
> > Nevermind, I always wanted to know, how this newt thing works :)
>
> Here is the next step, I still can't sleep and there are to many patches
> pending to make something useful :)
> Cause nobody wanted to play with me, I've made a screenshot.
> The device list is sorted in alphabetical order now and if there are only
> a few recently discovered devices, they are placed on top of the list.
>
> For those who want to have a look:
>
> http://vrfy.org/projects/udev/udevruler.png
>
> The patch applies on top of today's mmap() patch. The db format is
> changed to have the file and line number of the applied rule. So it
> should be easy to edit the matching rule with this beast. It compiles
> with "make all udevruler".
Nice, I've had some people ask me about a gui like tool. This is a
great first step.
Applied, thanks.
greg k-h
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id\x1470&alloc_id638&op=click
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
prev parent reply other threads:[~2004-03-23 18:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-15 20:28 [patch] first stupid try for a rule compose gui Kay Sievers
2004-03-18 2:55 ` Kay Sievers
2004-03-23 18:46 ` Greg KH [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040323184631.GC5694@kroah.com \
--to=greg@kroah.com \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.