Am 12.09.2014 06:13, schrieb Eric Blake:
On 09/11/2014 09:16 PM, Denis Mühle wrote:
Hello,
today i've updated my cygwin and now i have a big problem. the "su"
command was removed.
https://sourceware.org/ml/cygwin/2014-08/msg00245.html
i need "su" to start my services as seperate user,
becau
On Fri, Sep 12, 2014 at 6:24 PM, Eric Blake wrote:
> On 09/12/2014 02:15 PM, Christian Franke wrote:
unsetenv("PATH");
>>> This is undefined behavior, per POSIX. POSIX recommends that you always
>>> leave PATH defined to at least a bare minimum of the results of
>>> confstr(_CS_PATH, ...)
On 9/12/2014 7:12 PM, Björn Kautler wrote:
Hi there,
bash completion completely got broken with bash completion 1.9.
It changed the layout from having the stuff in /etc to having the
stuff in /usr/share/bash-completion
Cygwin's bash-completion is at version 1.3 and puts all of its
non-documen
Dat Head wrote:
I have a symlink from /usr/local/bin to /3TB-external/bin/CYGWIN to keep
architecture independent bin files on an external drive for portability.
I've tried similar and wasn't able to convince anyone (my track
record on being convincing is significantly lamer than mosts')
Hi there,
bash completion completely got broken with bash completion 1.9.
It changed the layout from having the stuff in /etc to having the
stuff in /usr/share/bash-completion
Any existing .bashrc file including the one in /etc/skel do still
reference the old location which is not present anymore
On 09/12/2014 05:03 PM, Eric Blake wrote:
> On 09/12/2014 04:50 PM, Christian Franke wrote:
>> Andrey Repin wrote:
Hmm... is postfix actually broken?
Unsetting PATH is IMO sane (from the POSIX POV) if all exec() calls use
absolute path names.
>>> If all exec() calls are made with ful
On 09/12/2014 04:50 PM, Christian Franke wrote:
> Andrey Repin wrote:
>>> Hmm... is postfix actually broken?
>>> Unsetting PATH is IMO sane (from the POSIX POV) if all exec() calls use
>>> absolute path names.
>> If all exec() calls are made with full paths, unsetting $PATH does not
>> improve
>> s
Andrey Repin wrote:
Hmm... is postfix actually broken?
Unsetting PATH is IMO sane (from the POSIX POV) if all exec() calls use
absolute path names.
If all exec() calls are made with full paths, unsetting $PATH does not improve
security in any way,
Of course. But postfix could be configured to
On 09/12/2014 02:15 PM, Christian Franke wrote:
>>>unsetenv("PATH");
>> This is undefined behavior, per POSIX. POSIX recommends that you always
>> leave PATH defined to at least a bare minimum of the results of
>> confstr(_CS_PATH, ...); it also states that implementations are free to
>> do wh
Ken Brown wrote:
> Maybe I should make that the current release; it does seem to be pretty
> stable.
I've been running it ever since it came out on x86_64 and have seen a
lot less crashes than with the "official" release. I'd love if this
became curr.
--
David Rothenberger daver...@acm.or
Greetings, Christian Franke!
>>> Enabling the SetDllDirectory() Win32 call fixes the problem.
>>> Would possibly make sense to add this call to cygwin1.dll.
>> That said, just because POSIX has already given us the
>> get-out-of-jail-free card doesn't mean that we can't be nice and improve
>> cygw
Greetings, All!
There's a major discrepancy between 32- and 64-bit versions.
https://cygwin.com/cgi-bin2/package-cat.cgi?file=x86%2Ftidy%2Ftidy-041206-1
https://cygwin.com/cgi-bin2/package-cat.cgi?file=x86_64%2Ftidy%2Ftidy-20090325-1
I.e. 64-bit distribution missing /usr/share/doc/Cygwin/$package
On 9/12/2014 5:14 PM, Matthew Cummings wrote:
Hi,
I'm running 64bit Windows 7, a relatively new OS install. I've been
using the 64bit version of Cygwin for about a month now on this
machine, including the emacs that ships with it.
I haven't changed any part of my cygwin/emacs configuration in t
Hi,
I'm running 64bit Windows 7, a relatively new OS install. I've been
using the 64bit version of Cygwin for about a month now on this
machine, including the emacs that ships with it.
I haven't changed any part of my cygwin/emacs configuration in the
past few weeks but starting today, emacs has
Eric Blake wrote:
On 09/12/2014 11:02 AM, Christian Franke wrote:
If PATH variable is unset or does not contain /bin or /usr/bin,
exec("/not_bin/program", ...) fails because cygwin DLLs could not be
loaded.
This affects postfix which cleans the environment to the bare minimum
for security reaso
On 2014-09-08 20:04, Aidan Gauland wrote:
I am trying to run a non-cygwin program in gdb, and when I enter the `run`
command, I get the following error.
Traceback (most recent call last):
File "/usr/share/gdb/auto-load/usr/bin/cyggobject-2.0-0.dll-gdb.py", line
9, in
from gobject import
On 09/12/2014 11:02 AM, Christian Franke wrote:
> If PATH variable is unset or does not contain /bin or /usr/bin,
> exec("/not_bin/program", ...) fails because cygwin DLLs could not be
> loaded.
>
> This affects postfix which cleans the environment to the bare minimum
> for security reasons.
> (fo
On 2014-08-13 09:28, Ken Brown wrote:
I'm getting errors with the latest gdb when trying to debug programs
that depend on glib. Here's an example, run from an xterm window:
$ gdb /usr/bin/gvim
GNU gdb (GDB) 7.8
[...]
Reading symbols from /usr/bin/gvim...(no debugging symbols found)...done.
(gdb
On 9/12/2014 2:02 PM, Ken Brown wrote:
Hi Corinna,
On 8/28/2014 9:57 AM, Corinna Vinschen wrote:
On Aug 13 16:57, Corinna Vinschen wrote:
On Aug 13 10:28, Ken Brown wrote:
I'm getting errors with the latest gdb when trying to debug programs
that
depend on glib. Here's an example, run from an
Hi Corinna,
On 8/28/2014 9:57 AM, Corinna Vinschen wrote:
On Aug 13 16:57, Corinna Vinschen wrote:
On Aug 13 10:28, Ken Brown wrote:
I'm getting errors with the latest gdb when trying to debug programs that
depend on glib. Here's an example, run from an xterm window:
$ gdb /usr/bin/gvim
GNU
If PATH variable is unset or does not contain /bin or /usr/bin,
exec("/not_bin/program", ...) fails because cygwin DLLs could not be loaded.
This affects postfix which cleans the environment to the bare minimum
for security reasons.
(fortunately there is an easy workaround, so this does not blo
A new version of lftp, 4.5.5-1, is available in the Cygwin distribution.
This is a new upstream release, with bug fixes. Please see
http://lftp.yar.ru/news.html for the list of changes.
This release removes the dependency of lftp on perl. lftp comes with a few
sample scripts that are written in
A new version of autossh, 1.4d-1, is available in the Cygwin distribution.
This is a new upstream release, with bug fixes:
* Fixes file descriptor issues when started without standard input
available (for example, in system initialization scripts)
autossh is a program to start an instance of ssh
A new version of stunnel, 5.03-1, is available in the Cygwin distribution.
This is a new upstream release, with assorted minor updates and bug fixes.
You can read the upstream changelog at
https://www.stunnel.org/sdf_ChangeLog.html.
stunnel is a program that allows you to encrypt arbitrary TCP con
Le 12/09/2014 14:21, איציק בק a écrit :
I've read already tremendous amount of articles, tutorials, and
instructions about how to solve my problem - but still - no gain. I
just can't put it into work.
My goal is pretty simple: I want to compile a DLL file using Cygwin
gcc tool, and then use it
I've read already tremendous amount of articles, tutorials, and
instructions about how to solve my problem - but still - no gain. I
just can't put it into work.
My goal is pretty simple: I want to compile a DLL file using Cygwin
gcc tool, and then use it within MSVC2010. I'm actually want to do it
26 matches
Mail list logo
