Date: Sun, 15 Jun 2008 19:11:19 +0200 (CEST)
From: Jan Engelhardt <jengelh@medozas.de>
To: Samuel Thibault <samuel.thibault@ens-lyon.org>
cc: linux-kernel@vger.kernel.org
Subject: Re: path to speakup control variables?
In-Reply-To: <20080615164422.GS4770@implementation>
Message-ID: <alpine.LNX.1.10.0806151907590.22495@fbirervta.pbzchgretzou.qr>
References: <20080615164422.GS4770@implementation>
User-Agent: Alpine 1.10 (LNX 962 2008-03-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1012
Lines: 28


On Sunday 2008-06-15 18:44, Samuel Thibault wrote:
>Hello,
>
>The speakup module used to put of its control variables (e.g. speech
>speed) in /proc/speakup/ . To better stick with common practice,
>should that go to somewhere in /sys or in /proc/sys/speakup (though
>it looked to me like non-mainstream modules can't go there because of
>sysctl_check)?

For some tasks, neither procfs nor sysfs seem to be the right place.
Which is really odd. The two unwritten rules are

(a) "No new files should go into /proc"

 -> so we use sysfs, we would think

(b) "/sys files have only one value"

 -> that's possibly expensive in terms of dentries and kobjects
    when you think of files with lots of variables like /proc/stat

So we're in a draw for some sort of files...
--
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/