I am reading up on udev, about its purpose, history and implementation. I have read the Wikipedia article and next I’m going to read the man pages. Meanwhile, I watched this video (Invidious link here) to see an example of what udev rules can do. I just have some questions regarding this video specifically:

  1. Following the principle of least privilege, shouldn’t I create a separate group - usb or whatever - rather than using wheel this way, which gives it double roles?
  2. Why don’t I just chmod and chown the /dev file(s) in question, if udev already provides persistent device naming (=the raw device won’t have a different designation at next disconnect-connect)? Or does the designation change perhaps?
  • printf("%s", name);@piefed.blahaj.zoneOPEnglish
    2·
    5 days ago

    Thanks!

    1. I’m going to interpret this as such: it doesn’t really matter, since - on my system - creating new groups require root privileges, requiring a superuser or a user part of wheel anyway. This way, I can create a group with name that reflects its purpose, which in turn gives readability to the udev rule file.

    2. This makes sense. Thanks for the fstab example/reminder!