1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
|
--------------------------------------------------------------------------------
Quick-Start Guide for libticables2 set-up
--------------------------------------------------------------------------------
A burning issue with this library, and GNU/Linux, is good set-up of device
access. GNU/Linux is secure because it heavily relies on permissions... but it
becomes harder to use in some situations.
This document describes methods for manual setup using standard *nix groups and
a recent method for automatically giving access to locally logged on users.
On the first run, you should always run your program as root. By this way,
you will be almost sure to run it successfully.
If you want to run your program as a regular (non-privileged) user, you need to
take care of permissions. This is explained below.
--------------------------------------------------------------------------------
ParallelLink cable
--------------------------------------------------------------------------------
The node is '/dev/parportX". You must have r/w permissions on this device, and
the device must not be locked exclusively by any other parallel port driver
(such as some CUPS drivers for parallel port printers) - otherwise libticables2
won't be able to acquire and use the port.
This can be done by:
- giving up r/w permissions to others (chmod ugo+rw /dev/parport?) or, better,
- adding your user to the group 'lp' (edit /etc/group and add your
username after the ':').
Example 1:
crw-rw-rw- 1 root lp 99, 0 2005-02-26 07:39 parport0
Example 2:
lp:x:7:romain
- On some distributions (e.g. Fedora 12), an alternative, groupless setup
detailed in the last section can also be used.
If you have a parallel port printer, for libticables2 to work, you may need to
stop the CUPS printing service (the way to do this depends on your distribution)
and unload the 'lp' kernel module (`rmmod lp` as root), so as to liberate the
exclusive lock on the parallel port held by CUPS / the printer driver.
--------------------------------------------------------------------------------
BlackLink & GrayLink cables
--------------------------------------------------------------------------------
The node is '/dev/ttySx". You must have r/w permissions on this device.
This can be done by:
- giving up r/w permissions to others (chmod ugo+rw /dev/ttyS0) or, better,
- adding your user to the group 'dialout' (edit /etc/group and add your
username after the ':').
Example 1:
crw-rw-rw- 1 root dialout 4, 64 2006-02-08 13:40 /dev/ttyS0
Example 2:
dialout:x:20:romain
- On some distributions (e.g. Fedora 12), an alternative, groupless setup
detailed in the last section can also be used.
--------------------------------------------------------------------------------
SilverLink cable
--------------------------------------------------------------------------------
For SilverLink cable, things are more complicated...
- The following technique can be used for manual setup (using POSIX groups,
as used e.g. on Debian) on udev-using systems:
It may depend on your distribution, but you will have to add a rule to
/etc/udev. As a template, you can create an
/etc/udev/rules.d/20-ticables.rules file with the following rules:
# SilverLink
ACTION=="add", SUBSYSTEM=="usb_device", ATTR{idVendor}=="0451",
ATTR{idProduct}=="e001", MODE="0660", GROUP="plugdev"
# TI-84+ DirectLink
ACTION=="add", SUBSYSTEM=="usb_device", ATTR{idVendor}=="0451",
ATTR{idProduct}=="e003", MODE="0660", GROUP="plugdev"
# TI-89 Titanium DirectLink
ACTION=="add", SUBSYSTEM=="usb_device", ATTR{idVendor}=="0451",
ATTR{idProduct}=="e004", MODE="0660", GROUP="plugdev"
# TI-84+ SE DirectLink
ACTION=="add", SUBSYSTEM=="usb_device", ATTR{idVendor}=="0451",
ATTR{idProduct}=="e008", MODE="0660", GROUP="plugdev"
# TI-Nspire DirectLink
ACTION=="add", SUBSYSTEM=="usb_device", ATTR{idVendor}=="0451",
ATTR{idProduct}=="e012", MODE="0660", GROUP="plugdev"
(Replace ATTR by SYSFS if your very old version of udev doesn't support ATTR).
The template relies on a group called 'plugdev'. If it doesn't exist, you will
have to create it or choose another group which matches better your system.
You will have to add the user to the group 'plugdev' (by using one of the
user/group management tools, or editing /etc/group to add your username after
the ':'). For example, the line will become:
plugdev:x:46:romain
- On some distributions (e.g. Fedora 12), an alternative, groupless setup
detailed in the last section can also be used.
--------------------------------------------------------------------------------
Groupless setup for udev >= 143 with udev-acl and ConsoleKit
--------------------------------------------------------------------------------
The above manual setup methods require users to be manually added to groups to
hand out device access. If this is not desired, on some distributions, it is
also possible to set up the system so the user physically in front of the
computer, if any, gets access to what's assumed to be his/her calculator
automatically. The exact procedure varies depending on the individual
distribution and its age. The following procedure works for systems using udev
143 or newer with udev-acl enabled, such as Fedora 12.
How udev-acl works is that a nice system service called ConsoleKit keeps track
of what user(s) is/are currently logged in locally. The udev-acl tool uses this
information to hand out ACLs for these devices to those users.
To use this setup, create a /lib/udev/rules.d/69-libticables.rules file with
the contents listed below.
IMPORTANT NOTE:
* on udev >= 154, replace ENV{ACL_MANAGE}="1" by TAG+="udev-acl".
* on udev >= 165, you can alternatively replace ENV{ACL_MANAGE}="1" by ENV{ID_PDA}="1".
/lib/udev/rules.d/69-libticables.rules:
ACTION!="add", GOTO="libticables_end"
# serial device (assume TI calculator)
KERNEL=="ttyS[0-3]", ENV{ACL_MANAGE}="1"
# parallel device (assume TI calculator)
SUBSYSTEM=="ppdev", ENV{ACL_MANAGE}="1"
# SilverLink
SUBSYSTEM=="usb", ATTR{idVendor}=="0451", ATTR{idProduct}=="e001", ENV{ACL_MANAGE}="1"
# TI-84+ DirectLink
SUBSYSTEM=="usb", ATTR{idVendor}=="0451", ATTR{idProduct}=="e003", ENV{ACL_MANAGE}="1"
# TI-89 Titanium DirectLink
SUBSYSTEM=="usb", ATTR{idVendor}=="0451", ATTR{idProduct}=="e004", ENV{ACL_MANAGE}="1"
# TI-84+ SE DirectLink
SUBSYSTEM=="usb", ATTR{idVendor}=="0451", ATTR{idProduct}=="e008", ENV{ACL_MANAGE}="1"
# TI-Nspire DirectLink
SUBSYSTEM=="usb", ATTR{idVendor}=="0451", ATTR{idProduct}=="e012", ENV{ACL_MANAGE}="1"
LABEL="libticables_end"
|
