The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Microcai <microcai@fedoraproject.org>
To: Alexey Gladkov <gladkov.alexey@gmail.com>
Cc: "Ted Ts'o" <tytso@mit.edu>, Lisa Milne <lisa@ltmnet.com>,
	"jonsmirl@gmail.com" <jonsmirl@gmail.com>,
	linux-kernel@vger.kernel.org, linux-console@vger.kernel.org,
	Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: VT console need rewrite
Date: Mon, 29 Nov 2010 10:14:06 +0800	[thread overview]
Message-ID: <1290996846.877.23.camel@cai.gentoo> (raw)
In-Reply-To: <4CF3081B.9090307@gmail.com>

在 2010-11-29一的 04:55 +0300,Alexey Gladkov写道:
> 28.11.2010 22:46, Ted Ts'o wrote:
> > How many people do regular login, development, reading e-mail, etc.,
> > on the console?  Very few!
> 
> Once I broke the euro symbol in the kbd keymaps and got a kick in the
> ass very quickly :). It means that users continue to use the console
> quite active.
> 
> Another example: I keep getting a new keymaps and console fonts for
> each new kbd release.
> 
> Maybe not a lot of console users, but more of them than you think.
> 
> > If the answer is because you hate X, as
> > you've already pointed out, we already have fbterm.  Where is it
> > written that we need to have a full unicode-capable console system?
> 
> fbterm ‎can't help in all cases. For example: we have a limitation
> NR_KEYS, which makes it impossible to use keycode > 256 in keymaps.
> I've already received several complaints about it.
> 

YES, user-space can't always fit! Some function need to be implemented
in kernel. And that's why we have KMS, we have auto cgroup ....

Don't say, hey , hard to implement, all you have to to is apply the
path .. No need to do for you.

If the patch isn't as good as you expected, reject, I'll try better one.
The thing is, you really should agree that, implementing UNICODE font in
kernel isn't a bad idea.




  reply	other threads:[~2010-11-29  2:13 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-28 10:57 VT console need rewrite Microcai
2010-11-28 13:24 ` Theodore Tso
2010-11-28 13:42   ` Microcai
2010-11-28 14:05     ` jonsmirl
2010-11-28 14:29       ` Microcai
2010-11-28 14:49         ` jonsmirl
2010-11-28 19:11         ` Samuel Thibault
2010-11-29  1:10           ` Microcai
2010-11-29  2:49             ` Américo Wang
2010-11-29  2:48               ` Microcai
2010-11-29  8:16             ` Samuel Thibault
2010-11-29  8:20               ` microcai
2010-11-29  8:27                 ` Samuel Thibault
2010-11-29  8:53                   ` Microcai
2010-11-29  8:59                     ` Samuel Thibault
2010-11-28 16:06       ` Lisa Milne
2010-11-28 16:20         ` Microcai
2010-11-28 19:46           ` Ted Ts'o
2010-11-29  1:14             ` Microcai
2010-11-29  8:58               ` Samuel Thibault
2010-11-29  9:32                 ` Microcai
2010-11-29  9:58                   ` Samuel Thibault
2010-11-29 10:11                     ` Microcai
2010-11-29 10:17                       ` Samuel Thibault
2010-11-29 10:40                         ` Microcai
2010-11-29 10:39                           ` Samuel Thibault
2010-12-15 14:45                     ` Pavel Machek
2010-12-15 15:04                       ` Samuel Thibault
2010-11-29  1:55             ` Alexey Gladkov
2010-11-29  2:14               ` Microcai [this message]
2010-11-29 14:02                 ` Alan Cox
2010-11-29 17:50                 ` Valdis.Kletnieks
2010-11-29 21:23                   ` Jerome Glisse
2010-11-28 23:46           ` Alan Cox
2010-11-29  1:28             ` Microcai
2010-11-29 14:07               ` Alan Cox
2010-11-30  5:05                 ` microcai
2010-12-20  6:35                   ` Pavel Machek
2010-11-29 10:01 ` Andi Kleen
2010-11-29 10:12   ` Microcai
2010-12-07 20:37     ` Jesse Barnes
2010-12-13  7:13   ` Pavel Machek
2010-12-13 10:18     ` Alan Cox
2010-12-15 14:40       ` Pavel Machek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1290996846.877.23.camel@cai.gentoo \
    --to=microcai@fedoraproject.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=gladkov.alexey@gmail.com \
    --cc=jonsmirl@gmail.com \
    --cc=linux-console@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lisa@ltmnet.com \
    --cc=tytso@mit.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox