Problem with xterm-301-1

2014-02-20 Thread Ola Strömfors

Hi,

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.

/bin/ash
/bin/bash
/bin/dash
/bin/sh
/bin/tcsh
/bin/zsh

Regards,
Ola Strömfors

--
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/



Re: Problem with xterm-301-1

2014-02-20 Thread Jim Reisert AD1C
On Thu, Feb 20, 2014 at 10:47 AM, Ola Strömfors wrote:

 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.

I saw the same thing, but only on my home computer running Windows 7
Pro 64-bit, not on my work laptop running Windows 7 Enterprise 64-bit.

I start Xwin this way (i.e. same as Cygwin-X group in Start menu):

C:\Cygwin\bin\run.exe /usr/bin/bash.exe -l -c /usr/bin/startxwin.exe

I don't know why SHELL defined as /bin/sh by default (my entry in the
/etc/passwd file invokes bash).  I could not find a way to change
SHELL before XWin starts.

One way I fixed it was to launch xterm from .XWinrc like this:

xterm  EXEC  xterm -e /bin/bash

instead of this:

xterm  EXEC  xterm -ls

-- 
Jim Reisert AD1C, jjreis...@alum.mit.edu, http://www.ad1c.us

--
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/



RE: Problem with xterm-301-1

2014-02-20 Thread Matt Seitz (matseitz)
 From: Ola Strömfors [mailto:ola.stromf...@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.

From http://invisible-island.net/xterm/xterm.log-contents.html#xterm_301:

Patch #301 - 2014/01/19
only set SHELL environment variable to programs found in /etc/shells (prompted 
by patch/report by Al Poole).


--
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/



Re: Problem with xterm-301-1

2014-02-20 Thread Thomas Dickey
On Thu, Feb 20, 2014 at 11:33:22AM -0700, Jim Reisert AD1C wrote:
 On Thu, Feb 20, 2014 at 10:47 AM, Ola Strömfors wrote:
 
  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.
 
 I saw the same thing, but only on my home computer running Windows 7
 Pro 64-bit, not on my work laptop running Windows 7 Enterprise 64-bit.
 
 I start Xwin this way (i.e. same as Cygwin-X group in Start menu):
 
 C:\Cygwin\bin\run.exe /usr/bin/bash.exe -l -c /usr/bin/startxwin.exe
 
 I don't know why SHELL defined as /bin/sh by default (my entry in the
 /etc/passwd file invokes bash).  I could not find a way to change

That sounds like a case reported Saturday - see

ftp://invisible-island.net/temp/xterm-301a.patch.gz

I have a few other reports on different issues to iron out, and
expect to be ok with #302 sometime next week.

-- 
Thomas E. Dickey dic...@invisible-island.net
http://invisible-island.net
ftp://invisible-island.net


signature.asc
Description: Digital signature


Re: Problem with xterm-301-1

2014-02-20 Thread Thomas Dickey
On Thu, Feb 20, 2014 at 06:45:00PM +, Matt Seitz (matseitz) wrote:
  From: Ola Strömfors [mailto:ola.stromf...@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.
 
 From http://invisible-island.net/xterm/xterm.log-contents.html#xterm_301:
 
 Patch #301 - 2014/01/19
 only set SHELL environment variable to programs found in /etc/shells 
 (prompted by patch/report by Al Poole).

yes.

(whether xterm should use $SHELL incoming is a different issue that I
am reconsidering)

-- 
Thomas E. Dickey dic...@invisible-island.net
http://invisible-island.net
ftp://invisible-island.net


signature.asc
Description: Digital signature