=2D----BEGIN PGP SIGNED MESSAGE-----
Woudn't it be easier to make a ifp-line ebuild with mc flag,
rather than a mc ebuild with ifp flag?=20
And thanks for the ebuild and for the patch.
On Tuesday 06.01.2004 21:48, Javier Marcet wrote:
> * Cedric Staub <im_empire@...> [040106 21:26]:
> >Hm, nice, an ebuild :-)
> >I wrote my one little ebuild not long ago for ifp-line...
> >Was my first ebuild, it doesn't take care of non-root usage etc.
> >Was just for learning :D
> >Did you include MC Support as a use Flag?
> >I'm interested, show us that ebuild ;-)
> >But I use UMS, so I'm also happy about that Patch D:
> >See you...
> >>For those of you having problems with the UMS firmware under 2.6.x
> >>Also, those who prefer the non-UMS firmware and use ifp-line, I have
> >>written a nice ebuild for Gentoo which takes care of everything,
> >>including non root permissions et all, hence if there's any interest or
> >>you want to see it on ifp-line's sourceforge page, just tell me :)
> All right,
> as for the patch:
> that was a very quick attempt to just get it to work under 2.6.x
> However, in case you used other SCSI devices which ARE removable (be it
> a CD-ROM, a MO or whatever), that would break.
> It seems the iRiver UMS incorrectly says it is removable, when it is
> not. I've written a new patch which takes care of this, flagging
> specially the iRiver iFP Mass Storage, hence not breaking anything.
> I've sent it to the kernel list for more comments, to see if it is the
> best place to insert that info.
> To sum it up, please, use the new patch I attach :)
> As for the ebuild:
> I have an ebuild for ifp-line which includes ifprecconv, and have a
> modified mc ebuild which adds a 'ifp' use flag. I attach both of them :)
=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
=2D----END PGP SIGNATURE-----