> having installed Cygwin on my old computer it's now time to move to new
> hardware. Are there any Cygwin configuration or status files I could
> copy from the old box to the new one which would cause "setup.exe" on
> the new machine to automatically install the same packages as on the old
Marco,
On Tuesday, 2015-09-01 15:57:03 +0200, you wrote:
> ...
> $ cygcheck -cd | awk 'BEGIN{printf("setup-x86_64.exe ")} {if (NR>2) {
> printf ("-P " $1 " ") }} END { printf ("\r\n pause ")}' >
> cyg-install-x86_64.bat
Even if I slightly compress the command line created that way by using a
Hi Cygwin friends and users,
I released a new TEST version of Cygwin, 2.3.0-0.1.
This is the "new POSIX ACL handling reloaded" release.
In local testing I successfully integrated AuthZ into the current Cygwin
code to generate more correct user permissions by being able to generate
effective per
On 02/09/2015 12:53, Dr Rainer Woitok wrote:
Marco,
On Tuesday, 2015-09-01 15:57:03 +0200, you wrote:
...
$ cygcheck -cd | awk 'BEGIN{printf("setup-x86_64.exe ")} {if (NR>2) {
printf ("-P " $1 " ") }} END { printf ("\r\n pause ")}' > cyg-install-x86_64.bat
Even if I slightly compress the co
Hi,
The ssh command keeps prompting "password:" repeatedly with the latest
OpenSSH package after I started ssh-agent and registered key with
ssh-add command.
Followings are my environment.
% uname -a
CYGWIN_NT-10.0 win8 2.2.1(0.289/5/3) 2015-08-20 11:42 x86_64 Cygwin
% ssh -V
OpenSSH_7.1p1, OpenS
Greetings, Hiroyuki Kurokawa!
> Hi,
> The ssh command keeps prompting "password:" repeatedly with the latest
> OpenSSH package after I started ssh-agent and registered key with
> ssh-add command.
> Followings are my environment.
> % uname -a
> CYGWIN_NT-10.0 win8 2.2.1(0.289/5/3) 2015-08-20 11:4
Dear folks, here is a few update:
This bug was originally found with MSYS2, but I've confirm it happens
on Cygwin (CYGWIN_NT-5.1 2.2.1(0.289/5/3) 2015-08-20 11:40 i686
Cygwin) as well.
For convenient of compile&test I'm mostly debugging on MSYS2, which is
rebased above the below Cygwin commit:
c
Looks like I hit a wall with this problem. I would appreciate if someone
could help out with this issue.
On 2015-08-17 21:39, yaro...@hotmail.com wrote:
I have Cygwin installed on a couple of servers in a domain
environment. Of all machines regular user accounts can ssh to only one
box.
Once i
On Sat, 2015-08-29 at 16:52 -0400, Ken Brown wrote:
> On 8/29/2015 1:15 PM, Ken Brown wrote:
> > hunspell seems to have a problem with UTF-8:
> >
> > $ hunspell
> > error: unknown encoding UTF8: using iso88591 as fallback
> > error: unknown encoding UTF8: using iso88591 as fallback
> > error: unkno
Corinna Vinschen writes:
> This is the "new POSIX ACL handling reloaded" release.
Oh joy… I just have no time to test it thoroughly (or even at all)
during the next three weeks. I'll try to at least install it locally
tomorrow (the mirrors hadn't cought up in the afternoon) and give it a
quick lo
Hello,
I'm currently searching the mailing list archive as well as google but
I thought I would ask out right aw well.. I'm looking to implement a
private Cygwin mirror. The process seem fairly straight forward
setting up an apache instance and rsycing twice a day. However our
NetSec folks have as
Hi:
I currently use Cygwin and rsync to provide Time Machine-like
functionality to a NAS on my home network. This works fine for user
data.
I'm also interested in generating images to preserve the entire disk.
What I'm wondering is whether doing this on a live system through
Cygwin would produce
On 09/02/2015 03:57 PM, Clint Olsen wrote:
> I'm also interested in generating images to preserve the entire disk.
> What I'm wondering is whether doing this on a live system through
> Cygwin would produce a safe, bootable disk image or if the the APIs
> that Cygwin has to use or having the disk m
Mike DePaulo sent the following at Tuesday, September 01, 2015 7:47 PM
>On 09/01/2015 07:13 PM, Jared Buck wrote: [...]
>> On Tue, Sep 1, 2015 at 4:07 PM, Yaakov Selkowitz
>> wrote:
>>> The following package has been added to the Cygwin distribution:
>>>
>>> * sl-5.02-1
>>>
>>> SL (Steam Locomoti
> -Original Message-
> From: Eric Blake
> Sent: Wednesday, September 02, 2015 6:06 PM
>
> On 09/02/2015 03:57 PM, Clint Olsen wrote:
>
> > I'm also interested in generating images to preserve the
> entire disk.
> > What I'm wondering is whether doing this on a live system through
> > Cy
On 09/02/2015 04:23 PM, Jason Pyeron wrote:
>> There are various solutions that CAN capture an accurate
>> point-in-time disk snapshot.
>
> For cygwin/Windows use the Volume Shadow Service (VSS). I have used (XP)
> cygwin dd and rsync to take (clone) images from the VSS managed drive.
What's
Greetings, All!
I had this issue running for some time, but recently I've (with a little help
from my friends) stumbled upon another Cygwin rip-off, and the hack they
implemented to get around this issue. (Yes, they just renamed the ping.exe to
cygping.)
I understand, that some of the ping functi
Greetings, Chris Louden!
> I'm currently searching the mailing list archive as well as google but
> I thought I would ask out right aw well.. I'm looking to implement a
> private Cygwin mirror. The process seem fairly straight forward
> setting up an apache instance and rsycing twice a day. Howeve
Greetings, Clint Olsen!
> I'm also interested in generating images to preserve the entire disk.
> What I'm wondering is whether doing this on a live system through
> Cygwin would produce a safe, bootable disk image or if the the APIs
> that Cygwin has to use or having the disk mounted would make t
Hi,
Thanks Andrey for reply to my question.
George gave me an advice by a direct mail.
And his instruction solve my problem.
> If you use dsa key type, you need to add to your ssh client configuration
> file, either ~/.ssh/config or /etc/ssh_config, the following parameter:
>
> PubkeyAcceptedKe
Greetings, Hiroyuki Kurokawa!
> Thanks Andrey for reply to my question.
> George gave me an advice by a direct mail.
> And his instruction solve my problem.
>> If you use dsa key type, you need to add to your ssh client configuration
>> file, either ~/.ssh/config or /etc/ssh_config, the followi
Hi Andrey,
> This is not the right solution. Right solution would be to change your keys.
> While DSA keys aren't inherently insecure (quite opposite), FIPS compliant
> systems enforce DSA key length to 1024 bits, which is considered to be weak
> nowadays. You CAN use longer DSA keys, but not all
22 matches
Mail list logo
