From: Nick Warne <nick@linicks.net>
To: linux-kernel@vger.kernel.org
Subject: Re: newbie kernel hacking question.
Date: Fri, 3 Dec 2004 18:23:41 +0000 [thread overview]
Message-ID: <200412031823.41165.nick@linicks.net> (raw)
In-Reply-To: <1102096955.14037.5.camel@mcmanus.datapower.com>
On Friday 03 December 2004 18:02, patrick mcmanus wrote:
> maybe a helpful hint:
>
> "lilo -R newimage" will let you boot a new kernel for just the next boot
> without changing your default.. that way if it hangs/crashes you can
> just punch the reset button and it will reboot into the old working
> version..
Excellent, excellent tip. So much good stuff here.
But it all worked anyway! My first hack :D
uname -r 2.4.28
Nov 24 13:29:44 quake kernel: Floppy drive(s): fd0 is 1.44M
Nov 24 13:29:44 quake kernel: keyboard: Timeout - AT keyboard not present?(ed)
Nov 24 13:29:44 quake kernel: keyboard: Timeout - AT keyboard not present?
(f4)
Nov 24 13:29:44 quake kernel: FDC 0 is a National Semiconductor PC87306
Nov 24 13:29:44 quake kernel: loop: loaded (max 8 devices)
uname -r 2.4.28.nokb
Dec 3 18:08:47 quake kernel: Floppy drive(s): fd0 is 1.44M
Dec 3 18:08:47 quake kernel: FDC 0 is a National Semiconductor PC87306
Dec 3 18:08:47 quake kernel: loop: loaded (max 8 devices)
Seemd to boot faster too, but reading the code I can't see why - maybe I am
all excited ;)
Many thanks,
Nick
--
"When you're chewing on life's gristle,
Don't grumble, Give a whistle..."
prev parent reply other threads:[~2004-12-03 18:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-03 17:15 newbie kernel hacking question Nick Warne
2004-12-03 17:22 ` Randy.Dunlap
2004-12-03 17:44 ` Nick Warne
[not found] ` <1102096955.14037.5.camel@mcmanus.datapower.com>
2004-12-03 18:23 ` Nick Warne [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=200412031823.41165.nick@linicks.net \
--to=nick@linicks.net \
--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