| |
| | “Fuse for FreeBSD” documentation |
 | | In Linux, this couldn’t work out this way (given the design chosen by Linux Fuse): there is one Fuse device only, and a fail-safe identification of the subject of the mount is possible only within the scope of one process. |
 | | To add, Linux Fuse doesn’t seem to rely on its more protected situation: Linux Fuse was immune to those crashing schemes that were used to be possible to summon by non-privileged users in FreeBSD (in Linux, these were attempted as root, of course). |
 | | In Linux, the buffers hosting the fields of a request are allocated on the stack (that is, these fields are pointers to structures held in variables of syscall handlers), in FreeBSD, they are allocated dynamically (they are not freed when the ticket gets dropped, they are kept, reused, and reallocated on demand). |
| fuse4bsd.creo.hu /doc/html_single_out/doc.html (6671 words) |
|