On 4/10/2018 2:12 PM, Yaakov Selkowitz wrote:
In order to speed up the adoption of the latest setup.exe, would it make
sense to ship it as a package? Here is an initial draft of what this
might look like:
https://github.com/cygwinports/setup/blob/master/setup.cygport
Note that the executable i
In order to speed up the adoption of the latest setup.exe, would it make
sense to ship it as a package? Here is an initial draft of what this
might look like:
https://github.com/cygwinports/setup/blob/master/setup.cygport
Note that the executable itself is version/release-numbered so that we
nev
We're in the midst of switching to a different LDAP domain
organisation. All my accounts still arein the old domain and that leads
to problems when lookking at shares from a mchine in the new domain:
--8<---cut here---start->8---
(1027)/mnt/upload > touch bla
As briefly discussed on IRC I've got a new Server 2016 blade with 2
sockets × 8 cores × 2 HT =32 logical processors and Cygwin spews errors
for processor ID 16 and up (also top doesn't quite work, which likely
has the same reason, although the code path may be unrelated to the
/proc/cpuinfo bug de
