Alistair Delva | beaee83 | 2021-02-24 11:27:23 -0800 | [diff] [blame] | 1 | '\" t |
Yi Kong | 39bbd96 | 2022-01-09 19:41:38 +0800 | [diff] [blame] | 2 | .TH floppyd_installtest 1 "08Jan22" mtools-4.0.37 |
Alistair Delva | beaee83 | 2021-02-24 11:27:23 -0800 | [diff] [blame] | 3 | .SH Name |
| 4 | floppyd_installtest - tests whether floppyd is installed and running |
| 5 | '\" t |
| 6 | .de TQ |
| 7 | .br |
| 8 | .ns |
| 9 | .TP \\$1 |
| 10 | .. |
| 11 | |
| 12 | .tr \(is' |
| 13 | .tr \(if` |
| 14 | .tr \(pd" |
| 15 | |
| 16 | .SH Note\ of\ warning |
| 17 | This manpage has been automatically generated from mtools's texinfo |
| 18 | documentation, and may not be entirely accurate or complete. See the |
| 19 | end of this man page for details. |
| 20 | .PP |
| 21 | .SH Description |
| 22 | .PP |
| 23 | \&\fR\&\f(CWFloppyd_installtest\fR is used to check for the presence of a running |
| 24 | floppyd daemon. This is useful, if you have a small front-end script to |
| 25 | mtools, which decides whether to use floppyd or not. |
| 26 | .PP |
| 27 | \&\fR\&\f(CWfloppyd_installtest\fR [\fR\&\f(CW-f\fR] Connect-String |
| 28 | .PP |
| 29 | If the \fR\&\f(CW-f\fR option is specified, \fR\&\f(CWfloppyd_installtest\fR does a |
| 30 | full X-Cookie authentication and complains if this does not work. |
| 31 | .PP |
| 32 | The connect-String has the format described in the floppyd-section: |
| 33 | \&\fIhostname\fR\fR\&\f(CW:\fR\fIdisplaynumber\fR[\fR\&\f(CW/\fR\fIbaseport\fR] |
| 34 | .PP |
| 35 | .SH See\ Also |
| 36 | Mtools' texinfo doc |
| 37 | .SH Viewing\ the\ texi\ doc |
| 38 | This manpage has been automatically generated from mtools's texinfo |
| 39 | documentation. However, this process is only approximative, and some |
| 40 | items, such as crossreferences, footnotes and indices are lost in this |
| 41 | translation process. Indeed, these items have no appropriate |
| 42 | representation in the manpage format. Moreover, not all information has |
| 43 | been translated into the manpage version. Thus I strongly advise you to |
| 44 | use the original texinfo doc. See the end of this manpage for |
| 45 | instructions how to view the texinfo doc. |
| 46 | .TP |
| 47 | * \ \ |
| 48 | To generate a printable copy from the texinfo doc, run the following |
| 49 | commands: |
| 50 | |
| 51 | .nf |
| 52 | .ft 3 |
| 53 | .in +0.3i |
| 54 | ./configure; make dvi; dvips mtools.dvi |
| 55 | .fi |
| 56 | .in -0.3i |
| 57 | .ft R |
| 58 | .PP |
| 59 | |
| 60 | \&\fR |
| 61 | .TP |
| 62 | * \ \ |
| 63 | To generate a html copy, run: |
| 64 | |
| 65 | .nf |
| 66 | .ft 3 |
| 67 | .in +0.3i |
| 68 | ./configure; make html |
| 69 | .fi |
| 70 | .in -0.3i |
| 71 | .ft R |
| 72 | .PP |
| 73 | |
| 74 | \&\fRA premade html can be found at |
| 75 | \&\fR\&\f(CW\(ifhttp://www.gnu.org/software/mtools/manual/mtools.html\(is\fR |
| 76 | .TP |
| 77 | * \ \ |
| 78 | To generate an info copy (browsable using emacs' info mode), run: |
| 79 | |
| 80 | .nf |
| 81 | .ft 3 |
| 82 | .in +0.3i |
| 83 | ./configure; make info |
| 84 | .fi |
| 85 | .in -0.3i |
| 86 | .ft R |
| 87 | .PP |
| 88 | |
| 89 | \&\fR |
| 90 | .PP |
| 91 | The texinfo doc looks most pretty when printed or as html. Indeed, in |
| 92 | the info version certain examples are difficult to read due to the |
| 93 | quoting conventions used in info. |
| 94 | .PP |