trohling@uceng.UC.EDU (tom rohling) (01/11/90)
In the previous posting about the ./ things, I've found out that the problem is not there when you log in through telnet. Only when you login on the console. More reason to say: ?????????? Tom
jweldon@renegade.sgi.com (Jack Weldon) (01/12/90)
In article <3300@uceng.UC.EDU> trohling@uceng.UC.EDU (tom rohling) writes: >In the previous posting about the ./ things, I've found out that the >problem is not there when you log in through telnet. Only when you login >on the console. More reason to say: ?????????? > >Tom One very obvious question is, "Is "." in your path"? I have attempted to duplicate your problem here at SGI, but need some more information. Are you logging in to the same account on the console as you are when you telnet in? What do you get after you telnet in and type "echo $path". If "." is in your path, there should be no reason why you cannot execute the files without having to type ./foo If you are still having trouble with this, give the Product Support Group a call. We will resolve this if you can't. Jack Weldon Product Support Engineering
henry@utzoo.uucp (Henry Spencer) (01/16/90)
In article <2738@odin.SGI.COM> jweldon@renegade.sgi.com (Jack Weldon) writes: >... What do you get after you telnet in and type >"echo $path". ... One possibility, of course, is "nothing", because he's using the standard shell and getting the path requires "echo $PATH" instead. Just a hint for future reference: not everyone uses csh, so such a request should always be prefaced with "what shell are you using?". (Apologies if this was clear from earlier context, I came in in the middle of this topic.) It's really very annoying to find companies whose software, documentation, or support has a deeply-imbedded assumption that everyone agrees with their preference on which shell to use. Tain't so. -- 1972: Saturn V #15 flight-ready| Henry Spencer at U of Toronto Zoology 1990: birds nesting in engines | uunet!attcan!utzoo!henry henry@zoo.toronto.edu