On Mon, 2009-06-01 at 06:45 -0500, Victor Lowther wrote:
> On Mon, 2009-06-01 at 07:15 -0400, David Dillow wrote:
> > On Mon, 2009-06-01 at 06:02 -0500, Victor Lowther wrote:
> > > On Mon, 2009-06-01 at 06:54 -0400, David Dillow wrote:
> > > > On Mon, 2009-06-01 at 04:26 -0500, Victor Lowther wrote:
> > > > > Which editor are you using that highlights bash but not sh correctly?
> > > >
> > > > vim on F10 has different rules for sh and bash -- things like $() and
> > > > ${t%%:*} are lit in red for sh, but they are valid; they don't highlight
> > > > that way if vim sees #!/bin/bash
> > >
> > > Ah, that explains it. I am a fan of the OS with an editor tacked onto
> > > the side.
> >
> > So, ditch the whole shebang at the top? No #!/bin/sh or #!/bin/bash?
>
> All scripts on the initramfs should be POSIX -- #!/bin/sh is another way
> of declaring that for people who haven't R'ed TFM. #!/bin/bash is
> misleading.
I agreed with that, I just wondered if you wanted #!/bin/sh gone as well
for the scripts that are being sourced.
--
To unsubscribe from this list: send the line "unsubscribe initramfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
