[SOLVED] Using wildcards in a sed command

jthill · 11-23-2011, 07:11 PM

Code:

/bin/tcsh

And that explains the last puzzle. I just checked: tcsh does history substitution even inside single-quotes. I've never used it, I hear it has other gratuitous inconsistencies.

You're still very new to shells, may I recommend you switch to bash if only to get yourself on a shell most people will unthinkingly presume you're using? It'll be a little different but shouldn't be too hard.

The command to do it is "chsh -s /bin/bash". "cat /etc/shells" to get a list of the options it'll accept on your system if you're curious.

Lokelo · 11-23-2011, 07:20 PM

Thanks for the additional information. I'm not sure if I can actually change the shell on the high performance computer.

Oh, and I think I forgot to answer this before, I log in using putty.

If I start my scripts with /bin/bash I should at least be safe there? It's just the active command lines that run on tcsh?

Code:

[jc167987@login]$ cat /etc/shells
/bin/sh
/bin/bash
/sbin/nologin
/bin/tcsh
/bin/csh
/bin/zsh
/bin/ksh


[jc167987@login]$ chsh -s /bin/bash
chsh: can only change local entries; use ypchsh instead.


[jc167987@login ~]$ ypchsh -s /bin/bash
ypchsh: invalid option -- 's'


[jc167987@login ~]$ ypchsh /bin/bash
Unknown error
ypchsh: unknown user (uid=89649).

jthill · 11-23-2011, 08:25 PM

say 'man ypcsh', it'll tell you how to run it. Seems everyone uses putty, must be at least pretty good. Yes, to the /bin/bash part, from the command line you can also just say bash like "bash myscript", but /bin/bash is explicit for security. I still recommend changing, it won't be long at all before you start composing one-liners at the keyboard because that's pretty much what unix is made for, it's a toolmaker's paradise. He who made kittens put snakes in the grass, natch :-)