From: Gerard J. C. <gj...@ci...> - 2008-09-26 15:36:46
|
Hi List, I had to back port my fuse file system to RH9 kernel 2.4.20-31.9 . Everything looks fine on my development machine where I can build and install fuse 2.7.2 from the distributed sources. I have a problem when I must install on a non-development machine (no build tools). I have done this trick on ES4 machines successfully. When I try to start any fuse file system I get an error: -bash-2.05b# ./fusexmp_fh /mnt/mafs /bin/mount: invalid option -- i Usage: mount -V : print version mount -h : print this help mount : list mounted filesystems mount -l : idem, including volume labels So far the informational part. Next the mounting. The command is `mount [-t fstype] something somewhere'. Details found in /etc/fstab may be omitted. mount -a [-t|-O] ... : mount all stuff from /etc/fstab mount device : mount device at the known place mount directory : mount known device here mount -t type dev dir : ordinary mount command Note that one does not really mount a device, one mounts a filesystem (of the given type) found on the device. One can also mount an already visible directory tree elsewhere: mount --bind olddir newdir or move a subtree: mount --move olddir newdir A device can be given by name, say /dev/hda1 or /dev/cdrom, or by label, using -L label or by uuid, using -U uuid . Other options: [-nfFrsvw] [-o options]. For many more details, say man 8 mount . The development machine and target both have mount version mount-2.11y I used the fuse included libtool to install fusermount: ./libtool --mode=install /usr/bin/install -c ./util/fusermount "/usr/local/bin/fusermount" Any ideas what I missed on installing? Gerard |