LMAO @ myself

Here it goes:

I like to remotely connect to my homebsd box from the office every day. Specially now that I'm getting used to FreeBSD. Well, I wanted to have colors while in text mode, so I decided to use bash for root. What did I do? I su'ed root, ran chsh, changed the line /bin/sh to /bin/bash, logged out, tried to su again, WRONGO, /bin/bash doesn't exist. LOL While signed on with my regular account, I cd into /bin, did a ls and yep bash was not in there. Good ol' bash is under /usr/local/bin/bash. LOL Now I have to figure out how to recover from this. Otherwise, it's all about reinstalling the OS.

Isn't this a riot!

I'm sure you should be able to reboot to a single user mode or just down to a shell prompt and change the configuratin from there to point to the correct shell path.. Got to love making mistakes.. its so fun to try and fix afterwards..

Thanks trickykid. Someone else also suggested booting into single-user mode. I've yet to try it because I'm at work, but I will stop by my house at lunch time and give it a try.

Sheesh, I felt so stupid yet not mad because I brought it onto myself. Then I just started laughing about it. LOL

Could not swiftly recover from the fsck up! So I ended up reinstalling the whole shebang. I made sure to install the sudo pkg this time around. Oh, and I got colors working with 'csh'.

.cshrc :

setenv CLICOLOR yes
setenv TERM cons25

Woohoo!

I did this with my regular user so with root I just made a symbolic link from /usr/local/bin/bash to /bin/bash. Too bad you didn't have a root logged in on the local machine still.

yeah or at the console log in as root and vipw
edit...