mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bob Gill <gillb4@telusplanet.net>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Boot failure, 2.6.10-rc2 (resolved)
Date: Tue, 16 Nov 2004 18:47:25 -0700	[thread overview]
Message-ID: <1100656045.5008.3.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.53.0411162122200.32739@yvahk01.tjqt.qr>

Ok, thanks, I can get 2.6.10-rc2 to boot/run.  I didn't need devfs to
build new kernels in Fedora Core 2 (and devfs is marked as obsolete),
but the new distribution -FC3- needs devfs to run.
Thanks,
Bob  

On Tue, 2004-11-16 at 21:24 +0100, Jan Engelhardt wrote:
> >> How, after all, did you run into this error? Directly after upgrading (if
> >> applicable)?
> >No, [...] but I prefer to run my own custom kernels.
> (So the post here is justified)
> 
> >Thanks for your reply though.  Your question as to whether /dev/console
> >exists at boot time is making me question whether /dev/console exists at
> >boot time.
> 
> You could find out by taking a live distro and checking. That's because I
> suspect your old kernel, which probably still works, to contain ~~ something
> magical ~~ that /dev/console is created at the right time.
> devfs probably?
> 
> 
> Jan Engelhardt
-- 
Bob Gill <gillb4@telusplanet.net>


      reply	other threads:[~2004-11-17  2:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-16 19:08 Boot failure, 2.6.10-rc2 Bob Gill
2004-11-16 19:36 ` Jan Engelhardt
2004-11-16 20:19   ` Bob Gill
2004-11-16 20:24     ` Jan Engelhardt
2004-11-17  1:47       ` Bob Gill [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=1100656045.5008.3.camel@localhost.localdomain \
    --to=gillb4@telusplanet.net \
    --cc=jengelh@linux01.gwdg.de \
    --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

Powered by JetHome