All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev for /dev
Date: Sat, 28 Feb 2004 00:32:33 +0000	[thread overview]
Message-ID: <20040228003233.GJ13580@kroah.com> (raw)
In-Reply-To: <20040220062015.85721.qmail@web14907.mail.yahoo.com>

On Wed, Feb 25, 2004 at 10:10:25PM -0800, Jon Smirl wrote:
> --- Mike Frysinger <vapier@gentoo.org> wrote:
> > > The same here. init needs it.
> > 
> > no, no one *needs* it ... i think i posted an e-mail here about it before but 
> > it's only 'needed' if you want to see output before the *getty apps are 
> > started.  the kernel will open that device node before executing init so that 
> > init will have the proper stdout file descriptor to write to.  if you dont 
> > have /dev/console, the kernel prints the warning about not being able to open 
> > it, and then just runs init which works *fine* without the node.
> > -mike
> > 
> Redhat stops the boot process with an error if /dev/console can't be opened.
> Only choice is to reboot the system. Maybe they adjust this in FC2 if they
> integrate udev.

Works for me here without that node, running rawhide (which is almost FC2).

thanks,

greg k-h


-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id\x1356&alloc_id438&op=click
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

      parent reply	other threads:[~2004-02-28  0:32 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-20  6:20 udev for /dev Jon Smirl
2004-02-20  6:26 ` Jon Smirl
2004-02-20 16:19 ` Jon Smirl
2004-02-20 16:36 ` John L Fjellstad
2004-02-20 16:50 ` Frédéric L. W. Meunier
2004-02-20 16:58 ` Frédéric L. W. Meunier
2004-02-20 17:13 ` Marco d'Itri
2004-02-20 17:38 ` Jon Smirl
2004-02-20 17:39 ` Marco d'Itri
2004-02-20 17:49 ` Jon Smirl
2004-02-20 19:25 ` Mike Frysinger
2004-02-20 21:41 ` Jon Smirl
2004-02-20 22:06 ` Jon Smirl
2004-02-23  7:37 ` mjl
2004-02-26  6:10 ` Jon Smirl
2004-02-28  0:32 ` Greg KH [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=20040228003233.GJ13580@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-hotplug@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.