Forget it!
I put the space in the wrong place: "# !/bin/sh", as opposed to
"#! /bin/sh".
I'm really sorry :(
Thanks.
--
H Huang
Joey Hess writes:
> > But how can you explain
> > --
> > #! /bin/ash
> > mkdir -p test/{foo,bar}
> > --
> > does expand the {foo,bar}, while
>
> It doesn't here.
Sorry. It doesn't here either. But try:
-
I can't reproduce that behaviour here (potato with ash 0.3.5-9).
On Thu, Jan 13, 2000 at 12:16:02PM -0800, H Huang wrote:
>
> I've been experimenting using /bin/ash as /bin/sh recently. No big
> problem so far. However, a couple of debian/rules failed to
> build. Further examination shows that:
>
I can't reproduce your results here. With both '#!/bin/ash' and
'#! /bin/ash' I get 'test/{foo,bar}' as a directory. I'll guess that
on your system, the space causes the #! to be ignored and the script
run by your current shell (presumably bash). Try changing your shell to
ash and rerunning
Joey Hess writes:
> > produces one directory under test: test/{usr,bin}
> >
> > Note that /bin/sash also has the same problem, while /bin/bash,
> > /bin/tcsh, and /usr/bin/ksh do not.
> >
> > Any comment?
>
> Yes. {foo,bar} is a bashism. Do not expect
H Huang wrote:
> produces one directory under test: test/{usr,bin}
>
> Note that /bin/sash also has the same problem, while /bin/bash,
> /bin/tcsh, and /usr/bin/ksh do not.
>
> Any comment?
Yes. {foo,bar} is a bashism. Do not expect any shell except bash to expand it.
--
see shy jo
duces two: test/usr and test/bin, which is probably what we want.
Note that /bin/sash also has the same problem, while /bin/bash,
/bin/tcsh, and /usr/bin/ksh do not.
Any comment?
--
H Huang
G'day Raul.
i have sash installed as the root shell i typed exit and it through me out of
myconsole to a login prompt ( well thats ok as i wanted to logout ) But now i
cant login anymore. it tells me its running a restricted shell called exit and
drops me back to the login screen again? i
8 matches
Mail list logo
