Debian Codegraph @

upstream/mageia-cauldron/man1/floppyd.1

raw
1 '\" t
2 .TH floppyd 1 "14Jun25" mtools-4.0.49
3 .SH Name
4 floppyd - floppy daemon for remote access to floppy drive
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\fR is used as a server to grant access to the floppy drive
24 to clients running on a remote machine, just as an X server grants
25 access to the display to remote clients. It has the following syntax:
26 .PP
27 \&\fR\&\f(CWfloppyd\fR [\fR\&\f(CW-d\fR] [\fR\&\f(CW-D\fR] [\fR\&\f(CW-l\fR] [\fR\&\f(CW-s\fR \fIport\fR] [\fR\&\f(CW-r\fR
28 \&\fIuser\fR] [\fR\&\f(CW-b\fR \fIipaddr\fR] [\fR\&\f(CW-x\fR \fIdisplay\fR] \fIdevicenames\fR
29 .PP
30 \&\fR\&\f(CWfloppyd\fR is always associated with an X server. It runs on the
31 same machine as its X server, and listens on port 5703 and above.
32 .PP
33 .SH Authentication
34 .PP
35 \&\fR\&\f(CWfloppyd\fR authenticates remote clients using the \fR\&\f(CWXauthority\fR
36 protocol. Xhost authentication is not supported. Each floppyd is
37 associated with an X server. When a remote client attempts to connect
38 to floppyd, it sends floppyd the X authority record corresponding to
39 floppyd's X server. Floppyd in turn then tries to open up a connection
40 to the X server in order to verify the authenticity of the xauth record.
41 If the connection to the X server succeeds, the client is granted
42 access.
43 \&\fR\&\f(CWDISPLAY\fR.
44 .PP
45 \&\fBCaution\fR: In order to make authentication work correctly, the
46 local host should \fBnot\fR be listed in the \fR\&\f(CWxhost\fR list of
47 allowed hosts.
48 Indeed, hosts listed in \fR\&\f(CWxhost\fR do not need a correct
49 \&\fR\&\f(CWXauthority\fR cookie to connect to the X server. As \fR\&\f(CWfloppyd\fR
50 runs on the same host as the X server, all its probe connection would
51 succeed even for clients who supplied a bad cookie. This means that
52 your floppy drive would be open to the world, i.e. a huge security hole.
53 If your X server does not allow you to remove \fR\&\f(CWlocalhost:0\fR and
54 \&\fR\&\f(CW:0\fR from the \fR\&\f(CWxhost\fR list, you can prevent floppyd from
55 probing those display names with the \fR\&\f(CW-l\fR option.
56 .PP
57 .SH Command\ line\ options
58 .TP
59 \&\fR\&\f(CWd\fR\
60 Server mode. Floppyd runs its own server loop. Do not supply this if
61 you start floppyd from \fR\&\f(CWinetd.conf\fR
62 .TP
63 \&\fR\&\f(CWD\fR\
64 Do not daemonize. Floppyd will not put itself into the background even
65 if started in server mode.
66 .TP
67 \&\fR\&\f(CWs\ \ \fIport\fR\&\f(CW\fR\
68 Port number for daemon mode. Default is 5703 + \fIdisplaynumber\fR.
69 This flag implies daemon mode. For example, for display
70 \&\fR\&\f(CWhitchhiker:5\fR, the port would be 5708.
71 .TP
72 \&\fR\&\f(CWb\ \ \fIipaddr\fR\&\f(CW\fR\
73 Bind address (for multi homed hosts). This flag implies daemon mode
74 .TP
75 \&\fR\&\f(CWr\ \fIuser\fR\&\f(CW\fR\
76 Run the server under as the given user
77 .TP
78 \&\fR\&\f(CWx\ \fIdisplay\fR\&\f(CW\fR\
79 X display to use for authentication. By default, this is taken from the
80 \&\fR\&\f(CWDISPLAY\fR variable. If neither the \fR\&\f(CWx\fR attribute is present
81 nor \fR\&\f(CWDISPLAY\fR is set, floppyd uses \fR\&\f(CW:0.0\fR.
82 .PP
83 \&\fIdevicenames\fR is a list of device nodes to be opened. Default
84 is \fR\&\f(CW/dev/fd0\fR. Multiple devices are only supported on mtools
85 versions newer than 3.9.11.
86 .PP
87 .SH Connecting\ to\ floppyd
88 .PP
89 In order to use floppyd, add the flag \fR\&\f(CWremote\fR to the device
90 description in your \fR\&\f(CW\(if~/.mtoolsrc\(is\fR file. If the flag \fR\&\f(CWremote\fR
91 is given, the \fR\&\f(CWfile\fR parameter of the device description is taken
92 to be a remote address. It's format is the following:
93 \&\fIhostname\fR\fR\&\f(CW:\fR\fIdisplaynumber\fR[\fR\&\f(CW/\fR[\fIbaseport\fR][\fR\&\f(CW/\fR\fIdrive\fR]]. When
94 using this entry, mtools connects to port
95 \&\fIbaseport\fR+\fIdisplaynumber\fR at \fIhostname\fR. By default
96 \&\fIbaseport\fR is 5703. The drive parameter is to distinguish among
97 multiple drives associated with a single display (only mtools versions
98 more recent than 3.9.11)
99 .PP
100 .SH Examples:
101 .PP
102 The following starts a floppy daemon giving access to \fR\&\f(CW\(if/dev/fd0\(is\fR,
103 listening on the default port 5703, tied to the default X servers:
104 .PP
105
106 .nf
107 .ft 3
108 .in +0.3i
109 floppyd -d /dev/fd0
110 .fi
111 .in -0.3i
112 .ft R
113 .PP
114
115 \&\fR
116 .PP
117 Each of the following starts a floppy daemon giving access to
118 \&\fR\&\f(CW\(if/dev/fd1\(is\fR, tied to the :1 local X servers, and listening on port
119 5704. We assume that the local host is named \fR\&\f(CWhitchhiker\fR.
120 .PP
121
122 .nf
123 .ft 3
124 .in +0.3i
125 floppyd -d /dev/fd0
126 floppyd -d -x :1 -p 5704 /dev/fd0
127 .fi
128 .in -0.3i
129 .ft R
130 .PP
131
132 \&\fR
133 .PP
134 If you want to start floppyd by \fR\&\f(CWinetd\fR instead of running it as a
135 daemon, insert the following lines into \fR\&\f(CW\(if/etc/services\(is\fR:
136
137 .nf
138 .ft 3
139 .in +0.3i
140 # floppy daemon
141 floppyd-0 5703/tcp # floppy daemon for X server :0
142 floppyd-1 5704/tcp # floppy daemon for X server :1
143 .fi
144 .in -0.3i
145 .ft R
146 .PP
147
148 \&\fR
149 .PP
150 And insert the following into \fR\&\f(CW\(if/etc/inetd.conf\(is\fR (assuming that you
151 have defined a user named floppy in your \fR\&\f(CW\(if/etc/passwd\(is\fR):
152 .PP
153
154 .nf
155 .ft 3
156 .in +0.3i
157 # floppy daemon
158 floppyd-0 stream tcp wait floppy /usr/sbin/floppyd floppyd /dev/fd0
159 floppyd-1 stream tcp wait floppy /usr/sbin/floppyd floppyd -x :1 /dev/fd0
160 .fi
161 .in -0.3i
162 .ft R
163 .PP
164
165 \&\fR
166 .PP
167 Note that you need to supply the X display names for the second
168 floppyd. This is because the port is opened by inetd.conf, and hence
169 floppyd cannot know its number to interfere the display number.
170 .PP
171 On the client side, insert the following into your \fR\&\f(CW\(if~/.mtoolsrc\(is\fR
172 to define a drive letter accessing floppy drive in your X terminal:
173
174 .nf
175 .ft 3
176 .in +0.3i
177 drive x: file="$DISPLAY" remote
178 .fi
179 .in -0.3i
180 .ft R
181 .PP
182
183 \&\fR
184 .PP
185 If your X terminal has more than one drive, you may access the
186 additional drives as follows:
187
188 .nf
189 .ft 3
190 .in +0.3i
191 drive y: file="$DISPLAY//1" remote
192 drive z: file="$DISPLAY//2" remote
193 .fi
194 .in -0.3i
195 .ft R
196 .PP
197
198 \&\fR
199 .PP
200 .SH See\ Also
201 Mtools' texinfo doc
202 .SH Viewing\ the\ texi\ doc
203 This manpage has been automatically generated from mtools's texinfo
204 documentation. However, this process is only approximative, and some
205 items, such as crossreferences, footnotes and indices are lost in this
206 translation process. Indeed, these items have no appropriate
207 representation in the manpage format. Moreover, not all information has
208 been translated into the manpage version. Thus I strongly advise you to
209 use the original texinfo doc. See the end of this manpage for
210 instructions how to view the texinfo doc.
211 .TP
212 * \ \
213 To generate a printable copy from the texinfo doc, run the following
214 commands:
215
216 .nf
217 .ft 3
218 .in +0.3i
219 ./configure; make dvi; dvips mtools.dvi
220 .fi
221 .in -0.3i
222 .ft R
223 .PP
224
225 \&\fR
226 .TP
227 * \ \
228 To generate a html copy, run:
229
230 .nf
231 .ft 3
232 .in +0.3i
233 ./configure; make html
234 .fi
235 .in -0.3i
236 .ft R
237 .PP
238
239 \&\fRA premade html can be found at
240 \&\fR\&\f(CW\(ifhttp://www.gnu.org/software/mtools/manual/mtools.html\(is\fR
241 .TP
242 * \ \
243 To generate an info copy (browsable using emacs' info mode), run:
244
245 .nf
246 .ft 3
247 .in +0.3i
248 ./configure; make info
249 .fi
250 .in -0.3i
251 .ft R
252 .PP
253
254 \&\fR
255 .PP
256 The texinfo doc looks most pretty when printed or as html. Indeed, in
257 the info version certain examples are difficult to read due to the
258 quoting conventions used in info.
259 .PP