From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kay Sievers Date: Thu, 19 May 2005 14:12:20 +0000 Subject: Re: new release of udev? Message-Id: <20050519141220.GA857@vrfy.org> List-Id: References: <20050519065848.GA25640@kroah.com> In-Reply-To: <20050519065848.GA25640@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org On Thu, May 19, 2005 at 12:32:20PM +0200, Marco d'Itri wrote: > On May 19, Kay Sievers wrote: > > > Only the use of the RUN key is a bit difficult then. To solve that, I > > will implement deferred(question mark) assignment, like in Makefiles for > > the default system-supplied rules to use: > > SUBSYSTEM="block", GROUP?="disk" > > > > will only set the permissions if no other rule has already set the > > group. This should solve that small issue. > As I explained in our private discussion, this is complex and does not > solve the SYMLINK problem: users would still not be able to override > the distribution SYMLINK directives without using last_rule, which is > not an option because it breaks RUN processing. Well, SYMLINK is a list not a single value. Why does someone want to supress the additional system-supplied symlinks? > With its current semantics, last_rule should almost never be used by > users. Yeah, it can be used exactly for what the name stands for. :) > I still think that having different "last_rule" directives for NAME and > RUN rules would be a better solution, and it looks much simpler to > implement and understand too. I don't think that this is simpler in any kind. That moves the complexity away from the system-rules to the user-rules. And the system-rule writer _must_ understand the complexity anyway. :) Kay ------------------------------------------------------- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_idt12&alloc_id344&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