| History log of /src/share/examples/refuse/virtdir/virtdir.c |
| Revision | | Date | Author | Comments |
| 1.9 |
| 07-Feb-2008 |
agc | Set a definitive FUSE ABI before including fuse.h, to avoid situations
where different operating ssystems default to different levels.
|
| 1.8 |
| 11-Nov-2007 |
agc | Only use the bottom 20bits for an inode number to prevent the inode number creeping out of range for fts
|
| 1.7 |
| 11-Nov-2007 |
agc | Include a (random) inode number in the virtual directory information that
is held. Return this as part of the virtual entry information.
Prevents problems with fts code thinking that some directories create
a cycle.
|
| 1.6 |
| 21-Jun-2007 |
agc | branches: 1.6.4;
Record the root directory at initialisation time.
Add a function to "normalise" a path to condense multiple repeated '/'
characters into one.
|
| 1.5 |
| 21-May-2007 |
agc | Add a size parameter to virtdir_add, so that binary information can be
attached to a virtual directory entry.
|
| 1.4 |
| 19-May-2007 |
agc | Add a function to return the virtual offset in the virtdir_t tree.
|
| 1.3 |
| 18-Apr-2007 |
agc | When adding virtual directory entries, check the path to see that
intermediate directories have already been created. If not, then
create the intermediate directories. This means that callers don't
need to create the intermediate directories themselves.
When reading a virtual directory, don't return a zero-length
virtual directory entry.
|
| 1.2 |
| 17-Apr-2007 |
agc | Don't allow duplicate directory entries to be created.
Correct a comment.
|
| 1.1 |
| 15-Apr-2007 |
agc | Add routines to manipulate virtual directory entries, for use with
librefuse-based file systems.
These are especially useful for file systems which present virtual
directory hierarchies to the caller.
The routines build up and manage an array of virtual directory
entries, indexed upon full pathname within the file system. This is
analogous to the way refuse indexes its own entries. Routines are
available to add, delete, and find entries. Each entry can be one of
3 types - file ('f'), directory ('d') or symbolic link ('l'). Each
entry can also be associated with a target, which is a character
string allocated upon addition. This can be useful for virtual
directory entries of the symbolic link type.
The virtual directory entries can be traversed as an ordered list
(the entries are ordered alphabetically), or can be accessed by
directory component, using routines analogous to opendir(3), readdir(3),
and closedir(3).
|
| 1.6.4.2 |
| 23-Mar-2008 |
matt | sync with HEAD
|
| 1.6.4.1 |
| 09-Jan-2008 |
matt | sync with HEAD
|
