from small one page howto to huge articles all in one place
 

search text in:





Poll
Which linux distribution do you use?







poll results

Last additions:
using iotop to find disk usage hogs

using iotop to find disk usage hogs

words:

887

views:

20152

userrating:

average rating: 3.4 (203 votes) (1=very good 6=terrible)


May 25th. 2007:
Words

486

Views

35931

why adblockers are bad


Workaround and fixes for the current Core Dump Handling vulnerability affected kernels

Workaround and fixes for the current Core Dump Handling vulnerability affected kernels

words:

161

views:

20945

userrating:

average rating: 1.0 (50 votes) (1=very good 6=terrible)


April, 26th. 2006:

Druckversion
You are here: manpages





floppyd

Section: User Commands (1)
Updated: 28Feb10
Index Return to Main Contents
 

Name

floppyd - floppy daemon for remote access to floppy drive

 

Note of warning

This manpage has been automatically generated from mtools's texinfo documentation, and may not be entirely accurate or complete. See the end of this man page for details.

 

Description

Floppyd 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:

floppyd [-d] [-l] [-s port] [-r user] [-b ipaddr] [-x display] devicenames

floppyd is always associated with an X server. It runs on the same machine as its X server, and listens on port 5703 and above.

 

Authentication

floppyd authenticates remote clients using the Xauthority 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. DISPLAY.

Caution: In order to make authentication work correctly, the local host should not be listed in the xhost list of allowed hosts.
 Indeed, hosts listed in xhost do not need a correct Xauthority cookie to connect to the X server. As floppyd 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 localhost:0 and :0 from the xhost list, you can prevent floppyd from probing those display names with the -l option.

 

Command line options

d 
Daemon mode. Floppyd runs its own server loop. Do not supply this if you start floppyd from inetd.conf
s  port 
Port number for daemon mode. Default is 5703 + displaynumber. This flag implies daemon mode. For example, for display hitchhiker:5, the port would be 5708.
b  ipaddr 
Bind address (for multi homed hosts). This flag implies daemon mode
user 
Run the server under as the given user
display 
X display to use for authentication. By default, this is taken from the DISPLAY variable. If neither the x attribute is present nor DISPLAY is set, floppyd uses :0.0.

devicenames is a list of device nodes to be opened. Default is /dev/fd0. Multiple devices are only supported on mtools versions newer than 3.9.11.

 

Connecting to floppyd


 In order to use floppyd, add the flag remote to the device description in your Infinity~/.mtoolsrcIntegral file. If the flag remote is given, the file parameter of the device description is taken to be a remote address. It's format is the following: hostname:displaynumber[/[baseport][/drive]]. When using this entry, mtools connects to port baseport+displaynumber at hostname. By default baseport 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)

 

Examples:


 The following starts a floppy daemon giving access to Infinity/dev/fd0Integral, listening on the default port 5703, tied to the default X servers:


 

floppyd -d /dev/fd0


 


 Each of the following starts a floppy daemon giving access to Infinity/dev/fd1Integral, tied to the :1 local X servers, and listening on port 5704. We assume that the local host is named hitchhiker.


 

floppyd -d /dev/fd0
floppyd -d -x :1 -p 5704 /dev/fd0 


 


 If you want to start floppyd by inetd instead of running it as a  daemon, insert the following lines into Infinity/etc/servicesIntegral:
 

# floppy daemon
floppyd-0    5703/tcp    # floppy daemon for X server :0
floppyd-1    5704/tcp    # floppy daemon for X server :1


 


 And insert the following into Infinity/etc/inetd.confIntegral (assuming that you have defined a user named floppy in your Infinity/etc/passwdIntegral):


 

# 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 


 


 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 Infinity~/.mtoolsrcIntegral to define a drive letter accessing floppy drive in your X terminal:
 

drive x: file="$DISPLAY" remote


 

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


 

 

See Also

Mtools' texinfo doc  

Viewing the texi doc

This manpage has been automatically generated from mtools's texinfo documentation. However, this process is only approximative, and some items, such as crossreferences, footnotes and indices are lost in this translation process. Indeed, these items have no appropriate representation in the manpage format. Moreover, not all information has been translated into the manpage version. Thus I strongly advise you to use the original texinfo doc. See the end of this manpage for instructions how to view the texinfo doc.
*   
To generate a printable copy from the texinfo doc, run the following commands:
 
    ./configure; make dvi; dvips mtools.dvi


 

*   
To generate a html copy, run:
 
    ./configure; make html


  A premade html can be found at Infinityhttp://www.gnu.org/software/mtools/manual/mtools.htmlIntegral

*   
To generate an info copy (browsable using emacs' info mode), run:
 
    ./configure; make info


 

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.


 

Index

Name
Note of warning
Description
Authentication
Command line options
Connecting to floppyd
Examples:
See Also
Viewing the texi doc

Please read "Why adblockers are badwww.cars2fast4u.de



Other free services
toURL.org
Shorten long
URLs to short
links like
http://tourl.org/2
tourl.org
.
FeedCollector
Combine various newsfeeds to one customized webpage
www.feedcollector.org
.
Reverse DNS lookup
Find out which hostname(s)
resolve to a
given IP or other hostnames for the server
www.reversednslookup.org
rdf newsfeed | rss newsfeed | Atom newsfeed
- Powered by LeopardCMS - Running on Gentoo -
Copyright 2004-2011 S&P Softwaredesign
Valid XHTML1.1 : Valid CSS : buttonmaker
- Level Triple-A Conformance to Web Content Accessibility Guidelines 1.0 -
- Copyright and legal notices -
Time to create this page: 30.2 ms
system status display