Didier: > Le 10/03/2019 à 11:22, k...@aspodata.se a écrit : > > Since nowadays the kernel can provide devtmpfs, what is the role of > > udev et al apart from handling usb devices ? > >    1) Change owner, group and permissions because the kernel defaults > everything to root.root and (I guess) 0600 > >    2) Create and populate /dev/disk/by-*, which is sometimes usefull > on a desktop or laptop. > >    3) Rename network devices (for people who want that) > >    The first 2 items might be done by monitoring /dev with inotify. > This must be checked though because, in principle, inotify only reports > interactions with the VFS issued from userspace, which is why it doesn't > work on /sys and /proc. Inotify works fine when /dev and > /dev/disk/by-label are popluated by udev, but I didn't check with > devtmpfs. We would then resort to reading the netlink.
Isn't the above moot if you have a no usb devices and static dev: 1) changing owner/group/permissions are persistent, i.e. set it once and be done with it 2) isn't that mostly useful for if you have lots of disks, say more than 5. If you just have one or two, you don't need that. Also that could be generated by a script which you run manually when needed. 3) can't you do ifrename from rc.local So unless you change things you don't need udev. Unfortunately, many things have grown to dependent of udev which technically isn't. Regards, /Karl Hammar
_______________________________________________ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
