Fire up the Tor [0] and Privoxy [1] daemons then set variables <i>these vary by text browser</i> to use the Privoxy proxy with your text browser. <i>links, lynx, w3m, etc...</i> The variables are usually <i>http_proxy, ftp_proxy, etc...</i> and specifically also <i>PROTOCOL_proxy</i> for lynx but I would read the man page for whichever you end up using. curl can use variables or the --proxy flag. Privoxy acts as a regular proxy and talks to Tor on the socks port. There are other ways to accomplish this as well.<p>Another method is to use Squid chained to Privoxy to get caching and find grained controls over URI, Method, File Type, Client / Server Headers and other ACL's. Newer major versions of Squid <i>6</i> can talk directly to SOCKS but most distros still have 3 in their repositories probably due to the configuration directives changing so dramatically between 3 and 6.<p>[0] - <a href="https://dist.torproject.org/?C=M;O=D" rel="nofollow">https://dist.torproject.org/?C=M;O=D</a><p>[1] - <a href="https://www.privoxy.org/" rel="nofollow">https://www.privoxy.org/</a>