New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
borgfs
in Standalone Binary Installation Docs
#8207
Comments
Usually that works, borg internally detects the name by which it was invoked and then behaves differently. Try:
If one or more of these does not behave like "borg mount" when invoked as |
Thanks for the clarification! I've tested it and you're right, it works as expected. I suggest adding a note to the documentation explaining that Borg internally detects the name by which it was invoked and adjusts its behavior accordingly. This isn't immediately apparent, and such a note would help clarify why creating a symlink serves as a functional alias. |
I noticed a potential issue in the Standalone Binary installation section of the documentation where it suggests creating a symlink to make
borgfs
an alias forborg mount
Quote:
A symlink to
borg
will just replicate theborg
command under a new name,borgfs
, but does not restrict or modify its behavior to only executeborg mount
.The documentation might consider suggesting the use of a shell alias or a wrapper script instead.
For example:
The text was updated successfully, but these errors were encountered: