This is the mail archive of the
mailing list for the Cygwin project.
Re: BUG: cygwin warning: barfs on domain-based-mboxes; env corrupted by login(-p disabled)
- From: Linda Walsh <cygwin at tlinx dot org>
- To: cygwin at cygwin dot com
- Date: Wed, 29 Oct 2014 17:12:12 -0700
- Subject: Re: BUG: cygwin warning: barfs on domain-based-mboxes; env corrupted by login(-p disabled)
- Authentication-results: sourceware.org; auth=none
- References: <544F3313 dot 6050604 at tlinx dot org> <20141028110312 dot GH20607 at calimero dot vinschen dot de> <1107228111 dot 20141029042128 at yandex dot ru>
Andrey Repin wrote:
Greetings, Corinna Vinschen!
The next Cygwin release will have CYGWIN=dosfilewarning set to OFF
If anybody thinks it's really worth to keep this option available
and ON by default, please speak up.
I don't think it's worth the hassle. What little of the programs that is
unable to deal with native paths are printing obvious enough error messages to
convince the user that they should change their habits.
Not that I disagree with Corinna's decision, but Andrey's followup
doesn't necessarily apply (nor is it important in my case).
Bash is testing for the existence of a user's "mbox", in the spool
directory -- it prints no error if it is not found -- I don't know
that it is important that it should as one can [re]set the system mbox
path if they want, in the startup scripts. Just that this mbox
check uses some internally compiled name that is checked before
any user scripts are run.
Still doesn't fix the problem of the ENV being zeroed in 'login'
which triggered this problem in the first place.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple