Now that notifiers are in, (yay!), people are going to start writing adapters
for visually and motor impaired individuals.
I suggest we place them in drivers/adapters in the source tree,
and I suggest they put their virtual files in the directory /proc/adapters,
which would be created via fs/proc/root.c as part of the /proc file system.
Adapter foo would create /proc/adapters/foo, and put its files in that directory.
Naturaly it would rm -r /proc/adapters/foo upon module exit.
I'm already working on my third adapter, and we need some kind of organization.
What do you think?
If you like, I can write and submit a patch that does this.
Karl Dahlke
On Tue, Feb 19, 2008 at 08:01:48AM -0500, Karl Dahlke wrote:
> Now that notifiers are in, (yay!), people are going to start writing adapters
> for visually and motor impaired individuals.
> I suggest we place them in drivers/adapters in the source tree,
> and I suggest they put their virtual files in the directory /proc/adapters,
> which would be created via fs/proc/root.c as part of the /proc file system.
/proc is for processes (and was in the past used for all sort of crap).
So without knowing what an adapter is in this context /proc
seems to be a bad choice.
Sam
On Feb 19 2008 08:01, Karl Dahlke wrote:
>
>Now that notifiers are in, (yay!), people are going to start writing adapters
>for visually and motor impaired individuals.
>I suggest we place them in drivers/adapters in the source tree,
Umph, that sounds a bit generic. Network cards are sometimes referred
to as "network [card] adapter" and graphic cards to as "graphics adapter",
so by your suggestions, they would all go into drivers/adapters/.
When such a driver actually comes along, we can revisit the topic.
>and I suggest they put their virtual files in the directory /proc/adapters,
>which would be created via fs/proc/root.c as part of the /proc file system.
Please not. Either character-based devices or sysfs files, depending
on which flies best. Adapters are not really proc-related.