.ns
\\$1 .. .tr \(is' .tr \(if` .tr \(pd"
\fR\f(CWFloppyd is used as a server to grant access to the floppy drive to clients running on a remote machine, just as an X server grants access to the display to remote clients. It has the following syntax:
\fR\f(CWfloppyd [\f(CW-d] [\f(CW-l] [\f(CW-s port] [\f(CW-r \fIuser] [\f(CW-b ipaddr] [\f(CW-x display] devicenames
\fR\f(CWfloppyd is always associated with an X server. It runs on the same machine as its X server, and listens on port 5703 and above.
\fR\f(CWfloppyd authenticates remote clients using the \f(CWXauthority protocol. Xhost authentication is not supported. Each floppyd is associated with an X server. When a remote client attempts to connect to floppyd, it sends floppyd the X authority record corresponding to floppyd's X server. Floppyd in turn then tries to open up a connection to the X server in order to verify the authenticity of the xauth record. If the connection to the X server succeeds, the client is granted access. \fR\f(CWDISPLAY.
\fBCaution: In order to make authentication work correctly, the local host should not be listed in the \f(CWxhost list of allowed hosts. Indeed, hosts listed in \f(CWxhost do not need a correct \fR\f(CWXauthority cookie to connect to the X server. As \f(CWfloppyd runs on the same host as the X server, all its probe connection would succeed even for clients who supplied a bad cookie. This means that your floppy drive would be open to the world, i.e. a huge security hole. If your X server does not allow you to remove \f(CWlocalhost:0 and \fR\f(CW:0 from the \f(CWxhost list, you can prevent floppyd from probing those display names with the \f(CW-l option.
\fR\f(CWd Daemon mode. Floppyd runs its own server loop. Do not supply this if you start floppyd from \f(CWinetd.conf
\fR\f(CWs port\f(CW Port number for deamon mode. Default is 5703 + displaynumber. This flag implies daemon mode. For example, for display \fR\f(CWhitchhiker:5, the port would be 5708.
\fR\f(CWb ipaddr\f(CW Bind address (for multihomed hosts). This flag implies daemon mode
\fR\f(CWr user\f(CW Run the server under as the given user
\fR\f(CWx display\f(CW X display to use for authentication. By default, this is taken from the \fR\f(CWDISPLAY variable. If neither the \f(CWx attribute is present nor \f(CWDISPLAY is set, floppyd uses \f(CW:0.0.
\fIdevicenames is a list of device nodes to be opened. Default is \f(CW/dev/fd0. Multiple devices are only supported on mtools versions newer than 3.9.11.
In order to use floppyd, add the flag \f(CWremote to the device description in your \f(CW\(if~/.mtoolsrc\(is file. If the flag \f(CWremote is given, the \f(CWfile parameter of the device description is taken to be a remote address. It's format is the following: \fIhostname\f(CW:displaynumber[\f(CW/[baseport][\f(CW/drive]]. When using this entry, mtools connects to port \fIbaseport+displaynumber at hostname. By default \fIbaseport is 5703. The drive parameter is to distinguish among multiple drives associated with a single display (only mtools versions more recent than 3.9.11)
The following starts a floppy daemon giving access to \f(CW\(if/dev/fd0\(is, listening on the default port 5703, tied to the default X servers:
floppyd -d /dev/fd0.lp \fR
Each of the following starts a floppy daemon giving access to \fR\f(CW\(if/dev/fd1\(is, tied to the :1 local X servers, and listening on port 5704. We assume that the local host is named \f(CWhitchhiker.
floppyd -d /dev/fd0 floppyd -d -x :1 -p 5704 /dev/fd0.lp \fR
If you want to start floppyd by \f(CWinetd instead of running it as a daemon, insert the following lines into \f(CW\(if/etc/services\(is:
# floppy daemon floppyd-0 5703/tcp # floppy daemon for X server :0 floppyd-1 5704/tcp # floppy daemon for X server :1.lp \fR
And insert the following into \f(CW\(if/etc/inetd.conf\(is (assuming that you have defined a user named floppy in your \f(CW\(if/etc/passwd\(is):
# floppy daemon floppyd-0 stream tcp wait floppy /usr/sbin/floppyd floppyd /dev/fd0 floppyd-1 stream tcp wait floppy /usr/sbin/floppyd floppyd -x :1 /dev/fd0.lp \fR
Note that you need to supply the X display names for the second floppyd. This is because the port is opened by inetd.conf, and hence floppyd cannot know its number to interfere the display number.
On the client side, insert the following into your \f(CW\(if~/.mtoolsrc\(is to define a drive letter accessing floppy drive in your X terminal:
drive x: file="$DISPLAY" remote.lp \fR
If your X terminal has more than one drive, you may access the additional drives as follows:
drive y: file="$DISPLAY//1" remote drive z: file="$DISPLAY//2" remote.lp \fR
* To generate a printable copy from the texinfo doc, run the following commands:
./configure; make dvi; dvips mtools.dvi.lp \fR
* To generate a html copy, run:
./configure; make html.lp \fRA premade html can be found at \fR\f(CW\(ifhttp://www.gnu.org/software/mtools/manual/mtools.html\(is
* To generate an info copy (browsable using emacs' info mode), run:
./configure; make info.lp \fR
The texinfo doc looks most pretty when printed or as html. Indeed, in the info version certain examples are difficult to read due to the quoting conventions used in info.