shell question

From: accy guy (accy_guy_at_yahoo.com)
Date: 08/29/03

  • Next message: Me: "SUMMARY: Disksuite metadb replicas on 3310 JBOD" 
    Date: Fri, 29 Aug 2003 02:52:40 -0700 (PDT)
To: sunmanagers@sunmanagers.org

    hi ,
     
     I hv inherited a few Solaris boxes (Solaris 8) and I installed the latest SUNWexplo package(4.1.1) on them . However , when i try to run it ...it returns the foll error and exits
     
     ./explorer[49]: sed: not found
    ./explorer[55]: ksh: not found
    ./explorer[85]: cat: not found
    ./explorer[86]: ps: not found
    ./explorer[86]: grep: not found
    ./explorer[86]: grep: not found
    ./explorer[86]: grep: not found
    ./explorer[86]: wc: not found
    ./explorer[87]: test: argument expected
    Explorer starting.
    ./explorer[32]: date: not found
    ./explorer[32]: uname: not found
    ./explorer[32]: date: not found
    ./explorer[32]: sed: not found
    ./explorer[32]: uname: not found
     
    Root's shell is /sbin/sh which on my boxes are linked to /usr/bin/bash (/usr is not a separate file system ,but is part of / ) .i tried running sh explorer, ksh explorer etc ...still it gives same error . Any idea why this is happening ?
     
    I can think of some workarounds
    1) remove the link to /usr/bin/bash and copy /sbin/sh from another machine running the same OS
    2) change root's shell in /etc/passwd to /bin/ksh .
     
    Just wanted to know if the above workarounds are safe ...or will I land up with a broken system
     
    Thanks
    accy
    Yahoo! SiteBuilder - Free, easy-to-use web site design software
    _______________________________________________
    sunmanagers mailing list
    sunmanagers@sunmanagers.org
    http://www.sunmanagers.org/mailman/listinfo/sunmanagers

  • Next message: Me: "SUMMARY: Disksuite metadb replicas on 3310 JBOD"

    Relevant Pages

    • Re: number of CPUs
      ... With psrinfo you can also grep the number of online CPUs while "uname -X" ...
      (comp.unix.solaris)
    • Re: how to identify 32 vs 64 bit CPU?
      ... AFAIK, uname only tells you what you are running, not what you *could* ... bit capable machine or a 32 bit only machine. ... you're on a 64-bit processor regardless whether it's a 32- or 64-bit OS. ... so you could grep for x86_64 to see if a 64 bit os is in use. ...
      (Fedora)
    • Re: how to identify 32 vs 64 bit CPU?
      ... AFAIK, uname only tells you what you are running, not what you *could* ... bit capable machine or a 32 bit only machine. ... so you could grep for x86_64 to see if a 64 bit os is in use. ... can we be more specific about which uname option would give us that ...
      (Fedora)
    • Re: how to identify 32 vs 64 bit CPU?
      ... If you need more than just x86, ... AFAIK, uname only tells you what you are running, not what you *could* ... RES=`uname -a | grep 64` ... echo -n "operating system on a " ...
      (Fedora)
    • Re: number of CPUs
      ... With psrinfo you can also grep the number of online CPUs while "uname -X" ...
      (comp.unix.solaris)