Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263172AbVBCVAv (ORCPT ); Thu, 3 Feb 2005 16:00:51 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263213AbVBCVAu (ORCPT ); Thu, 3 Feb 2005 16:00:50 -0500 Received: from ns1.lanforge.com ([66.165.47.210]:40865 "EHLO www.lanforge.com") by vger.kernel.org with ESMTP id S263172AbVBCVAe (ORCPT ); Thu, 3 Feb 2005 16:00:34 -0500 Message-ID: <420290ED.8020302@candelatech.com> Date: Thu, 03 Feb 2005 13:00:29 -0800 From: Ben Greear Organization: Candela Technologies User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.7.3) Gecko/20041020 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Pavel Roskin CC: linux-kernel@vger.kernel.org Subject: Re: Please open sysfs symbols to proprietary modules References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1008 Lines: 26 Pavel Roskin wrote: > All I want to do is to have a module that would create subdirectories > for some network interfaces under /sys/class/net/*/, which would contain > additional parameters for those interfaces. I'm not creating a new > subsystem or anything like that. sysctl is not good because the data is > interface specific. ioctl on a socket would be OK, although it wouldn't > be easily scriptable. The restriction on sysfs symbols would just force > me to write a proprietary userspace utility to set those parameters > instead of using a shell script. How about /proc/net/pavelStuff Still scriptable, and does not require GPL symbols.... Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/