linux-kernel - Re: Why use /bin/sh in kernel build system?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 29 Apr 2008 17:40:01 -0500
From:	Timur Tabi <timur@...escale.com>
To:	Willy Tarreau <w@....eu>
CC:	Alexey Dobriyan <adobriyan@...il.com>,
	Mark Rustad <mrustad@...il.com>,
	Sam Ravnborg <sam@...nborg.org>,
	Roland Kuhn <rkuhn@....physik.tu-muenchen.de>,
	linux-kernel@...r.kernel.org, viro@...IV.linux.org.uk
Subject: Re: Why use /bin/sh in kernel build system?

Willy Tarreau wrote:

> Hint: not every joe user may install bash into /bin... That's why we
> see some scripts begin with "/usr/bin/env bash" as there are less
> systems without env in /usr/bin than systems without bash in /bin (or
> at all).

I agree that #!/bin/bash is a bad idea.  I think the easiest, and maybe the
best, approach is to fix shell issue one-by-one.  The one I found was easily
fixed by Al Viro's here-document change.

-- 
Timur Tabi
Linux kernel developer at Freescale
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/