On 11 March 2011 19:36, David Sastre wrote:
>> David, any problem to create tmp.sh and tmp.csh in profile.d for this
>> purpose?
>>
>> Anyway, after that change it's really time to start using the new
>> base-files package. It's pending already too long, IMHO.
>
> I've been thinking about this, an
On Thu, Mar 10, 2011 at 10:17:08AM +0100, Corinna Vinschen wrote:
> On Mar 9 20:29, Thomas Wolff wrote:
> > Am 09.03.2011 10:26, schrieb Corinna Vinschen:
> > >That's certainly feasible in some way, but I don't understand what
> > >you're trying to accomplish. In what situation would this have to
Am 10.03.2011 15:40, schrieb Jon TURNEY:
On 09/03/2011 19:29, Thomas Wolff wrote:
For example if cygwin is still installed on a FAT drive (I know ...) it may be
useful (for all users) to switch /tmp to an NTFS directory (e.g. XWin used to
fail with a FAT /tmp for a while).
This is wrong on seve
On 09/03/2011 19:29, Thomas Wolff wrote:
> For example if cygwin is still installed on a FAT drive (I know ...) it may be
> useful (for all users) to switch /tmp to an NTFS directory (e.g. XWin used to
> fail with a FAT /tmp for a while).
This is wrong on several counts.
XWin still fails with /tm
On Mar 9 20:29, Thomas Wolff wrote:
> Am 09.03.2011 10:26, schrieb Corinna Vinschen:
> >That's certainly feasible in some way, but I don't understand what
> >you're trying to accomplish. In what situation would this have to be
> >changed on a per-system level? Why isn't it sufficient that the
>
Am 09.03.2011 10:26, schrieb Corinna Vinschen:
On Mar 9 08:25, Andy Koppe wrote:
On 8 March 2011 15:03, Andy Koppe wrote:
On Mar 8 13:49, David Sastre wrote:
2011/3/8, Chris Sutcliffe wrote:
FWIW, I'd prefer to keep the unsetting of TEMP/TMP in ~/.bashrc (i.e.
based on user preference) vs.
On 9 March 2011 10:33, Corinna Vinschen wrote:
> On Mar 9 09:46, Andy Koppe wrote:
>> On 9 March 2011 09:26, Corinna Vinschen wrote:
>> > On Mar 9 08:25, Andy Koppe wrote:
>> >> >> On Mar 8 13:49, David Sastre wrote:
>> >> >>> if TMP/TEMP has to be unset, or set to /tmp per default, or any
>> >>
On Mar 9 09:46, Andy Koppe wrote:
> On 9 March 2011 09:26, Corinna Vinschen wrote:
> > On Mar 9 08:25, Andy Koppe wrote:
> >> >> On Mar 8 13:49, David Sastre wrote:
> >> >>> if TMP/TEMP has to be unset, or set to /tmp per default, or any
> >> >>> other default
> >> >>> decided here, that is some
On 9 March 2011 09:26, Corinna Vinschen wrote:
> On Mar 9 08:25, Andy Koppe wrote:
>> >> On Mar 8 13:49, David Sastre wrote:
>> >>> if TMP/TEMP has to be unset, or set to /tmp per default, or any
>> >>> other default
>> >>> decided here, that is something to be done in /etc/profile, IMHO.
>>
>> O
On Mar 9 08:25, Andy Koppe wrote:
> On 8 March 2011 15:03, Andy Koppe wrote:
> >> On Mar 8 13:49, David Sastre wrote:
> >>> 2011/3/8, Chris Sutcliffe wrote:
> >>> > FWIW, I'd prefer to keep the unsetting of TEMP/TMP in ~/.bashrc (i.e.
> >>> > based on user preference) vs. /etc/profile, since I ha
On 8 March 2011 15:03, Andy Koppe wrote:
>> On Mar 8 13:49, David Sastre wrote:
>>> 2011/3/8, Chris Sutcliffe wrote:
>>> > FWIW, I'd prefer to keep the unsetting of TEMP/TMP in ~/.bashrc (i.e.
>>> > based on user preference) vs. /etc/profile, since I have multiple
>>> > accounts on one of my machi
> On Mar 8 13:49, David Sastre wrote:
>> 2011/3/8, Chris Sutcliffe wrote:
>> > FWIW, I'd prefer to keep the unsetting of TEMP/TMP in ~/.bashrc (i.e.
>> > based on user preference) vs. /etc/profile, since I have multiple
>> > accounts on one of my machines and with my 'work' account, if I
>> > cygs
On Mar 8 13:49, David Sastre wrote:
> 2011/3/8, Chris Sutcliffe wrote:
> > FWIW, I'd prefer to keep the unsetting of TEMP/TMP in ~/.bashrc (i.e.
> > based on user preference) vs. /etc/profile, since I have multiple
> > accounts on one of my machines and with my 'work' account, if I
> > cygstart se
2011/3/8, Chris Sutcliffe wrote:
> On 7 March 2011 17:46, Andy Koppe wrote:
>> On 7 March 2011 22:13, Ken Brown wrote:
>>> On 3/7/2011 8:42 AM, Andy Koppe wrote:
In the current 3.9-3, TEMP and TMP are unset in ~/.bashrc, as
suggested here by Corinna. Thing is, ~/.bashrc is only sourced fo
On 8 March 2011 12:06, Chris Sutcliffe wrote:
> On 7 March 2011 17:46, Andy Koppe wrote:
>> On 7 March 2011 22:13, Ken Brown wrote:
>>> On 3/7/2011 8:42 AM, Andy Koppe wrote:
In the current 3.9-3, TEMP and TMP are unset in ~/.bashrc, as
suggested here by Corinna. Thing is, ~/.bashrc is on
On 7 March 2011 17:46, Andy Koppe wrote:
> On 7 March 2011 22:13, Ken Brown wrote:
>> On 3/7/2011 8:42 AM, Andy Koppe wrote:
>>> In the current 3.9-3, TEMP and TMP are unset in ~/.bashrc, as
>>> suggested here by Corinna. Thing is, ~/.bashrc is only sourced for
>>> non-login shells, yet the default
On 7 March 2011 22:48, Thomas Wolff wrote:
> Indeed. But a question emerges: what does it happen if one starts a
> Windows
> application, which needs TEMP or TMP, from Cygwin?
>
> A Windows application is likely to fail on cygpath-transformed values of
> TEMP and TMP anyway, or am I mis
Just commenting on one aspects:
On Mon, Nov 30, 2009 at 6:37 PM, Angelo Graziosi wrote:
...
Ken Brown wrote:
That's precisely why I suggested unsetting TEMP and TMP in /etc/profile.
Then things should work as in linux.
Indeed. But a question emerges: what does it happen if one starts a Windows
On 7 March 2011 22:13, Ken Brown wrote:
> On 3/7/2011 8:42 AM, Andy Koppe wrote:
>> In the current 3.9-3, TEMP and TMP are unset in ~/.bashrc, as
>> suggested here by Corinna. Thing is, ~/.bashrc is only sourced for
>> non-login shells, yet the default console/mintty/rxvt shortcuts all
>> invoke ba
On 3/7/2011 8:42 AM, Andy Koppe wrote:
On 1 December 2009 09:15, Corinna Vinschen wrote:
On Nov 30 20:53, Robert Pendell wrote:
On Mon, Nov 30, 2009 at 6:37 PM, Angelo Graziosi wrote:
Robert Pendell wrote:
P.S. - On linux (when I tested) TEMP, TMP, and TMPDIR were not set and
patch defaulted
Just for the record...
Andy Koppe wrote:
Some (badly written) Windows programs expect TEMP and/or TMP to always
be set to a valid directory and will misbehave when they aren't.
[...]
and if
they're unlucky, stuff might even get overwritten.
For Windows native applications, I adopted this s
On 1 December 2009 09:15, Corinna Vinschen wrote:
> On Nov 30 20:53, Robert Pendell wrote:
>> On Mon, Nov 30, 2009 at 6:37 PM, Angelo Graziosi wrote:
>> > Robert Pendell wrote:
>> >>
>> >> P.S. - On linux (when I tested) TEMP, TMP, and TMPDIR were not set and
>> >> patch defaulted to /tmp.
>> >
>>
On Tue, Dec 1, 2009 at 1:03 PM, Christopher Faylor wrote:
> On Tue, Dec 01, 2009 at 11:32:43AM -0500, Robert Pendell wrote:
>>They are not reset but during an strace I discovered that cygwin will
>>internally default to the system defined TEMP if one isn't defined in
>>cygwin. In other words if it
On Tue, Dec 01, 2009 at 11:32:43AM -0500, Robert Pendell wrote:
>They are not reset but during an strace I discovered that cygwin will
>internally default to the system defined TEMP if one isn't defined in
>cygwin. In other words if it has been unset. This is similar to
>linux using /tmp by defau
On Tue, Dec 1, 2009 at 5:44 AM, John Morrison wrote:
> On Tue, December 1, 2009 9:15 am, Corinna Vinschen wrote:
>> On Nov 30 20:53, Robert Pendell wrote:
>>> On Mon, Nov 30, 2009 at 6:37 PM, Angelo Graziosi
>>>wrote:
>>> > Robert Pendell wrote:
>>> >>
>>> >> P.S. - On linux (when I tested) TEMP, T
On Dec 1 14:24, Angelo Graziosi wrote:
> Ken Brown wrote:
> >Here's one possibility, but it may be a little too verbose:
>
> Melius abundare quam deficere!
>
> I want just to flag that in the next release of base-files package,
> one should remove '/usr/X11R6/bin' from the definition of PATH. Bu
On Dec 1 08:12, Ken Brown wrote:
> On 12/1/2009 5:44 AM, John Morrison wrote:
> >They don't get 'reset' to the windows default... but then, I've not really
> >been following this thread. Is that what's wanted?
>
> No, they're not expected to get reset.
>
> >Also, $PATCH and $TMPDIR weren't defi
2009/12/1 Ken Brown:
> On 12/1/2009 5:44 AM, John Morrison wrote:
>> Unsetting them in the skel .bashrc files shouldn't be a problem to do, but
>> on my system...
>>
>> $ echo $TMP
>> /cygdrive/c/DOCUME~1/morrijr/LOCALS~1/Temp
>>
>> Tue Dec 01 10:40 AM
>> $ unset TMP
>>
>> Tue Dec 01 10:40 AM
>> $
Ken Brown wrote:
Here's one possibility, but it may be a little too verbose:
Melius abundare quam deficere!
I want just to flag that in the next release of base-files package, one
should remove '/usr/X11R6/bin' from the definition of PATH. But,
perhaps, this is already in John's ToDo list. :
On 12/1/2009 5:44 AM, John Morrison wrote:
On Tue, December 1, 2009 9:15 am, Corinna Vinschen wrote:
I'm wondering if /etc/profile is actually the right place for unsetting
TMP and TEMP. What about etc/defaults/etc/skel/.bashrc instead? It
allows every user simple access to the setting of TMP
On Tue, December 1, 2009 9:15 am, Corinna Vinschen wrote:
> On Nov 30 20:53, Robert Pendell wrote:
>> On Mon, Nov 30, 2009 at 6:37 PM, Angelo Graziosi
>> wrote:
>> > Robert Pendell wrote:
>> >>
>> >> P.S. - On linux (when I tested) TEMP, TMP, and TMPDIR were not set
>> and
>> >> patch defaulted to
On Nov 30 20:53, Robert Pendell wrote:
> On Mon, Nov 30, 2009 at 6:37 PM, Angelo Graziosi
> wrote:
> > Robert Pendell wrote:
> >>
> >> P.S. - On linux (when I tested) TEMP, TMP, and TMPDIR were not set and
> >> patch defaulted to /tmp.
> >
> > I noticed that too...
> >
> > Ken Brown wrote:
> >>
>
On Mon, Nov 30, 2009 at 6:37 PM, Angelo Graziosi
wrote:
> Robert Pendell wrote:
>>
>> P.S. - On linux (when I tested) TEMP, TMP, and TMPDIR were not set and
>> patch defaulted to /tmp.
>
> I noticed that too...
>
> Ken Brown wrote:
>>
>> That's precisely why I suggested unsetting TEMP and TMP in /
Robert Pendell wrote:
P.S. - On linux (when I tested) TEMP, TMP, and TMPDIR were not set and
patch defaulted to /tmp.
I noticed that too...
Ken Brown wrote:
That's precisely why I suggested unsetting TEMP and TMP in /etc/profile. Then
things should work as in linux.
Indeed. But a question
Robert Pendell wrote:
> Is there a reason for not using the cygwin /tmp folder by default?
Dunno. I can't think of a good reason for it but that doesn't mean there
isn't one.
cheers,
DaveK
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwi
On Mon, Nov 30, 2009 at 12:11 PM, Dave Korn
wrote:
> Ken Brown wrote:
>> On 11/30/2009 11:23 AM, Robert Pendell wrote:
>
>>> I guess a side question here is if TMP does not exist then should it
>>> be defaulting to the system wide TEMP variable, the one defined in
>>> .bashrc for the user or shoul
On Mon, Nov 30, 2009 at 11:50 AM, Ken Brown wrote:
> On 11/30/2009 11:23 AM, Robert Pendell wrote:
>>>
>>> Ken Brown wrote:
Nevertheless, it's somewhat startling to see permissions change as a
side
effect of patching a file. One simple way to prevent this is to unset
TMP
>>
Ken Brown wrote:
> On 11/30/2009 11:23 AM, Robert Pendell wrote:
>> I guess a side question here is if TMP does not exist then should it
>> be defaulting to the system wide TEMP variable, the one defined in
>> .bashrc for the user or should it even be created at all? I posted an
>> strace and it
On 11/30/2009 11:23 AM, Robert Pendell wrote:
Ken Brown wrote:
Nevertheless, it's somewhat startling to see permissions change as a side
effect of patching a file. One simple way to prevent this is to unset TMP
and TEMP in /etc/profile. Is there any downside to doing this? A search of
the mailin
On Mon, Nov 30, 2009 at 8:40 AM, Angelo Graziosi wrote:
> Ken Brown wrote:
>>
>> Nevertheless, it's somewhat startling to see permissions change as a side
>> effect of patching a file. One simple way to prevent this is to unset TMP
>> and TEMP in /etc/profile. Is there any downside to doing this? A
Ken Brown wrote:
Nevertheless, it's somewhat startling to see permissions change as a side
effect of patching a file. One simple way to prevent this is to unset TMP and
TEMP in /etc/profile. Is there any downside to doing this? A search of the
mailing list archives shows that the default /etc/
On Nov 30 07:31, Ken Brown wrote:
> On 11/30/2009 4:43 AM, Corinna Vinschen wrote:
> >On Nov 29 18:22, Robert Pendell wrote:
> >>On Sun, Nov 29, 2009 at 5:41 PM, Angelo Graziosi wrote:
> >>>Ken Brown wrote:
> I just confirmed this on my XP SP3 system. I initially got similar
> behavior to w
On 11/30/2009 4:43 AM, Corinna Vinschen wrote:
On Nov 29 18:22, Robert Pendell wrote:
On Sun, Nov 29, 2009 at 5:41 PM, Angelo Graziosi wrote:
Ken Brown wrote:
I just confirmed this on my XP SP3 system. I initially got similar
behavior to what Angelo and Robert reported, but it doesn't happen i
On Nov 29 18:22, Robert Pendell wrote:
> On Sun, Nov 29, 2009 at 5:41 PM, Angelo Graziosi wrote:
> > Ken Brown wrote:
> >>
> >> I just confirmed this on my XP SP3 system. I initially got similar
> >> behavior to what Angelo and Robert reported, but it doesn't happen if I
> >> export TMPDIR=/tmp bef
Ken Brown wrote:
I just confirmed this on my XP SP3 system. I initially got similar behavior to
what Angelo and Robert reported, but it doesn't happen if I export TMPDIR=/tmp
before running patch.
Indeed!
On my system TMPDIR isn't defined by default; instead TMP and TEMP point
to $USERPROFI
On Sun, Nov 29, 2009 at 3:48 PM, Ken Brown wrote:
> On 11/29/2009 3:19 PM, Ken Brown wrote:
>>
>> On 11/29/2009 2:59 PM, Robert Pendell wrote:
>>>
>>> On Sun, Nov 29, 2009 at 9:32 AM, Corinna Vinschen wrote:
On Nov 28 19:12, Robert Pendell wrote:
>
> On Sat, Nov 28, 2009 at 12:13
On 11/29/2009 3:19 PM, Ken Brown wrote:
On 11/29/2009 2:59 PM, Robert Pendell wrote:
On Sun, Nov 29, 2009 at 9:32 AM, Corinna Vinschen wrote:
On Nov 28 19:12, Robert Pendell wrote:
On Sat, Nov 28, 2009 at 12:13 PM, Angelo Graziosi wrote:
Corinna Vinschen wrote:
Fixes a few last-minute bugs:
On 11/29/2009 2:59 PM, Robert Pendell wrote:
On Sun, Nov 29, 2009 at 9:32 AM, Corinna Vinschen wrote:
On Nov 28 19:12, Robert Pendell wrote:
On Sat, Nov 28, 2009 at 12:13 PM, Angelo Graziosi wrote:
Corinna Vinschen wrote:
Fixes a few last-minute bugs:
Now, it seems that creating directories
On Sun, Nov 29, 2009 at 9:32 AM, Corinna Vinschen wrote:
> On Nov 28 19:12, Robert Pendell wrote:
>> On Sat, Nov 28, 2009 at 12:13 PM, Angelo Graziosi wrote:
>> >
>> > Corinna Vinschen wrote:
>> >>
>> >> Fixes a few last-minute bugs:
>> >
>> > Now, it seems that creating directories and files in so
Corinna Vinschen wrote:
Therefore I put them
back in -63.
Hum... This is strange. I always upgrade after reading your
announcements, and never noticed this behavior. It seems that it starts
from 24-25 November 2009.
Any way, thanks for clarification.
Apart from that, I don't see the extra
On Nov 28 19:12, Robert Pendell wrote:
> On Sat, Nov 28, 2009 at 12:13 PM, Angelo Graziosi wrote:
> >
> > Corinna Vinschen wrote:
> >>
> >> Fixes a few last-minute bugs:
> >
> > Now, it seems that creating directories and files in some manner acquires
> > an extra unexpected '+' flag. For example
Hi,
Corinna Vinschen wrote:
> - Fix a potential stack corruption in stat() which only occurs
> on filesystems not supporting security (FAT, FAT32). See
> http://cygwin.com/ml/cygwin/2009-11/msg00881.html
it seems to me that the recent patch in stat() for 1.7.0-67 actually fixed the
problem re
On Sat, Nov 28, 2009 at 12:13 PM, Angelo Graziosi wrote:
>
> Corinna Vinschen wrote:
>>
>> Fixes a few last-minute bugs:
>
> Now, it seems that creating directories and files in some manner acquires an
> extra unexpected '+' flag. For example (from Cygwin.bat or MinTTY):
>
>
> $ echo "Not " > foo1
Corinna Vinschen wrote:
Fixes a few last-minute bugs:
Now, it seems that creating directories and files in some manner
acquires an extra unexpected '+' flag. For example (from Cygwin.bat or
MinTTY):
$ echo "Not " > foo1.txt
$ echo "Not OK" > foo2.txt
$ diff -Naur foo1.txt foo2.txt > foo.
Hi folks,
I just uploaded a new Cygwin 1.7 test release, 1.7.0-67.
Fixes a few last-minute bugs:
Bugfixes in relation to 1.7.0-66:
=
- Fix a potential stack corruption in stat() which only occurs
on filesystems not supporting security (FAT, FAT32). See
htt
55 matches
Mail list logo
