On 10/31/05, Aaron <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> I have this strange behaviour that when I open a new term session or
> even in an existing term sesstion I will execute a common command such
> as ls or cd and the shell returns command not found. usually I can close

"cd" command not found?? "cd" is an internal shell command (doesn't make
sense to run it in a separate process). Are you sure that's what happened?

What's your PATH ("echo $PATH")?

> that session and open another and things work again, sometimes I must
> log out and back in  and sometimes (rarely ) that doesn't help.
>
>
> I am using demudi which is debian and this once happened while I was
> having other problems and I was forced to reinstall since I couldn't use
> the command line....

I'd reckon it's a favourite passtime for "real" linux users to try to get out of
any "broken" situation without having to (in degrading order of preferences)
kill-program/exit-shell/logout/kill-xserver (ctrl-backspace)/reboot/reinstall.
I think it's a very instructive experience to try to achieve these
goals (what is
a learned "for fun" one day can come up as a real session-saver on another,
"/usr/bin/reset" might turn out to be more useful than you would
normally expect :).

>
> Any thoughts on what might be causing this very strange behaviour would
> be most appreciated.

Messed up environment (variables), trojans, bad disk blocks, broken packages
installed come up to my mind right now.

Try looking in dmesg(8) and /var/log/messages* for odd kernel messages.

Is this a private personal computer or some public/lab/family box used
by others?

--Amos

================================================================To unsubscribe, 
send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]

Reply via email to