On Thu, 7 Dec 2006 08:14:50 +0900 Simon Fryer <[EMAIL PROTECTED]> wrote:
> Hey All, > > > A while ago Ben Calvert tapped: > > > On Mon, 4 Dec 2006 19:59:00 -0800 > > "Bryan Irvine" <[EMAIL PROTECTED]> wrote: > > > > [slow console on imac 333Mhz] > > > look at /etc/ttys. you'll notice the following: > > > > ttyC0 "/usr/libexec/getty std.9600" vt220 off secure > > ttyp0 none network > > > > > > the 9600 is the speed that data gets written to your console > > ( ttyc0 ). Notice that ttyp* (xterms, remote ssh sessions ) have no > > such restriction? > > Um, to my knowledge this disagrees with the /etc/ttys on my 3.9 i386 > box. > > The argument "std.9600" tells getty to set the serial port to 9600 > baud, which is only relavent if you are using a serial console. Hmm.. so then, what's this line for? console "/usr/libexec/getty std.57600" unknown off secure # for serial > To my > knowledge there is no *nix (OpenBSD or otherwise) that will throttle > a frame buffer based console in the way described. > , > I am ignoring the fact that in the example /etc/ttys, getty on ttyC0 > does not get executed. correct - i'm running xdm, so i disable the ttyC0 > > The real reason was given by an earlier message. Well, IANA(obsd)D, and IANTdR, so I'm hesitant to clam that I have access to the 'real' reason. but let me propose the following experiment: run an output intensive task on the console, then run X in wsfb mode, and run the same task in an xterm. compare the execution times. I bet you'll find that running the same app in an xterm -- using the same framebuffer -- is much faster than on the console. Ben ----- "The intrepid Spaceman Spiff is stranded on a distant planet! ..our hero ruefully acknowledges that this happens fairly frequently.." --- Calvin and Hobbes
