From: Firstname L. <ms...@ho...> - 2000-03-07 00:56:23
|
Hi. I've seen a lot of good stuff written in this list so far. (and were not even a week old ;) As for keeping things simple, the simplest way to get multi-console support is to add /dev/InputX (event) support to GGI. Someone said they were planning to do this, i forgot who. with /dev/InputX support, you should be able to run XGGI on one monitor, with a keyboard and mouse, and run a seperate instance on a second monitor, with a USB keybaord and differn't mouse. It might not be as flexable as you were hopeing, (actually you could probably just make extra drivers to generate /dev/InputX events, like one that hooks to telnetd, so someone could telnet in, and that input comming over the network could be used as the input of the console), or as fast as you were hopeing, but should be able to satisfy a large number of the cases, with minimal work, and get a lot more people interested in the project. (and ready to bitch about what they don't like with the way it's being done :) also i've heard that there's a ggi-terminal emulator, which let's you run a shell. Of course linus wouldn't be needed to do this either, since it dosn't mess with the kernel. also, another possiblity would be to make solid api's for the fb, and inputX, then create whatever console code you wanted in userspace, bypassing any of linus's kernel decisions. But adding event support to GGI is still the quickest way to get feedback. Corey (note: i don't know about others, but i intend to actually use this once it's created ;) ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com |