Re: [blfs-dev] fuse
Andrew Benton wrote: On Sat, 05 May 2012 01:58:11 +0100 Bruce Dubbs bruce.du...@gmail.com 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. Fair enough. I'll add this to the ticket and close it. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] fuse
Fernando de Oliveira wrote: On 05-05-2012 07:06, Andrew Benton wrote: On Sat, 05 May 2012 01:58:11 +0100 Bruce Dubbs bruce.du...@gmail.com wrote: [...] 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. /etc/fuse.conf can be useful. $ cat /etc/fuse.conf user_allow_other $ ls -l /etc/fuse.conf -rw-r--r-- 1 root root 17 Mar 18 11:06 /etc/fuse.conf With these permissions (0644), sshfs can mount as myuser and access as root is granted: Example: sshfs -o default_permissions -o allow_root ???.???.???.???:$HOME/MyDownloadFiles/Sistema/Linux/lfs/sources6.8 $HOME/sshfs where ???.???.???.??? is to be replaced by the actual ip of the server. Have no idea how vulnerable I am nor if anything can be done about if so. In *buntu: $ cat /etc/fuse.conf # Set the maximum number of FUSE mounts allowed to non-root users. # The default is 1000. # #mount_max = 1000 # Allow non-root users to specify the 'allow_other' or 'allow_root' # mount options. # user_allow_other $ ls -l /etc/fuse.conf -rw-r--r-- 1 root fuse 216 2011-12-31 08:55 /etc/fuse.conf Originally: 1. user_allow_other was commented 2. permissions were 0640 or 0600, can't remember, and command above could not be used, as others and other-groups had no access permission. 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 i do not use bootscript for it. Ubuntu has: -rw-r- 1 root fuse 216 Oct 18 2011 /etc/fuse.conf $ sudo cat /etc/fuse.conf # Set the maximum number of FUSE mounts allowed to non-root users. # The default is 1000. # #mount_max = 1000 # Allow non-root users to specify the 'allow_other' or 'allow_root' # mount options. # #user_allow_other Perhaps we need to add that just for completenes, but still not bother with a boot script we don't know if we need or not. I can't find such a script in ubuntu. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] fuse
On 05-05-2012 12:54, Bruce Dubbs wrote: [..] Ubuntu has: -rw-r- 1 root fuse 216 Oct 18 2011 /etc/fuse.conf $ sudo cat /etc/fuse.conf # Set the maximum number of FUSE mounts allowed to non-root users. # The default is 1000. # #mount_max = 1000 # Allow non-root users to specify the 'allow_other' or 'allow_root' # mount options. # #user_allow_other Perhaps we need to add that just for completenes, but still not bother with a boot script we don't know if we need or not. I can't find such a script in ubuntu. -- Bruce I agree. I am replying because, I missed to tell the main point. For very long builds, I had trouble, because could not cp or access files from sshfs mount point as root. So, the script started in myuser, and had to sudo for some operations, and I had to keep watching when the password was asked. Now, for these long builds, such as FF, SM, TB, WK, QT, LO, everything can be run by root from start, and files can be copied/edited/deleted/downloaded/uploaded from/to server, to/from machine or web. -- []s, Fernando -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
[blfs-dev] fuse
Looking at the new fuse page, wouldn't it be easier to use: ./configure --prefix=/usr INIT_D_PATH=/dev/null ??? --- Also looking at the still open ticket, http://wiki.linuxfromscratch.org/blfs/ticket/2815 There is a boot script: MOUNTPOINT=/sys/fs/fuse/connections start: if ! grep -qw fuse /proc/filesystems; then modprobe fuse /dev/null 21 || error Unable to load module fuse. fi if grep -qw fusectl /proc/filesystems \ ! grep -qw $MOUNTPOINT /proc/mounts; then mount -t fusectl none $MOUNTPOINT /dev/null 21 || error Unable to mount control filesystem. fi stop: if grep -qw $MOUNTPOINT /proc/mounts; then umount $MOUNTPOINT /dev/null 21 || error Unable to unmount control filesystem. fi Is this needed? If so, should it be incorporated into mountfs? -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] fuse
On Fri, 04 May 2012 22:51:19 +0100 Bruce Dubbs bruce.du...@gmail.com wrote: Looking at the new fuse page, wouldn't it be easier to use: ./configure --prefix=/usr INIT_D_PATH=/dev/null make install would fail. /dev/null is not a directory. Andy -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] fuse
Andrew Benton wrote: On Fri, 04 May 2012 22:51:19 +0100 Bruce Dubbs bruce.du...@gmail.com wrote: Looking at the new fuse page, wouldn't it be easier to use: ./configure --prefix=/usr INIT_D_PATH=/dev/null make install would fail. /dev/null is not a directory. OK, that makes sense. Do you know anything about the bootscript? If you build in the capability to the kernel then the modprobe is obviously unneeded, 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. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
