> Ok. I duplicated it. It has to be a share as in //foo/bar, not,
> /foo/bar/blaz. The next snapshot should fix it.
It did! Thanks!
--
Ken Shaffer
- - - - - - - Appended by Scientific-Atlanta, Inc. - - - - - - -
This e-mail and any attachments may contain information which is conf
On Wed, Jun 15, 2005 at 05:41:29PM -0400, Christopher Faylor wrote:
>On Wed, Jun 15, 2005 at 04:22:01PM -0400, Shaffer, Kenneth wrote:
Along similar lines as the ls failure on shares with
CYGWIN=check_case:strict, if /etc/passwd has a home directory set to a
share, bash won't even start
On Wed, Jun 15, 2005 at 04:22:01PM -0400, Shaffer, Kenneth wrote:
>>>Along similar lines as the ls failure on shares with
>>>CYGWIN=check_case:strict, if /etc/passwd has a home directory set to a
>>>share, bash won't even start.
>>
>>WJFFM. There was a problem pre-snapshot but bash still started.
>>Along similar lines as the ls failure on shares with
>>CYGWIN=check_case:strict, if /etc/passwd has a home directory set to a
>>share, bash won't even start.
>
>WJFFM. There was a problem pre-snapshot but bash still started. Now I
>get no errors.
Really? You DID edit your /etc/passwd and chan
On Wed, Jun 15, 2005 at 09:08:40AM -0400, Shaffer, Kenneth wrote:
>Along similar lines as the ls failure on shares with
>CYGWIN=check_case:strict, if /etc/passwd has a home directory set to a
>share, bash won't even start.
WJFFM. There was a problem pre-snapshot but bash still started. Now I
get
Along similar lines as the ls failure on shares with
CYGWIN=check_case:strict, if /etc/passwd has a home directory set to a
share, bash won't even start.
--
Ken Shaffer
- - - - - - - Appended by Scientific-Atlanta, Inc. - - - - - - -
This e-mail and any attachments may contain informat
6 matches
Mail list logo
