From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261825AbTDKUpr (for ); Fri, 11 Apr 2003 16:45:47 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261830AbTDKUpr (for ); Fri, 11 Apr 2003 16:45:47 -0400 Received: from e31.co.us.ibm.com ([32.97.110.129]:4561 "EHLO e31.co.us.ibm.com") by vger.kernel.org with ESMTP id S261825AbTDKUpo (for ); Fri, 11 Apr 2003 16:45:44 -0400 Date: Fri, 11 Apr 2003 13:59:48 -0700 From: Greg KH To: David Lang Cc: "Perez-Gonzalez, Inaky" , "'Jeremy Jackson'" , "'linux-kernel@vger.kernel.org'" , "'linux-hotplug-devel@lists.sourceforge.net'" Subject: Re: [ANNOUNCE] udev 0.1 release Message-ID: <20030411205948.GV1821@kroah.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Apr 11, 2003 at 01:48:17PM -0700, David Lang wrote: > ant then you also have all the same problems as devfs about default > permissions, making permissions persistant across reboots, etc. You can store the default permissions in the database you use to store the naming data. This solves the reboot problem, as long as you can convince people to not modify the permissions on their own (well even if they do, at shutdown, you can always validate that they are the same before you clean up the node.) And provide an easy way for users to change the permissions so they show up in the database. devchmod and devchown anyone? :) thanks, greg k-h