On Thu, 05 Jul 2018 16:59:21 +0100, Peter Percival wrote:

> Ahem A Rivet's Shot wrote:
>> On Thu, 5 Jul 2018 15:42:43 +0100 Peter Percival
>>  wrote:
>>
>>> Thank you.  I have added . to PATH and it now works.
>>
>>  I hope you put it at the end.
>
> I did.  It now seems it shouldn't be there at all and I need a ~/bin
> directory for my executables.
>
>

As usual... it depends.

I've always run with '.' at the end of $PATH, but I'm careful about
restricting access:

- the firewall on am ADSL router is locked down so tight that from the
  outside its not possible to tell whether its turned off or alive and
  well.

- My main machines (laptops and a desktop) all run fairly restrictive
  firewalls and are logged out when not in use. I tend to use a lot of
  directories and logins, so different projects and running services
  (mail handling, house web server) all tend to have their own logins
  and associated directory structures.

- I have a small, encrypted partition which is used for sensitive data,
  e.g external passwords etc.

- My RPi is the same, but no firewall or encrypted partition. However,
  its turned off unless I'm using it.

- my desktop acts a house server, so runs a web server, mail server,
  spamassassin.... and is also my central CVS version control repository,
  so contains the master copies of all program source and shell scripts.

- the house server is backed up overnight every night and all machines
  are backed up to offline disks each week immediately before their
  weekly software update.

I can live with this level of protection: I haven't lost anything yet.
Others may want more protection or less.

Either way its something to think about, work out what you need and are
prepared to manage, and then get it set up and working.


--
Martin    | martin at
Gregorie  | gregorie dot org

--- SoupGate-Win32 v1.05