mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Raphael Schmid <Raphael_Schmid@CUBUS.COM>
To: "'alexander.riesen@synopsys.COM'" <alexander.riesen@synopsys.COM>
Cc: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: AW: Bootscreen
Date: Tue, 28 Jan 2003 11:01:15 +0100	[thread overview]
Message-ID: <398E93A81CC5D311901600A0C9F29289469372@cubuss2> (raw)

> try init=/bin/bash in kernel command line.
Maybe I have a bad aura towards Linux or 
something, but I can *still* press Alt-Fx.

You know, I've thought about the Bootscreen
thingy again, and also had a quick peek (on
Windows here) at those patches.

2.5 is all nice and fluffy, but you shouldn't
use it for any end user software really.

Would it be possible/easy (i.e.: the least
way of resistance) to modify the kernel so
that console initialization does not happen
until everything is up and running? What I
was up to in the first place was getting into
X as fast as possible, and without too many
different screens. I've even been thinking
of setting the hostname, bringing up loop-
back networking and calling xinit directly 
from within the kernel (init/main.c or where
was it?).

So if Linux would not do *anything* to the
screen (as in: just leave alone whatever the 
bootloader put there) just one command before
xinit is called, I'd be the most happy guy
on the planet and you'd see me jump around
in circles :-)

- Raphael 

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

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-28 10:01 Raphael Schmid [this message]
2003-01-28 10:32 ` John Bradford
2003-01-28 10:45   ` Alex Riesen
  -- strict thread matches above, loose matches on Subject: below --
2003-01-29 14:01 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 14:11 Raphael Schmid
2003-01-28 14:26 ` John Bradford
2003-01-28 14:29 ` Robert Morris
2003-01-28 12:52 Raphael Schmid
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=398E93A81CC5D311901600A0C9F29289469372@cubuss2 \
    --to=raphael_schmid@cubus.com \
    --cc=alexander.riesen@synopsys.COM \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®