From: Eric Piel <Eric.Piel@tremplin-utc.net>
To: Steve Barnhart <stb52988@gmail.com>
Cc: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: bootsplash integration
Date: Fri, 11 Aug 2006 19:07:39 +0200 [thread overview]
Message-ID: <44DCB95B.4060101@tremplin-utc.net> (raw)
In-Reply-To: <15ce3ec0608110839i586e6f5cj3fd448aeddf4cddb@mail.gmail.com>
08/11/2006 05:39 PM, Steve Barnhart wrote/a écrit:
> I am aware of Splashy and it does seem rather nice, but I also am for
> several alternatives and Bootsplash has been around for a long time
> and gensplash continues to enhance it. SuSE has used bootsplash
> forever and mandrake does also I believe. It would be nice to finally
> have one of those actually integrated into the kernel since the
> technology and patches to do so are already there. It requires less
> work out of people like me ha and would be a nice feature addition in
> addition to good alternatives like splashy.
>
The kernel only incorporates what is _really_ necessary. A jpeg decoder
and a progress bar manager would never become part of the kernel!
splashy proves that this kind of feature are absolutely not necessary in
the kernel as it's feasible in the user-space. Move to splashy, it'll
require you less work than patching your kernel ;-)
I just wonder if one can also put background pictures on the TTY only
from user-space...
See you,
Eric
next prev parent reply other threads:[~2006-08-11 17:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-11 14:36 Steve Barnhart
2006-08-11 14:52 ` Michal Piotrowski
2006-08-11 15:39 ` Steve Barnhart
2006-08-11 17:07 ` Eric Piel [this message]
2006-08-11 17:35 ` Alan Cox
2006-08-12 14:27 ` Vernon Mauery
2006-08-12 17:14 ` Jan Engelhardt
2006-08-17 16:02 ` Gábor Lénárt
2006-08-17 19:23 ` Jan Engelhardt
2006-08-17 15:54 ` Pavel Machek
2006-08-17 21:10 ` Otavio Salvador
2006-08-17 21:59 ` Valdis.Kletnieks
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=44DCB95B.4060101@tremplin-utc.net \
--to=eric.piel@tremplin-utc.net \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.k.k.piotrowski@gmail.com \
--cc=stb52988@gmail.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
all inboxes | Powered by JetHome®