Re: [[/]] in shell conditionals (was: lvm on raid)
- To: firstname.lastname@example.org
- Subject: Re: [[/]] in shell conditionals (was: lvm on raid)
- From: Colin Watson <email@example.com>
- Date: Wed, 3 Nov 2004 10:56:07 +0000
- Message-id: <[🔎] 20041103105607.GB3432@riva.ucam.org>
- Mail-followup-to: firstname.lastname@example.org
- In-reply-to: <20041028081740.GB28814@cirrus.madduck.net>
- References: <20041020070231.GA26316@daedalus.andrew.net.au> <email@example.com> <20041020110258.GX16415@daedalus.andrew.net.au> <20041020113038.GN5294@mykerinos.kheops.frmug.org> <20041024054728.GB16500@daedalus.andrew.net.au> <20041024181624.GA23836@kitenet.net> <20041024222020.GA24926@daedalus.andrew.net.au> <20041025173605.GA29480@cirrus.madduck.net> <20041025184331.GF24639@riva.ucam.org> <20041028081740.GB28814@cirrus.madduck.net>
On Thu, Oct 28, 2004 at 10:17:40AM +0200, martin f krafft wrote:
> also sprach Colin Watson <firstname.lastname@example.org> [2004.10.25.2043 +0200]:
> > You're on debian-boot at the moment. [[ ... ]] is a bashism, not
> > supported by busybox, and therefore useless in d-i.
> As far as I can tell, [[/]] is POSIX 1003.2 syntax. Therefore, it's
> more like busybox cannot do POSIX.
The POSIX 1003.1-2001 shell specification merely says
The following words may be recognized as reserved words on some
implementations (when none of the characters are quoted), causing
[[ ]] function select
http://www.opengroup.org/austin/papers/posix_faq.html says that POSIX
1003.2 has been incorporated into POSIX 1003.1, and so POSIX.2 no longer
exists. The Scope section of 1003.1-2001 agrees.
How did you determine that this was POSIX shell?
Colin Watson [email@example.com]