Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: device node creation
Date: Mon, 12 Nov 2012 14:08:09 -0700	[thread overview]
Message-ID: <50A16539.30405@mlbassoc.com> (raw)
In-Reply-To: <CAKmrg8MS91e7tQK2HWr7SogsNpXhw+oyGS_rbROcQDm+u6aPQQ@mail.gmail.com>

On 2012-11-12 10:42, anton@angri.ru wrote:
> Hello,
>
> I'm trying to create a device node in the generated rootfs image: /dev/net/tun. It is required for openvpn to work. Adding it in the living system is as trivial as "mkdir /dev/net;
> mknod /dev/net/tun c 10 200", but I want it to be there with no manual intrusion required.
>
> I tried several ways:
>
> * IMAGE_DEVICE_TABLES
> * IMAGE_DEVICE_TABLE
> * adding /dev/net/tun file to the package
> * adding a node file to the IMAGE_ROOTFS in rootfs postprocess script
> * using postinst script that creates the node
>
> None of it worked.
>
> What is the way /dev is populated? Where do all those 256 (why so many btw?) pty* nodes come from? How do I create the new node?

Your kernel needs to be built with CONFIG_TUN (not common, you'll
probably need to rebuild it with this option).  Once this option
is in place, udev will automatically create that device for you.

Note: if you add this as an module (CONFIG_TUN=m) the device will
be created when you install the module.

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------



      reply	other threads:[~2012-11-12 21:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAKmrg8OVpDG58t_jARYGvjBSenbdL7S0C077b7+ivHmpfveeDA@mail.gmail.com>
2012-11-12 17:42 ` device node creation anton
2012-11-12 21:08   ` Gary Thomas [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=50A16539.30405@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=openembedded-core@lists.openembedded.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