Re: Installing Tor in Linux

On Sat, 28 Apr 2007 09:37:44 -0700, sk8terg1rl wrote:

Hi Douglas,

On Apr 28, 2:35 pm, Douglas Mayne <d...@xxxxxxxxxxxxxxxxxx> wrote:

<snip>

I'm forced to stick to Windows at the moment mostly because that's
what I'm familiar with and I'm extremely pressured for time at the
moment to be able to learn, let alone, import, things over to Linux
even if I was good at it. Once I finish my final year, then I will
have more time on my hands to do so. I am determined to jump ship soon
because I will not let Microsoft force me to use Vista.

When you get some spare time, check out VMWare (or another form of
virtualization.) That way, Windows runs in a window and can be protected
by NAT and IPtables.

<snip>

I was reading Wikipedia's article on Slackware:

http://en.wikipedia.org/wiki/Slackware "Slackware employs a minimalist
approach to package management.[11] Its package management system can
install, upgrade, and remove packages as easily as other distributions.
However, it makes no attempt to track or manage dependencies, relying on
the user to ensure that the system has all the supporting system
libraries and programs required by the new package. If any of these are
missing, there may be no indication until one attempts to use the newly
installed software."

Does this mean that Slackware can potentially end up with overlapping
libraries and packages? Can this lead to buggy behaviour and if so how
do you rectify it?

The computer is always at the "mercy" of the root user. That user can do
great damage to a system, regardless of the "package manager." At least
with Slackware this fact is not hidden, and the user is advised to be very
careful not to break consistency, or symbolic links to library versions,
etc. RPM distro's only mask the fact that the system is somewhat fragile.
The best defense is being careful and testing in advance before putting in
place on a critical system.

[ Going OT ]
Slackware is closer to the "metal." That is a definite advantage in
certain situations. Adding software to a Slackware release can be
similar to other distributions. For example, you can begin by looking
for a compiled binary that will work. It should work as long as it has
been compiled for your specific release version. If there is no
compiled binary available, then the user can "use the source, Luke."
Remember, free software did not magically appear on earth. Someone had
to write it. The big advantage of the movement is that the source code
is available. You miss at least half of what the free software movement
is about if you choose to always ignore the source component.

Unfortunately I don't have any formal training in software languages
other than Fortran. Much of the source looks like C++ to me. When you
talk about missing part of the free software movement - for me to take
advantage of it, must I learn C++?

While thinking this over, I came to the conclusion that the most important
language in the free software movement is English. The README in the
documentation is often the first step to making sure the program has a
chance of compiling. For example, the instructions tell you what you
should have before attempting the compile. Configuration files with
parameters in English are easiest for people to understand, although they
may not be in the most compact (binary) form.

After English, then perhaps, learning about "make" is one of the next
steps. You have already posted some of a make file output where the
rigorous configuration checks are performed. The fact that these programs
are designed to work on various other unix-like OSs should make compiling
between flavors of GNU/Linux a cinch.

Thanks (and sorry for not listening to you earlier!)

skate xx

Note: comments inline.

It sounds like you are working hard and have your priorities straight. The
computer is a tool, first and foremost for most people. It's easy for me
to forget that sometimes. I just wish more people were like you and would
investigate the alternative provided by _free_ software. Perhaps, more
people will come to GNU/Linux, if only fleeing draconian licensing and
absolute vendor lockin by one monopoly or another.

--
Douglas Mayne
.