public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: John Bradford <john@grabjohn.com>
To: Raphael_Schmid@CUBUS.COM (Raphael Schmid)
Cc: rob@r-morris.co.uk, Raphael_Schmid@CUBUS.COM,
	linux-kernel@vger.kernel.org
Subject: Re: AW: Bootscreen
Date: Tue, 28 Jan 2003 14:26:27 +0000 (GMT)	[thread overview]
Message-ID: <200301281426.h0SEQRRn001008@darkstar.example.net> (raw)
In-Reply-To: <398E93A81CC5D311901600A0C9F29289469380@cubuss2> from "Raphael Schmid" at Jan 28, 2003 03:11:10 PM

> > Wait screen, then just hangs", which would then require an
> > engineer visit, as opposed to, for example, "it says Obtaining IP
> > Address... then hangs"
> I do have a solution for that. Just make the image 640x440 instead
> 640x480, and have the initscripts output on one of the lower lines
> only, always over-writing the previous message. That way, the
> support engineer would know what's going wrong and you'd still have
> a cute picture.

At the moment, the framebuffer reserves a few lines for the Tux icons,
and uses the rest for text.  Why not just modify that code to achieve
what you want, (a large logo, and a text window).

You could do that on the Atari 65XE, have a text mode window at the
bottom of a graphics screen :-)

John

  reply	other threads:[~2003-01-28 14:16 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-28 14:11 AW: Bootscreen Raphael Schmid
2003-01-28 14:26 ` John Bradford [this message]
2003-01-28 14:48   ` Bootscreen Stefan Reinauer
2003-01-28 14:29 ` AW: Bootscreen Robert Morris
2003-01-28 14:59   ` Bootscreen Stefan Reinauer
2003-01-28 14:34 ` Bootscreen jeff millar
2003-01-28 14:40   ` Bootscreen John Bradford
2003-01-29 13:09     ` Scaring the non-geeks (was Bootscreen) Roy Sigurd Karlsbakk
2003-01-29 13:19       ` Richard B. Tilley  (Brad)
2003-01-29 13:58         ` Xavier Bestel
2003-01-29 14:01           ` Richard B. Tilley  (Brad)
2003-01-29 17:15             ` Wakko Warner
2003-01-29 14:12           ` Murray J. Root
2003-01-29 14:51             ` Tomas Szepe
2003-01-29 15:08         ` Alan Cox
2003-01-29 17:12       ` Rik van Riel
2003-01-30 18:53       ` Lars 'Cebewee' Noschinski
2003-01-30 19:29         ` Chris Friesen
2003-01-31  2:04         ` Barry K. Nathan
2003-01-31 16:09           ` Alvaro Lopes
2003-01-28 16:41   ` Bootscreen Valdis.Kletnieks
  -- strict thread matches above, loose matches on Subject: below --
2003-01-29 14:01 AW: Bootscreen Raphael Schmid
2003-01-29 11:56 Raphael Schmid
2003-01-29 12:33 ` Tomas Szepe
2003-01-29 13:54   ` John Bradford
2003-01-29 15:11     ` Dave Jones
2003-01-29 14:00 ` Jesse Pollard
2003-01-28 15:18 Raphael Schmid
2003-01-28 14:58 Raphael Schmid
2003-01-28 15:52 ` Stephen Wille Padnos
2003-01-28 17:05 ` Alan Cox
2003-01-28 14:53 Raphael Schmid
2003-01-28 18:21 ` Aaron Lehmann
2003-01-28 14:51 Raphael Schmid
2003-01-28 14:48 Raphael Schmid
2003-01-28 15:41 ` Xavier Bestel
2003-01-28 14:47 Raphael Schmid
2003-01-29 10:10 ` Horst von Brand
2003-01-29 10:18   ` John Bradford
2003-01-29 15:16   ` Valdis.Kletnieks
2003-01-28 14:46 Raphael Schmid
2003-01-28 12:52 Raphael Schmid
2003-01-28 10:01 Raphael Schmid
2003-01-28 10:32 ` John Bradford
2003-01-28 10:45   ` Alex Riesen
2003-01-28  9:57 Raphael Schmid

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=200301281426.h0SEQRRn001008@darkstar.example.net \
    --to=john@grabjohn.com \
    --cc=Raphael_Schmid@CUBUS.COM \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rob@r-morris.co.uk \
    /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