Re: When specifying path to file - confused about ./ and ~/

[kAt <giathnygeia@openmailbox.org>]

Richard Owlett:
> 
> SEE https://lists.debian.org/debian-user/2017/03/msg01167.html
> 
> Where I said "I was not aware that search engines accepted
> non-alphanumeric strings as legitimate search terms. Previous experience
> had suggested otherwise.
> 
> Thank you, this old dog has learned a new trick.
> 
> P.S. Fourth hit of https://www.google.com/search?q=~/+tutorial was
> David's first link ;/

I have an example where this might be useful or then I am not
understanding the difference.

Let's say you have an executable package in the system and let's call it
pkgX
If you type pkgX in any prompt then /usr/bin/pkgX will be executed
But let's say you want to download and run a variation of this package,
edit its source and modify it, or just want to run separately a
standalone package in /xyz/packageX/pkgX
If you $cd /xyz/packageX and then $ ./pkgX the standalone would run,
right?  While pkgX will run the /usr/bin/pkgX
Alternatively in creating a local web-page set the ./index.html as the
site's root directory can easily be implemented in domain.net/index.html
and all links ./****.html will work on the remote site.

PS  off-topic rant
I just updated and a package named busybox came up.  Since I didn't know
what it was I went into the page and its most recent revision of 1/2017
seemed to be 3 years ahead of the testing/unstable version that we just
updated now!  And this is very basic common stuff like cp and fdisk
......  How conservative is our system?  Wowww!