|
|
1.1 root 1: .TH dmsdosd 1 "10 Oct 1998" "dmsdos 0.9.2.0" "dmsdos MC external fs tool"
2: .SH NAME
3: mcdmsdos \- dmsdos tool for Midnight Commander external filesystem
4: .SH SYNOPSIS
5:
6: .BI mcdmsdos " mc-extfs-command args ..."
7:
8: i.e.
9:
10: .BI mcdmsdos " list <CVF_name> "
11:
12: .BI mcdmsdos " copyout <CVF_name> <path/name_in_CVF> <outfile> "
13:
14: .BI mcdmsdos " copyin <CVF_name> <path/name_in_CVF> <infile> "
15:
16: .SH DESCRIPTION
17: .I mcdmsdos
18: represents an interface for Midnight Commander
19: .I mc(1)
20: according to the documentation of 3.0 version for external filesystems.
21: See the Midnight Commander documentation for more information about
22: external filesystems.
23:
24: .I mc-extfs-command
25: can be:
26:
27: .B list:
28: lists the contents of a CVF (recursively) i.e. the names of all files
29: in the CVF are printed.
30:
31: .B copyout:
32: extracts a file from the CVF.
33:
34: .B copyin:
35: stores a file in the CVF. This is currently not yet implemented and results
36: in an error message.
37:
38: .SH BUGS
39: .I mcdmsdos
40: can interfere with mounted CVFs. You should not use mcdmsdos on a CVF that
41: is currently mounted by dmsdos. This would not make any sense either.
42:
43: .SH SEE ALSO
44:
45: Refer to the dmsdos main documentation for further information.
46: See the Midnight Commander documentation for more information about
47: its external filesystem interface.
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.