summaryrefslogtreecommitdiffstats
path: root/tde-i18n-en_GB/docs/kdebase/kioslave/fish.docbook
diff options
context:
space:
mode:
authorTimothy Pearson <kb9vqf@pearsoncomputing.net>2011-11-21 02:23:03 -0600
committerTimothy Pearson <kb9vqf@pearsoncomputing.net>2011-11-21 02:23:03 -0600
commit9b58d35185905f8334142bf4988cb784e993aea7 (patch)
treef83ec30722464f6e4d23d6e7a40201d7ef5b6bf4 /tde-i18n-en_GB/docs/kdebase/kioslave/fish.docbook
downloadtde-i18n-9b58d35185905f8334142bf4988cb784e993aea7.tar.gz
tde-i18n-9b58d35185905f8334142bf4988cb784e993aea7.zip
Initial import of extracted KDE i18n tarballs
Diffstat (limited to 'tde-i18n-en_GB/docs/kdebase/kioslave/fish.docbook')
-rw-r--r--tde-i18n-en_GB/docs/kdebase/kioslave/fish.docbook110
1 files changed, 110 insertions, 0 deletions
diff --git a/tde-i18n-en_GB/docs/kdebase/kioslave/fish.docbook b/tde-i18n-en_GB/docs/kdebase/kioslave/fish.docbook
new file mode 100644
index 00000000000..21173bcbe61
--- /dev/null
+++ b/tde-i18n-en_GB/docs/kdebase/kioslave/fish.docbook
@@ -0,0 +1,110 @@
+<article lang="&language;" id="fish">
+<title
+>fish</title>
+<articleinfo>
+<authorgroup>
+<author
+>&Joerg.Walter; &Joerg.Walter.mail;</author>
+<othercredit role="translator"
+><firstname
+>Malcolm</firstname
+><surname
+>Hunter</surname
+><affiliation
+><address
+><email
+>malcolm.hunter@gmx.co.uk</email
+></address
+></affiliation
+><contrib
+>Conversion to British English</contrib
+></othercredit
+>
+</authorgroup>
+
+<date
+>2002-06-23</date>
+<releaseinfo
+>1.1.1</releaseinfo>
+
+</articleinfo>
+
+<para
+>Allows you to access another computer's files using a simple <acronym
+>SSH</acronym
+> shell account and standard &UNIX; utilities on the remote side. This way, no server software is needed and you gain access to that computer's files as if they were local (or on <acronym
+>NFS</acronym
+>, since it is slower than local access). It uses the same protocol as <application
+>MidnightCommander</application
+>'s #sh <acronym
+>VFS</acronym
+> handler.</para>
+
+<para
+>Fish should work with any roughly <acronym
+>POSIX</acronym
+> compatible &UNIX; based remote computer. It uses the shell commands <command
+>cat</command
+>, <command
+>chgrp</command
+>, <command
+>chmod</command
+>, <command
+>chown</command
+>, <command
+>cp</command
+>, <command
+>dd</command
+>, <command
+>env</command
+>, <command
+>expr</command
+>, <command
+>grep</command
+>, <command
+>ls</command
+>, <command
+>mkdir</command
+>, <command
+>mv</command
+>, <command
+>rm</command
+>, <command
+>rmdir</command
+>, <command
+>sed</command
+>, and <command
+>wc</command
+>. Fish starts <command
+>/bin/sh</command
+> as its shell and expects it to be a Bourne shell (or compatible, like <command
+>bash</command
+>). If the <command
+>sed</command
+> and <command
+>file</command
+> commands are available, as well as a <filename
+>/etc/apache/magic</filename
+> file with &MIME; type signatures, these will be used to guess &MIME; types. </para>
+
+<para
+>If <application
+>Perl</application
+> is available on the remote machine, it will be used instead. Then only <command
+>env</command
+> and <command
+>/bin/sh</command
+> are needed. Using <application
+>Perl</application
+> has the additional benefit of being faster.</para>
+
+<para
+>Fish may even work on &Windows; machines, if tools like <application
+>Cygwin</application
+> are installed. All the above utilities must be in the system <envar
+>PATH</envar
+>, and the initial shell must be able to process the command <command
+>echo FISH:;/bin/sh</command
+> correctly.</para>
+
+</article>