if a user's login shell is /bin/tcsh, /etc/motd is displayed twice, once by pam_motd (as it should be) and once again by csh.login (rather unusual). To prevent motd from being printed again unless it has changed, csh.login makes a copy(!!!) of /etc/motd in every user's homedir to be able to detect differences to the one in /etc!!! Also, on every login ~/.tcsh.config is created if it doesn't exist. Since the settings in this file cover only a (very) tiny subset of what users usually have in their private .tcshrc, they'll have to have one anyway. Seems more annoying than useful to me. Tcsh users usually know what they're doing and don't need this kind of nonsense! Also, is there a particular reason PATH is in a different order for tcsh users? bash: echo $PATH /bin:/usr/bin:/usr/local/bin:/opt/bin:/usr/i686-pc-linux-gnu/gcc-bin/3.2:\ /usr/X11R6/bin tcsh: echo $PATH /usr/local/bin:/opt/bin:/usr/i686-pc-linux-gnu/gcc-bin/3.2:\ /usr/X11R6/bin:/bin:/usr/bin Positive aspect here, /usr/local/bin comes first as it does on almost every known UN*X system, although /bin and /usr/bin are still in the wrong order (reasoning: you are supposed to be able to override small binaries with reduced functionality in /bin with more full-featured ones in /usr/bin once /usr becomes available, f.ex. small vi (elvis) in /bin; vim (linked to X-libs) in /usr/bin. This way you can repair config files using elvis if /usr is unavailable, and use vim if the system is fully up. With /bin first in PATH, however, this won't work!) Still, regardless of gentoo's PATH policy, I'd even more prefer a uniform PATH for all users regardless of their shell preferences.
note to self: - motd issue resolved - .tcsh.config is now only copied if no .tcshrc exists (allows removal of the file) - fixed path to reflect current bash setting: /usr/local/bin /usr/bin /bin /opt/bin $path
Fixed in 6.14-r1 Redid whole config system, to have much more cleaner defaults which should certainly resolve all the mentioned issues.
