I'm boycotting FreeBSD until such time as they change the default root shell to ksh or something Bourne compatible. There's just nothing more frustrating then tcsh.
I have not checked lately, but it used to be the case that a lot of things broke if you changed the root shell.
I don't believe you've checked... EVER. There's nothing TO break by changing the root user's login shell.
All the services that start up (eg. crond) are completely ignorant of what root's shell is set to. Services don't go through the process of logging-in as root and then spawning processes... They use the setting and environment they inherited from the rc* scripts, from start-up, while the system was single-user.
Any programs or shell scripts you run once the system is multiuser as root, will be run with whatever interpreter they're set to use with the #! line. They don't know or care what your shell is.
In short, there's practically no way that changing root's login shell to something different could possibly break anything. Now, if you do something stupid, like replace/bin/sh with something else, you'll break the whole damn system, but that's an idiotic mistake, and not how anybody should ever change a user's preferred shell.
tcsh (Score:0)
I'm boycotting FreeBSD until such time as they change the default root shell to ksh or something Bourne compatible. There's just nothing more frustrating then tcsh.
Re: (Score:3)
Seems a stupid reason, because it takes all of 5 minutes to "fix."
Re: (Score:0)
I have not checked lately, but it used to be the case that a lot of things broke if you changed the root shell. Maybe they have fixed that.
As long as it's not bash I'm happy. Bash is terrible, why would you ever use that?
Re:tcsh (Score:2)
I don't believe you've checked... EVER. There's nothing TO break by changing the root user's login shell.
All the services that start up (eg. crond) are completely ignorant of what root's shell is set to. Services don't go through the process of logging-in as root and then spawning processes... They use the setting and environment they inherited from the rc* scripts, from start-up, while the system was single-user.
Any programs or shell scripts you run once the system is multiuser as root, will be run with whatever interpreter they're set to use with the #! line. They don't know or care what your shell is.
In short, there's practically no way that changing root's login shell to something different could possibly break anything. Now, if you do something stupid, like replace /bin/sh with something else, you'll break the whole damn system, but that's an idiotic mistake, and not how anybody should ever change a user's preferred shell.