>>55311477
Can't you do the same thing with dd + ssh / rsync

>>55311477
Zfs is not a network filesystem. But you could send (incremental) snapshots between two zfs hosts.
>zfs send tank/porn@snap | ssh foo@bar zfs recv tank/porn

>>55311477
Why not?

sshfs doesn't even require zfs.

That's just because of how POSIX OSes grew up in networked systems where Windows grew up on shitty microcomputer desktops.

You can ssh -X into a remote box, run a command that opens a GUI program and the GUI program will open seamlessly on your local machine...

>>55311982
sshfs is God minus performance issues. It's 2014+2 and while MS has a linux subsystem, there's no FUSE for glorious sshfs.

Always hated how I'm too retarded to figure out how to get the applications to run on the remote machine's display.
How do?

>>55312230
> xhost +
> export DISPLAY=":0.0"
You're welcome

>>55312482
So this?

export DISPLAY=":0.0" xhost mpv file.mkv

>>55312653
Ssh to the box
xhost + (it's like access control)
That export command
Whatever X program you want.

This may sound confusing, but your desktop will actually be the server in the case ( an X server )

>>55312653
Well?

>>55312741
xhost opens another shell or something? investigating.

ssh [email protected]
Password:
$ xhost +
$ export DISPLAY=":0.0"
$ mpv file.mkv

Like that? ^
Is xhost making the remote server the client and then piping commands to it?

>>55313228
Er shit.. Just realized I meant to say run xhost + on your box first, then ssh, run the export bit, then MPV.

>>55313228
should have just

man xhost
[/host]

I see that + is a global access allow option for the x server, but the attack surface is negligible anyway on a local, home server. Cheers.

>>55313263
Not to totally scare you off but you can check the sshd_config setting for X11Forwarding, should be set to yes. That's a good man page too. Good luck.

>>55311607
Enjoy your inconsistent file system :^)