[JCB]

When I start my terminal, I get the following:
Last login: Wed Jan 5 12:02:36 on console
Welcome to Darwin!
tcsh: /sw/bin/init.csh: No such file or directory.
[Jeremie-Barber:~] jeremie%

Do I have a problem? Why do I get:
tcsh: /sw/bin/init.csh: No such file or directory. ?

[Eugene]

Why? Because Fink sucks.

[Wickers]

Well I am guessing that it is looking for that file to run on startup of the shell. . . just like a .bashrc file if the shell was bash. Why not just create a text file in it's place that says something to the effect of:

echo -----Type 'exit' to quit-----

or whatever... even just creating to file should remove the error. (echo > /sw/bin/init.csh)...

[Brad]

Originally Posted by Eugene Why? Because Fink sucks.

I Eugene.

[JCB]

Thanks Vickes. I will give it a try.

[JCB]

I made a file called init.csh, but I still get the original error. How do I get tcsh link to it? Also there is a file already in my home directory called .cshrc . It is not a directory, and if I use the commands more or cat to try and read it, I get: source /sw/bin/init.csh . It looks like tcsh is using that file, and it looks like it is linked to /sw/bin/init.csh . I looked under root (/) for the /sw directory, but it does not exist (by terminal or finder). If I do eventually get the new init.csh file working, will I lose any of my current settings? Any help would be appreciated. Thanks

When the shell starts, it is reading that .cshrc file and thus looking for that /sw/bin/init.csh. Now, I don't know if that file should exist on your machine, but if you just want to get by the message, edit the .cshrc file and add a # in front of that line like:

# source /sw/bin/init.csh

This makes it into a comment which is ignored when the shell starts.

You could, of course, just delete the line...but it is often unwise to destroy such information in case that you really should have a certain file at that location.

[Wickers]

Yah, that would work too...

Good luck! I wish I could help more, but I'm a bash/linux guy, and it would be all guess-work.

As I see it... bash it if that's your thing, if not, there are many other choices out there... zsh seems like a neat example. I just wish my tcsh/unix skills were better, they will be in time but that time is not now.

lates