The Tor Browser bundle and the Tor Daemon are different beasts, and there's some confusion what does what. The fact that 'tor' isn't familiar to you means you should probably be looking into what different commands do before trying to alias things together. (For example, tor
is an actual program - using that to call the Tor Browser is not the correct approach)
Tor Browser
Tor Browser is a software bundle which comes with its own Tor daemon that is launched by the "Start Tor Browser" script. This software bundle includes a fork of Firefox which is bundled with plugins that are specific to Tor Browser, to make it function effectively on the Tor network.
Tor Browser is only run usually with the ./start-tor-browser.desktop
launcher, or the ./start-tor-browser
shell script/function which executes everything that needs to run for Tor Browser to work.
This is its own software bundle, and is different than the standalone Tor daemon (which is tor
).
tor
aka "The Tor Daemon"
The Tor daemon can be launched and run on a system to connect it to the Tor network. It in turn operates on a SOCKS proxy over which you can send application traffic through to send over the Tor network. It is designed to run transparently and silently on the system, and does not execute any type of other programs - it only runs the daemon and the corresponding proxy which can be used to send data through.
It does not launch the Tor Browser as it is designed to run separately as its own daemon, and not to launch the Tor browser.
Best Answer
As @bodhi.zazen said in the comments, the
tor
command is working fine; it's just that Tor is already running. If you read the output from thetor
command, you'll see that this is indeed the case.This is similar to how you can't have to instances of Audacity running at the same time.
If the
tor
command were really not working, you'd get this output: