In simple terms as long as you are linking dynamically (the default)
there are no limitations on linking with libfuse. For example you may
distribute the filesystem itself in binary form, without source code,
-under any propriatery license.
+under any proprietary license.
Under what conditions may I distribute a filesystem that uses the raw
---------------------------------------------------------------------
being to atomically obtain a read/write file handle and make the file
read-only. Unfortunately, this does not work very well in fuse, since
you first get a mknod, and then an open call. At the time of open,
-you can't distinguish easily wether this is the first open issued by
+you can't distinguish easily whether this is the first open issued by
cp, or another process trying to write a read-only file.
Defining the 'create' method solves this problem, however this
* You are running a 64 bit kernel but using a 32 bit libfuse. In this case
you will need to install a 64 bit version of the FUSE userspace library,
64 bit versions of all of the FUSE filesystems or language bindings that
- link to it, and 64 bit versions of all of their dependancies. Your
- distribution may provide 64 bit versions of the basic dependancies like
+ link to it, and 64 bit versions of all of their dependencies. Your
+ distribution may provide 64 bit versions of the basic dependencies like
libc even in its 32 bit environment
Misc
* information without calling this method. This ensures, that
* for local locks the l_pid field is correctly filled in. The
* results may not be accurate in case of race conditions and in
- * the presence of hard links, but it's unlikly that an
+ * the presence of hard links, but it's unlikely that an
* application would rely on accurate GETLK results in these
* cases. If a conflicting lock is not found, this method will be
* called, and the filesystem may fill out l_pid by a meaningful
*
* If this flag is set then retry operation on file descriptor
* until .size bytes have been copied or an error or EOF is
- * detetected.
+ * detected.
*/
FUSE_BUF_FD_RETRY = (1 << 3),
};
/**
* Option description
*
- * This structure describes a single option, and and action associated
+ * This structure describes a single option, and action associated
* with it, in case it matches.
*
* More than one such match may occur, in which case the action for
/**
* Key value passed to the processing function for all non-options
*
- * Non-options are the arguments beginning with a charater other than
+ * Non-options are the arguments beginning with a character other than
* '-' or all arguments after the special '--' option
*/
#define FUSE_OPT_KEY_NONOPT -2
*
* The 'arg' parameter will always contain the whole argument or
* option including the parameter if exists. A two-argument option
- * ("-x foo") is always converted to single arguemnt option of the
+ * ("-x foo") is always converted to single argument option of the
* form "-xfoo" before this function is called.
*
* Options of the form '-ofoo' are passed to this function without the
* argument vector
*
* Adds the argument to the N-th position. This is useful for adding
- * options at the beggining of the array which must not come after the
+ * options at the beginning of the array which must not come after the
* special '--' option.
*
* @param args is the structure containing the current argument list
fuse_session_exit(se);
return 0;
}
- /* Errors occuring during normal operation: EINTR (read
+ /* Errors occurring during normal operation: EINTR (read
interrupted), EAGAIN (nonblocking I/O), ENODEV (filesystem
umounted) */
if (err != EINTR && err != EAGAIN)
if (!auto_unmount)
return 0;
- /* Decome a daemon and wait for the parent to exit or die.
+ /* Become a daemon and wait for the parent to exit or die.
ie For the control socket to get closed.
btw We don't want to use daemon() function here because
it forks and messes with the file descriptors. */