From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1ISU1s-0002bi-E2 for garchives@archives.gentoo.org; Tue, 04 Sep 2007 08:45:00 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.14.0/8.14.0) with SMTP id l848bNrZ014460; Tue, 4 Sep 2007 08:37:23 GMT Received: from mail-out.m-online.net (mail-out.m-online.net [212.18.0.10]) by robin.gentoo.org (8.14.0/8.14.0) with ESMTP id l848Y7HJ009602 for ; Tue, 4 Sep 2007 08:34:07 GMT Received: from mail01.m-online.net (mail.m-online.net [192.168.3.149]) by mail-out.m-online.net (Postfix) with ESMTP id 0F38922320F for ; Tue, 4 Sep 2007 10:34:07 +0200 (CEST) Received: from gauss.x.fun (DSL01.83.171.150.191.ip-pool.NEFkom.net [83.171.150.191]) by mail.nefkom.net (Postfix) with ESMTP id DAB6690823 for ; Tue, 4 Sep 2007 10:34:06 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by gauss.x.fun (Postfix) with ESMTP id 6542944DCD for ; Tue, 4 Sep 2007 10:34:06 +0200 (CEST) From: Matthias Schwarzott To: gentoo-dev@lists.gentoo.org Subject: [gentoo-dev] [RFC] udev rules cleanup / merging rules files with other distros Date: Tue, 4 Sep 2007 10:34:05 +0200 User-Agent: KMail/1.9.7 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200709041034.05788.zzam@gentoo.org> X-Archives-Salt: f696333a-7e29-4e48-897e-f0e5e710f5ab X-Archives-Hash: 80f23cd20c30d0f233d8a745a29979e9 Hi there! As you all know up to now we have our very own rules file 50-udev.rules This is good for getting our specials - but bad from maintainance view. So here we are: In udev git-gtree suse and redhat rules are already merged. But they use a different permission / group system than we have, they have less groups and assign some desktop permissions via pam_console. I also got all of our rules files (except 50-udev.rules) merged with what the other distros use (already in git). Slackware has already started merging the rules with this "upstream" common rules, and they also are more near to our approach by using groups for audio/tape/cdrom/... But I have not yet seen their rules yet. So for now we are on our own. So before doing to much work we should get a sane concept. And for that concept we need: * A (maybe formal) definition what each group should be used for * what devices it contains (if not obvious) * if permissions should be read/read-write for the group * and nothing/read for world. The question arises as we use MODE=660 for most groups but upstream does 640 most of the time. This are the groups. 1. audio All alsa and oss devices. Rules are not contained in upstream rules - they will in future be installed by media-libs/alsa-lib And upstream split of file for also also does not contain this group but sure it should keep MODE=660 / group audio (Or should we still support oss without having alsa installed) 2. cdrom Used for all cdrom/cdwriter devices and for scsi also the associated sg device. MODE=660 Upstream has no such group - member of disk for them. 3. cdrw Only used for pktcdvd with MODE=660 Should this be merged into group cdrom? 4. disk Contains every device with SUBSYSTEM==block, with MODE=660 the raw-devices (still needed?) + some devices needed for ata-over-ethernet (with modes 220 or 440) Upstream uses MODE=640 (Like old unix group for backup usage). 5. floppy The fd* devices, MODE=660 Upstream uses MODE=640 6. lp Used for all *lp* and parport devices with MODE=660 Upstream uses it same way. 7. tape Contains all tape devices with MODE=660. Upstream has no such group - member of disk group. 8. tty Same usage as upstream (maybe only very slight changes) 9. usb Devices for libusb (/dev/bus/usb/...) with MODE=664. + legousbtower device Upstream has no such group but has libusb stuff root:root with MODE=644 If default world permission is reading then every package changing permissions here (like gphoto, iscan, sane) should also keep world-read I think! 10. uucp serial devices, isdn and more for dialout usage MODE=660 Upstream uses it same way. 11. video A lot of misc stuff: dri/card*, nvidia, 3dfx, framebuffer, ieee1394, v4l, dvb with MODE=660 Upstream has no such group - they keep group at root and grant access via pam. Groups we do not use yet: 12. kmem Upstream uses it for /dev/mem /dev/kmem /dev/port with MODE=640 Should be ok to use - we have group=root, MODE=640 for now Matthias -- Matthias Schwarzott (zzam) -- gentoo-dev@gentoo.org mailing list