>> Clarence Verge wrote:
> I also TRY to alias ls -la to dir and it IGNORES me. <G>
Alias is included with all the full distributions. Apparently
it's one of the things pygmy has left out. If you want to see
if it's in your path, do 'which alias' If it's in your path
it'll show the path to the command. If it's not in your path,
it'll show the directories presently included in your path
(where it searched and didn't find it).
Unlike DOS, just being in the same directory with an executable
file doesn't mean you can just type it and it'll run. The two
ways Linux differs from DOS in this respect are that the executable
flag must be set on the file and if the file isn't in your path,
you must give the complete path to it. (In the case where you're
in the same directory, you need to tell it './arachne' rather than
just 'arachne'. That lets the command interpreter know that you
mean to run *this* arachne rather than one which might be on
your path or which might be in some other directory.
> I'm writing to let you know that the new PygmyLinux contains "links"
> as does your distribution, and I quite like links.
Links are very useful things to have. Usually you'll use
a soft link rather than a hard one, but they both have their
uses.
> The begging begins here:
> I have Pygmy06 also, which has pine. I would like to transport pine
> to Pygmy07, but I have no idea how one determines what files belong
> to what application.
Usually you'll download a tarball (much like a *.zip file)
which will contain all the files you need.
Red Hat and Debian each have their own packaging formats
which differ from tarballs in that they also contain information
about dependencies, and enter all the filenames into a database
so for instance with pine, the single command 'rpm -e pine' will
remove *all* those scattered files.
> Files seem to be strewn generally all over the
> place.
In many ways, it's more organized than DOS, but until you
get the hang of it, also more confusing.
> I find scripts and inis and rcs (what's that?) and
> setups and totally unrecognizable exes all separated.
Most executables will go to /bin, /usr/bin, /sbin, or
/usr/sbin. There aren't any hard and fast rules, but in
general, normal executables will go in /bin. Programs
added by users will likely go to /usr/bin. Standard
system executables will be in /sbin. System executables
allowed to be run by users will fall into /usr/sbin.
System configurations go to /etc, and user configurations
will generally be put into hidden *.rc or *.ini or *.conf
files in the user's home directory.
If you do 'ls -a' all those "invisible" files will be
shown.
> So, how does one a) delete an application,
The easiest way is with one of the packaging tools, such
as Red Hat's rpm, or Debian's dpackage. Otherwise, you might
go back and look at the original tarball to see what was there.
Use mc, if you have it installed, to examine the tarball to see
what directories and files it contains. Otherwise, you can use
'tar -ztf arachne-1.66.tar.gz' to get a list of everything it
contains.
> and b) transport one ?
Again, the easiest way is to transfer the entire package
or tarball.
> Talking about droppings, I have loaded Arachne1.66 into Pygmy07
> and it (Arachne) has accepted it's surroundings.
> Any idea how I might invoke it ?
It sounds like you ran the install script. During that
process, it asked you what and where you wanted to put the
command to launch it. Default was /usr/bin/arachne. If you
accepted that, and if /usr/bin is in your path (it certainly
should be), then simply 'arachne' should launch it.
If not, then there should be error message(s) to help pinpoint
the problem.
> p.s. Please CC to [EMAIL PROTECTED]
- Steve
-- This mail was written by user of Arachne, the Ultimate Internet Client
-- Arachne V1.69, NON-COMMERCIAL copy, http://arachne.cz/
