[opensuse] Re: Network settings in openSuse

On Tue, 3 Mar 2015 18:33, don fisher wrote:

On 03/03/15 10:24, Michael Foerster wrote:

...

On Tue, 3 Mar 2015 18:09, don fisher wrote:

...

On 03/02/15 17:53, I.Petrov wrote: [snip]

...

I have tried the chsh command with some success. But when I changed root to tcsh I could no longer su into it, nor would yast accept the root passwd. When I changed the root shell back to bash, it all appeared to recover. Any ideas?

Have you tried what happens in a 'bash' root shell, if you use a small group of commands: (presume tcsh is /usr/bin/tcsh) [code] export SHELL=/usr/bin/tcsh; exec /usr/bin/tcsh -l [/code]

If this does not satify you, try ...tcsh -i

If that works for you, edit your "~/.bash_profile" or "~/.bashrc" to end with this commands.

Shrugs, Hack? Yes, but what else is new?

- Yamaban.

Thanks, I had thought of a similar idea. But I was curious why root will not run under tcsh? I like to understand what is going on. Is this just a suse thing? And what is breaking? I have used tcsh for root in my previous life under Fedora, but don't care for that distribution anymore.

AFAIK there are some deeply ingrained bashisms and some other specific shell dependencies that simply do not work with csh/tcsh/ksh/pdksh, ash/sash/dash/bash are working, bash the best. Some of this is historic in the depth of SUSE history, some of this is carelessness from the devs in younger times. For a long time there was no Senior SLE dev member that used something other than bash as root-shell, and such discrepancies have crept in undetected. I'm not pointing at people, just showing how this was possible without being detected long before. There are efforts to reduce bashism in simple shell scripts, but not all scriptlets are caught that way. In some areas this is more a tribulations bordering on exertion than a simple endevour. - Yamaban. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org