From: Ken Moffat <ken@kenmoffat.uklinux.net>
To: jbradford@dial.pipex.com
Cc: pommnitz@yahoo.com, linux-kernel@vger.kernel.org
Subject: Re: Framebuffer still "EXPERIMENTAL"?
Date: Sat, 28 Sep 2002 23:20:40 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.21.0209282313200.5184-100000@ppg_penguin.linux.bogus> (raw)
In-Reply-To: <200209281550.g8SFoeXx001215@darkstar.example.net>
On Sat, 28 Sep 2002 jbradford@dial.pipex.com wrote:
> >
> > Normal operation. Either switch to a different tty, or set a font.
>
> Hmmm, if that's normal operation, surely it's a bug?
>
Only if you don't need to set a font anyway to be able to see your
desired character set !
> Infact, why not use the wasted space to the right of the penguin for something useful - I.E. a status line, like on old terminals, showing disk and serial port activity!?
>
That space is reserved for more penguins! Think SMP, or perhaps a P4 with
hyperthreading! But seriously, once you've configured your machine
correctly the penguin doesn't stay around for long, so the space is not
available for a status line.
> > There does seem to be a bug in your mailer, though (excessive line
> > length) :->
>
> I guess maybe it's time for me to move away from using 'mail' from the command line for my day to day E-Mail needs :-(. Already, I have to use elm when I need the quoting capabilities so lacking from my favourite mailer :-).
>
> John.
>
Nothing wrong with doing it the hard way, I s'pose <g>
Ken
--
Out of the darkness a voice spake unto me, saying "smile, things could be
worse". So I smiled, and lo, things became worse.
prev parent reply other threads:[~2002-09-28 23:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-27 7:09 Framebuffer still "EXPERIMENTAL"? Joerg Pommnitz
2002-09-27 11:06 ` jbradford
2002-09-28 15:02 ` Ken Moffat
2002-09-28 15:50 ` jbradford
2002-09-28 22:20 ` Ken Moffat [this message]
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=Pine.LNX.4.21.0209282313200.5184-100000@ppg_penguin.linux.bogus \
--to=ken@kenmoffat.uklinux.net \
--cc=jbradford@dial.pipex.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pommnitz@yahoo.com \
/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;
as well as URLs for NNTP newsgroup(s).