doc/plugins.rst: merge redundant nfs:// documentation
This commit is contained in:
parent
402663de74
commit
0b59f4eaee
@ -78,19 +78,7 @@ Load music files from a NFS server. It is used when
|
|||||||
:code:`music_directory` contains a ``nfs://`` URI according to
|
:code:`music_directory` contains a ``nfs://`` URI according to
|
||||||
RFC2224, for example :samp:`nfs://servername/path`.
|
RFC2224, for example :samp:`nfs://servername/path`.
|
||||||
|
|
||||||
This plugin uses libnfs, which supports only NFS version 3. Since
|
See :ref:`input_nfs` for more information.
|
||||||
:program:`MPD` is not allowed to bind to "privileged ports", the NFS
|
|
||||||
server needs to enable the ``insecure`` setting; example
|
|
||||||
:file:`/etc/exports`:
|
|
||||||
|
|
||||||
.. code-block:: none
|
|
||||||
|
|
||||||
/srv/mp3 192.168.1.55(ro,insecure)
|
|
||||||
|
|
||||||
Don't fear: ``insecure`` does not mean that your NFS server is
|
|
||||||
insecure. A few decades ago, people thought the concept of "privileged
|
|
||||||
ports" would make network services "secure", which was a fallacy. The
|
|
||||||
absence of this obsolete "security" measure means little.
|
|
||||||
|
|
||||||
udisks
|
udisks
|
||||||
------
|
------
|
||||||
@ -211,25 +199,33 @@ mms
|
|||||||
|
|
||||||
Plays streams with the MMS protocol using `libmms <https://launchpad.net/libmms>`_.
|
Plays streams with the MMS protocol using `libmms <https://launchpad.net/libmms>`_.
|
||||||
|
|
||||||
|
.. _input_nfs:
|
||||||
|
|
||||||
nfs
|
nfs
|
||||||
---
|
---
|
||||||
|
|
||||||
Allows :program:`MPD` to access files on NFSv3 servers without
|
Allows :program:`MPD` to access files on NFS servers without actually
|
||||||
actually mounting them (i.e. in userspace, without help from the
|
mounting them (i.e. with :program:`libnfs` in userspace, without help
|
||||||
kernel's VFS layer). All URIs with the ``nfs://`` scheme are used
|
from the kernel's VFS layer). All URIs with the ``nfs://`` scheme are
|
||||||
according to RFC2224. Example:
|
used according to RFC2224. Example:
|
||||||
|
|
||||||
.. code-block:: none
|
.. code-block:: none
|
||||||
|
|
||||||
mpc add nfs://servername/path/filename.ogg
|
mpc add nfs://servername/path/filename.ogg
|
||||||
|
|
||||||
Note that this usually requires enabling the ``insecure`` flag in the
|
This plugin uses :program:`libnfs`, which supports only NFS version 3.
|
||||||
server's /etc/exports file, because :program:`MPD` cannot bind to
|
Since :program:`MPD` is not allowed to bind to so-called "privileged
|
||||||
so-called "privileged" ports. Don't fear: this will not make your file
|
ports", the NFS server needs to enable the ``insecure`` setting;
|
||||||
server insecure; the flag was named in a time long ago when privileged
|
example :file:`/etc/exports`:
|
||||||
ports were thought to be meaningful for security. By today's
|
|
||||||
standards, NFSv3 is not secure at all, and if you believe it is,
|
.. code-block:: none
|
||||||
you're already doomed.
|
|
||||||
|
/srv/mp3 192.168.1.55(ro,insecure)
|
||||||
|
|
||||||
|
Don't fear: this will not make your file server insecure; the flag was
|
||||||
|
named a time long ago when privileged ports were thought to be
|
||||||
|
meaningful for security. By today's standards, NFSv3 is not secure at
|
||||||
|
all, and if you believe it is, you're already doomed.
|
||||||
|
|
||||||
smbclient
|
smbclient
|
||||||
---------
|
---------
|
||||||
|
Loading…
Reference in New Issue
Block a user