On Mon, Mar 12, 2012 at 07:51:03PM -, James Johnston wrote:
> I have also noticed this issue; again it was with the XML serialization
> functions like Andres Martinelli originally noted. The root of the problem
> is that Windows environment variables are not case sensitive, while they
> *ar
I have also noticed this issue; again it was with the XML serialization
functions like Andres Martinelli originally noted. The root of the problem is
that Windows environment variables are not case sensitive, while they *are* in
a Unix environment. Cygwin passes an environment block with dupli
On Mon, Mar 05, 2012 at 09:37:50AM -0700, Eric Blake wrote:
> On 03/05/2012 07:13 AM, Nellis, Kenneth wrote:
> > From: Corinna Vinschen
> > > Thanks for the review. Like this?
> > If you're open to improvements, the form
> > x=$(($x + 1))
> > could arguably be improved with any of the followin
On 03/05/2012 07:13 AM, Nellis, Kenneth wrote:
> From: Corinna Vinschen
>
>> Thanks for the review. Like this?
>
> If you're open to improvements, the form
> x=$(($x + 1))
> could arguably be improved with any of the following:
> x=$((x + 1))
Still POSIX, and supported by /bin/sh (e
On Mar 5 08:13, Nellis, Kenneth wrote:
> From: Corinna Vinschen
>
> > Thanks for the review. Like this?
>
> If you're open to improvements, the form
> x=$(($x + 1))
> could arguably be improved with any of the following:
> x=$((x + 1))
> let x=x+1
> ((x=x+1))
> ((x
From: Corinna Vinschen
> Thanks for the review. Like this?
If you're open to improvements, the form
x=$(($x + 1))
could arguably be improved with any of the following:
x=$((x + 1))
let x=x+1
((x=x+1))
((x++))
((++x))
--Ken Nellis
On Fri, Mar 02, 2012 at 11:46:05AM +0100, Corinna Vinschen wrote:
> On Mar 1 11:08, Corinna Vinschen wrote:
> > # Fix a problem introduced by older versions of setup.exe
> > [...]
>
> David, ping? Can we add the below two files to base-files asap and
> remove the tmp/temp workaround, please?
On 03/02/2012 05:41 AM, Corinna Vinschen wrote:
> On Mar 2 04:59, Eric Blake wrote:
>> On 03/02/2012 03:46 AM, Corinna Vinschen wrote:
>>> /etc/profile.d/1777fix.sh:
>>>
>>> #!/bin/bash
>>
>> As long as we're requiring bash,...
>> [...]
>
> Thanks for the review. Like this?
Yes, looks better
On Mar 2 04:59, Eric Blake wrote:
> On 03/02/2012 03:46 AM, Corinna Vinschen wrote:
> > /etc/profile.d/1777fix.sh:
> >
> > #!/bin/bash
>
> As long as we're requiring bash,...
> [...]
> > if getfacl "${file}" | grep -Eq 'default:(group:|other):rwx'
>
> Is it worth converting this to case
On 03/02/2012 03:46 AM, Corinna Vinschen wrote:
> On Mar 1 11:08, Corinna Vinschen wrote:
>> # Fix a problem introduced by older versions of setup.exe
>> [...]
>
> David, ping? Can we add the below two files to base-files asap and
> remove the tmp/temp workaround, please?
>
> /etc/profile.d
On Mar 1 11:08, Corinna Vinschen wrote:
> # Fix a problem introduced by older versions of setup.exe
> [...]
David, ping? Can we add the below two files to base-files asap and
remove the tmp/temp workaround, please?
/etc/profile.d/1777fix.csh:
#!/bin/tcsh
# Fix a problem introduced by o
"Corinna Vinschen" wrote news:
> On Mar 1 10:16, Matt Seitz (matseitz) wrote:
> >
> > Here's another thought: is the problem only with the "/home"
directory
> > that Cygwin setup creates (ex: /cygdrive/c/cygwin/home)? If so,
would
> > it be possible to only modify that original "/home" director
On Mar 1 10:16, Matt Seitz (matseitz) wrote:
> "Corinna Vinschen" wrote:
> >
> > Maybe it's better if the code tests the permissions first, along these
> > lines:
>
> Thanks. I would feel better with a solution that doesn't change my
> permissions if they don't really need to be changed.
>
> H
"Corinna Vinschen" wrote:
>
> Maybe it's better if the code tests the permissions first, along these
> lines:
Thanks. I would feel better with a solution that doesn't change my
permissions if they don't really need to be changed.
Here's another thought: is the problem only with the "/home" dir
On Feb 29 13:36, Matt Seitz (matseitz) wrote:
> "Corinna Vinschen" wrote:
> > setfacl -m d:g::r-x,d:o:r-x /home /tmp /usr/tmp /var/log /var/run
> /var/tmp 2>/dev/null
>
> Will that cause problems if I have:
>
> $ mount | grep home
> C:/Documents and Settings on /home type ntfs (binary)
> $ getf
"Corinna Vinschen" wrote:
>
> David, instead of setting tmp/temp, What about adding the following
line
> to /etc/profile?
>
> setfacl -m d:g::r-x,d:o:r-x /home /tmp /usr/tmp /var/log /var/run
/var/tmp 2>/dev/null
Will that cause problems if I have:
$ mount | grep home
C:/Documents and Setting
On Feb 29 07:39, Earnie Boyd wrote:
> On Wed, Feb 29, 2012 at 7:22 AM, Andrey Repin wrote:
> >
> > %SystemRoot%/Temp then ?
> >
>
> This isn't guaranteed to exist.
And it wouldn't change anything. It all depends on a safe ACL setting
one way or the other.
Corinna
--
Corinna Vinschen
On Wed, Feb 29, 2012 at 7:22 AM, Andrey Repin wrote:
>
> %SystemRoot%/Temp then ?
>
This isn't guaranteed to exist.
--
Earnie
-- https://sites.google.com/site/earnieboyd
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation:
Greetings, Corinna Vinschen!
>> > Dead on, thanks! The definitions of tmp and temp in /etc/profile result
>> > in a double definition of the %TMP% and %TEMP% dos variables from the
>> > .Net applications POV and it's too dumb to handle that gracefully.
>>
>> > So the solution is, either we drop
On Feb 29 02:51, Andrey Repin wrote:
> Greetings, Corinna Vinschen!
>
> > Dead on, thanks! The definitions of tmp and temp in /etc/profile result
> > in a double definition of the %TMP% and %TEMP% dos variables from the
> > .Net applications POV and it's too dumb to handle that gracefully.
>
> >
On Feb 28 22:41, Corinna Vinschen wrote:
> The culprit is setup.exe apparently. If it sets 1777 permissions, it
> uses the same permissions for the inheritable default permissions. It
> should remove the write bits before creating the inheritable default
> permissions. In Cygwin this is controll
Greetings, Corinna Vinschen!
> Dead on, thanks! The definitions of tmp and temp in /etc/profile result
> in a double definition of the %TMP% and %TEMP% dos variables from the
> .Net applications POV and it's too dumb to handle that gracefully.
> So the solution is, either we drop the tmp and tem
On Feb 28 21:39, David Sastre Medina wrote:
> On Tue, Feb 28, 2012 at 03:17:54PM +0100, Corinna Vinschen wrote:
> > On Feb 28 08:51, Jon Clugston wrote:
> > > Just a guess, but it does look suspiciously like the name of an
> > > environment variable. Wasn't there some discussion lately about
> > >
On Tue, Feb 28, 2012 at 03:17:54PM +0100, Corinna Vinschen wrote:
> On Feb 28 08:51, Jon Clugston wrote:
> > Just a guess, but it does look suspiciously like the name of an
> > environment variable. Wasn't there some discussion lately about
> > differing case environment variables ("tmp" as oppose
On Feb 28 08:51, Jon Clugston wrote:
> On Tue, Feb 28, 2012 at 7:56 AM, Corinna Vinschen wrote:
>
>
> > The problem is that I have not the faintest insight into .Net. This is
> > an application written in a language I don't know, using a class library
> > I don't know, using a compiler I don't k
On Tue, Feb 28, 2012 at 7:56 AM, Corinna Vinschen wrote:
> The problem is that I have not the faintest insight into .Net. This is
> an application written in a language I don't know, using a class library
> I don't know, using a compiler I don't know. And the executable isn't
> even a Cygwin ap
On Feb 27 16:23, Andres Martinelli wrote:
> Hi Cygwin,
>
> Many .Net programs that use to run correctly from a cygwin 1.7.9
> console started throwing exceptions after updating to versions
> 1.7.10/1.7.11. I have noticed this problem on machines running
> Windows XP and Vista (32bits).
>
> I atta
Hi Cygwin,
Many .Net programs that use to run correctly from a cygwin 1.7.9 console
started throwing exceptions after updating to versions 1.7.10/1.7.11. I
have noticed this problem on machines running Windows XP and Vista (32bits).
I attach a very small example that triggers the bug. The exa
Hi Cygwin,
Many .Net programs that use to run correctly from a cygwin 1.7.9 console
started throwing exceptions after updating to versions 1.7.10/1.7.11. I
have noticed this problem on machines running Windows XP and Vista (32bits).
I attach a very small example that triggers the bug. The exa
29 matches
Mail list logo
