If you have raw access to the physical device, you can basically do what you want to it. But I don't think it'll be likely that this is changed. All other /dev nodes are attempted to be grouped or given reduced permissions. It's the same reason we add the cdrom, video and usb groups. Having raw access to a device is a privilege.
Yes, I can see how having this standard would make sense at the lowest level, as each of us can do our own management of group memberships for our builds/distros. This particular build will be a media friendly build so I will want to add newly created users by default to audio, video, etc.
Devices are created with default permissions of 0660 with current udev. So, BLFS just tacks the audio group onto these devices. Any user in the audio group will have access. If you want to override this security feature, you can just change the LFS udev rules to make everything mode 0666. Or, add all your users to the root group.
With Joe's help, I modified my /usr/bin/adduser script to automatically add the user to the audio group upon being created. This seems to work well. (I'm trying to give this build to a newbie for testing, and he doesn't have a clue about permissions). I don't just want to give all users root permissions, even I need protection from myself once in awhile. :) Thanks a bunch Dan and Joe! The 6.2 LFS release is working out very well, and I have run into no LFS dependency issues. I am sure I will be able to report a few BLFS bugs, but haven't needed to as of yet. Enjoy, Craig Jackson [EMAIL PROTECTED] -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
