mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Henk <Henk.Vergonet@gmail.com>
To: Edgar Toernig <froese@gmx.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] new 7-segments char translation API
Date: Mon, 6 Jun 2005 11:26:08 +0200	[thread overview]
Message-ID: <20050606092608.GA16471@god.dyndns.org> (raw)
In-Reply-To: <20050605005329.70d9461a.froese@gmx.de>

On Sun, Jun 05, 2005 at 12:53:29AM +0200, Edgar Toernig wrote:
> By your reasoning /usr/dict/words had to be in the kernel,
> too.

Well by my reasoning you should, if possible, define some usefull
standards that will allow te reuse of these dictionaries within other
applications.

And while we're on the subject of whats IN or OUT, (and I'll bet if you
ask 10 kernel developers you'll get 10 answers but I try anyway ;)

In my philosophy the OS (kernel + device drivers) is an abstraction of
the machine, it should present the 'machine' in such a way that allows
for other abstractions such as a word processor to operate without having
to know the specifics of hardware devices.

To have a guideline on the 7 segments notation and to have a few defines
that allow ASCII chars to be represented on 7 segments displays also help
to support the 'machine' abstraction.

Wheter or not /usr/dict/words should be 'in the kernel' is not being
discussed here, so I am not going to elaborate on that.

Cheers,

henk


PS I am not on the list, so please use CC if you're interested in a response.
PS Please excuse any spelling mistakes, I don't have a spelling checker
installed...



  reply	other threads:[~2005-06-06  9:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-31 22:07 Henk
2005-06-01  8:43 ` Jan-Benedict Glaw
2005-06-01 10:04 ` Henk
2005-06-01 12:33 ` Clemens Koller
2005-06-03 20:50   ` Henk
2005-06-04 20:44   ` Henk
2005-06-04 22:53     ` Edgar Toernig
2005-06-06  9:26       ` Henk [this message]
2005-06-06 16:19         ` randy_dunlap
2005-06-21 21:30           ` Henk
2005-06-04 15:24 ` 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=20050606092608.GA16471@god.dyndns.org \
    --to=henk.vergonet@gmail.com \
    --cc=froese@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®