Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'diagnostics' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
diagnostics
Authored by: babbage on Dec 04, '01 11:05:58PM
You're definitely getting the same error that people were talking about a year ago? The file /bin/tcsh has a zero file length? On my system, the /bin directory has four *sh files: csh, sh, tcsh, zsh. All of them have the same time stamp, corresponding to the day I installed the OS. Are you seeing the same timestamp for each file (assuming you can get that far), or if not is tcsh newer perchance? If so, that might point to the date where things went wrong, and that in turn might help you piece together how the shell got hosed.

One method of low level desperation would be to login as ">console" at the login screen. If you're lucky this will try to log you in with whatever shell is available, if you can't set your preferred shell to one of whichever ones remain for you. Similarly, you might be able to get in via "single user mode" -- boot while holding down shift-S (I think, haven't had a reason to use it yet but I think that's right), and this should dump you in as root & hopefully running under /bin/sh.

If you can get to a prompt somehow, and you have some kind of /bin/tcsh file present, you need to analyze it a bit. Try running "file /bin/tcsh", which should tell you "/bin/tcsh: Mach-O executable ppc". If you get nothing, or something else, then the tcsh you installed isn't valid. Copying over a copy from the install disc seems like a good idea, but I've never been through this so...

Let us know more & we can keep trying to help...

[ Reply to This | # ]