public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: christophe barbe <christophe.barbe@inup.com>
To: Mike Galbraith <mikeg@wen-online.de>
Cc: christophe barbe <christophe.barbe@inup.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] Animated framebuffer logo for 2.4.1
Date: Fri, 9 Feb 2001 09:12:27 +0100	[thread overview]
Message-ID: <20010209091227.A28797@pc8.inup.com> (raw)
In-Reply-To: <20010208150859.A19950@pc8.inup.com> <Pine.Linu.4.10.10102090732320.1612-100000@mikeg.weiden.de>
In-Reply-To: <Pine.Linu.4.10.10102090732320.1612-100000@ mikeg.weiden.de>; from mikeg@wen-online.de on ven, fév 09, 2001 at 08:03:14 +0100

On ven, 09 fév 2001 08:03:14 Mike Galbraith wrote:
> I hope that nothing like this is _ever_ integrated (and doubt I need
> be concerned;).  IMHO, hiding output from users arrogantly assumes
> that they are too stupid/ignorant to have any use for such information.

Most user don't want to learn the internal stuff of their OS. They only want to use it and assume (or would like to) that everything is ok. 
You hope graphic boot capability will never be integrated in the kernel but I'm sure you are aware of what is an "OPTION".

Sure it's not a vital need. Distribution makers can already add this on their kernels (and in fact they do that, per example by using aurora). But it could result in a proper implementation. Required modifications are really small.

Moreover there is no need to be ignorant. With LPP, messages are displayed during the boot process and if something goes wrong an little picture inform you. And you can switch to the classic console when you want (by a simple CTRL-ALT-F2).

Christophe

-- 
Christophe Barbé
Software Engineer
Lineo High Availability Group
42-46, rue Médéric
92110 Clichy - France
phone (33).1.41.40.02.12
fax (33).1.41.40.02.01
www.lineo.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  parent reply	other threads:[~2001-02-09  8:13 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-01 17:32 [ANNOUNCE] Animated framebuffer logo for 2.4.1 Juergen Schneider
2001-02-07 23:40 ` Pavel Machek
2001-02-08 12:37   ` Mike A. Harris
     [not found]     ` <Pine.LNX.4.33.0102080736190.5431-100000@as df.capslock.lan>
2001-02-08 14:08       ` christophe barbe
2001-02-08 18:42         ` Miles Lane
2001-02-09  7:03         ` Mike Galbraith
     [not found]           ` <Pine.Linu.4.10.10102090732320.1612-100000@ mikeg.weiden.de>
2001-02-09  8:12             ` christophe barbe [this message]
2001-02-09  9:45               ` Mike Galbraith
2001-02-12 11:00                 ` Adrian Cox
2001-02-11 14:07     ` Werner Almesberger
2001-02-12 15:23 ` Martin Laberge
2001-02-12 22:31   ` Miles Lane
2001-02-13  3:46 ` Rafael E. Herrera
2001-02-13  5:10 ` Jonathan Morton
2001-02-13  7:11   ` Rafael E. Herrera
  -- strict thread matches above, loose matches on Subject: below --
2001-02-09  9:21 Helge Hafting
2001-02-09  9:32 ` David Lang
2001-02-09 10:21 ` Miles Lane
2001-02-09 11:36   ` Werner Almesberger
2001-02-09 11:47     ` Miles Lane
2001-02-09 12:28       ` Werner Almesberger
2001-02-10  3:50     ` Nick Papadonis
2001-02-09 16:40   ` Mike Porter
2001-02-11 22:47   ` Pavel Machek
2001-02-12 17:18     ` Peter Kundrat
2001-02-12 22:00     ` Miles Lane

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=20010209091227.A28797@pc8.inup.com \
    --to=christophe.barbe@inup.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikeg@wen-online.de \
    /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