who knows how to do that???
I found alot of files in the zipped file with the encoder for Linux, bud i dontknow where to put it... and what is $path??? (sorry, im newbie to linux....)

You can safely extract the files to /usr/bin/. Path is list of directories used to search executable programs.

tanx alot!!!

/usr/local/bin would be even a bit saver, since /usr/bin is primary for packages (RPMs) / stuff installed by the distribution...
dev0

There is nothing that makes it 'safer' to have stuff in /usr/local/bin instead of /usr/bin that is related to packages.

A good reason to have them in /usr/local/bin instead of /usr/bin is to prevent root from running them, because that might be a security risk (if Frank Klemm decides to go for total world domination or so and needs control of your computer to accomplish that goal).

The packaging systems won't be affected by the location of where you copy the files to.

Edit: Hmm, ok, if there already is a program installed that is also named mpcenc, you're right - you could overwrite it. Not too damn likely though, moreover, in that case installing it either way won't work as expected.

--
GCP

tnx guyz... think I put it local...
btw imho the system of dos, seperate directory's for every prog, is easier. on the other hand, all those dll-shit from Micro$oft really sucks... (leftovers etc - u know...)

There is no reason why you can't do this with Linux as well. In fact, it'll work exactly the same.

--
GCP

If I recall correctly a very good reason for the executable to be in /usr/local/bin is because the CD ripper "Grip" looks first in that directory for the encoder you choose.

....yeah yeah yeah...

i think the most obvious reason is that /usr [distribution installation] and /usr/local [additional installations] are quite often on seperate partitions.

many people have read-only permissions for /usr and not for /usr/local

atleast that is what i have been doing...

but i haven't been around linux long

later
mike