I'm seeing a error when creating hard links under Vista using the
cygwin1.dll snapshots starting at cygwin1-20070802.dll (through at
least cygwin1-20080112.dll).
To reproduce:
* stop/exit all cygwin processes
* replace bin/cygwin1.dll with one of the snapshot dlls above
* fire up bash and
On Jan 21 16:23, Corinna Vinschen wrote:
> On Jan 21 15:53, Corinna Vinschen wrote:
> > On Jan 19 07:30, Herb Maeder wrote:
> > > I'm seeing a error when creating hard links under Vista using the
> > > cygwin1.dll snapshots starting at cygwin1-20070802.dll
On 13 Nov 2008 11:35:43 +0100, Corinna Vinschen wrote:
> > Looking ahead, I suspect that this combo (sshd + 1.7 + vista + domain user)
> > will be pretty common. Is there a plan for steering users in the right
> > direction during the setup of sshd, or maybe giving a more descriptive
> > error me
On 14 Nov 2008 10:53:12 +0100, Corinna Vinschen wrote:
> Actually this isn't a ssh-host-config problem, but a generic problem
> for all admin tasks. Installing any service requires elevation, or
> running in a Admin shell. I'm not really convinced that we need it.
> Admins running admin tasks sho
On 19 Nov 2008 09:54:41 EST, Christopher Faylor wrote:
> On Wed, Nov 19, 2008 at 07:24:33AM -0500, Brett Serkez wrote:
> >I spent considerable time on this and reported were the problem is
> >occurring to no avail, don't waste your time. In a nutshell the issue
> >is with Cygwin's bi-directional p
On 20 Nov 2008 11:37:23 +0100, Corinna Vinschen wrote:
> > Note, I'm not requesting any changes. I'm just trying to understand if we
> > could/should establish guidelines for admin tasks requiring elevation.
>
> All nice points but I don't think that you have to convince anybody that
> better doc
With a fresh install of cygwin-1.7 on a vanilla Vista system, I see that
the 'mv' command appends a .exe extension to the destination file for any
source files that have a .bat or .com extensions.
To reproduce:
% mkdir foobar
% touch foo.bat
% mv foo.bat foobar
% ls foobar
foo.
On Oct 1 21:02, Thorsten Kampe wrote:
> * Herb Maeder (Wed, 01 Oct 2008 09:27:25 -0700)
> > With a fresh install of cygwin-1.7 on a vanilla Vista system, I see that
> > the 'mv' command appends a .exe extension to the destination file for any
> > source files that
On a fresh install of cygwin-1.7 (1.7.0-30) on Vista, the output of
"cygcheck -s" sometimes gets truncated. This seems to be more reproducible
when the output is piped to another command.
I find that this sequence is shows problem quite regularly (typically more
than half of the cycheck commands
On Sun, Oct 05, 2008 at 12:51:59 -0400, Christopher Faylor wrote:
> >On a fresh install of cygwin-1.7 (1.7.0-30) on Vista, the output of
> >"cygcheck -s" sometimes gets truncated. This seems to be more
> >reproducible when the output is piped to another command.
>
> This has been reported before
The current setup.hint for release-2/libtool specifies the following
current version:
curr: 1.5.27a-1
But the corresponding libtool-1.5.27a-1.tar.bz2 file does not exist on
the mirrors. Only libtool-2.2.2-2.tar.bz2 exists (listed in the "test:"
field).
I believe that if a package that requir
The "Special values of user and group ids" section of the Cygwin User's
Guide (http://cygwin.com/1.7/cygwin-ug-net.html#ntsec-ids) states:
Also, since Cygwin release 1.3.20, if the current user is present in
/etc/passwd, but that user's login group is not present in /etc/group,
the grou
On 09 Oct 2008 13:05:36 +0200, Corinna Vinschen wrote:
> On Oct 7 11:22, Herb Maeder wrote:
> > The "Special values of user and group ids" section of the Cygwin User's
> > Guide (http://cygwin.com/1.7/cygwin-ug-net.html#ntsec-ids) states:
> >
> >
On 10 Oct 2008 11:35:08 +0200, Corinna Vinschen wrote:
> > But I think that means that some of the information in the "Special values
> > of user and group ids" section of the Cygwin User's Guide is out of date.
> >
> > Would it be appropriate to include some of the information from your
> > descr
The "mkpasswd -c" command produces the wrong gid for the current user
under the following set of circumstances:
* it is invoked from a cmd.exe shell
* there are no running cygwin bash shells
* output is redirected to cygwin's /etc/passwd file (with the permissions
that setup.exe sets
On 11 Oct 2008 07:29:12 PDT, Herb Maeder wrote:
> The "mkpasswd -c" command produces the wrong gid for the current user
> under the following set of circumstances:
>
>* it is invoked from a cmd.exe shell
>* there are no running cygwin bash shells
>* outp
On 13 Oct 2008 17:54:36 +0200, Corinna Vinschen wrote:
> > But if it ends up sticking around, then it probably makes sense to account
> > for the additional special case that was just introduced:
> >
> > passwd/group_GID_clash* )
> > echo "Your group is currently \"passwd/group_GID_clash\".
On 14 Oct 2008 12:57:43 +0200, Marco Atzeri wrote:
> try with
> starting sshd service and connect with
>
> rsync --rsh=ssh ...
Though it should be noted that with cygwin-1.5, rsync to a cygwin machine
running sshd will hang on transferring large directories. For example,
(from some directory no
On a fresh install of the cygwin-1.7 base package + openssh, I believe we
should expect the following to work for installing and testing sshd:
ssh-host-config -y
cygrunsrv --start sshd
ssh localhost pwd
If sshd had been previously installed on the system, the following
cleanup sho
On 17 Oct 2008 20:06:35 EDT, Christopher Faylor wrote:
> On Fri, Oct 17, 2008 at 12:50:48PM -0700, Herb Maeder wrote:
> >2. (Vista/XP) The tcp_wrappers dependency is missing in openssh/setup.hint
> >
> >Sincd sshd.exe depends on cygwrap-0.dll, the tcp_wrappers package must be
On 20 Oct 2008 11:53:19 PDT, "Manning, Sid" wrote:
> Of course I needed an excuse to ask the question, surprised or curious
> either would have sufficed. So the implementation of a GNU/Posix stack
> over windows is expensive and that is understandable (I suffer from cross
> platform headaches all
On 20 Oct 2008 11:53:19 PDT, "Manning, Sid" wrote:
> Of course I needed an excuse to ask the question, surprised or curious
> either would have sufficed. So the implementation of a GNU/Posix stack
> over windows is expensive and that is understandable (I suffer from cross
> platform headaches all
On 20 Oct 2008 11:53:19 PDT, "Manning, Sid" wrote:
> Of course I needed an excuse to ask the question, surprised or curious
> either would have sufficed. So the implementation of a GNU/Posix stack
> over windows is expensive and that is understandable (I suffer from cross
> platform headaches all
On 20 Oct 2008 11:53:19 PDT, "Manning, Sid" wrote:
> Of course I needed an excuse to ask the question, surprised or curious
> either would have sufficed. So the implementation of a GNU/Posix stack
> over windows is expensive and that is understandable (I suffer from cross
> platform headaches all
On 20 Oct 2008 11:53:19 PDT, "Manning, Sid" wrote:
> Of course I needed an excuse to ask the question, surprised or curious
> either would have sufficed. So the implementation of a GNU/Posix stack
> over windows is expensive and that is understandable (I suffer from cross
> platform headaches all
On 20 Oct 2008 11:53:19 PDT, "Manning, Sid" wrote:
> Of course I needed an excuse to ask the question, surprised or curious
> either would have sufficed. So the implementation of a GNU/Posix stack
> over windows is expensive and that is understandable (I suffer from cross
> platform headaches all
On 20 Oct 2008 11:53:19 PDT, "Manning, Sid" wrote:
> Of course I needed an excuse to ask the question, surprised or curious
> either would have sufficed. So the implementation of a GNU/Posix stack
> over windows is expensive and that is understandable (I suffer from cross
> platform headaches all
On 20 Oct 2008 11:53:19 PDT, "Manning, Sid" wrote:
> Of course I needed an excuse to ask the question, surprised or curious
> either would have sufficed. So the implementation of a GNU/Posix stack
> over windows is expensive and that is understandable (I suffer from cross
> platform headaches all
Apologies to the list for getting the same message sent over and over to
the list from my account. I can't yet explain what is happening, but I can
assure you that I only sent the message once (and in no way differently
than my other posts to the list).
I've been on the phone with my ISP for the
On 20 Oct 2008 11:53:19 PDT, "Manning, Sid" wrote:
> Of course I needed an excuse to ask the question, surprised or curious
> either would have sufficed. So the implementation of a GNU/Posix stack
> over windows is expensive and that is understandable (I suffer from cross
> platform headaches all
On 20 Oct 2008 11:53:19 PDT, "Manning, Sid" wrote:
> Of course I needed an excuse to ask the question, surprised or curious
> either would have sufficed. So the implementation of a GNU/Posix stack
> over windows is expensive and that is understandable (I suffer from cross
> platform headaches all
On 20 Oct 2008 11:53:19 PDT, "Manning, Sid" wrote:
> Of course I needed an excuse to ask the question, surprised or curious
> either would have sufficed. So the implementation of a GNU/Posix stack
> over windows is expensive and that is understandable (I suffer from cross
> platform headaches all
On 20 Oct 2008 11:53:19 PDT, "Manning, Sid" wrote:
> Of course I needed an excuse to ask the question, surprised or curious
> either would have sufficed. So the implementation of a GNU/Posix stack
> over windows is expensive and that is understandable (I suffer from cross
> platform headaches all
On 20 Oct 2008 11:53:19 PDT, "Manning, Sid" wrote:
> Of course I needed an excuse to ask the question, surprised or curious
> either would have sufficed. So the implementation of a GNU/Posix stack
> over windows is expensive and that is understandable (I suffer from cross
> platform headaches all
On 20 Oct 2008 11:53:19 PDT, "Manning, Sid" wrote:
> Of course I needed an excuse to ask the question, surprised or curious
> either would have sufficed. So the implementation of a GNU/Posix stack
> over windows is expensive and that is understandable (I suffer from cross
> platform headaches all
by 127.0.0.1
(qmail-ldap-1.03) with SMTP for ; 23 Oct
2008 20:43:31 -
To: cygwin AT cygwin DOT com
From: Herb Maeder
In-reply-to: "Manning, Sid" 's message of
Mon, 20 Oct 2008 11:53:19 PDT.
Subject: Re: Compile time Local Cygwin vs. VMware ses
On 20 Oct 2008 11:53:19 PDT, "Manning, Sid" wrote:
> Of course I needed an excuse to ask the question, surprised or curious
> either would have sufficed. So the implementation of a GNU/Posix stack
> over windows is expensive and that is understandable (I suffer from cross
> platform headaches all
On 24 Oct 2008 18:28:24 BST, Dave Korn wrote:
> > (I've got a hunch that the root cause may be some miscommunication between
> > the servers due to timeouts or something, but I have no way to verify
> > that).
>
> You don't have access to the maeder.org server?
I have access to maeder.org, whic
On 20 Oct 2008 11:53:19 PDT, "Manning, Sid" wrote:
> Of course I needed an excuse to ask the question, surprised or curious
> either would have sufficed. So the implementation of a GNU/Posix stack
> over windows is expensive and that is understandable (I suffer from cross
> platform headaches all
On 28 Oct 2008 10:38:21 EDT, Christopher Faylor wrote:
> >>Please correct me if I am wrong, but this type of thing has happened to
> >>the list before, right? I seem to remember it happening to someone
> >>else a while back, but I cannot find it in the archives at the moment.
> >
> >Sure. Not all
On 07 Nov 2008 12:00:56 +0100, Corinna Vinschen wrote:
> I've just updated the version of OpenSSH to 5.1p1-6.
>
> This is a bugfix release which fixes a bug in the ssh-host-config script
> which stumbles over user names with a substring of "ssh" in them and
> thinks that ssh processes are still ru
On 07 Nov 2008 12:00:56 +0100, Corinna Vinschen wrote:
> This is a bugfix release which fixes a bug in the ssh-host-config script
> which stumbles over user names with a substring of "ssh" in them and
> thinks that ssh processes are still running.
>
On 07 Nov 2008 12:00:56 +0100, Corinna Vinschen wrote:
> This is a bugfix release which fixes a bug in the ssh-host-config script
> which stumbles over user names with a substring of "ssh" in them and
> thinks that ssh processes are still running.
Is the intent now to catch only processes named
On 07 Nov 2008 17:10:02 EST, Christopher Faylor wrote:
> On Fri, Nov 07, 2008 at 01:37:44PM -0800, Herb Maeder wrote:
> >On 07 Nov 2008 12:00:56 +0100, Corinna Vinschen wrote:
> >> This is a bugfix release which fixes a bug in the ssh-host-config script
> >> which st
Running sshd (openssh 5.1p1-d57 or 5.1p1-7) on cygwin-1.7 and vista
results in the following error:
% ssh localhost pwd
[EMAIL PROTECTED]'s password:
initgroups: Permission denied
I think this should be easily reproducible with a fresh installation of
just cygwin 1.7 base
On 10 Nov 2008 15:48:15 +0100, Corinna Vinschen wrote:
> On Nov 8 07:44, Herb Maeder wrote:
> > Running sshd (openssh 5.1p1-d57 or 5.1p1-7) on cygwin-1.7 and vista
> > results in the following error:
> >
> > % ssh localhost pwd
> >
On 11 Nov 2008 12:22:42 EST, Linus Hicks wrote:
> > So the question is what is wrong? I can't beleive that rsync can't handle
> > with such a big volume of data when it is necessary to transmit only a
> > small part of it.
> >
> > Any ideas and suggestions would be very much appreciated.
>
> Thi
On 13 Nov 2008 14:57:20 +0100, Corinna Vinschen wrote:
> On Nov 13 11:35, Corinna Vinschen wrote:
> > On Nov 12 16:57, Herb Maeder wrote:
> > > Bum deal. But thanks for the explanation. That clarifies what I was
> > > seeing.
> >
> > Actually there is
48 matches
Mail list logo
