Package: udev Version: 0.114-2 Severity: wishlist Hi (again) Marco,
I'm currently working on packaging OpenCBM (ITP: #437316), which includes a kernel module that creates /dev/cbm (c 10 177, registered in the Linux Device List). Unfortunately, the default permissions are not particularly useful for this device, so a GROUP or MODE rule would probably be needed. (If you'd rather not touch this issue until after the sponsorship and upload of that package, let me know and I'll ping you when the time has come.) To provide you with some background info, OpenCBM allows for communication with devices, typically floppy drives, that were used by the VIC-20 and C-64. These devices are connected, via a custom cable, to the parallel port. Now, I'm not sure what permissions would be best for this device, so I wouldn't mind hearing your advice on this. I see three possibilities: * MODE=0666: What most people usually do. I would feel uneasy with this, for what I assume are obvious reasons. * GROUP=lp: Somewhat fitting, as this module accesses the parport, which also belongs to lp. * GROUP=floppy: I would tend to lean towards this, as floppy has a history of being assigned to local/removable devices, and local users typically already belong to it. That, and I suspect most people would use OpenCBM to transfer C64 floppies anyway. Let me know what you think. Thanks! -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.21-2-k7 (SMP w/1 CPU core) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages udev depends on: ii debconf [debconf-2.0] 1.5.14 Debian configuration management sy ii libc6 2.6-5 GNU C Library: Shared libraries ii libselinux1 2.0.15-2+b1 SELinux shared libraries ii libvolume-id0 0.114-2 libvolume_id shared library ii lsb-base 3.1-24 Linux Standard Base 3.1 init scrip udev recommends no packages. -- debconf information excluded -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]