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]
Message-ID: <alpine.LNX.1.10.0804301347530.5623@fbirervta.pbzchgretzou.qr>
Date:	Wed, 30 Apr 2008 13:48:02 +0200 (CEST)
From:	Jan Engelhardt <jengelh@...ozas.de>
To:	Willy Tarreau <w@....eu>
cc:	Alexey Dobriyan <adobriyan@...il.com>,
	Mark Rustad <mrustad@...il.com>,
	Sam Ravnborg <sam@...nborg.org>,
	Timur Tabi <timur@...escale.com>,
	Roland Kuhn <rkuhn@....physik.tu-muenchen.de>,
	linux-kernel@...r.kernel.org
Subject: Re: Why use /bin/sh in kernel build system?


On Wednesday 2008-04-30 00:24, 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).

Too bad #!bash does not search $PATH.
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ