View Single Post
Old 09-21-2013, 04:03 AM   #46
knc1
Going Viral
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
Quote:
Originally Posted by nasser View Post
there seems to be a difference between logging in through ssh and "logging in" through kterm.. see screenshots..
ssh recognises the "new" home at /home/root..
while the kterm session is still hung up on /tmp/root..
My guess - -
kterm isn't being started in a "login shell" but instead in an "interactive shell".

Check how your copy of kterm is being invoked.
Or -
Start in new shell instance in kterm:
su -l (su - lower case ell)
and then check - -
just be sure to remember to 'exit' both levels of command shell in kterm.
knc1 is offline   Reply With Quote