Date: Fri, 28 Oct 2005 14:35:40 -0400 From: John Baldwin <jhb@freebsd.org> To: babkin@users.sourceforge.net Cc: Gordon Bergling <gbergling@0xfce3.net>, phk@phk.freebsd.dk, freebsd-arch@freebsd.org Subject: Re: wscons for FreeBSD? Message-ID: <200510281435.41700.jhb@freebsd.org> In-Reply-To: <12768156.1130520253107.JavaMail.root@vms073.mailsrvcs.net> References: <12768156.1130520253107.JavaMail.root@vms073.mailsrvcs.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Friday 28 October 2005 01:24 pm, Sergey Babkin wrote: > >From: John Baldwin <jhb@freebsd.org> > > > >> Things that are personally crucial to me: > >> * Speed. (syscons is lightning fast) > >> * text mode mouse cursor with cut/paste that Just Works. > >> * cursor movement control code compatibility. No less than perfect > >> compatibility is good enough! The cons25 termcap entry has to work. > > > > * truly supports framebuffers as well as displays that can render text > > directly (i.e. VGA, EGA, etc.) > > * allows displays, keyboards, and mice to be tied together in arbitrary > > combinations such that each "console" can consist of zero-or-more > > displays, keyboards, and mice with well-defined behavior for what > > state is shared vs. private when multiple objects of the same class > > are connected to a single console. > > And by default connects all the keyboards/mice to > the first console. This makes the installs on > the machines with USB-only keyboard transparent. Yes. > * When entering panic/debugger mode the console > should reset its video mode to the one where > the panic information is visible. I think this might be kind of hard since you really don't know what X has done to the hardware unless you make X talk to the console driver to do everything. -- John Baldwin <jhb@FreeBSD.org> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200510281435.41700.jhb>