From: Tom Rini <trini@kernel.crashing.org>
To: Riley Williams <rhw@infradead.org>
Cc: Justin Hibbits <jrh29@po.cwru.edu>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Michael Elizabeth Chastain <mec@shout.net>
Subject: Re: Patch for Menuconfig script
Date: Mon, 8 Jul 2002 11:18:38 -0700 [thread overview]
Message-ID: <20020708181838.GL695@opus.bloom.county> (raw)
In-Reply-To: <Pine.LNX.4.21.0207081841380.9595-100000@Consulate.UFP.CX>
On Mon, Jul 08, 2002 at 06:44:55PM +0100, Riley Williams wrote:
> Hi Tom.
>
> >>> This is just a patch to the Menuconfig script (can be easily adapted
> >>> to the other ones) that allows you to configure the kernel without
> >>> the requirement of bash (I tested it with ksh, in POSIX-only mode).
> >>> Feel free to flame me :P
>
> >> Does it also work in the case where the current shell is csh or tcsh
> >> (for example)?
>
> > Er.. why wouldn't it?
> > $ head -1 scripts/Menuconfig
> > #! /bin/sh
>
> > So this removes the /bin/sh is not bash test, yes?
>
> Q> # ls -l /bin/sh | tr -s '\t' ' '
> Q> lrwxrwxrwx 1 root root 4 May 7 1999 /bin/sh -> tcsh
> Q> #
>
> You tell me - the above is from one of the systems I regularly use,
> which does not even have bash installed...
So does tcsh work as a POSIX-sh when invoked as /bin/sh ?
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
next prev parent reply other threads:[~2002-07-08 18:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-07 1:05 Patch for Menuconfig script Justin Hibbits
2002-07-07 22:22 ` Riley Williams
2002-07-08 15:14 ` Tom Rini
2002-07-08 15:22 ` Justin R Hibbits
2002-07-08 17:44 ` Riley Williams
2002-07-08 18:18 ` Tom Rini [this message]
2002-07-11 20:06 ` Riley Williams
2002-07-11 20:23 ` Tom Rini
2002-07-08 22:53 ` Keith Owens
2002-07-08 23:27 ` Sanctus Evanidus
2002-07-08 23:40 ` Thunder from the hill
2002-07-10 23:13 ` David Weinehall
2002-07-10 23:40 ` HDD test bench Mukesh Rajan
2002-07-10 23:49 ` Mr. James W. Laferriere
2002-07-11 7:35 ` Patch for Menuconfig script Adrian Bunk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020708181838.GL695@opus.bloom.county \
--to=trini@kernel.crashing.org \
--cc=jrh29@po.cwru.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=mec@shout.net \
--cc=rhw@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox