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 workar
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,
> 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.
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 lap
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
Rega
