В Sun, 31 May 2015 10:26:46 +0800
cee1 пишет:
> 2015-05-31 5:52 GMT+08:00 Lennart Poettering :
> >> Then udevd is only responsible for
> >> 1) Making nodes, and doing other device initialization stuffs.
> >
> > udev does not create device nodes. That's the job of devtmpfs in the
> > kernel. udev
On Sun, May 31, 2015 at 10:26:46AM +0800, cee1 wrote:
> 2015-05-31 5:52 GMT+08:00 Lennart Poettering :
> >> Then udevd is only responsible for
> >> 1) Making nodes, and doing other device initialization stuffs.
> >
> > udev does not create device nodes. That's the job of devtmpfs in the
> > kernel.
2015-05-31 5:52 GMT+08:00 Lennart Poettering :
>> Then udevd is only responsible for
>> 1) Making nodes, and doing other device initialization stuffs.
>
> udev does not create device nodes. That's the job of devtmpfs in the
> kernel. udev will however apply access modes/acls/fix ownership create
>
On Sat, 30.05.15 21:53, cee1 (fykc...@gmail.com) wrote:
> Hi all,
>
> If a service wants to be notified when a device is plugged in, it
> invokes routines of libudev which actually:
> * Receive notifications from the kernel via NETLINK socket.
Not quite. udev receives notifications from the kern
On Sat, May 30, 2015 at 09:53:36PM +0800, cee1 wrote:
> Hi all,
>
> If a service wants to be notified when a device is plugged in, it
> invokes routines of libudev which actually:
> * Receive notifications from the kernel via NETLINK socket.
> * Query the detailed info from /sys/...
>
> Am I righ
