From: Troy Dack <tad@gentoo.org>
To: "gentoo-dev@gentoo.org" <gentoo-dev@gentoo.org>
Subject: Re: [gentoo-dev] Fwd: Re: Bootsplash in 2.6 kernels
Date: Thu, 06 Nov 2003 23:52:11 +1100 [thread overview]
Message-ID: <1068123130.6232.2.camel@carbon.internal.lan> (raw)
In-Reply-To: <200311060725.38687.mafteah@mafteah.co.il>
[-- Attachment #1: Type: text/plain, Size: 1209 bytes --]
On Thu, 2003-11-06 at 16:25, Okrain Genady wrote:
> ---------- Forwarded Message ----------
>
> Subject: Re: Bootsplash in 2.6 kernels
> Date: Thursday 06 November 2003 00:52
> From: Stefan Reinauer <stepan@bootsplash.org>
> To: Okrain Genady <Mafteah@Mafteah.Co.iL>
> Cc: kwwii@bootsplash.org
>
> Okrain Genady wrote:
> >I want to use 2.6 kernel but no bootsplash there.
> >You are doing something about it?
> >When a patch for 2.6 will released?
>
> It took quite a while, but here's an initial version:
>
> ftp://ftp.suse.com/pub/people/stepan/bootsplash/kernel/bootsplash-3.1.1-2.6.0
> -test9.diff
>
Applies and builds cleanly against -test9-mm1.
I can't seem to get the initrd image to come up.
Setting the image manually from the cli using the 'splash' utility works
however.
Building a VM to test the initrd stuff some more. It's easier to
continually reboot the VM than my box :)
--
Troy Dack Gentoo moves pretty fast; if you don't stop and
tad@gentoo.org look around once in awhile, you could miss out.
Public Key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x4D90BE3C
Key fingerprint = 1F3D 6C15 16AA 09D5 0C96 92E5 FD89 16F9 4D90 BE3C
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2003-11-06 12:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-06 5:25 [gentoo-dev] Fwd: Re: Bootsplash in 2.6 kernels Okrain Genady
2003-11-06 12:52 ` Troy Dack [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=1068123130.6232.2.camel@carbon.internal.lan \
--to=tad@gentoo.org \
--cc=gentoo-dev@gentoo.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