>> For exactly one particular purpose I still use 32-bit Cygwin.
>> Can I confirm that the appropriate setup exe file, with qualifiers, is
>> setup-x86_32.exe
--allow-unsupported-windows
--site
http://ctm.crouchingtigerhiddenfruitbat.org/pub/cygwin/circa/2022/11/23/063457
>> and that
For exactly one particular purpose I still use 32-bit Cygwin.
Can I confirm that the appropriate setup exe file, with qualifiers, is
setup-x86_32.exe
--allow-unsupported-windows
--site
http://ctm.crouchingtigerhiddenfruitbat.org/pub/cygwin/circa/2022/11/23/063457
and that the exe file
>>This looks like a bug. Can anyone help? Is there a work-around?
Hi Andy,
There was some chatter the last week or 2 on someone trying to get ssh to work.
At the archive mailing list, you can read and see if that answers any of it.
I thought the gist of it is that a cipher is being swapped out
On 9/3/2024 9:13 AM, Rich Draves via Cygwin wrote:
I often use grep -r --include. But it has a really annoying problem - the
comparison of the filename is case-sensitive. The -i option seems to apply
only to the regex not the filename matching.
For example, I have many files named virtualenvi
Hi,
I've installed Cygwin and OpenSSH on a Windows machine and set up the
sshd daemon as follows:
mkpassd -l > /etc/passwd
mkgroup -l > /etc/group
chmod +r /etc/passwd /etc/group
chmod 777 /var
ssh-host-config
cygrunsrv -S cygsshd
SSH now works for user account that set up SSHD, ie 'ssh
admin@lo
I often use grep -r --include. But it has a really annoying problem - the
comparison of the filename is case-sensitive. The -i option seems to apply only
to the regex not the filename matching.
For example, I have many files named virtualenvironment.ini. But unfortunately,
sometimes it is virtu
6 matches
Mail list logo