From: Chris Sutcliffe <ir0nh34d@gmail.com>
To: Cygwin-apps <cygwin-apps@cygwin.com>
Subject: Re: [RFC] /etc/shells management (fish, mksh, posh, tcsh, zsh)
Date: Fri, 13 May 2016 14:30:00 -0000 [thread overview]
Message-ID: <CAGHJv4fGBjCvYd83kYvrbHrnjO6cqz+ENQ-Vy_t5NAmamK6nYA@mail.gmail.com> (raw)
In-Reply-To: <923ajbhksgtuiu12fktfsliguvgjq8e58q@4ax.com>
On 13 May 2016 at 06:29, Andrew Schulman wrote:
>> On 2016-05-11 14:06, Yaakov Selkowitz wrote:
>> > On 2016-05-11 12:09, Andrew Schulman wrote:
>> >>> Am 10.05.2016 um 20:19 schrieb Andrew Schulman:
>> >>>> Achim, can you please add /bin/fish and /usr/bin/fish to /etc/shells in
>> >>>> base-files?
>> >>>
>> AFAICS this should be a two-step process.
>>
>> 1) base-files' default /etc/shells should contain only the shells in a
>> Base install, namely:
>>
>> /bin/sh
>> /bin/ash
>> /bin/bash
>> /bin/dash
>> /usr/bin/sh
>> /usr/bin/ash
>> /usr/bin/bash
>> /usr/bin/dash
>> /sbin/nologin
>
> Yep.
>
>> 2) Then all non-Base shells, namely:
>>
>> fish Andrew Schulman
>> mksh Chris Sutcliffe
>> posh Jari Aalto
>> tcsh Corinna Vinschen
>> zsh Peter A. Castro
>>
>> will bump release adding an update_etc_shells call, per the attached
>> patch, with the path of their shell(s).
>
> Agreed.
I'm fine with this approach as well.
Thanks,
Chris
--
Chris Sutcliffe
prev parent reply other threads:[~2016-05-13 14:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <pe94jbtrjf32qn2u0mbtrful36o1trjguj@4ax.com>
[not found] ` <ngvnm4$tms$1@ger.gmane.org>
[not found] ` <lro6jbph7mumea7qcf0jbdnut23kujk3i4@4ax.com>
[not found] ` <cf899cc5-4267-3f59-478e-b7ba5361e2eb@cygwin.com>
2016-05-12 21:36 ` Yaakov Selkowitz
2016-05-12 21:44 ` Warren Young
2016-05-13 10:29 ` Andrew Schulman
2016-05-13 14:30 ` Chris Sutcliffe [this message]
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=CAGHJv4fGBjCvYd83kYvrbHrnjO6cqz+ENQ-Vy_t5NAmamK6nYA@mail.gmail.com \
--to=ir0nh34d@gmail.com \
--cc=cygwin-apps@cygwin.com \
/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).