All of lore.kernel.org
 help / color / mirror / Atom feed
From: "F. Heitkamp" <heitkamp@ameritech.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: /dev/shm and /dev/pts not been created by devtmpfs or udev
Date: Thu, 19 Apr 2012 03:20:23 +0000	[thread overview]
Message-ID: <4F8F8477.1020204@ameritech.net> (raw)
In-Reply-To: <4F8EB679.7080107@ameritech.net>

On 04/18/12 10:37, Kay Sievers wrote:
> On Wed, Apr 18, 2012 at 14:41, F. Heitkamp<heitkamp@ameritech.net>  wrote:
>> I am using kernel 3.3.2 and udev 182.
>> I have TMPFS, DEVTMPFS, DEVTMPFS_MOUNT and SHMEN all yes.
>>
>> However after the machine boots there is no /dev/shm or /dev/pts in the
>> /dev/ directory and udev does not create them even though they are in the
>> /usr/libexec/udev/devices directory.
> Udev uses /lib/udev/. never libexec/, (/usr)/lib/udev/ is a de-facto
> API and should not be changed.
>
> "strace udevd" might show what goes wrong on your box.
>
> Kay
> --
> To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
Sorry.  The devices directory is "/lib/udev/devices".

udev seems to be mostly working AFAICT.  When I plug/unplug USB or 
firewire, I can see events being processed with udevadm monitor.

There is no shm or pts directory shown in /proc/devices.  Should there be?

There is also lots of information in the /run directory tree.

Fred


      parent reply	other threads:[~2012-04-19  3:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-18 12:41 /dev/shm and /dev/pts not been created by devtmpfs or udev F. Heitkamp
2012-04-18 13:45 ` Marco d'Itri
2012-04-18 14:37 ` Kay Sievers
2012-04-19  3:20 ` F. Heitkamp [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=4F8F8477.1020204@ameritech.net \
    --to=heitkamp@ameritech.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 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.