News for hackers. Stuff that matters.
Re:AppFS, a FUSE filesystem via HTTP for running software wi... by rgovostes on Tuesday February 16, 2016 @07:14AM (#11109323)
This is built into OS X:

hdiutil attach https://adiumx.cachefly.net/Adium_1.5.10.1.dmg -shadow Adium.shadowfile

The -shadow option allows the image to be mounted read-write, with writes being redirected into the shadow file.

Re:AppFS, a FUSE filesystem via HTTP for running software wi... by peeters on Tuesday February 16, 2016 @09:06AM (#11109833)
I'm not an Apple guy so let me ask a naive question: is this even close to a functional equivalent? Quick research makes this look like just mounting a remote filesystem.

That's very different than being a package format, with dependency resolution, caching equivalent files, etc.

Re:AppFS, a FUSE filesystem via HTTP for running software wi... by rgovostes on Tuesday February 16, 2016 @10:24AM (#11110395)
Yes it is mounting a remote filesystem, it does not have all the same features. I was replying to the title "a FUSE filesystem via HTTP for running software without installing it," which the above command permits; the linked page (at least without exploring deeper into the site) doesn't describe dependency resolution. Caching will performed by the kernel, but I don't know how it operates in a multi-user environment.
Re:AppFS, a FUSE filesystem via HTTP for running software wi... by rkeene2 on Wednesday February 17, 2016 @08:41AM (#11117731)
Dependency resolution is implicit to the design -- the entire global namespace is available on every system so any dependencies are resolved as they are requested.

That is, if you have an executable such as "ls" that relies upon the dynamic linker provided by "glibc", then the glibc requested will be fetched automatically because you attempted to open the dynamic linker.

Additionally, the design is superior to the single-user nature of a remote disk image in that each user's writes are redirected to their own home directory (by default, you can change this in a config file).

Even further, it allows for setuid files to be handled safely which is sometimes needed (e.g., "sudo" or "chrome-sandbox").

Caching is handled by the kernel for the VFS cache but also by a more persistent disk cache so that you can use applications offline as long as you have cached them (by running them, usually) ahead of time.

Re:AppFS, a FUSE filesystem via HTTP for running software wi... by herbst on Tuesday February 16, 2016 @11:59AM (#11111238)
We also have SSHFS. Like on any system? (Probably not windows, no idea, but that sucks anyway for any producivity)
Re:AppFS, a FUSE filesystem via HTTP for running software wi... by rkeene2 on Wednesday February 17, 2016 @08:44AM (#11117758)
AppFS is built on FUSE just like SSHFS, it just uses a different transport protocol, doesn't support pushing writes back the origin server, does heavy caching, safely supports multiple users (including writes), can safely connect to untrusted servers (uses end-to-end PKI, so verification works even if the original URLs are not the same for example if mirroring is used), and handles setuid-root files in a safe way.