diod 1.0.14-5 source package in Ubuntu

Changelog

diod (1.0.14-5) unstable; urgency=medium


  * Add 'exit 0' to the end of the init script. This should stop it from
    failing in non-verbose mode. Thanks to Andrew Shadura (Closes: #731589)

 -- Євгеній Мещеряков <email address hidden>  Mon, 09 Dec 2013 23:49:33 +0100

Upload details

Uploaded by:
Eugeniy Meshcheryakov
Uploaded to:
Sid
Original maintainer:
Eugeniy Meshcheryakov
Architectures:
any
Section:
admin
Urgency:
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section
Trusty release universe admin

Downloads

File Size SHA-256 Checksum
diod_1.0.14-5.dsc 1.3 KiB 36a4807bee05bd2e1fcdbcdc0b9e9fed2bd9ced3708b936dd586cd5f5b259206
diod_1.0.14.orig.tar.gz 2.4 MiB 06bd4cb6e99f510fe6a99eb9bc6c99d3605cd0f00249fd7c26e59c5b85eb5895
diod_1.0.14-5.debian.tar.gz 5.9 KiB a8ce2485f0fc7ad5ce2536ec25b8378e4b3ec51b3fad689734623578a612a02c

Available diffs

No changes file available.

Binary packages built by this source

diod: I/O forwarding server for 9P

 diod is an I/O forwarding server that implements a variant of the 9P protocol
 from (9P2000.L) the Plan 9 operating system. When paired with a modern version
 of the v9fs Linux 9P client, diod allows a file system to be exported over a
 TCP/IP network in a manner similar to NFS.
 .
 The file system that is exported can itself be NFS or a parallel file system
 like Lustre or GPFS. This can be done with minimal loss of distributed
 semantics because the v9fs client (when used with appropriate mount options)
 has no page or directory cache - all I/O operations trigger a network request.
 The page cache effectively moves to the server system, with diod appearing as
 a multi-threaded user application accessing the file system in the usual way
 through the VFS.