Annotated edit history of
dlpsh(1) version 2, including all changes.
View license author blame.
Rev |
Author |
# |
Line |
1 |
perry |
1 |
DLPSH |
|
|
2 |
!!!DLPSH |
|
|
3 |
NAME |
|
|
4 |
SYNOPSIS |
|
|
5 |
DESCRIPTION |
|
|
6 |
USEAGE |
|
|
7 |
BUGS |
|
|
8 |
AUTHOR |
|
|
9 |
---- |
|
|
10 |
!!NAME |
|
|
11 |
|
|
|
12 |
|
|
|
13 |
dlpsh - command shell for executing DLP commands to a Palm Device |
|
|
14 |
!!SYNOPSIS |
|
|
15 |
|
|
|
16 |
|
|
|
17 |
__dlpsh /dev/cua?__ |
|
|
18 |
!!DESCRIPTION |
|
|
19 |
|
|
|
20 |
|
|
|
21 |
This manual page documents the small application |
|
|
22 |
__dlpsh__. __dlpsh__ allows the user to connect to a |
|
|
23 |
Pilot and execute arbitrary __Data Link Protocol__ (DLP) |
|
|
24 |
commands to a Pilot connected to the specified callout |
|
|
25 |
device. Once __dlpsh__ is started, the user must invoke |
2 |
perry |
26 |
!HotSync on the target device. Once connected, the user may |
1 |
perry |
27 |
execute any of the built-in __DLP__ commands. (See |
|
|
28 |
__BUILT-IN COMMANDS__). The connection to the Pilot is |
2 |
perry |
29 |
kept alive by sending a __!PadTickle__ packet to the Pilot |
1 |
perry |
30 |
after a small period of non-activity. (7 seconds by |
|
|
31 |
default) |
|
|
32 |
|
|
|
33 |
|
|
|
34 |
__BUILT-IN COMMANDS__ |
|
|
35 |
|
|
|
36 |
|
|
|
37 |
user [[-n username] [[-i user id] [[-v viewer id] [[-p pc |
|
|
38 |
id] |
|
|
39 |
|
|
|
40 |
|
|
|
41 |
__OPTIONS__ |
|
|
42 |
|
|
|
43 |
|
|
|
44 |
none |
|
|
45 |
!!USEAGE |
|
|
46 |
|
|
|
47 |
|
|
|
48 |
The program will connect to a target, and give the user a |
|
|
49 |
prompt for executing commands. |
|
|
50 |
!!BUGS |
|
|
51 |
|
|
|
52 |
|
|
|
53 |
__dlpsh__ has no known bugs. |
|
|
54 |
!!AUTHOR |
|
|
55 |
|
|
|
56 |
|
|
|
57 |
__dlpsh__ was written by Chris Stevens and Damien |
|
|
58 |
Neil |
|
|
59 |
---- |
This page is a man page (or other imported legacy content). We are unable to automatically determine the license status of this page.