Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Kenton <skenton@ou.edu>
To: buildroot@busybox.net
Subject: [Buildroot] Where is /dev/console created when using devtmpfs?
Date: Wed, 25 Mar 2015 12:44:58 -0500	[thread overview]
Message-ID: <5512F41A.3080208@ou.edu> (raw)

I'm currently running with devtmpfs only but am looking into using mdev
so I spent some time looking at my device usage and for the life of me
I can't find where /dev/console gets created during the build process.
Looking at the root filesystem when it's not running shows this in /dev

drwxrwxr-x 2 root root 4096 Mar  1 15:26 pts
lrwxrwxrwx 1 root root   10 Mar  1 15:26 log -> ../tmp/log
crw--w--w- 1 root root 5, 1 Mar 22 21:52 console

and I see that pts and log come from the skeleton but I can't find console.
I'm running an x86_64 system using the default vga console if that matters.
I'm obviously missing something but I can't find a mknod or mkdevs for it.

Where is /dev/console created when using devtmpfs?

Thanks,

Steve

             reply	other threads:[~2015-03-25 17:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-25 17:44 Steve Kenton [this message]
2015-03-26 19:51 ` [Buildroot] Where is /dev/console created when using devtmpfs? Rob Landley
2015-03-27  4:14   ` Steve Kenton
2015-03-27 22:14     ` Arnout Vandecappelle
2015-03-27 23:35       ` Steve Kenton
2015-03-28 20:17       ` [Buildroot] Something odd about /dev/console creation Steve Kenton
2015-03-28 23:04       ` [Buildroot] Where is /dev/console created when using devtmpfs? Rob Landley

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=5512F41A.3080208@ou.edu \
    --to=skenton@ou.edu \
    --cc=buildroot@busybox.net \
    /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