Debian Codegraph @

debian/control

raw
1 Source: diod
2 Section: admin
3 Priority: optional
4 Maintainer: Євгеній Мещеряков <[email protected]>
5 Build-Depends: debhelper (>= 10~), libpopt-dev, liblua5.1-0-dev,
6 libmunge-dev, libcap-dev, libncurses-dev, libwrap0-dev,
7 valgrind [amd64 i386 powerpc], pkg-config
8 Build-Conflicts: valgrind [armel]
9 Standards-Version: 4.5.0
10 Homepage: https://github.com/chaos/diod
11 Vcs-Git: https://salsa.debian.org/debian/diod.git
12 Vcs-Browser: https://salsa.debian.org/debian/diod
13
14 Package: diod
15 Architecture: any
16 Depends: ${shlibs:Depends}, ${misc:Depends}, lsb-base
17 Description: I/O forwarding server for 9P
18 diod is an I/O forwarding server that implements a variant of the 9P protocol
19 from (9P2000.L) the Plan 9 operating system. When paired with a modern version
20 of the v9fs Linux 9P client, diod allows a file system to be exported over a
21 TCP/IP network in a manner similar to NFS.
22 .
23 The file system that is exported can itself be NFS or a parallel file system
24 like Lustre or GPFS. This can be done with minimal loss of distributed
25 semantics because the v9fs client (when used with appropriate mount options)
26 has no page or directory cache - all I/O operations trigger a network request.
27 The page cache effectively moves to the server system, with diod appearing as
28 a multi-threaded user application accessing the file system in the usual way
29 through the VFS.