public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: James Courtier-Dutton <James@superbug.demon.co.uk>
To: kernel list <linux-kernel@vger.kernel.org>
Subject: /dev problems with boot: unable to open an initial console.
Date: Sun, 08 Aug 2004 21:06:08 +0100	[thread overview]
Message-ID: <411687B0.1070901@superbug.demon.co.uk> (raw)

I am using linux kernel 2.6.7 with udev.

I thought that with this, I would never have to create any files in /dev 
again, because hotplug etc. would do the job for me.

Just after booting the kernel image, it starts running the first process 
id 1 "init".

If /dev is empty, init fails to complete and returns the error message:
"unable to open an initial console."

Once I manually created /dev/console, and /dev/tty0, linux booted up ok, 
and it reached a login prompt.

To me, this seems like a bug in the linux kernel.

I would have expected that when using udev, I would not have had to put 
anything in /dev

Here is what gets mounted at boot time from /etc/mtab

/dev/sdb5 on / type reiserfs (rw,noatime)
none on /proc type proc (rw)
none on /sys type sysfs (rw)
none on /dev type ramfs (rw)
none on /dev/pts type devpts (rw)
/dev/sdb6 on /u type reiserfs (rw)
none on /dev/shm type tmpfs (rw)
none on /proc/bus/usb type usbfs (rw)

Maybe the problem is that not everything is getting mounted before 
"init" is started, or maybe hotplug is not given enough time to act 
before "init" is started.

I can see this causing problems if one tries to boot from a hotplugable 
device like usb.

Any comments?

James

                 reply	other threads:[~2004-08-08 20:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=411687B0.1070901@superbug.demon.co.uk \
    --to=james@superbug.demon.co.uk \
    --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