On Tue, 19 Feb 2008 14:39:45 EST, Karl Dahlke said:
> Really, /proc is the only place for these virtual files that interact
> directly with the kernel and/or its modules;
> I just wanted a fixed place under /proc for adapters to live,
> like sys ttys scsi net, and so on.
There's an awful lot of s
On Tue, 19 Feb 2008 14:39:45 -0500 Karl Dahlke wrote:
> > So without knowing what an adapter is in this context /proc
> > seems to be a bad choice.
>
> The best explanation might be an example.
> I use my Jupiter speecha dapter all day, every day.
> It basically sends text to a speech synthesizer
> So without knowing what an adapter is in this context /proc
> seems to be a bad choice.
The best explanation might be an example.
I use my Jupiter speecha dapter all day, every day.
It basically sends text to a speech synthesizer.
It also has some virtual files.
/proc/adapters/jupiter/synth can
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 ref
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
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/r
6 matches
Mail list logo
