From mboxrd@z Thu Jan 1 00:00:00 1970 From: Erik van Konijnenburg Date: Mon, 28 Feb 2005 21:14:44 +0000 Subject: Re: The Next Generation Message-Id: <20050228221444.B9920@banaan.localdomain> List-Id: References: <20050217190941.GA1561@vrfy.org> In-Reply-To: <20050217190941.GA1561@vrfy.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org On Mon, Feb 28, 2005 at 09:50:22PM +0100, Marco d'Itri wrote: > On Feb 28, Kay Sievers wrote: > > > It is nicer to read, yes. But renaming some of the keys would be nice > > too, like: > > ADD_SYMLINK, ADD_HOTPLUG, MATCH_ACTION, SET_GROUP, SET_MODE, SET_NAME > Please don't... this would make rules files excessively verbose, and I > believe that it's already quite clear which rules are conditions and > which one are actions. Once you're fully familiar with the rules, yes. However, when I was learning the rules, a bit of syntactic sugar would have helped. How about: "IF the separator is an arrow instead of a comma, then the conditions must be on the left and the actions on the right" KERNEL="js[0-9]*" => NAME="input/%k", MODE="0664" It's less verbose, backward compatible, and allows udev to catch some misunderstandings from a beginning rule author. Regards, Erik ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_ide95&alloc_id396&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