From 399aaf28e538fc1c6f5adda3cf90cc6303b5721b Mon Sep 17 00:00:00 2001 From: Thomas Schwinge Date: Fri, 23 Jul 2010 21:31:44 +0200 Subject: hurd/libtrivfs: New. --- hurd/libnetfs.mdwn | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) (limited to 'hurd/libnetfs.mdwn') diff --git a/hurd/libnetfs.mdwn b/hurd/libnetfs.mdwn index a2bf47ee..8625f8bc 100644 --- a/hurd/libnetfs.mdwn +++ b/hurd/libnetfs.mdwn @@ -1,4 +1,5 @@ -[[!meta copyright="Copyright © 2007, 2008 Free Software Foundation, Inc."]] +[[!meta copyright="Copyright © 2007, 2008, 2010 Free Software Foundation, +Inc."]] [[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable id="license" text="Permission is granted to copy, distribute and/or modify this @@ -33,7 +34,7 @@ which is, generally speaking, seriously different from *libnetfs*. All in all, *libnetfs* is the library you would choose when you want to write a translator which will show a file (or a directory) in a modified way (for example, if you'd like to show only *.sh* files or -make an archive look unpacked). As different from *libtrivfs*, using +make an archive look unpacked). As different from *[[libtrivfs]]*, using *libnetfs*, you can show to your clients not just a single file, but a whole directory tree. @@ -229,7 +230,7 @@ performance or to solve specific problems. ##Synchronization is Crucial A *libnetfs* programmer shall always keep in mind that, as different -from *libtrivfs*-based translators, *libnetfs*-based translators are +from *[[libtrivfs]]*-based translators, *libnetfs*-based translators are always multithreaded. To guard data against damage each node incorporates a lock. Moreover, each light node usually contains a lock, too. This happens because *libnetfs* nodes and light nodes are -- cgit v1.2.3