Chaos of confusion RESOLVED - was [Re: When specifying path to file - confused about ./ and ~/]

2017-04-03 Thread Richard Owlett
] Of course, if you start your path with /, it's an absolute path, like /usr/local/bin/foo/command. That was the key. *BUT* it went unrecognized until crashed full tilt into another problem. My subject line SHOULD HAVE BEEN: " When specifying path to file - confused about ./ and ~/ and /"

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

2017-03-28 Thread Brian
On Tue 28 Mar 2017 at 13:09:57 -0400, songbird wrote: > kAt wrote: > ... > > 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

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

2017-03-28 Thread songbird
kAt wrote: ... > 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 maybe, maybe not (depends upon

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

2017-03-27 Thread David Wright
On Mon 27 Mar 2017 at 21:48:00 (+), kAt wrote: > 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 >

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

2017-03-27 Thread Mark Fletcher
On Mon, Mar 27, 2017 at 09:48:00PM +, kAt wrote: > > 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

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

2017-03-27 Thread Ben Caradoc-Davies
On 28/03/17 10:48, kAt wrote: 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

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

2017-03-27 Thread kAt
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

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

2017-03-27 Thread Brian
On Mon 27 Mar 2017 at 14:51:08 -0500, Richard Owlett wrote: > On 03/27/2017 02:25 PM, Brian wrote: > > > >Not only do you want a web page but you want one with particular > >characteristics. That's a tall order but we will try. Any particular > >colours it has to be in? > > > > SEE

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

2017-03-27 Thread Richard Owlett
On 03/27/2017 02:25 PM, Brian wrote: Not only do you want a web page but you want one with particular characteristics. That's a tall order but we will try. Any particular colours it has to be in? SEE https://lists.debian.org/debian-user/2017/03/msg01167.html Where I said "I was not aware

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

2017-03-27 Thread tomas
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, Mar 27, 2017 at 10:39:41AM -0500, Richard Owlett wrote: > On 03/27/2017 09:37 AM, to...@tuxteam.de wrote: [...] > >[give us examples] > > Thought I did ;/ I was just paraphrasing your paragraph, which I snipped out ;-) > >FWIW I studied

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

2017-03-27 Thread Brian
On Mon 27 Mar 2017 at 06:39:49 -0500, Richard Owlett wrote: > > On 03/27/2017 01:14 PM, Richard Owlett wrote: > *Please avoid trying to briefly explain.* Its hard - but we will try. > *_Please refer me to a good web page._ Deconstruction: Please do my searching for me. > I *KNOW* I'm

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

2017-03-27 Thread Richard Owlett
On 03/27/2017 09:37 AM, to...@tuxteam.de wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, Mar 27, 2017 at 09:26:58AM -0500, Richard Owlett wrote: On 03/27/2017 07:47 AM, to...@tuxteam.de wrote: On Mon, Mar 27, 2017 at 11:25:30PM +1100, David wrote: On 27 March 2017 at 22:39,

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

2017-03-27 Thread Richard Owlett
On 03/27/2017 08:27 AM, Mark Fletcher wrote: On Mon, Mar 27, 2017 at 08:38:08AM -0400, The Wanderer wrote: On 2017-03-27 at 07:14, Richard Owlett wrote: Please avoid trying to briefly explain. Please refer me to a good web page. I *KNOW* I'm missing something fundamental. A web page will

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

2017-03-27 Thread Jochen Spieker
Richard Owlett: > On 03/27/2017 07:38 AM, The Wanderer wrote: >> >> Can you explain what your question is? > > No, not even after having having had an explanation that alleviated the > problem. I think you could have posed your question as simply: "What do ./ and ~/ mean? What is the

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

2017-03-27 Thread David Wright
On Mon 27 Mar 2017 at 22:27:05 (+0900), Mark Fletcher wrote: > On Mon, Mar 27, 2017 at 08:38:08AM -0400, The Wanderer wrote: > > On 2017-03-27 at 07:14, Richard Owlett wrote: > > > > > Please avoid trying to briefly explain. > > > Please refer me to a good web page. > > > I *KNOW* I'm missing

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

2017-03-27 Thread tomas
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, Mar 27, 2017 at 09:26:58AM -0500, Richard Owlett wrote: > On 03/27/2017 07:47 AM, to...@tuxteam.de wrote: > > > >On Mon, Mar 27, 2017 at 11:25:30PM +1100, David wrote: > >>On 27 March 2017 at 22:39, Richard Owlett wrote:

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

2017-03-27 Thread Richard Owlett
On 03/27/2017 07:38 AM, The Wanderer wrote: On 2017-03-27 at 07:14, Richard Owlett wrote: Please avoid trying to briefly explain. Please refer me to a good web page. I *KNOW* I'm missing something fundamental. A web page will either have links to whatever my underlying problem is. Or it will

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

2017-03-27 Thread Richard Owlett
On 03/27/2017 07:47 AM, to...@tuxteam.de wrote: On Mon, Mar 27, 2017 at 11:25:30PM +1100, David wrote: On 27 March 2017 at 22:39, Richard Owlett wrote: On 03/27/2017 01:14 PM, Richard Owlett wrote: *Please avoid trying to briefly explain.* *_Please refer me to a good

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

2017-03-27 Thread Richard Owlett
On 03/27/2017 07:25 AM, David wrote: On 27 March 2017 at 22:39, Richard Owlett wrote: On 03/27/2017 01:14 PM, Richard Owlett wrote: *Please avoid trying to briefly explain.* *_Please refer me to a good web page._ http://www.ee.surrey.ac.uk/Teaching/Unix/unix1.html

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

2017-03-27 Thread Mark Fletcher
On Mon, Mar 27, 2017 at 08:38:08AM -0400, The Wanderer wrote: > On 2017-03-27 at 07:14, Richard Owlett wrote: > > > Please avoid trying to briefly explain. > > Please refer me to a good web page. > > I *KNOW* I'm missing something fundamental. > > A web page will either have links to whatever my

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

2017-03-27 Thread tomas
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, Mar 27, 2017 at 11:25:30PM +1100, David wrote: > On 27 March 2017 at 22:39, Richard Owlett wrote: > >> On 03/27/2017 01:14 PM, Richard Owlett wrote: > > *Please avoid trying to briefly explain.* > > *_Please refer me to

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

2017-03-27 Thread The Wanderer
On 2017-03-27 at 07:14, Richard Owlett wrote: > Please avoid trying to briefly explain. > Please refer me to a good web page. > I *KNOW* I'm missing something fundamental. > A web page will either have links to whatever my underlying problem is. > Or it will inherently use keywords for which I

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

2017-03-27 Thread David
On 27 March 2017 at 22:39, Richard Owlett wrote: >> On 03/27/2017 01:14 PM, Richard Owlett wrote: > *Please avoid trying to briefly explain.* > *_Please refer me to a good web page._ http://www.ee.surrey.ac.uk/Teaching/Unix/unix1.html

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

2017-03-27 Thread Richard Owlett
> On 03/27/2017 01:14 PM, Richard Owlett wrote: *Please avoid trying to briefly explain.* *_Please refer me to a good web page._ I *KNOW* I'm missing something fundamental. A web page will either have links to whatever my underlying problem is. Or it will inherently use keywords for which I

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

2017-03-27 Thread Peter Ludikovsky
./ - the current director, usually used when running a script from it and it not being in the search path for executables ~/ - the current users home directory Trying to get through an interview? Regards, /peter On 03/27/2017 01:14 PM, Richard Owlett wrote: > Please avoid trying to briefly

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

2017-03-27 Thread Richard Owlett
Please avoid trying to briefly explain. Please refer me to a good web page. I *KNOW* I'm missing something fundamental. A web page will either have links to whatever my underlying problem is. Or it will inherently use keywords for which I can search. Thank you.