My note was merely to say that I've started to look into this. Of
course, commenting out the offending line from .login by-passes the
loss of PATH problem.
> isn't found. Probably means whatever is defined in the "#!/..." statement
> at the top of epath has moved home.
Indeed. awk is located in a different place. Why do the various Linux
suppliers mess around with the paths to fundamental commands and tools?
Can't they agreed on a standard set of locations?
Is there a portable way to specify the path for an awk script?
Malcolm
|