[lcdproc] "named pipe" is different from /dev/lcdkernel code. :-)]

[Joris Robijn]

> Hehehehehe. Windows seems designed not to handle much of anything in a
> nice way. You do, however, bring up another potential target OS. I must
> admit, though, to having absolutely *no* way to actually install OS/2 on
> any of my boxen (don't have the install media anywhere).

I have not worked with it the last 4 years either, but I still have v3 
or v4 laying around here somewhere.

> You mean something like:
> 
> - LCDd runs on the 'doze box
> - Display driver runs as its own process, listening on a network port 
> - LCDd connects to said port and does its thing

Yes that looks like it. I only think the driver should connect to LCDd, 
so you can dynamically change the attached displays and keyboards (nice 
for GIF creating etc., see earlier mails with other subject). 

LCDd can then have the quiet chalanging task to multiplex all these 
connections, manage the framebuffer or some other content-buffer and 
handling keypresses (and passing them to lcdproc-processes if needed). 
Aint that cool, ay ?

Joris

-- 
 Joris Robijn <joris@robijn.net>
 Home: 053 4311 553
 Mobile: 06 288 41 964

 // To understand recursion, we must first understand recursion


-----------------------------------------------------------
To unsubscribe from this list send a blank message to
lcdproc-unsubscribe@lists.omnipotent.net