search for: fusef

Hi there, I've been trying to mount my NTFS partitions with the NTFS-3g project's FUSE implementation but am unable to mount anything. I'm on 6-STABLE and have the latest versions of FUSE installed: fusefs-kmod-0.3.0_4 Kernel module for fuse fusefs-libs-2.6.2 FUSE allows filesystem implementation in userspace fusefs-ntfs-0.20070207RC1 Mount NTFS partitions and disk images I use the sysutils/ntfsprogs port to create a NTFS filesystem. I can also mount this filesystem using mount.ntfs, yet I fail t...

Hello, There is a problem with fusefs-kmod and FreeBSD 9.2 and rsync. While starting rsync on fuse share, one encounters kernel panic with: fuse4bsd: version 0.3.9-pre1, FUSE ABI 7.19 Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x0 fault code...

...qca devel/qt4-qdbusviewer devel/qt4-script emulators/qemu-devel graphics/cairo graphics/graphite2 graphics/libfpx graphics/opencv-core graphics/podofo graphics/vigra lang/sbcl math/cln net-im/libmsn net-p2p/libtorrent net/hupnp net/ns3 net/xmlrpc-c-devel science/openbabel security/pinentry sysutils/fusefs-kmod sysutils/synergy textproc/clucene x11/nvidia-driver where at least ns3 can be ignored ( I created that port myself ). I think nvidia-driver and fusefs-kmod now fails due to -stdlib=libc++ in LDFLAGS, normally fusefs-kmod just fails install-phase due to missing pkg-message file. I saved the...

...and plug in a FreeBSD installation with Samba 3.6.25 running and tested on another machine. Fortunately it's a small installation and everybody is using the same share on the Windows server. Very little is stored by each user separately. I can mount the existing Windows data drive r/w with fusefs. What should I look out for? - I already had problems moving files from one disc to the other under Windows because of a mix of historical clients (file names/paths too long, permissions etc.) Otherwise I add the FreeBSD server into the network and ask people to move their files over manually...

...can help me. my server: FreeBSD laverne.physik-pool.tu-berlin.de 7.1-RELEASE amd64 I've testet some glusterfs-releases, beginning with Glusterfs 1.4x. I'm now using glusterfs2.0.0rc4 (also testet with rc2, it's still the same) How Glusterfs was build: support packages: bison-2.3_4,1, fusefs-kmod-0.3.9.p1.20080208_4, fusefs-libs-2.7.3 i've used glusterfs-2.0.0rc4: > export LDFLAGS="-L/usr/local/lib -liconv" > export CFLAGS="-O0 -g -DDEBUG -I/usr/local/include/" > ./configure > make install clean server-vol-file: http://www.physik.tu-berlin.de/~fren...

...er. Its my private playground, but I have some issues I can't figure out why they happen. I use RHEL5.7, packetlist: rpm -qa|grep samba samba-3.0.33-3.29.el5_7.4.x86_64 samba-common-3.0.33-3.29.el5_7.4.x86_64 2 servers, one provides samba-shares and one I use as client. Samba-Server (HOST2): FuseFS: hadoop-fuse-dfs#dfs://HOSTNAME:9000 /123/hdfs fuse usetrash,rw 0 0 mount: fuse on /123/hdfs type fuse (rw,nosuid,nodev,allow_other,default_permissions) the mount /123 is accessible over ssh, cp, rsnyc from any host. Now I was using NFS for populating, but the performance was not as I expected....

A while back, I submitted a patch for PR kern/124621, which allows the mounting of an ext2(3) filesystem created with an inode size other than 128. The e2fsprogs' default is now 256, so file systems created on newer Linux distributions or with the port will not be mountable. I was hopeful this would get committed in time for 7.1-RELEASE (and 6.4-RELEASE), however the PR remains open. If

Normally the FreeBSD Project tries very hard to avoid ABI breakage in "Stable Branches". However occasionally the fix for a bug can not be implemented without ABI breakage, and it is decided that the fix warrants the impact of the ABI breakage. We have one of those situations coming along for RELENG_7 (what will become FreeBSD 7.1). The ABI breakage should only impact kernel modules

...k = yes inherit permissions = yes vfs objects = recycle recycle:repository = .recycle/%U recycle:keeptree = yes recycle:versions = yes recycle:touch = yes recycle:directory_mode = 0777 recycle:subdir_mode = 0700 ======= = eof = ======= My mounts look like this: /dev/fuse0 on /mnt/noontec-movies (fusefs, local, synchronous) /dev/da1s1 on /mnt/noontec (msdosfs, local) (fuse0 due to the ntfs) I've tried every which way to mount the FAT32 disk, including: mount_msdosfs -o large=yes,longnames=yes,nowin95=yes -u root -g wheel -m 777 /dev/da1s1 /mnt/noontec mount_msdosfs -o large=yes,longnames=y...

...allation with Samba 3.6.25 running and tested on another > machine. > > Fortunately it's a small installation and everybody is using the same > share on the Windows server. Very little is stored by each user > separately. > I can mount the existing Windows data drive r/w with fusefs. > > What should I look out for? > - I already had problems moving files from one disc to the other under > Windows because of a mix of historical clients (file names/paths too > long, permissions etc.) > > Otherwise I add the FreeBSD server into the network and ask people to...

Hi all, I noticed when porting ext2fuse to run on 7.1-PRERELEASE, that the port sysutils/fusefs-ntfs needs some additional steps in order to mount user-space FUSE filesystems on startup. These steps weren't necessary in 6.x. It seems mount(8) can't deal with new mount binaries unless it has been explicitly built with support for them; please see /usr/local/share/doc/ntfs-3g/...

Hello, I have not had much time to research this problem yet, so please let me know what further information I might be able to provide. This weekend I attempted to upgrade a computer from 8.2-RELEASE-p3 to 8.4 using freebsd-update. After I rebooted to test the new kernel, I got a panic. I had to take a picture of the screen. Here's a condensed version: panic: page fault cpuid = 1 KDB: