Page MenuHomeFreeBSD

linux: improve FUSE support
ClosedPublic

Authored by trasz on Jun 1 2021, 7:34 PM.
Tags
None
Referenced Files
Unknown Object (File)
Wed, Oct 15, 12:50 AM
Unknown Object (File)
Wed, Oct 15, 12:50 AM
Unknown Object (File)
Wed, Oct 15, 12:50 AM
Unknown Object (File)
Tue, Oct 14, 4:08 PM
Unknown Object (File)
Tue, Oct 14, 1:51 PM
Unknown Object (File)
Wed, Oct 8, 5:15 PM
Unknown Object (File)
Tue, Oct 7, 12:55 AM
Unknown Object (File)
Sat, Oct 4, 4:12 AM
Subscribers

Details

Summary

This fixes a number of AppImages; tested with
scribus-1.5.6.1-linux-x86_64.AppImage.

Reported By: probonopd

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

trasz requested review of this revision.Jun 1 2021, 7:34 PM

The code looks good to me. Was the problem that a Linux command like "mount -t fuse.ntfs ..." wouldn't work?

This revision is now accepted and ready to land.Jun 1 2021, 7:44 PM

Much weirder than that. Strace, on the AppImage I'm using for testing, shows this:

[pid  1792] mount("scribus-1.5.6.1-linux-x86_64.AppImage", "/tmp/.mount_scribuH15vRB", "fuse.scribus-1.5.6.1-linux-x86_6"..., MS_RDONLY|MS_NOSUID|MS_NODEV, "fd=5,rootmode=40000,user_id=0,gr"...) = 0

The fstype is fuse.scribus-1.5.6.1-linux-x86_64.AppImage; options are fd=5,rootmode=40000,user_id=0,group_id=0.

The fstype is fuse.scribus-1.5.6.1-linux-x86_64.AppImage; options are fd=5,rootmode=40000,user_id=0,group_id=0.

That is a pretty weird name, but there's nothing illegal about it. A fuse daemon is allowed to specify anything it wants for the file system subtype.

This revision was automatically updated to reflect the committed changes.