[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#251154: ITP: ifp-common -- ITP: ifp-common -- hotplug scripts for iRiver iFP devices



On Fri, 2004-05-28 at 09:32, Eduard Bloch wrote:
> #include <hallo.h>
> * Joe Wreschnig [Thu, May 27 2004, 07:38:08PM]:
> 
> > > >  Installing this package will make hotplug automatically iRiver iFP
> > > >  audio players plugged into the system. It creates an 'ifp-driver' group,
> > > >  to which you can add users you want to be able to access iFP devices.
> > > 
> > > Is this group name really specific for the the iRiver devices or could
> > > we create a common group name for all programs of this kind? Maybe
> > > "mob-audio" or so.
> > 
> > I agree this would be a good thing, though I'm not sure about that name.
> > ('mob'?)
> 
> Shorter name for mobile. Not sure about how to choose the best one.
> 
> > I'll look into the rioutil/rio packages to see how easy it would be to
> > integrate there. What other portable audio devices (that aren't just USB
> > mass storage) are supported in Debian?
> 
> In Debian? No idea.

Hum. I looked at the Rio utils available in Debian, and it doesn't seem
possible to integrate this scheme with them. YEPP uses the parallel
port. The iHP and iPod use USB mass storage. So, short of reworking the
parallel port permissions (a bad idea IMO) I'm not sure how useful this
will be. I don't know enough about sysfs yet to know how useful it could
be for the iPod and iHP. Is it possible to say "when this device is
plugged in, make the resulting device readable (i.e. mountable) only to
users in group X?"

Still, I'm up for renaming the package in case I have some insight about
how to do it in the future. Maybe pmp-common (and 'pmp-driver' for the
group from 'portable music player'; the original Rio used this in all
its model names, and 'pmp' seems to be a sufficiently unique string in
package descriptions.
-- 
Joe Wreschnig <piman@debian.org>

Attachment: signature.asc
Description: This is a digitally signed message part


Reply to: