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.mdwn | 1 + hurd/libnetfs.mdwn | 7 ++++--- hurd/libtrivfs.mdwn | 31 +++++++++++++++++++++++++++++++ 3 files changed, 36 insertions(+), 3 deletions(-) create mode 100644 hurd/libtrivfs.mdwn diff --git a/hurd.mdwn b/hurd.mdwn index 067a15fc..78242651 100644 --- a/hurd.mdwn +++ b/hurd.mdwn @@ -93,6 +93,7 @@ in the *unstable* branch of the Debian archive. * [[libstore]] * [[libchannel]] * [[libhello_example]] -- Hurd library example + * [[libtrivfs]] * [[libnetfs]] -- short introductory material * [[IO_Path]] * [[Porting]] 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 diff --git a/hurd/libtrivfs.mdwn b/hurd/libtrivfs.mdwn new file mode 100644 index 00000000..b15aeabe --- /dev/null +++ b/hurd/libtrivfs.mdwn @@ -0,0 +1,31 @@ +[[!meta copyright="Copyright © 1994, 1996, 1998, 1999, 2000, 2001, 2002, 2003, +2004, 2005, 2007, 2008, 2009, 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 +document under the terms of the GNU Free Documentation License, Version 1.2 or +any later version published by the Free Software Foundation; with no Invariant +Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license +is included in the section entitled [[GNU Free Documentation +License|/fdl]]."]]"""]] + +Certain [[translator]]s do not need to be very complex, because they represent +a single file rather than an entire directory hierarchy. The *trivfs library*, +which is declared in ``, does most of the work of implementing +this kind of translator. This library requires the [[iohelp|libiohelp]] and +[[ports|libports]] libraries. + +Using `libtrivfs` is not the only way to implement such a single-file +translator, but is a convenient abstraction: the library hides a lot of +low-level stuff and you just have to provide a number of call-back functions +and symbols in order to get a functioning (for file I/O, etc.) node in the file +system. + + +# Further Reading + + * In the *[[The_GNU_Hurd_Reference_Manual|reference_manual]]*: + . + + * In the *[[Hurd_Hacking_Guide]]*: + . -- cgit v1.2.3