Craig Sanders <[EMAIL PROTECTED]> writes:
> /bin/sh and /bin/bash are not equivalent. bash is a superset of sh
> functionality. bash behaves differently depending on whether it is
> invoked as sh or as bash (at least the new version 2 does).
>
> bash when invoked as /bin/sh is more posix complian
Carey Evans ([EMAIL PROTECTED]) wrote on 14 March 1997 13:32:
>Here (with gzip 1.2.4-14) the postinst script is for /bin/sh.
>I suspect the problem is the line in /etc/zshenv:
>
>PATH="/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games:."
>
>which means that every time zsh is used, /usr
On Wed, 12 Mar 1997, Steve wrote:
> The problem is that the scripts only work with bash in sh mode and not
> with sh-compatible shells such as ash. Try making /bin/sh a symlink to
> /bin/ash and reboot. You'll get error messages from the startup
So if these script doesn't work with ash nor zsh in
[EMAIL PROTECTED] writes:
[snip]
> The only problem is that some packages, such as gzip, give an error
> in the perl (!!??) postinst script.
Here (with gzip 1.2.4-14) the postinst script is for /bin/sh.
I suspect the problem is the line in /etc/zshenv:
PATH="/usr/local/bin:/usr/bin:/bin:/us
zsh can be used as sh instead of bash for almost everything. I have
two machines here where /bin/sh is a link to /bin/zsh. This makes
apsfilter work. bash gives an error in a pipe, complaining about some
signal. It's a bash bug; with zsh it works. The only problem is that
some packages, such as gzi
Maybe either the scripts are so old that they were never updated when
newer shells besides bash came out, or maybe they assumed that all newer
shells would be bash-compatible, or maybe the people who wrote them are
just stupid :) Not everyone's a genius you know :)
On Wed, 12 Mar 1997, Steve wrot
On Mar 03, 1997 at 01:45:37PM -0800, Steve wrote:
> > I set my system shell to zsh as well, and replaced all the /bin/bash in
> > /etc/passwd to /usr/bin/zsh, but when I tried to move /bin/sh to point to
> > /usr/bin/zsh, all of the /etc/init.d/* scripts blew up.
>
> If those scripts actually requ
> > If those scripts actually require bash then why isn't the first line
> > #!/bin/bash? Is this a bug, or is it written in stone that /bin/sh and
> > /bin/bash are equivalent?
>
> /etc/init.d/* do, in fact, all start with "#!/bin/sh" as they should.
> I believe that bash was written to be a free
On Wed, 12 Mar 1997, Steve wrote:
> > I set my system shell to zsh as well, and replaced all the /bin/bash
> > in /etc/passwd to /usr/bin/zsh, but when I tried to move /bin/sh to
> > point to /usr/bin/zsh, all of the /etc/init.d/* scripts blew up.
>
> If those scripts actually require bash then w
> I set my system shell to zsh as well, and replaced all the /bin/bash in
> /etc/passwd to /usr/bin/zsh, but when I tried to move /bin/sh to point to
> /usr/bin/zsh, all of the /etc/init.d/* scripts blew up.
If those scripts actually require bash then why isn't the first line
#!/bin/bash? Is this
I set my system shell to zsh as well, and replaced all the /bin/bash in
/etc/passwd to /usr/bin/zsh, but when I tried to move /bin/sh to point to
/usr/bin/zsh, all of the /etc/init.d/* scripts blew up. Most of their
scripting is done in bash format, so unless you want to either make zsh
bash-compa
[EMAIL PROTECTED] (James W. Lynch) writes:
> This subject brings up a question I've had for a long time. Bash appears
> to be the shell that I get when I log in as root or do an su command.
> I'm from the old school and prefer vi editing of commands, but I have
> yet to be able to make bash use vi
Here are two ways I know of:
1) echo "set editing-mode vi" >> ~root/.inputrc
2) exec bash -o vi
--Bob
James W. Lynch wrote:
>
> - Received message begins Here -
>
> This subject brings up a question I've had for a long time. Bash appears
> to be the shell that I get when I
Telephone Game! James W. Lynch said (on 08:43 AM 3/11/97 -0500):
->- Received message begins Here -
->
->This subject brings up a question I've had for a long time. Bash appears
->to be the shell that I get when I log in as root or do an su command.
->I'm from the old school and
- Received message begins Here -
This subject brings up a question I've had for a long time. Bash appears
to be the shell that I get when I log in as root or do an su command.
I'm from the old school and perfer vi editing of commands, but I have
yet to be able to make bash use v
On Sat, 8 Mar 1997, Bob Clark wrote:
> This is *not* a flame. This list is kind of touchy lately. It's just
> that I'm a big fan of bash (with vi editting mode instead of emacs) and
> if there's a better shell out there I'd like to give it a try. It just
> doesn't sound like zsh has anything to
Richard Kettlewell <[EMAIL PROTECTED]> writes:
> hosts=(valour cushioned myrddin tacitus chiark \
> mercury.elmailer.net wigwam.elmail.co.uk sunsite.doc.ic.ac.uk \
> ftp.uu.net ftp.sendmail.org tlingit.elmail.co.uk)
> ssh=(chiark)
> compctl -k ssh ssh
> compctl -k hosts
Both are excellent interactive shells.
>* automatic completion on variables names, e.g. type
> "export DISP" and hit tab. (I just checked, in bash you can use
> Esc-$ to specifically complete a variable name; in zsh the default
> compctl (completion) has been setup to complete for a variable
On 8 Mar 1997, Richard Sharman wrote:
[completion control]
> compctl (completion) has been setup to complete for a variable name
> if the command is "export". While the zsh seemed easier, I guess
> the bash approach allows you to control it more.)
I hope that's a typo.. The zsh way is mo
Bob Clark <[EMAIL PROTECTED]> writes:
> This is *not* a flame. This list is kind of touchy lately. It's just
> that I'm a big fan of bash (with vi editting mode instead of emacs) and
> if there's a better shell out there I'd like to give it a try. It just
> doesn't sound like zsh has anything t
This is *not* a flame. This list is kind of touchy lately. It's just
that I'm a big fan of bash (with vi editting mode instead of emacs) and
if there's a better shell out there I'd like to give it a try. It just
doesn't sound like zsh has anything to offer that bash doesn't.
Comments anyone?
21 matches
Mail list logo
