Page 1 of 1

Changed install pathway for binaries between 1.9.4 and 2.0.0

PostPosted: Tue Jan 05, 2021 10:11 pm
by FadingIntoBlue
I'm interested in the effect of the change in binary paths with the latest version, as I haven't seen much comment or documentation about it. Not an issue for most people I suspect, but it is one of the simpler things that seems to stop the new version working immediately.

So 1.9.4 path: /usr/local/bin/zfs
and 2.0.0 path: /usr/local/zfs/bin/zfs
for the zfs binary and the others

Obviously, if the path isn't in your shell profile commands will not run without a full path.

I notice that ZetaWatch won't launch under 2.0.0 running on both Catalina and BigSur, is the binary pathway hard coded?

I suspect we will turn up a few other situations where this causes problems and thought it was worth mentioning.

Re: Changed install pathway for binaries between 1.9.4 and 2

PostPosted: Wed Jan 06, 2021 4:31 pm
by lundman
Yes, in the 2.0 pre-releases we are trying out keeping everything in "/usr/local/zfs/" as there has been many issues in the past with which-path-is-in-use, so hopefully this will be a little more
contained. Once the change over is done with.

We do add to /etc/paths.d/zfs so in theory you should get PATH set correctly, unless you are using a different shell perhaps.