[vconsole-discuss] vconsoles: physical and ttya console
Yes, virtual console provides this functionality. You can redirect system console to ttya/ttyb and the other virtual consoles would be left as is. Regards, Aaron Jim Klimov wrote: Is it possible with the current vconsole infrastructure to set up ttya/ttyb and physical console in parallel, i.e. to administer a server remotely as well as with a keyboard? -- This message posted from opensolaris.org ___ vconsole-discuss mailing list vconsole-discuss at opensolaris.org http://mail.opensolaris.org/mailman/listinfo/vconsole-discuss
[vconsole-discuss] virtual console new release based on snv_85
Hi all, The new release for virtual console is available on OpenSolaris now. Please check out the download page of virtual console project: http://opensolaris.org/os/project/vconsole/Downloads/ And for those who have access to SWAN, you can get the install DVD image at: /net/jericho.prc/export/home/workspace/vt_85x_product3/solarisdvd.iso My apology to the others. Since our download center has limited disk space, uploading the whole DVD install image is not welcomed. Regards, Aaron
[vconsole-discuss] vconsoles: physical and ttya console
jimklimov at cos.ru wrote: Thanks... and where would the system messages go? Is there still one sink device for /dev/console - EITHER physical OR ttya? Yes, you are right. And the system message would still go to /dev/console by default. //Jim Aaron Zang wrote: Yes, virtual console provides this functionality. You can redirect system console to ttya/ttyb and the other virtual consoles would be left as is. Regards, Aaron Jim Klimov wrote: Is it possible with the current vconsole infrastructure to set up ttya/ttyb and physical console in parallel, i.e. to administer a server remotely as well as with a keyboard? -- This message posted from opensolaris.org ___ vconsole-discuss mailing list vconsole-discuss at opensolaris.org http://mail.opensolaris.org/mailman/listinfo/vconsole-discuss
[vconsole-discuss] -k or disable options/hotkeys
End users are not supposed to interact with /usr/lib/vtdaemon binary directly, instead they should manage VT via SMF functionalities. The -k option is used to disable VT switching even when vtdaemon SMF service is running. Yes, vtdaemon manpage will be provided in the future. Regards, Aaron On 12/10/08 09:10, Robert Milkowski wrote: What's the reason for -k option? When would it be useful? Also, do you intend to provide vtdaemon man page? -- You know some birds are not meant to be caged, their feathers are just too bright.
[vconsole-discuss] Need a VT console HOW to:
Hi Ron, Thanks for the feed back. If you can describe your problem more concisely, we can better solve it. We need the information such as how many console-login service instances are there. If console-login:vt3 does not exist, ALt F3 does nothing even if vtdaemon is running. And there are too many other possibilities that your hotkeys do not work. It might be the problem of your keyboard layout or it could be hardware issues... This project is still under development, what people can use now is the fruit of phase 1. So the documents may not be very comprehensive, please be patient. I understand your feelings when struggling to get everything to working on your desktop, but better communication comes from polite communication. So if we really want to solve the problem, using emotional words help nothing. Regards, Aaron On 12/15/08 01:05, Ron Halstead wrote: On build 103, I have set hotkeys = true, refreshed the service so that pgrep -fl vtdaemon shows 17590 /usr/lib/vtdaemon -c 16 but ALT L f3 does nothing. I assume Alt L means the left Alt key. Nowhere have I seen a concise writeup of how to set up and use virtual console. Its as if this feature is a puzzle and the prize is, it works, but only If you solve the puzzle. Someone posted above the description lame. 1+ --ron -- You know some birds are not meant to be caged, their feathers are just too bright.
[vconsole-discuss] How can I know, the machine is vm or physical?
Hello, I think you got the wrong alias. This is the alias for the discussion about virtual console, which is not related to virtual machine. You may want to send your question to xen-discussion at opensolaris.org, there may be experts to answer your question. Regards. Aaron Paresh Devalekar wrote: Hi, I have one requirement, where I have to check, whether machine is physical or VM (virtual machine)? Anyone have idea, how to know it? Regards, Paresh -- This message posted from opensolaris.org ___ vconsole-discuss mailing list vconsole-discuss at opensolaris.org http://mail.opensolaris.org/mailman/listinfo/vconsole-discuss
[vconsole-discuss] How can I know, the machine is vm or physical?
Aaron Zang wrote: Hello, I think you got the wrong alias. This is the alias for the discussion about virtual console, which is not related to virtual machine. You may want to send your question to xen-discussion at opensolaris.org, there may be experts to answer your question. Correct email alias, should be xen-discuss at opensolaris.org Regards. Aaron Paresh Devalekar wrote: Hi, I have one requirement, where I have to check, whether machine is physical or VM (virtual machine)? Anyone have idea, how to know it? Regards, Paresh -- This message posted from opensolaris.org ___ vconsole-discuss mailing list vconsole-discuss at opensolaris.org http://mail.opensolaris.org/mailman/listinfo/vconsole-discuss ___ vconsole-discuss mailing list vconsole-discuss at opensolaris.org http://mail.opensolaris.org/mailman/listinfo/vconsole-discuss
[vconsole-discuss] options/hotkeys
On 10/14/09 19:20, John Levon wrote: On Wed, Oct 14, 2009 at 09:21:34AM +0800, Aaron Zang wrote: Sorry, I missed your email since there were so many of them. No problem. Running b124 on a Lenovo T61P. If I do ctrl-alt-F1 from X when options/hotkeys is false, I do not get any ttymon visible, just a blank screen. What is this undocumented option, and why is it necessary? vtdaemon and console-login are enabled as expected. vtdaemon was designed to be enabled by default, although it is not the case now. So this option could be used to stop switching temporarily without disabling the whole service. I think I'm being a bit dumb: what's the point of enabling vtdaemon when it doesn't do anything useful without further config? That is, what's the intention of vtdaemon enabled, hotkeys==false? There are various reasons for doing so. For example, you lock up your gnome session, want to leave, and do not want others to switch to other consoles and login to your desktop. Worse, if you accidentally switch without setting hotkeys, then you've killed your machine - with no way to switch back, a hard reboot is needed. This is a bug, filed 6891778. There still be some flaws and imperfections, so if you want to us VT feature now, please set options/hotkeys true. Otherwise just disable the vtdaemon service. Do you want me to file a manpage bug so this requirement is documented somewhere? Already have one 6767228. Also, switching vt means resume fails (never get back the X display). I see this is an old bug, is there a fix planned? I think Alan gave a good list of the bugs. I am fixing 6885612 though there has already been a workaround available in snv_125. OK, thanks. regards john -- You know some birds are not meant to be caged, their feathers are just too bright.
[vconsole-discuss] vconsole [bluid 130]: does it work ?
Hi,
I am investigating the problem. And I was able to reproduce it,
it is not an hardware specific problem. Since 130 has new gdm and
Xorg was upgrade to 1.7.2, there might be some problems with the
cooperation between the kernel and Xorg and new gdm.
Regards,
Aaron
Francois Marcoux wrote:
Hello All,
I have the same issue as Neal. My laptop (Toshiba Tecra M3) has been
installed in osol2009.06 then upgraded to snv_130. Virtual Consoles do
not appear to work. That's the first time I test this feature, so I
don't know whether it worked before.
When using CNTRL-LALT-F# (F1 to F6), I get a garbled screen, mostly
black with a blurred OpenSolaris logo in the background. I can go back
to my graphical session by typing CNTRL-LALT-F# (F1 to F6 only) or by
typing LALT-F# (F1 to F6 only). See some traces at the end of this
email. I don't really see any error message.
As Neal, my laptop is using a nvidia graphics card.
Francois.
On 12/21/09 05:52 PM, Aaron Zang wrote:
/ Hi Neal,
//
// I updated the project page with the latest changes.
// My apologies for the inconvenience.
//
// http://hub.opensolaris.org/bin/view/Project+vconsole/
//
// Does it work on your system?
/
I had this working well on build 129 of OpenSolaris.
Today, I updated to build 130 (pkg image-update) which has new gnome
and also
new xorg, and virtual consoles appear to be very broken now.
FYI
Neal
/
// Regards,
// Aaron
//
// On 12/22/09 05:49, Neal Pollack wrote:
//On 12/21/09 12:41 PM, Alan Coopersmith wrote:
// Neal Pollack wrote:
// - If so, where is a simple step by step guide for turning it on.
//
http://mail.opensolaris.org/pipermail/opensolaris-announce/2009-August/001249.html
//
//
// (The same message was sent as an ON heads up as well, but the
// archives of those
// are currently non-functional, but those are less useful anyway,
// since they go
// to the much smaller audience of just ON developers instead of the
// broader user
/
fmarcoux at fmalaptop:~$ pfexec svcs *vt*
STATE STIMEFMRI
online 13:53:38 svc:/system/console-login:vt3
online 13:53:39 svc:/system/console-login:vt6
online 13:53:39 svc:/system/console-login:vt2
online 13:53:39 svc:/system/console-login:vt4
online 13:53:39 svc:/system/console-login:vt5
online 14:47:18 svc:/system/vtdaemon:default
fmarcoux at fmalaptop:~$ pgrep -lf vt
468 /usr/lib/saf/ttymon -g -d /dev/vt/4 -l console -m ldterm,ttcompat
-h -p fmalapt
483 /usr/lib/saf/ttymon -g -d /dev/vt/2 -l console -m ldterm,ttcompat
-h -p fmalapt
452 /usr/lib/saf/ttymon -g -d /dev/vt/3 -l console -m ldterm,ttcompat
-h -p fmalapt
479 /usr/lib/saf/ttymon -g -d /dev/vt/5 -l console -m ldterm,ttcompat
-h -p fmalapt
466 /usr/lib/saf/ttymon -g -d /dev/vt/6 -l console -m ldterm,ttcompat
-h -p fmalapt
1543 /usr/lib/vtdaemon -s -c 16
fmarcoux at fmalaptop:~$ ls -l /dev/vt
total 0
crw--- 1 root root 15, 0 2010-01-05 13:53 0
crw--- 1 root root 15, 1 2010-01-05 13:53 1
crw--- 1 root root 15, 10 2010-01-05 13:54 10
crw--- 1 root root 15, 11 2010-01-05 13:54 11
crw--- 1 root root 15, 12 2010-01-05 13:54 12
crw--- 1 root root 15, 13 2010-01-05 13:54 13
crw--- 1 root root 15, 14 2010-01-05 13:54 14
crw--- 1 root root 15, 15 2010-01-05 13:54 15
crw--w 1 root tty 15, 2 2010-01-05 13:53 2
crw--w 1 root tty 15, 3 2010-01-05 13:53 3
crw--w 1 root tty 15, 4 2010-01-05 13:53 4
crw--w 1 root tty 15, 5 2010-01-05 13:53 5
crw--w 1 root tty 15, 6 2010-01-05 13:53 6
crw--- 1 root root 15, 7 2010-01-05 13:54 7
crw--- 1 root root 15, 8 2010-01-05 13:54 8
crw--- 1 root root 15, 9 2010-01-05 13:54 9
lrwxrwxrwx 1 root root 1 2010-01-05 13:53 active - 7
fmarcoux at fmalaptop:~$ svcprop vtdaemon | grep options
options/nodecount count 16
options/value_authorization astring solaris.smf.value.vt
options/hotkeys boolean true
options/secure boolean false
fmarcoux at fmalaptop:~$
Pressing CTRL-LALT-F2, the truss of vtdaemon yields.
1543/3:door_return(0x, 0, 0x, 0xCE8AFE00,
1007360) = 0
1543/3:mmap(0x, 1040384, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_NORESERVE|MAP_ANON, -1, 0) = 0xCE6B3000
1543/3:uucopy(0xCE8AF8A4, 0xCE7B0FEC, 20)= 0
1543/3:lwp_create(0xCE8AFB34, LWP_DETACHED|LWP_SUSPENDED,
0xCE8AFB30) = 4
1543/3:lwp_continue(4)= 0
1543/4:lwp_create()(returning as new lwp ...)= 0
1543/4:setustack(0xCE9F1A60)
1543/4:schedctl()= 0xCE9E5030
1543/3:yield()= 0
1543/3:door_ucred(0x08064BE0)= 0
1543/3:open(/dev/vt/1, O_WRONLY)= 2
1543/3:ioctl(2, (('V'8)|100), 0xCE8AFD60)= 0
1543/3:close(2
