linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Todd Musall <tmusall@comcast.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev 024 and missing virtual consoles
Date: Mon, 12 Apr 2004 03:03:05 +0000	[thread overview]
Message-ID: <1081738985.2153.4.camel@parents> (raw)
In-Reply-To: <1081711157.7840.12.camel@parents>

Philippe,

That was it :) Thank you very much. I suspected that /dev/vc/0 was a
devfs naming convention (which arch linux uses) and just needed to use
the standard kernel device name but wasn't sure. Thanks again for the
help.

-Todd

On Sun, 2004-04-11 at 18:33, Philippe Gramoullé wrote:
> Hello Tod,
> 
> If by any chance, your /etc/inittab has something like:
> 
> 1:2345:respawn:/sbin/getty 38400 vc/1
> 2:23:respawn:/sbin/getty 38400 vc/2
> etc..
> 
> then replace it by:
> 
> 1:2345:respawn:/sbin/getty 38400 tty1
> 2:23:respawn:/sbin/getty 38400 tty2
> etc..
> 
> and look if this helps.
> 
> Thanks,
> 
> Bye,
> 
> Philippe
>  
> On Sun, 11 Apr 2004 15:19:17 -0400
> Todd Musall <tmusall@comcast.net> wrote:
> 
>   | I'm running udev 024 over /dev with on a 2.6.5 kernel and directory
>   | /dev/vc isn't being created. I had to manually create the vc devices to
>   | get logged in.
>   | 
>   | I searched the list archives and found an older thread talking about a
>   | patch to create virtual consoles. Does anyone know if this is still an
>   | issue, or I'm missing something? I'm using the start_udev script as
>   | described in HOWTO-udev_for_dev on an Arch linux distro that uses a
>   | simple LFS init system. Any help here is greatly appreciated.
>   | 
>   | Thanks.
>   | -- 
>   | Todd Musall <tmusall@comcast.net>
-- 
Todd Musall <tmusall@comcast.net>



-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id\x1470&alloc_id638&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

  reply	other threads:[~2004-04-12  3:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-11 19:19 udev 024 and missing virtual consoles Todd Musall
2004-04-12  3:03 ` Todd Musall [this message]
2004-04-12 19:18 ` Greg KH
2004-04-13  3:26 ` Todd Musall
2004-04-14 19:13 ` Greg KH
2004-04-14 19:58 ` Olivier Mehani

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=1081738985.2153.4.camel@parents \
    --to=tmusall@comcast.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).