> Forget about these discussions and those who prefer to hang on to the
> past. These discussions are moot. RH and others currently are merging
> those packages from Fedora.US and from some other sites into what is
> supposed to become Fedora.Extras.
> It's up to the users to decide on using Fedora.Extra or not.
To make a decision, users need information. Especially recent users who
aren't aware of how repositories work (ie. Fedora.Extra is not
compatible with other repositories but other repositories try to be
compatible with each other).
To not inform people of that is withholding important information that
people need to maintain their system. I hope the Fedora docs in the
future will at least be straight with users and not present Fedora.Extra
as the only way to do things in the "keeping up to date" section.
Your warning of not mixing repositories did little to educate me as to
what the situation really is, and shouldn't that be what docs do. Why
be so one sided in your presentation.
If Fedora.Extra isn't able to reach compatibility with other
repositories, why not at least offer them a link where they can explain
the merits of using their repository or repositories (which are working
After reading every post of this whole thread, I now know what my
choices are. Do you really expect every new reader to google this
topic, read all the posts, and figure it out?
I'm seeking information on the proper way (in Fedora) to deal with
getting PAM to authenticate users for usb devices.
In particular, I'm talking about the Ti Silverlink cable for Ti
Graphing Calculators. Fedora already comes with the kernel module, the
software already works with a serial cable (if you set up /etc/
security/console.perms to give the serial device to the console user) -
serial cable doesn't require a kernel module (anymore, it use to)
The problem I'm having with the software (TiLP) and USB isn't just
limited to authentication, but that is a hurdle I'll need to overcome
once I get it to work with the root user (which it currently does not).
The device node part is easy - same procedure as serial ports.
Problem is that the software also (for some reason) wants the user to
have permission to write (according to the error log anyway) to /proc/
bus/usb/devices - that I don't think can be properly overcome with pam
console, and if it can - I would be scared to do so because that looks
way too generic to let the console user write to it, so maybe it's the
software that is broken - but maybe I'm not understanding how user
space apps are suppose to talk to usb devices?
I'm not the TiLP developer, just someone trying to get it to work w/
usb in FC3 - and having little success (I did get it work ONCE as root
Cheap Linux CD's