search for: fuse_main

...WM Jones article "Using mount-local API from C" I became curious because I thought there WAS a way to combine aspects of FUSE with the tools provided by libguestfs. So if I wanted to create my own filesystem using callbacks placed in the 'fuse_operations' struct (parameter to 'fuse_main()'), I could do so using guestfs. But after reading the article and looking at the 'guestmount' api it appears that fuse support is limited. Only the '-o' FUSE options can be passed and "only some of them are a good idea". So how would one use guestfs with a filesystem...

...version (void) > +{ > + printf ("%s %s\n", PACKAGE_NAME, PACKAGE_VERSION); > +} > + > +static void > +fuse_help (const char *prog) > +{ > + static struct fuse_operations null_operations; > + const char *tmp_argv[] = { prog, "--help", NULL }; > + fuse_main (2, (char **) tmp_argv, &null_operations, NULL); > + exit (EXIT_SUCCESS); > +} > + > +static bool > +is_directory (const char *path) > +{ > + struct stat statbuf; > + > + if (stat (path, &statbuf) == -1) > + return false; > + return S_ISDIR (statbuf.s...

...); + exit (exitcode); +} + +static void +display_version (void) +{ + printf ("%s %s\n", PACKAGE_NAME, PACKAGE_VERSION); +} + +static void +fuse_help (const char *prog) +{ + static struct fuse_operations null_operations; + const char *tmp_argv[] = { prog, "--help", NULL }; + fuse_main (2, (char **) tmp_argv, &null_operations, NULL); + exit (EXIT_SUCCESS); +} + +static bool +is_directory (const char *path) +{ + struct stat statbuf; + + if (stat (path, &statbuf) == -1) + return false; + return S_ISDIR (statbuf.st_mode); +} + +int +main (int argc, char *argv[]) +{ +...

This version doesn't crash or cause hung processes or stuck mountpoints, so that's an improvement. Rich.

This patch is just for review. It enables FUSE support in the API via two new calls, 'guestfs_mount_local' and 'guestfs_umount_local'. FUSE turns out to be very easy to deadlock (necessitating that the machine be rebooted). Running the test from the third patch is usually an effective way to demonstrate this. However I have not yet managed to produce a simple reproducer that

This changes the proposed API slightly. Previously 'mount-local' generating a 'mounted' event when the filesystem was ready, and from the 'mounted' event you had to effectively do a fork. Now, 'mount-local' just initializes the mountpoint and you have to call 'mount-local-run' to enter the FUSE main loop. Between these calls you can do a fork or whatever

...ot;); - exit (1); + exit (EXIT_FAILURE); } } diff --git a/fuse/guestmount.c b/fuse/guestmount.c index 05cacef..07c28c0 100644 --- a/fuse/guestmount.c +++ b/fuse/guestmount.c @@ -858,7 +858,7 @@ fuse_help (void) { const char *tmp_argv[] = { program_name, "--help", NULL }; fuse_main (2, (char **) tmp_argv, &fg_operations, NULL); - exit (0); + exit (EXIT_SUCCESS); } static void __attribute__((noreturn)) @@ -936,7 +936,7 @@ main (int argc, char *argv[]) fuse_argv = realloc (fuse_argv, (1+fuse_argc) * sizeof (char *)); \ if (!fuse_argv) {...

Hi, this series update libguestfs to a recent gnulib version, so that we can use its new getprogname module, and solve altogether one of the porting issues (the need for 'program_name' by the error module of gnulib), and have a single way to get the name of the current program. A number of changes in tools mostly, although mechanical. Thanks, Pino Toscano (3): Update gnulib to latest

libguestfs has used double and triple underscores in identifiers. These aren't valid for global names in C++. (http://stackoverflow.com/a/228797) These large but completely mechanical patches change the illegal identifiers to legal ones. Rich.