From owner-freebsd-questions@FreeBSD.ORG Sun Mar 16 16:35:24 2014 Return-Path: Delivered-To: questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3F3127F6 for ; Sun, 16 Mar 2014 16:35:24 +0000 (UTC) Received: from mail-pa0-x230.google.com (mail-pa0-x230.google.com [IPv6:2607:f8b0:400e:c03::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 10FBBAE8 for ; Sun, 16 Mar 2014 16:35:24 +0000 (UTC) Received: by mail-pa0-f48.google.com with SMTP id hz1so4711048pad.21 for ; Sun, 16 Mar 2014 09:35:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=AcXbUlqH8qflNnxrIwgQvHBFbPce3/Qx+g8gy4ai3TY=; b=wgDZ0XKHhbGoL2km1FiQHz49BZENtXueU/ffs4xrJJyIKbBwoaPKwIoHXwPGx8mlqp yHaMGnoOmm/D7pguM4FNMgtgwx7X3LuebLaf6zLLMwmOA6/QxBki1oDwUZUSzCW4Lhe3 mYPrZ8tAcpHNAxgrvRU9aFvO8PBR9bIqQRvZSnM7tuAhefymDOdR8qhwkSZ/4ur6jP35 de5Y84AoObiHzER+SKzWJKSkc0uVHVptNGgGWfJjIBo72KpVV1JWCBsq5yoU4po11v+s tXGKzlQM0ywwMFjueXrekXJCiGxD69EVN4Lw7s9O3tuTLTr9hl1y9+O3wl7/w8Xd58sT nyZw== MIME-Version: 1.0 X-Received: by 10.66.227.193 with SMTP id sc1mr20774862pac.102.1394987723661; Sun, 16 Mar 2014 09:35:23 -0700 (PDT) Sender: kob6558@gmail.com Received: by 10.66.0.164 with HTTP; Sun, 16 Mar 2014 09:35:23 -0700 (PDT) In-Reply-To: References: <201402031656.18962.jmc-freebsd2@milibyte.co.uk> <20140206002637.GB74082@neutralgood.org> Date: Sun, 16 Mar 2014 09:35:23 -0700 X-Google-Sender-Auth: WWDDRekvj1jr7WQ0C4ph45kMNnY Message-ID: Subject: Re: fstab entry for fusefs based From: Kevin Oberman To: kpneal@pobox.com Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: Mike Clarke , questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Mar 2014 16:35:24 -0000 On Wed, Feb 5, 2014 at 10:57 PM, Kevin Oberman wrote: > On Wed, Feb 5, 2014 at 4:26 PM, wrote: > >> On Mon, Feb 03, 2014 at 12:03:48PM -0800, Kevin Oberman wrote: >> > On Mon, Feb 3, 2014 at 8:56 AM, Mike Clarke < >> jmc-freebsd2@milibyte.co.uk>wrote: >> > >> > > On Monday 03 Feb 2014 05:31:30 Kevin Oberman wrote: >> > > >> > > > I'd like to have file systems that use fusefs mount at boot time, >> but I >> > > > don't know what to put into the fstype field. I used ntfs in prior >> > > > versions, but it's been dropped and I now use ntfs-3g >> > > >> > > You can find instructions in >> /usr/local/share/doc/ntfs-3g/README.FreeBSD. >> > > >> > > Basically you specify the file type as ntfs-3g or rename >> /sbin/mount_ntfs, >> > > symlink ntfs-3g as the former, and use just "ntfs" as the file type. >> > > >> > > This works for me with 9.1-RELEASE >> > > >> > >> > Thanks! I now have a VERY long entry in my fstab with a to of options. >> I'll >> > re-boot later today to see if it works correctly. >> > >> > Replacing mount_ntfs with a link to ntfs-3g is what I did on version 9 >> for >> > NTFS, but 10 dropped ntfs, so I was unsure of how to do it. I missed the >> > README.FreeBSD file. Oops! Now to look to see if exFAT has similar >> > information! >> >> Sorry, I'm a little behind on my email, but does the 'mount' command >> run with no arguments give you the type for your fstab? >> >> I have no fuse or ntfs so I can't personally check on your case. >> > > All are identified as "fusefs": > /dev/fuse on /media/Windows7_OS (fusefs, local, synchronous) > /dev/fuse on /media/Media (fusefs, local, synchronous) > > The man page for mount_fusefs(8) explains this. If you are not familiar > with the fusefs implementation, fuse_mount is a the code that does allof > the heavy lifting. ntfs-3g and mount.exfat-fuse. are daemons that remain > resident as long as the volume remains mounted. so fusefs is all that is > known to the system. > > While the mount_fusefs command can be used to mount the system, it would > take several options that I am unsure how or if they can be entered into > the fstab file. > > Thanks for looking at this. I am completely baffled at this point. > -- > R. Kevin Oberman, Network Engineer, Retired > E-mail: rkoberman@gmail.com > Just to provide closure on this issue, I now have both my NTFS and ExFAT file systems mounting correctly from fstab(5). Thanks to a response by Rainer Hurling to a similar question in current@, I now know to use the mountprog option to specify hte program to be used to mount the filesystem. (This seems to completely override the fstype field in fstab, but I do use the closest one available.) This results in the following two extremely long fstab entries, the first for an NTFS fs and the second for the ExFAT one: /dev/ntfs/Windows7_OS /mnt/Windows7_OS ntfs rw,failok,uid=9381,gid=15,norecover,noatime,windows_names,late,mountprog=/usr/local/bin/ntfs-3g 0 0 /dev/ada0s5 /mnt/Media msdosfs rw,failok,uid=9381,gid=15,noatime,late,mountprog=/usr/local/bin/mount.exfat 0 0 I have to use the physical name of the ExFAT slice because the system fails to grok that fype and create an entry for /dev subdirectory for it. Thanks for the suggestions on resolving this one. -- R. Kevin Oberman, Network Engineer, Retired E-mail: rkoberman@gmail.com