From 96746de4bfd19158a7d9c250076d5f3e9cbfd11d Mon Sep 17 00:00:00 2001 From: CismonX Date: Sat, 4 Jan 2025 16:18:16 +0800 Subject: [PATCH] doc: add more content to chapter "the filesystem" --- doc/bookmarkfs.texi | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/doc/bookmarkfs.texi b/doc/bookmarkfs.texi index 31a0e2f..469626b 100644 --- a/doc/bookmarkfs.texi +++ b/doc/bookmarkfs.texi @@ -173,6 +173,19 @@ which means patches are generally rejected unless trivial (e.g. typo fix). @node Filesystem @chapter The Filesystem +When a BookmarkFS filesystem is mounted using the @code{mount.bookmarkfs} +program, a daemon process acts as a proxy between the kernel (which relays +filesystem requests to FUSE requests) and the backend (which manipulates +actual bookmark data, @pxref{Backends}), thus providing POSIX +(and platform-specific) filesystem API access to bookmarks. + +BookmarkFS is designed in the hope that web browser bookmarks +can be managed flexibly using a combination of existing software, +without having to reinvent the wheel. +However, like most other pseudo-filesystems, +it cannot be considered fully POSIX-compliant. +Users should be aware of the limitations when using BookmarkFS. + @node Hierarchy @section Filesystem Hierarchy