I don't agree... again. What is the semantics _users_ are the most
comfortable with ? an stty size or a resolution ? All OSes so far
let user pick up resolutions (w/h/freq), this is the thing users are
getting used to :) 

  Fbcon is a graphical emulation of a VT220. You set a terminal size with 
stty. I do it all the time when logged in with a serial console. I'm going
to work on vgacon to also be able to change the size of text terminal. The 
same goes for sticon etc. See we have one tool that works on ANY terminal
if resizing is supported. Otherwise we need to make stiset and a vgaset.
Yuck!!!
   Now if the user want to program a graphics application and run it on 
the console then fine. I plan to put in sysfs a way to cat a string to
change the resolution using modedb. Then you get the function you want 
above.

Modedb isn't always a solution with some fancy displays too...

Then you add to the modedb. Right now we lack that functionalty.

Also, if I ever start doing dual head, I'll have interesting side
effects to deal with, which means for example  that enabling mirroring
will possibly change the resolution of the primary head. That means that
I'll have to trigger a mode change in console based on ... a resolution,
not a console size. I just want the console size to adapt.

I take up the challenge. I have dual head matrox card to experiment with.



-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g. 
Take an Oracle 10g class now, and we'll give you the exam FREE. 
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click