From: "Zack Weinberg" <zack@owlfolio.org>
To: "GNU libc development" <libc-alpha@sourceware.org>
Subject: Re: [PATCH] system: Add "--" after "-c" for sh (BZ #28519)
Date: Mon, 27 Mar 2023 15:50:35 -0400 [thread overview]
Message-ID: <e46464a4-4310-4dd4-94e2-1db4536fdb8a@app.fastmail.com> (raw)
In-Reply-To: <CAPBLoAe_VCPNr-Z9v8BQcxV2dRanfv2Gm6YU-NvANQ8VLrzAaQ@mail.gmail.com>
On Mon, Mar 27, 2023, at 3:34 PM, Cristian Rodríguez via Libc-alpha wrote:
> On Mon, Mar 27, 2023 at 3:56 PM Adhemerval Zanella Netto via Libc-
> alpha <libc-alpha@sourceware.org> wrote:
>
>> I am not sure if it should be ok to break such environments, at least
>> there are available shells in some environments.
>
> Isn't a posix compliant shell already required as "/bin/sh" ? if it is
> not in writing..it is already de facto required.
I wouldn't go so far as to say that, _but_ setting a version of the C
shell as /bin/sh is definitely an improper system configuration and will
break tons of other things.
> A lot of work has already been done to get basic components running
> with dash which has strict compliance as goals.
You're thinking about this patch from the wrong end of things; whether
this is a safe change to make is not about other programs that might not
work with _no more than_ the features specified by POSIX for /bin/sh.
Rather, it is a question of whether glibc can safely assume availability
of _all of_ the features specified by POSIX for /bin/sh, in particular
unusual corners of command line option handling.
I think it would be a good idea to test this patch on a system where
/bin/sh is busybox sh, and one where /bin/sh is mksh.
zw
next prev parent reply other threads:[~2023-03-27 19:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-22 18:04 Joe Simmons-Talbott
2023-03-27 18:56 ` Adhemerval Zanella Netto
2023-03-27 19:34 ` Cristian Rodríguez
2023-03-27 19:50 ` Zack Weinberg [this message]
2023-03-27 19:56 ` Adhemerval Zanella Netto
2023-03-27 20:14 ` Cristian Rodríguez
2023-03-28 12:52 ` Joe Simmons-Talbott
2023-03-28 13:02 ` Adhemerval Zanella Netto
2023-03-27 20:12 ` Andreas Schwab
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=e46464a4-4310-4dd4-94e2-1db4536fdb8a@app.fastmail.com \
--to=zack@owlfolio.org \
--cc=libc-alpha@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).