1. MacFUSE seems to be installed now, hopefully correctly. How can I verify that it is installed and working correctly?
2. Yes the problems may well be related to "encfs" filesystem on top of FUSE. I'll try to get in touch with that group. 3. Yes of course I created the mountpoint and mounted it: $ mount /dev/disk0s2 on / (hfs, local, journaled) devfs on /dev (devfs, local, nobrowse) map -hosts on /net (autofs, nosuid, automounted, nobrowse) map auto_home on /home (autofs, automounted, nobrowse) /dev/disk1s2 on /Users/admin (hfs, local, nodev, nosuid, journaled, nobrowse) en...@fuse0 on /Users/admin/Src/encfs-1.5/trials/crypt (fusefs, nodev, nosuid, synchronous, mounted by admin) en...@fuse1 on /Users/admin/Src/encfs-1.5/trials/crypto (fusefs, nodev, nosuid, synchronous, mounted by admin) $ pwd /Users/admin/Src/encfs-1.5/trials $ ls -F crypto/ raw/ $ lsvfs Filesystem Refs Flags -------------------------------- ----- --------------- nfs 0 unionfs 0 hfs 2 local, dovolfs devfs 0 autofs 2 fusefs 2 On Jun 13, 2:08 pm, Dan Shoop <[email protected]> wrote: > On Jun 13, 2010, at 1:14 PM, Mouse wrote: > > > I'm having the same issue with MacFUSE 2.0.3 and 2.1.7. > > No, you're having problems with a filesystem built atop FUSE, not with FUSE. > > > Initially (2.0.3) it worked - but encfs (v1.5) couldn't re-mount > > encrypted directory (boost-related problem with Fs6SubVersion field > > being too large). > > > After plenty of re-installs of MacFUSE, it stopped installing - i.e. > > after clicking "Install" in the Preference window (2.0.3) it would do > > something, then return to the original state: "Uninstall" button > > grayed out, "Install" available - and no MacFUSE functionality. > > So try installing from the command like or manually make/build? > > > After complete removal of MacFUSE and clean re-install, I'm getting > > this from encfs: > > All of the below has nothing to do with FUSE and you need to take up with the > maintainers of that filesystem. > > > > > > > $ encfs `pwd`/raw `pwd`/crypt > > Creating new encrypted volume. > > Please choose from one of the following options: > > enter "x" for expert configuration mode, > > enter "p" for pre-configured paranoia mode, > > anything else, or an empty line will select standard mode. > > ?> > > > Standard configuration selected. > > > Configuration finished. The filesystem to be created has > > the following properties: > > Filesystem cipher: "ssl/aes", version 2:2:1 > > Filename encoding: "nameio/block", version 3:0:1 > > Key Size: 192 bits > > Block Size: 1024 bytes > > Each file contains 8 byte header with unique IV data. > > Filenames encoded using IV chaining mode. > > File holes passed through to ciphertext. > > > Now you will need to enter a password for your filesystem. > > You will need to remember this password, as there is absolutely > > no recovery mechanism. However, the password can be changed > > later using encfsctl. > > > New Encfs Password: > > Verify Encfs Password: > > OK, so this probably creates the filesystem, but is it mounted at at > mountpoint? > > > $ cp ../t.cpp crypt/ > > cp: crypt/t.cpp: Not a directory > > $ ls -l crypt/ > > ls: : Device not configured > > > $ lsvfs > > Filesystem Refs Flags > > -------------------------------- ----- --------------- > > nfs 0 > > unionfs 0 > > hfs 2 local, dovolfs > > devfs 0 > > autofs 2 > > fusefs 1 > > More importantly did you create the mountpoint and mount it? > > What does `mount` say? > > -d > > ------------------------------------------------------------------------ > Dan Shoop > [email protected] > GoogleVoice: 1-646-402-5293 > twitter: @colonelmode -- You received this message because you are subscribed to the Google Groups "MacFUSE" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/macfuse?hl=en.
