On Sat, 05 May 2012 01:58:11 +0100 Bruce Dubbs <[email protected]> wrote:
> Do you know anything about the bootscript? If you build > in the capability to the kernel then the modprobe is obviously unneeded, On the Fuse page I advised that people build it into their kernel. My thinking is: if they build it as a module they probably have experience with using modules and will know how to modprobe. > but is > is necessary to mount /sys/fs/fuse/connections? > > I did some reading about fuse today, but I'm still confused about why it's > needed or what it really does. I don't know for sure. For me, Fuse is a required dep of sshfs-fuse (which I use everyday) and curftpfs (which I use occasionally) and an optional dep of Ntfs-3g (which I use everyday). None of them need /sys/fs/fuse/connections mounted, so for me the bootscript is unneeded. I'm not an expert on Fuse though, so I don't know about other use cases. Apart from the library (which are required by both sshfs-fuse and curlftpfs) and kernel config the other thing needed from Fuse is the command fusermount. fusermount -u is used to unmount a Fuse mountpoint. The config file, /etc/fuse.conf is another issue. It mentions is in the README file in the Fuse source. I've never needed to create /etc/fuse.conf so I didn't mention it on the Fuse page. My feeling is that the Fuse page is Ok for now. If there are use cases that require the bootscript or config file hopefully someone will mention them on one of the mail lists and we can improve the page then. Andy -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
