[Bug 280251] pilot-link configuration is incomplete

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

 



Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.

Summary: pilot-link configuration is incomplete


https://bugzilla.redhat.com/show_bug.cgi?id=280251





------- Additional Comments From redhat-bugzilla@xxxxxxxxxx  2008-04-16 05:22 EST -------
Ivana: I agree that from a user perspective the main change they're likely to
encounter (perhaps unknowingly) is the blacklisting, so it's important to
mention it first. 

However, after the initial "what's changed?" question, the next thing a user
thinks is "and what should I do about it?". This second answer is to use the
libusb port options - and given that we're also trying to alert users who may
have given up with pilot-link on Fedora, it's important we tell them what they
should  do differently (if they do what they used to - using /dev/pilot - it
still won't work).

I realise libusb has been built in since F7 (that's why I say "recent verions"),
but there was no previous *need* to use it whereas now there is - this very bug
started from using the old visor method on F7! We switched to using libusb to
work *around* these problems.

The HAL/PolicyKit configuration is secondary and "under the hood"; while it's
essential to enable smooth use of pilot-link/libusb, a user doesn't need to know
the full details *unless* they've previously manually changed the configuration
in a way that might clash (perhaps while working around the broken config in
previous releases).

I think it's important to come at the release notes from a user perspective
(mention -p usb: ), and to cover the most common problem we've encountered with
the new setup in this bug (mis-configuration). I also suspect these will be the
most likely source of new bugs (see bug #435266 which prompted the Release Note
discussion), so best to head them off at the pass ;)

In summary, I've structured my suggested release note as:
1) what's changed
2) what to do about it
3) what might go wrong and where to get help

Putting the libusb bit at the end would swap the order to 1,3,2 - which I don't
think reads as clearly.

I agree libusb is too opaque a term - I've changed it below to "direct USB access".

If someone in the wiki EditGroup could add me (krp/KevinPage), that would be
useful - thanks!


"
The pilot-link package now blacklists the visor module by default. Users are
encouraged to try the direct USB access present in recent versions of
pilot-link. This is enabled by passing the "--port usb:" option instead of the
serial devices used in the past (typically /dev/pilot or /dev/ttyUSB0). For example:

pilot-xfer --port usb: --list

HAL and PolicyKit have been updated to correctly set permissions for the
necessary USB devices. If you have any existing manual configuration please
ensure it is reverted to avoid possible conflicts.

For further information see README.fedora included in the pilot-link package.
"

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

--
Fedora-relnotes-content mailing list
Fedora-relnotes-content@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-relnotes-content

[Index of Archives]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [Gnome Users]     [KDE Users]

  Powered by Linux