Re: [osol-discuss] Any groups working on consol developement
Harry Putnam wrote: I hope this doesn't come over as just more carping, but I'm wondering if any developers are actively working on making the console login evironment more efficient? Are there already ways available to make the console a place where work can get done quickly and efficiently? Maybe somekind of framebuffer type setup to allow higher resolutions? In the default state lines take nearly 1/3 inch of realistate. Just huge, not allowing a more usable amount of text to appear at once. Then too, having no mouse to grab stuff out of the scrollback buffer seems a big hinderance to getting things done quickly and efficiently. In fact, there appears to be no scrollback buffer in console mode. Or at least I'm not seeing how to access it. There must be skilled users who work in console mode extensivley, maybe someone can give me some tips. There have been virtual console functionality in solaris kernel. It's easy to extend the console environment, like scrollable screen in future. You can refer to project page on opensolaris.org for the latest status. If anyone from community can offer help, that will be great. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Project Proposal: OpenSolaris Programming Contest in China Academic Developers
+1 joey wrote: Hi Folks, Attached please find the Project proposal for the OpenSolaris programming contest in China academic developers. Your comments and backing are appreciated! Thanks, OpenSolaris Programming Contest Proposal 1. Executive Summary This proposal is to organize the OpenSolaris Programming Contest within academic developers in China. The goal of the programming contest is to cultivate the OpenSolaris academic developers in China, as well as grow the OpenSolaris community. The contest will target at 20,000 Sun Studio active users as well as 20,000 OpenSolaris registration. As the side result, several Intern candidates will be selected out of the winners for the Campus Ambassador program. The proposal focuses on China academic developers now, but it can be easily expanded to academic developers across the world, or even commercial developers in the future. 2. Background With the OpenSolaris Curriculum Program, there are over 90 China universities integrated OpenSolaris into the Operating System Curricula. Since this January, OpenSolaris Registration Promotion has been launched on OpenTech website in China and it has attracted over 14,000 OpenSolaris developers to register and request for OpenSolaris Starter Kit. Moreover, the success of ACM/ICPC Xi'An Regional Contest on OpenSolaris has proven the viability of programming contest using OpenSolaris and Sun Studio. To make the development environment widely available for new developers, we have set up the cutting-edge server (unix-center.net) installed with Solaris and Sun Studio in China. In the past 6 weeks, over 10,000 people have login this server to try the development environment. 3. The Program To enable the contestants to innovate based on OpenSolaris, several factors are key to the success of the contest: a. Rules to keep the contest attractive, fair play and innovation-oriented b. Effective promotion to catch the right people in right way at right time c. Engineering support from the OpenSolaris community and Solaris team As the contestant, he/she will attend the contest with the below procedure: Register the projects => Attend the free training => Implement the project => Test the project => Submit the project From the organization point, the below steps are critical: (1) Prepare for the contest rules (awards; registration, implementation and submission rules), advertise plan, supporting infrastructure (project website and technical advisory board); (2) Hold university roadshow to widely spread the contest; (3) Offer free training on OpenSolaris programming to academic developers both on-campus and on-line; (4) Provide technical support for the contestant during the project implementation; (5) Evaluate the OpenSolaris contest to choose out winners. Once the winners come out, the Campus Ambassador recruiting team will interview the Intern candidates. 3.1 Contest Rules The contestants have to register and submit the work by the deadline. 3.1.1 Eligibility All university student, undergraduate and postgraduate, are eligible to the participate the OpenSolaris programming contest. The contestants will register the contest as a group: 1) Each group consists of at most 3 players; 2) The group needs to invite a professor to act as the mentor; 3) Each group will have to choose a project from our published project list or propose a new project from their research; 4) A lead is selected to register the project and submit the source code on line on behalf of the whole group. 3.1.2 Registration A successful registration includes: 1) Each group member has to register a user on opensolaris.org 2) Submit project proposal and group information on the project page 3) Request DVD on OpenTech to set up the environment 4) Register on Unix-center.net to try the development environment (OpenSolaris and Sun Studio) After the registration, the group will be granted with: 1) A notification e-mail to congratulate their successful registration; 2) Under the project page, there will be a repository to contain all the documents and source code for the project; 3.1.3 Implementation 1) All source codes, creative or derivative, should be compliant with the Common Development and Distribute License (CDDL); 2) The project should be compiled and tested with Sun Studio (Studio 11, Studio Express or Studio 12 EA); 3) To ensure the compatibility, all the project should run the sanity test on unix-center.net; 3.1.4 Submission 1) The submitted source code should be licensed under CDDL; 2) All submission should be done on the project page on-line; 3) The complete submission will include project source code tarball, demo, user guides, supporting tools, etc.; 4) The newer submission will replace the existing submission without the version check tool. After the submission, a notification e-mail will send to the lead. 3.1.5 R
Re: [osol-discuss] Re: Virtual Console new release available NOW!
Richard L. Hamilton wrote:
LingBo Tang wrote:
Roland Mainz wrote:
[...]
- What about adding an option ("on" by default) to
use the first line of
the virtual console to hold the "window title" ?
This idea is quite interesting. But what will be
displayed in that
position? I'm afraid there is no sense to display
"console #" for end
users. But if we make the console display like X, why
not use X instead
of text mode?
Actually, it might be useful to display console number there (as an aid
to remembering which one is on), but also two other things (subdivide
the reserved line into three parts): an area reserved for a Trusted Solaris
Extensions window label (yes, even on console mode, at least if there is a
possibility that different virtual consoles could be assigned to different
zones), and an area reserved for a user-settable title (like one can have
in various terminal emulators via an escape sequence).
If the line was used for the special purpose, the tty window rows
(struct winsize member ws_row?) should be reduced by one accordingly.
If a TSX label was set (which shouldn't be possible by the user), the
line would be enabled automatically.
We may name this feature as Trusted Console. ;)
Anyway, we will try to investigate this with TX system.
If doable, we may have this feature because I really want to use
TX in text mode without touching global zone as in X.
Regards,
Lingbo
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
Re: [i18n-discuss] Re: [osol-discuss] Virtual Console new release available NOW!
We are going to request for the second round review by PSARC in next month. The exact build number may be known after that if the architecture looks good from PSARC viewpoints. Manoj Joseph wrote: LingBo Tang wrote: So far, we have no backport plan for S10. Would this be making its way into onnv? Which build? Cheers Manoj ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Virtual Console new release available NOW!
John Plocher wrote:
LingBo Tang wrote:
- What about adding an option ("on" by default) to use the first line of
the virtual console to hold the "window title" ?
This idea is quite interesting. But what will be displayed in that
position? I'm afraid there is no sense to display "console #" for end
users.
Since you already manage backing store copies, how about taking this
concept
and making a navigational aid out of it:
When you switch to a different virtual console, display the text
"console #xx" in row 1 column 65-75 for 1 to 2 seconds, then
replace it with the characters from the backing store.
At present, if you enable secure switching ( it's default ), after you
press "Alt + F#" sequence, the secure daemon will ask password first
if there has been one login user on that console. You can see the
name of virtual console like "vt3" in prompt line; If there is no login
user at that console, the login prompt also has such name while asking
username and passwd.
For online virtual console title display, I feel it's like a trusted
path stripe in Trusted Extensions GUI environment. The cost is we need
make sure this line can not be overrided or modified by any malicious
programs in kernel space.
Regards,
Lingbo
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
Re: [i18n-discuss] Re: [osol-discuss] Virtual Console new release available NOW!
Ken Frank wrote: I didnt see on the vconsole page about what it is and usually used for and how its used. Are there any pointers to this kind of information ? Also, Is it in current solaris 10 ? The usage of virtual console will like other existing OSes, like Linux. We are going to make the function compatible with Linux as much as possible except secure issues. We suppose the usage is straight forth. Of course, we will have a detailed documentation for solaris in future because it really has some extensions upon Linux' virtual console. You can refer the vconsole-discussion alias for some details. So far, we have no backport plan for S10. Regards, Lingbo ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Virtual Console new release available NOW!
[EMAIL PROTECTED] wrote:
On Thu, Apr 19, 2007 at 06:35:30PM +0800, LingBo Tang wrote:
- What about adding an option ("on" by default) to use the first line of
the virtual console to hold the "window title" ?
This idea is quite interesting. But what will be displayed in that
position? I'm afraid there is no sense to display "console #" for end
users.
But there is sense to name each virtual console so that each has
meaning full names e.g.:
- log
- /etc/syslog.conf (edition)
- dtrace script
- bash
etc
Of course you will know each console's name as "/dev/vt/#" ( which might
be more meaningful in future ), and you can use these names into any
places if you like.
At present, you can know the status of console login via "who" command,
as what you can do in other systems.
What is more, it would be good to have list of virtual consoles (like in
KVM switches) to switch between them.
We will have a GUI tool in X system to choose different X window if
there are more than one user logged into X via "gdmflexiserver".
For text mode, I think the command line like "vtchange vtno" maybe
more powerful.
Regards,
Lingbo
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Virtual Console new release available NOW!
Roland Mainz wrote:
LingBo Tang wrote:
This mail has been posted in virtual console discussion alias. The
broadcasting is for those who may be interested in this feature on solaris.
The new release for "Virtual Console" is available now, you can download
and try for fun:
http://opensolaris.org/os/project/vconsole/Downloads/
There is a brief changes list for your reference:
1. Add many secure feature, like secure switch via vtdaemon, which
require password during switching. Follow SMF policy for vtdaemon and
console-login service etc.
2. Virtual terminal names are changed as "/dev/vt/#", and the 1st
virtual terminal uses "/dev/console", which can be accessed via
"Alt-F1". The second one uses "/dev/vt/2" accordingly.
One small request: Could you please rename /dev/vt/ to something longer,
e.g. /dev/vtconsole/ (the idea is to make the name more descriptive and
avoid possible "fun" with name collisions � la libcmd (see
http://www.opensolaris.org/os/community/arc/caselog/2006/561/onepager/))
?
We will read the reference first.
3. You can keep pressing "Alt" key during switching between several
virtual consoles.
Random ideas/thoughs:
- What about adding a capabilty to cycle through virtual terminals, e.g.
using the <+>/<-> keys and/or / ?
There have been such functions:
1. "Alt+->" / "Alt+n" can go through all virtual consoles in ascending
order;
2. "Alt+<-" / "Alt+p" can go through all consoles in reverse turn;
3. "Alt+uparrow" / "Alt+l" will go back last used console;
Because of resource, there is no much doc for the usage, but you can
use this function like at other systems. Of course, any questions
or comments are welcome!
- A small tool would be nice to switch between virtual consoles from
scripts, add/remove consoles, enumerate consoles, dump current console
view to a file/stdout and set/get attributes, e.g. window title
we implemented necessary programming interfaces for above purpose in the
first step, some more tools will be available in next steps.
- What about adding an option ("on" by default) to use the first line of
the virtual console to hold the "window title" ?
This idea is quite interesting. But what will be displayed in that
position? I'm afraid there is no sense to display "console #" for end
users. But if we make the console display like X, why not use X instead
of text mode?
- Is there any plan for supporting an input method (e.g. to input
japanese/chinese/etc. (CC:'ing Ienup Sung <[EMAIL PROTECTED]> for
that...)) ?
This is out of scope for virtual console project. And I doubt whether
users will input such characters at command line.
Regards,
Lingbo
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
[osol-discuss] Virtual Console new release available NOW!
This mail has been posted in virtual console discussion alias. The broadcasting is for those who may be interested in this feature on solaris. The new release for "Virtual Console" is available now, you can download and try for fun: http://opensolaris.org/os/project/vconsole/Downloads/ There is a brief changes list for your reference: 1. Add many secure feature, like secure switch via vtdaemon, which require password during switching. Follow SMF policy for vtdaemon and console-login service etc. 2. Virtual terminal names are changed as "/dev/vt/#", and the 1st virtual terminal uses "/dev/console", which can be accessed via "Alt-F1". The second one uses "/dev/vt/2" accordingly. 3. You can keep pressing "Alt" key during switching between several virtual consoles. ... Your feedback are appreciated. Enjoy! Regards, Lingbo ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Project proposal: User Mode Driver
+1 [EMAIL PROTECTED] wrote: Hi, everyone, I would like to start a project to enable running a driver in usr mode as an application. By this way we can leverage source code from other OSes by converting them into Solaris user application. Also running in user mode make it easier to develop and debug. Maybe more robust. I would like to hear your opinions. Thank you --Freeman ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
