> > > Frankly, I was trying to see whether an external process reading > > > on somebody else's /proc/n/note would make any sense. One thing > > > that I wanted to implement was a "note thief" process that would > > > constantly read on a target's /proc/n/note and handle the notes > > > externally using a different kind of IPC to communicate with > > > the target. Am I dreaming? Would this be completely impossible > > > to implement using /proc/n/note ? > > > > If proc n needs to know about this design, then could > > you just always direct the notes to the "thief?" Or > > if the thief were a little file server, could you bind > > the file he listens to on top of /proc/n/note? > > the kernel would not notice this binding.
Oh yeah--good point. Before walk got down to it devproc would be in control and not care about the binding. I suppose you could do a sort of "note environment" where the server would interpose itself between apps and /proc sort of like how rio sits between apps and /dev/draw, etc. But that's getting complicated and there might be something there too that I'm overlooking. crawling back into my cave... BLS
