On Thu, Dec 21, 2006 at 02:37:33PM +0000, Ten wrote:
On Thursday 21 December 2006 08:46, cl@isbd.net wrote:
On Wed, Dec 20, 2006 at 11:37:08PM +0000, Wayne Stallwood wrote:
On Wed, 2006-12-20 at 22:59 +0000, cl@isbd.net wrote:
even though . is on my path.
oooh I used to punish people for doing that, normally by having a script called ls that relinked their home dir somewhere else :-)
It's a no, no for root of course but it's a big convenience for an ordinary user. Since I'm the only user (and I'm the admin) I don't feel too unsafe doing it.
Interesting. For me, that would make no sense and would be a big inconvenience if it were assumed in my scripts(although it's not as if it's ever likely to be forced on me, heh). You know where you are with dotslash if you want it - quite literally of course.
The trouble is in this case that even if I enter:-
./build
I still get the error:-
/bin/bash: ./build: No such file or directory
even though there is a build in the current directory and it's executable by me. Not to mention that sh can run it fine.
I do keep a pathed-up-for-that-user folder in every home directory (/home/me/scripts or whatever), which is a fairly common take on the same sort of thing, I suppose. :-)
Ten.