Weird behavior after flash install (CDE terminal window doesn't work!)

I installed a Solaris system from a flash archive (Solaris 8 -> Sunblade 150) and it seemed to go fine.  THe main problem is that when I go to a CDE terminal window on the new system and type "ls" I don't get any response...

#pwd
/
#ls
#
#ps -a
#

I tried it in bash and got the same result (my default shell is csh).  I have verified using the file manager app in CDE that there are lots of files there to list and the ls command works if I telnet into the machine from somewhere else (for one user at least, not for others).  Oddly, some commands do yield screen output from CDE terminal like pwd (see above) and df -k.  "ps -a" does not yield any output but it does from a telnet session.  What the heck is going on!!!

Thanks!
dcheestAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

wesly_chenCommented:
Hi,

   Could you do
# env > /tmp/env.txt 2>&1
and post /tmp/env.txt here?

Wesly
0
dcheestAuthor Commented:
I am not at the computer right now.  I'll post as soon as I can...
0
dcheestAuthor Commented:
DISPLAY=:0.0
DTAPPSEARCHPATH=//.dt/appmanager:/usr/dt/appconfig/appmanager/%L:/usr/dt/appconf
ig/appmanager/C
DTDATABASESEARCHPATH=//.dt/types,/usr/dt/appconfig/types/%L,/usr/dt/appconfig/ty
pes/C
DTHELPSEARCHPATH=//.dt/help//%H://.dt/help//%H.sdl://.dt/help//%H.hv://.dt/help/
%H://.dt/help/%H.sdl://.dt/help/%H.hv:/usr/dt/appconfig/help/%L/%H:/usr/dt/appco
nfig/help/%L/%H.sdl:/usr/dt/appconfig/help/%L/%H.hv:/usr/dt/appconfig/help/C/%H:
/usr/dt/appconfig/help/C/%H.sdl:/usr/dt/appconfig/help/C/%H.hv
DTSCREENSAVERLIST=StartDtscreenSwarm StartDtscreenQix     StartDtscreenFlame Sta
rtDtscreenHop StartDtscreenImage StartDtscreenLife     StartDtscreenRotor StartD
tscreenPyro StartDtscreenWorm StartDtscreenBlank
DTSOURCEPROFILE=true
DTXSERVERLOCATION=local
EDITOR=/usr/dt/bin/dtpad
HOME=/
LANG=en_US.ISO8859-1
LC_COLLATE=en_US.ISO8859-1
LC_CTYPE=en_US.ISO8859-1
LC_MESSAGES=C
LC_MONETARY=en_US.ISO8859-1
LC_NUMERIC=en_US.ISO8859-1
LC_TIME=en_US.ISO8859-1  
LOGNAME=root
MAIL=/var/mail/root
MANPATH=/usr/dt/man:/usr/share/man
OPENWINHOME=/usr/openwin
PATH=/usr/sbin:/usr/bin:/usr/dt/bin:/usr/openwin/bin:/bin:/usr/ucb
PWD=/
SESSION_SVR=pcr1
SHELL=/sbin/sh
TERM=dtterm
TERMINAL_EMULATOR=dtterm
TZ=US/Pacific
USER=root
WINDOWID=67108873
XMICONBMSEARCHPATH=//.dt/icons/%B%M.bm://.dt/icons/%B%M.pm://.dt/icons/%B:/usr/d
t/appconfig/icons/%L/%B%M.bm:/usr/dt/appconfig/icons/%L/%B%M.pm:/usr/dt/appconfi
g/icons/%L/%B:/usr/dt/appconfig/icons/C/%B%M.bm:/usr/dt/appconfig/icons/C/%B%M.p
m:/usr/dt/appconfig/icons/C/%B
XMICONSEARCHPATH=//.dt/icons/%B%M.pm://.dt/icons/%B%M.bm://.dt/icons/%B:/usr/dt/
appconfig/icons/%L/%B%M.pm:/usr/dt/appconfig/icons/%L/%B%M.bm:/usr/dt/appconfig/
icons/%L/%B:/usr/dt/appconfig/icons/C/%B%M.pm:/usr/dt/appconfig/icons/C/%B%M.bm:
/usr/dt/appconfig/icons/C/%B
_=/usr/dt/bin/sdt_shell    
dtstart_sessionlogfile=/dev/null
0
Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

wesly_chenCommented:
Is this done in telnet session or console login?
Could you also post the other (env > /tmp/env1.txt 2>&1) for comparison?

Wesly
0
dcheestAuthor Commented:
I ended up finding the answer on my own.  The system weird behavior was caused by the presence of numerous Solaris 6 binaries on the system (including ls, ps, etc.!).  THese existed in the original system probably the result of a botched patch job.  They didn't cause problems in the original system for whatever (slight difference in hardware caused a different manifestation of the problem).
0
dcheestAuthor Commented:
One more thing: the fix was simple, just copy the solaris 8 binaries from the install CD and those commands worked great!
0
wesly_chenCommented:
> weird behavior was caused by the presence of
> numerous Solaris 6 binaries on the system

Glad to hear your problem is resolved.

>copy the solaris 8 binaries from the install CD
However, FRESH (not flash) installation of Solaris 8 will be better to
avoid the trouble later on sinc you have Solaris 8 CD.
Besides, apply the latest recommended pateches from sunsolve.
http://sunsolve.sun.com/

Regards,

Wesly
0
moduloCommented:
PAQed with points refunded (500)

modulo
Community Support Moderator
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Unix OS

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.