1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
|
.\" Man page generated from reStructuredText.
.
.
.nr rst2man-indent-level 0
.
.de1 rstReportMargin
\\$1 \\n[an-margin]
level \\n[rst2man-indent-level]
level margin: \\n[rst2man-indent\\n[rst2man-indent-level]]
-
\\n[rst2man-indent0]
\\n[rst2man-indent1]
\\n[rst2man-indent2]
..
.de1 INDENT
.\" .rstReportMargin pre:
. RS \\$1
. nr rst2man-indent\\n[rst2man-indent-level] \\n[an-margin]
. nr rst2man-indent-level +1
.\" .rstReportMargin post:
..
.de UNINDENT
. RE
.\" indent \\n[an-margin]
.\" old: \\n[rst2man-indent\\n[rst2man-indent-level]]
.nr rst2man-indent-level -1
.\" new: \\n[rst2man-indent\\n[rst2man-indent-level]]
.in \\n[rst2man-indent\\n[rst2man-indent-level]]u
..
.TH "TNFS-FUSE" 1 "2022-07-24" "20130127_fd46ff" "SlackBuilds.org"
.SH NAME
tnfs-fuse \- trivial network filesystem client
.\" RST source for tnfs-fuse(1) man page. Convert with:
.
.\" rst2man.py tnfs-fuse.rst > tnfs-fuse.1
.
.\" rst2man.py comes from the SBo development/docutils package.
.
.SH SYNOPSIS
.sp
tnfs\-fuse \fBdirectory\fP \fB\-o address=host\fP[:\fIport\fP]
.SH DESCRIPTION
.sp
TNFS is a simplified Internet file transfer protocol, designed for
simplicity and ease of implementation on small systems, such as 8\-bit
computers. It\(aqs simpler than NFS, SMB, or FTP. It\(aqs similar to TFTP,
but has features TFTP lacks.
.sp
\fBtnfs\-fuse\fP is a client for the TNFS protocol.
.sp
Note that \fBtnfs\-fuse\fP uses TCP to communicate with the TNFS server.
Most TNFS clients are written for smaller systems (e.g. Atari or
Spectrum 8\-bit computers) and use UDP. This isn\(aqt an actual problem,
but it\(aqs a factor to take into account when e.g. setting up firewall
rules to allow TNFS traffic. Also, when troubleshooting a failed
TNFS connection from an 8\-bit client, just because you can connect
with \fBtnfs\-fuse\fP using TCP, doesn\(aqt mean the UDP port is open and
working.
.sp
When working with mounted TNFS directories, some error messages will
be wrong, e.g. instead of "Permission denied", you may get "Bad file
descriptor".
.SH OPTIONS
.INDENT 0.0
.TP
.B \fB\-o address=host\fP[:\fIport\fP]
The hostname or IP address of the TNFS server to mount. If \fI:port\fP is
not given, the default TNFS port (16384) is used.
.TP
.B \fB\-o ro\fP
Mount read\-only.
.UNINDENT
.sp
\fBtnfs\-fuse\fP supports the full set of \fBfuse\fP options. See
\fBfuse\fP(8) or \fBtnfs\-fuse \-\-help\fP for the list.
.SH EXAMPLE
.sp
To mount the TNFS server at \fBfujinet.online\fP:
.INDENT 0.0
.INDENT 3.5
.sp
.nf
.ft C
mkdir fujinet
tnfs\-fuse fujinet \-o address=fujinet.online
.ft P
.fi
.UNINDENT
.UNINDENT
.sp
Now the contents of the TNFS server are visible under fujinet/ (or
whatever name you chose). You might also want to add \fB\-o ro\fP to mount
read\-only.
.SH COPYRIGHT
.sp
See the file /usr/doc/tnfs\-fuse\-20130127_fd46ff/COPYING for license information.
.SH AUTHORS
.sp
tnfs\-fuse was written by Radu Cristescu.
.sp
This man page written for the SlackBuilds.org project
by B. Watson, and is licensed under the WTFPL.
.SH SEE ALSO
.sp
\fBtnfsd\fP(1), \fBfuse\fP(8)
.\" Generated by docutils manpage writer.
.
|
