OpenSolaris

Printable Version Enter a New Search
Bug ID 4309501
Synopsis Need additional local 'terminal'
State 10-Fix Delivered (Fix available in build)
Category:Subcategory kernel:console
Keywords iWork | kiss | modern_times | sunIT
Responsible Engineer Aaron Zang
Reported Against 2.0 , 2.8 , s10 , 5.10 , s10_69 , s10_71 , s10u1_15 , solaris_10 , solaris_10u2
Duplicate Of
Introduced In
Commit to Fix snv_100
Fixed In snv_100
Release Fixed solaris_nevada(snv_100)
Related Bugs 6341050 , 1178635 , 6452646 , 6480003 , 6624614 , 6695264 , 6752967 , 6758635 , 6759258 , 6764961 , 6767293 , 6775352 , 5062097 , 6191939 , 5107590
Submit Date 2-February-2000
Last Update Date 8-October-2008
Description
DETAILED DESCRIPTION: follows...
	Now that you guys have "unified" the console
	drivers for sparc and x86... How about adding
	a "clean" extra vty mechanism?
	
	The X server is still less than perfect. Sometimes,
	due to a problem with an APPLICATION, the entire
	X server will lockup.
	If the machine is not networked (due to security
	reasons), there is then no choice but to reset the
	server. This is unacceptible. It can result in the
	loss of valuable work.
	It just happened to me now, in fact (under 2.7)
	
	All that is neccessary is to have a simple
	"alternate console". Just a simple text-only
	vt, so that I can switch to that, kill the 
	offending process, and continue with my work.
	No, telling me "go find a wyse, a cable, and
	a null modem" is NOT an acceptible workaround.
	
	You dont even have to add lots of special
	"remember all the pixels on the screen" logic.
	Just force a full refresh via the X server.
		Similarly, all the text-based vt has to do, is
	remember 80x34 chars, and redraw them if made
	active.
	
	This should NOT be a lot of work for your expert
	programmers. Worst case, you can steal from some
	of the old x86 code, and fix the problems with it.

Hi Philip, 

What you are asking is not a supported feature. However, the following document may be helpful.

Thanks
Aparna



********************************************************************************
********************************************************************************

INFODOC ID: 13128
STATUS: Issued

SYNOPSIS: Setting up Solaris 2.x x86 to support Virtual Consoles
DETAIL DESCRIPTION:

The following directions are for setting up virtual consoles on Solaris 2.x 
x86.  Never try to start openwin under a virtual console.  It will fail 
and can lock your machine.  This means do not use openwin with CDE if it
is set up to auto-start during boot-up.

- First create the /dev entries.

# mknod /dev/vt01 c 100 1
# mknod /dev/vt02 c 100 2
# etc...

- Next, add the following to /etc/inittab (after the co entry):

v1:234:respawn:/usr/lib/saf/ttymon -g -h -p "VT01 Login: " -T AT386 -d 
/dev/vt01 -l console
v2:234:respawn:/usr/lib/saf/ttymon -g -h -p "VT02 Login: " -T AT386 -d
/dev/vt02 -l console

- Note: these are single lines that wrap around. (i.e., the above lines
  are two single lines and not four single ones)

- For inittab to use these new entries, it must receive the HUP signal:

# ps -e | grep init            (to determine the init process number)
     1 ?        0:08 init      (normally it is '1')
# kill -HUP 1

- Finally, test the virtual consoles:
 
- Use Alt-PrintScreen plus Function-Key to switch.
  Alt-PrintScreen F1 switches to VT01
  Alt-PrintScreen F2 switches to VT02

  Alt-PrintScreen P  switches to previous screen
  Alt-PrintScreen N  switches to next     screen
  Alt-PrintScreen H  switches to console  screen 

- Remember NOT to use openwin in a virtual console.


I KNOW it's not a supported feature. My service order detailed why it is still a
NECCESSARY feature.

I am quite familiar with the infodoc below.
Again, AS I MENTIONED IN THE SERVICE ORDER, this feature is GOING AWAY in
solaris 8
due to "consolidation" of the console drivers.

I want an RFE filed on this issue.
Work Around
N/A
Comments
N/A