lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080119080148.eklhad@comcast.net>
Date:	Tue, 19 Feb 2008 08:01:48 -0500
From:	Karl Dahlke <eklhad@...cast.net>
To:	linux-kernel@...r.kernel.org
Subject: Where to put adapters

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ