On Sun, Jan 19, 2003 at 02:37:29PM -0800, Joseph Davida wrote:
> I have compiled and installed ssh.com's 3.2.2
> ssh clients and daemon.
> I can start the daemon without a hitch.
> But the daemon is unable to authenticate
> the password, probably becasue the cygwin's
> libc password interface to th
I have compiled and installed ssh.com's 3.2.2
ssh clients and daemon.
I can start the daemon without a hitch.
But the daemon is unable to authenticate
the password, probably becasue the cygwin's
libc password interface to the Win2K password
authentication lib is not working.
The ssh client re-promp
ROTFL!
What can I say besides "open mouth, insert foot?"
On Sat, 2002-12-21 at 12:07, Randall R Schulz wrote:
David,
Now I'm a big Linux proponent and only currently wed to Windows by a quirk
of my personal employment history, but never did I realize that rebooting a
Linux system would
Does the meanness never end?
Won't you _please_ think of the children?!
At 09:57 2002-12-21, Christopher Faylor wrote:
On Sat, Dec 21, 2002 at 09:07:48AM -0800, Randall R Schulz wrote:
>David,
>
>Now I'm a big Linux proponent and only currently wed to Windows by a quirk
>of my personal employ
On Sat, Dec 21, 2002 at 09:07:48AM -0800, Randall R Schulz wrote:
>David,
>
>Now I'm a big Linux proponent and only currently wed to Windows by a quirk
>of my personal employment history, but never did I realize that rebooting a
>Linux system would fix a broken disk.
>
>Those Linux kernel program
David,
Now I'm a big Linux proponent and only currently wed to Windows by a quirk
of my personal employment history, but never did I realize that rebooting a
Linux system would fix a broken disk.
Those Linux kernel programmers really _are_ miracle workers, aren't they?
Wow!
Randall Schulz
A
Hum... I should have known. A reboot fixed the problem. I suppose that what I get for being a Unix geek: you don't _have_ to reboot a unix system to fix broken stuff. (unless it's really broken, like disks, etc, etc).
On Wed, 2002-12-18 at 13:50, [EMAIL PROTECTED] wrote:
I've recently inst
I've recently installed cygwin version 1.3.17.
When I attempt to ssh to the cygwin host more than once, with the
first connection still active, I get the error message
'setgid: invalid argument' , and then I'm disconnected.
Below is an example of the problem. The first 'ssh localhost' is
sucess
8 matches
Mail list logo
