public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: "Matt Seitz (matseitz)" <matseitz@cisco.com>
To: "cygwin-xfree@cygwin.com" <cygwin-xfree@cygwin.com>
Cc: "dickey@his.com" <dickey@his.com>
Subject: RE: Problem with xterm-301-1
Date: Thu, 27 Feb 2014 18:06:00 -0000	[thread overview]
Message-ID: <A0DB01D693D8EF439496BC8B037A0AEF33126666@xmb-rcd-x15.cisco.com> (raw)
In-Reply-To: <20140220224047.GC3983@aerie.jexium-island.net>

> From: Thomas Dickey [mailto:dickey@his.com]
> 
> On Thu, Feb 20, 2014 at 06:45:00PM +0000, Matt Seitz (matseitz) wrote:
> > > From: Ola Strömfors [mailto:ola.stromfors@gmail.com]
> > >
> > > After updating from 291-1 to 301-1 xterm starts /bin/sh instead of
> > > my shell specified in /etc/passwd or in the SHELL environment variable.
> > >
> > > The workaround I have found is to create /etc/shells with a list of
> > > permitted shells, e.g.
> >
> 
> (whether xterm should use $SHELL incoming is a different issue that I
> am reconsidering)

Is there any ETA for a resolution of this issue?

I've been holding off on upgrading to xterm-301 because of this issue.  I'm not sure if there is some patch coming soon (either to xterm or adding a default /etc/shells to Cygwin), or if I should just plan on manually creating my own "/etc/shells".


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://x.cygwin.com/docs/
FAQ:                   http://x.cygwin.com/docs/faq/


  reply	other threads:[~2014-02-27 18:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-20 17:47 Ola Strömfors
2014-02-20 18:33 ` Jim Reisert AD1C
2014-02-20 21:58   ` Thomas Dickey
2014-02-20 18:45 ` Matt Seitz (matseitz)
2014-02-20 22:40   ` Thomas Dickey
2014-02-27 18:06     ` Matt Seitz (matseitz) [this message]
2014-02-27 22:00       ` Thomas Dickey
2014-02-28  9:19         ` Corinna Vinschen

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=A0DB01D693D8EF439496BC8B037A0AEF33126666@xmb-rcd-x15.cisco.com \
    --to=matseitz@cisco.com \
    --cc=cygwin-xfree@cygwin.com \
    --cc=dickey@his.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).