mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Matt Mackall <mpm@selenic.com>
Cc: Miguel Boton <waninkoko@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] logo: random logo selection option
Date: Sat, 12 Sep 2009 09:25:05 +0200	[thread overview]
Message-ID: <10f740e80909120025v7ac5358ew48ae52d9cee5f078@mail.gmail.com> (raw)
In-Reply-To: <1252734272.31016.94.camel@calx>

On Sat, Sep 12, 2009 at 07:44, Matt Mackall<mpm@selenic.com> wrote:
> On Sat, 2009-09-12 at 01:03 +0200, Miguel Boton wrote:
>> If we select more than one logo in the kernel configuration, only the 'latest' one gets
>> displayed. Because of this the other logos do not ever have a chance to be displayed.
>>
>> This patch adds a selectable option to display a random logo during the bootup process.
>> This way the kernel will be able to display any available logo, making the bootup process
>> a little different every time ;)
>
> [I foolishly read every LKML message with 'random' in the title..]
>
> Bonus points if you add printing a fortune from a compiled-in fortune
> database? Let's not do this, please. Our goal is instead to boot so fast

Hey, we already have a compiled-in fortune database to choose from
(unless CONFIG_PRINTK is disabled)?

> that such things aren't visible.

100% agreed.

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds

      reply	other threads:[~2009-09-12  7:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-11 23:03 Miguel Boton
2009-09-12  5:44 ` Matt Mackall
2009-09-12  7:25   ` Geert Uytterhoeven [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=10f740e80909120025v7ac5358ew48ae52d9cee5f078@mail.gmail.com \
    --to=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpm@selenic.com \
    --cc=waninkoko@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®