From: Gregory Anders <greg@gpanders.com>
To: Greg KH <greg@kroah.com>
Cc: kernelnewbies@kernelnewbies.org
Subject: Re: Device file not appearing
Date: Wed, 17 Mar 2021 12:26:04 -0600 [thread overview]
Message-ID: <YFJJvE7O7cE3Ijub@gpanders.com> (raw)
In-Reply-To: <YFI5L9rykgmBkHKT@kroah.com>
On Wed, 17 Mar 2021 18:15:27 +0100, Greg KH <greg@kroah.com> wrote:
>Looks like you have mounted tmpfs on top of devtmpfs, which seems very
>odd. Try unmounting the tmpfs instance and see if the node really is
>there in devtmpfs.
>
>Or better yet, mount devtmpfs somewhere else right now to see if the
>node is there.
>
>Good luck with your userspace mount maze!
>
>greg k-h
Ok I finally tracked down what was going on. The embedded distribution I
am using uses mdev. mdev has an init script that mounts tmpfs on /dev,
which is why devtmpfs wasn't working as expected.
mdev requires the kernel option CONFIG_UEVENT_HELPER=y which was not
enabled in my configuration (it even has a scary help description,
something along the lines of "this should not be used", so I didn't
think to enable it until I saw it mentioned somewhere else). After
enabling that, the device file appears under /dev.
Thanks for your help Greg!
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2021-03-17 18:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-17 15:52 Device file not appearing Gregory Anders
2021-03-17 15:59 ` Greg KH
2021-03-17 16:13 ` Gregory Anders
2021-03-17 16:16 ` Greg KH
2021-03-17 16:56 ` Gregory Anders
2021-03-17 17:05 ` Gregory Anders
2021-03-17 17:15 ` Greg KH
2021-03-17 18:26 ` Gregory Anders [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-03-16 20:25 Gregory Anders
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=YFJJvE7O7cE3Ijub@gpanders.com \
--to=greg@gpanders.com \
--cc=greg@kroah.com \
--cc=kernelnewbies@kernelnewbies.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.