On 11/12/2014 3:28 AM, t s wrote:
I have some elementary questions regarding the cygwin setup program. I ran the
latest version 2.852 (64 bit).
wrong mailing list.
Use main one for these questions
the options are install / re-install / un-install / default
my understanding is as follows;
c
The following packages have been updated in the Cygwin distribution:
* libssh2_1-1.4.3-1
* libssh2-devel-1.4.3-1
libssh2 is a library implementing the SSH2 protocol.
This release is an update to the latest upstream release.
--
Yaakov
--
Problem reports: http://cygwin.com/problems.html
F
The following packages have been updated in the Cygwin distribution:
* autogen-5.18.4-1
* libopts25-5.18.4-1
* libopts-devel-5.18.4-1
AutoGen is a tool designed to simplify the creation and maintenance of
programs that contain large amounts of repetitious text. It is
especially valuable in pr
Hello everyone,
I'm just curious, has there been any special focus on performance
improvements in the 64-bit version compared to 32-bit?
I'm asking because I recently upgraded from 32-bit to 64-bit Cygwin, and I
noticed that my bash prompt would show up noticeably quicker when I opened a
new Cygw
On 11/11/2014 12:08 PM, Achim Gratz wrote:
Corinna Vinschen writes:
On Nov 11 10:02, Ken Brown wrote:
Of course, this still doesn't solve the problem of making sure that the
_autorebase postinstall script runs whenever the user installs a package
containing DLLs. I wonder if we should reconsid
On 11/11/2014 4:31 PM, phil rosenberg wrote:
This is discussed in the texlive release announcement
https://cygwin.com/ml/cygwin-announce/2014-07/msg0.html
under the heading "Fontconfig". See also
https://cygwin.com/ml/cygwin-xfree/2014-05/msg00020.html
Yaakov, could we get
>This is discussed in the texlive release announcement
> https://cygwin.com/ml/cygwin-announce/2014-07/msg0.html
>under the heading "Fontconfig". See also
> https://cygwin.com/ml/cygwin-xfree/2014-05/msg00020.html
>Yaakov, could we get a fontconfig update that fixes this?
>Thanks.
>Ke
On 2014-11-11 14:44, Dr. Volker Zell wrote:
Older gnutls versions compiled fine with cygwin. Latest versions come
with their own libopts source tree, which is newer than the latest
cygwin version. I get the following error when trying to compile gnutls-3.2.20
In file included from srptool-args.c
Hi
Older gnutls versions compiled fine with cygwin. Latest versions come
with their own libopts source tree, which is newer than the latest
cygwin version. I get the following error when trying to compile gnutls-3.2.20
In file included from srptool-args.c:43:0:
srptool-args.h:61:3: error: #error
Greetings, Corinna Vinschen!
>> >> > Shall the "db" entries utilize the Windows home folder if it exits(*)
>> >> > and drop using the unixHomeDirectory? It seems inevitable…
>> >>
>> >> Use of AD implies some level of security consciousness. The ability to
>> >> write to c:\cygwin — not just d
Hi
Files from /usr/doc/sitecopy should be installed under
/usr/share/doc/sitecopy
Ciao
Volker
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/m
Hi
Files from /usr/doc/html/docbook-utils-0.6.14/ should probably be
installed into /usr/share/doc/html/docbook-utils
Ciao
Volker
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubs
Greetings, Nellis, Kenneth!
>> From: Achim Gratz
>>
>> Nellis, Kenneth writes:
>> > Jeremy's solution is closest to what I was looking for; however I need
>> > it to work from a networked, non-drive-mapped folder.
>> > (CMD.EXE doesn't like UNC paths.) I hadn't realized that I could pipe
>> > a s
Greetings, Kertz, Denis (D)** CTR **!
> I am trying to port a cygwin application that uses cron from a WinXP PC to
> a Win7 Pro PC and I find some cron jobs won't run. Specifically, I need to
> run an Excel program from a cron job and this doesn't work on my Win7 PC.
> In order to run an Excel p
Hello, I noticed there was an update to libssh uploaded yesterday (11/10/14):
https://cygwin.com/packages/x86/libssh2_1/
I don't see anything about an update to this in the announcements section.
I also tried searching the site and can't find anything about an update to
libssh.
Can someone pl
Corinna Vinschen writes:
> I understand that you're patching setup to recognize the autorebase
> package by name, but how does it recognize other "perpetual" postinstall
> scripts ATM?
I actually match an "_always" suffix before the file extension. So once
such a file gets installed in /etc/posti
On Nov 11 18:08, Achim Gratz wrote:
> Corinna Vinschen writes:
> > On Nov 11 10:02, Ken Brown wrote:
> >> Of course, this still doesn't solve the problem of making sure that the
> >> _autorebase postinstall script runs whenever the user installs a package
> >> containing DLLs. I wonder if we shoul
I am trying to port a cygwin application that uses cron from a WinXP PC to a
Win7 Pro PC and I find some cron jobs won't run. Specifically, I need to run
an Excel program from a cron job and this doesn't work on my Win7 PC.
In order to run an Excel program from cygwin I have this run.excel bash
Corinna Vinschen writes:
> On Nov 11 10:02, Ken Brown wrote:
>> Of course, this still doesn't solve the problem of making sure that the
>> _autorebase postinstall script runs whenever the user installs a package
>> containing DLLs. I wonder if we should reconsider Achim's proposal. If I
>> unders
On Nov 11 18:29, Andrey Repin wrote:
> Greetings, Corinna Vinschen!
>
> >> > Shall the "db" entries utilize the Windows home folder if it exits(*)
> >> > and drop using the unixHomeDirectory? It seems inevitable…
> >>
> >> Use of AD implies some level of security consciousness. The ability to
On Nov 11 17:44, Achim Gratz wrote:
> Corinna Vinschen writes:
> >> Looks good, but maybe allow the AD attribute to be explicitly named (e.g.
> >> cygwinHomeDirectory).
> >
> > Cygwin schema extension? :)
>
> I don't see why not, given that there's the possibility of having
> different information
Corinna Vinschen writes:
>> Looks good, but maybe allow the AD attribute to be explicitly named (e.g.
>> cygwinHomeDirectory).
>
> Cygwin schema extension? :)
I don't see why not, given that there's the possibility of having
different information for Windows, Cygwin and UNIX in the same AD. But
m
On Nov 11 08:51, Jeffrey Altman wrote:
> On 11/11/2014 4:59 AM, Corinna Vinschen wrote:
> > Please keep in mind that I'm talking about the Cygwin home dir not as
> > a default value which can be overridden in /etc/passwd, but of a Cygwin
> > home dir as returned by Cygwin when fetching the passwd e
> From: Achim Gratz
>
> Nellis, Kenneth writes:
> > Jeremy's solution is closest to what I was looking for; however I need
> > it to work from a networked, non-drive-mapped folder.
> > (CMD.EXE doesn't like UNC paths.) I hadn't realized that I could pipe
> > a script into bash.
>
> The solution t
On Nov 11 10:02, Ken Brown wrote:
> On 11/11/2014 9:14 AM, Ken Brown wrote:
> >On 11/11/2014 6:53 AM, Corinna Vinschen wrote:
> >>On Nov 10 22:33, Yaakov Selkowitz wrote:
> >>>On 2014-11-10 22:23, Yaakov Selkowitz wrote:
> Dependency order of packages: libgcc1 base-cygwin cygwin dash tzcode
> >
Greetings, Corinna Vinschen!
>> > Shall the "db" entries utilize the Windows home folder if it exits(*)
>> > and drop using the unixHomeDirectory? It seems inevitable…
>>
>> Use of AD implies some level of security consciousness. The ability to
>> write to c:\cygwin — not just during installat
Greetings, Frank Fesevur!
>> I see literally zero reason to maintain separate, cygwin-specific "home"
>> directory.
> I think I have to disagree with you. When mixing MSYS, msysGit and
> Cygwin in the same home directory the dot-files can become a problem.
> Especially when it comes to line endin
On 11/11/2014 9:14 AM, Ken Brown wrote:
On 11/11/2014 6:53 AM, Corinna Vinschen wrote:
On Nov 10 22:33, Yaakov Selkowitz wrote:
On 2014-11-10 22:23, Yaakov Selkowitz wrote:
Dependency order of packages: libgcc1 base-cygwin cygwin dash tzcode
libstdc++6 terminfo sed gzip libpcre1 grep libreadli
On 11/11/2014 6:53 AM, Corinna Vinschen wrote:
On Nov 10 22:33, Yaakov Selkowitz wrote:
On 2014-11-10 22:23, Yaakov Selkowitz wrote:
Dependency order of packages: libgcc1 base-cygwin cygwin dash tzcode
libstdc++6 terminfo sed gzip libpcre1 grep libreadline7 bash
libncursesw10
[snip]
Now that
On 11/11/2014 4:59 AM, Corinna Vinschen wrote:
> Please keep in mind that I'm talking about the Cygwin home dir not as
> a default value which can be overridden in /etc/passwd, but of a Cygwin
> home dir as returned by Cygwin when fetching the passwd entry from AD,
> and no passwd file exists. Thi
>>> Another:
>>>
>>> 1. Add a setting to /etc/nsswitch.conf which allows to specify one of
>>> the above:
>>>
>>> home: [unix|win|home]...
>>>
>>>- "unix" means, set pw_dir to unixHomeDirectory
>>>- "win" means, set pw_dir to homeDirectory
>>>- "home" means, set pw_dir to /home
On Nov 11 07:11, Bryan Berns wrote:
> One big vote for the '/etc/nsswitch.conf' idea. I think the truth of
> the matter is that enterprise environments are way too dynamic (and
> inconsistent) to attempt to satisfy the majority of configurations
> with any particular default ordering assumption.
>
One big vote for the '/etc/nsswitch.conf' idea. I think the truth of
the matter is that enterprise environments are way too dynamic (and
inconsistent) to attempt to satisfy the majority of configurations
with any particular default ordering assumption.
Another user brought up a good point about d
Good evening:
I recently ran the latest setup-x86.exe to pick up the recent updates for my
Windows XP (SP3) system. I received the following error message.
Package: libgvc6
libgvc6.sh exit code 134
>From what I can tell, this means the installation process received a
SIGABORT signal during
On Nov 10 22:33, Yaakov Selkowitz wrote:
> On 2014-11-10 22:23, Yaakov Selkowitz wrote:
> >Dependency order of packages: libgcc1 base-cygwin cygwin dash tzcode
> >libstdc++6 terminfo sed gzip libpcre1 grep libreadline7 bash
> >libncursesw10
> [snip]
>
> Now that I think about it, regardless of lib
On Nov 11 07:39, Christian Franke wrote:
> Corinna Vinschen wrote:
> >On Nov 10 20:21, Christian Franke wrote:
> >>What will be the behavior of the predecessor of e.g. the csih function
> >>csih_create_unprivileged_user if called with USER without HOST prefix,
> >>machine is inside of domain and th
On Nov 11 11:05, Achim Gratz wrote:
> Corinna Vinschen cygwin.com> writes:
> > One possible, but not naturally useful default behaviour is what
> > the current code does:
> >
> > 1. Utilize the unixHomeDirectory AD attribute.
> > 2. If unixHomeDirectory is empty, fall back to /home/$USER.
> [...]
On Nov 11 11:18, Corinna Vinschen wrote:
> On Nov 10 23:09, Warren Young wrote:
> > On Nov 10, 2014, at 1:52 PM, Corinna Vinschen
> > wrote:
> >
> > > Shall the "db" entries utilize the Windows home folder if it exits(*)
> > > and drop using the unixHomeDirectory? It seems inevitable…
> >
> >
Corinna Vinschen cygwin.com> writes:
> One possible, but not naturally useful default behaviour is what
> the current code does:
>
> 1. Utilize the unixHomeDirectory AD attribute.
> 2. If unixHomeDirectory is empty, fall back to /home/$USER.
[...]
Default to /home/$USER unless a specific AD attr
On Nov 10 23:09, Warren Young wrote:
> On Nov 10, 2014, at 1:52 PM, Corinna Vinschen
> wrote:
>
> > Shall the "db" entries utilize the Windows home folder if it exits(*)
> > and drop using the unixHomeDirectory? It seems inevitable…
>
> Use of AD implies some level of security consciousness.
>Marco Atzeri wrote:
>>On 11/11/2014 7:40 AM, Andrey Repin wrote:
>>
>>In short, elusive benefits of having a separate cygwin-specific "clean"
>> homes
>>versus confusing disjoint of multiple places to look for single user's
>> files,
>>settings, and other stuff when it comes to back
On Nov 10 20:38, Jeffrey Altman wrote:
> On 11/10/2014 3:52 PM, Corinna Vinschen wrote:
> > Hi,
> >
> >
> > after a long discussion in RL today, I came to the conclusion that
> > there's a major problem in the current handling of the user's home
> > directory in AD environments in the new user ac
On Nov 10 23:19, Warren Young wrote:
> On Nov 10, 2014, at 6:38 PM, Jeffrey Altman
> wrote:
> > My personal preference would be for the Cygwin Home directory to be
> > created under
> >
> > %HOMEPATH%\AppData\Roaming\Cygwin
>
> That’s certainly the way you’re *supposed* to do it on Windows.
>
2014-11-11 1:45 GMT+01:00 Andrey Repin:
> I see literally zero reason to maintain separate, cygwin-specific "home"
> directory.
I think I have to disagree with you. When mixing MSYS, msysGit and
Cygwin in the same home directory the dot-files can become a problem.
Especially when it comes to line
On 11/11/2014 7:40 AM, Andrey Repin wrote:
Greetings, Yaakov Selkowitz!
In short, elusive benefits of having a separate cygwin-specific "clean" homes
versus confusing disjoint of multiple places to look for single user's files,
settings, and other stuff when it comes to backups and migrating pr
45 matches
Mail list logo
