At 11:37 AM 1/27/2004, Brian Ford you wrote:
>On Tue, 27 Jan 2004, Larry Hall wrote:
>
>> To me, that suggests that we need to either have a way to optionally
>> start the configuration of packages from setup.exe and/or somehow queue
>> the user into the READMEs.
>>
>Technically, the FAQ should hav
At 11:25 AM 1/27/2004, Edward W. Rouse you wrote:
>> -Original Message-
>>
>> At 11:03 AM 1/27/2004, Larry Hall you wrote:
>> >At 03:03 AM 1/27/2004, Brian Dessent you wrote:
>> >>Larry Hall wrote:
>> >>
>
>> >
>> >To me, that suggests that we need to either have a way to optionally
>> >
On Tue, 27 Jan 2004, Larry Hall wrote:
> To me, that suggests that we need to either have a way to optionally
> start the configuration of packages from setup.exe and/or somehow queue
> the user into the READMEs.
>
Technically, the FAQ should have accomplished that under "Where's the
documentation
Edward W. Rouse
ComSquared Systems, Inc.
Lead Developer, UniSearch Process Optimizer (R)
> -Original Message-
>
> At 11:03 AM 1/27/2004, Larry Hall you wrote:
> >At 03:03 AM 1/27/2004, Brian Dessent you wrote:
> >>Larry Hall wrote:
> >>
> >
> >To me, that suggests that we need to
At 11:03 AM 1/27/2004, Larry Hall you wrote:
>At 03:03 AM 1/27/2004, Brian Dessent you wrote:
>>Larry Hall wrote:
>>
>>> Precisely. The idea of adding to the FAQ for something that should be
>>> obvious goes against my grain but I'm OK with the notion if doing so
>>> addresses a problem. But, at
At 03:03 AM 1/27/2004, Brian Dessent you wrote:
>Larry Hall wrote:
>
>> Precisely. The idea of adding to the FAQ for something that should be
>> obvious goes against my grain but I'm OK with the notion if doing so
>> addresses a problem. But, at least to me, this one seems way off to one
>> end
Larry Hall wrote:
> Precisely. The idea of adding to the FAQ for something that should be
> obvious goes against my grain but I'm OK with the notion if doing so
> addresses a problem. But, at least to me, this one seems way off to one
> end of "obviousness" so I have to question the "obvious" s
On Mon, Jan 26, 2004 at 11:16:26AM -0800, Shankar Unni wrote:
>Christopher Faylor wrote:
>
>>I actually suspect that this is one of many cases where a FAQ entry
>>would be of little help and I'm always wary of adding so much verbiage
>>to the FAQ that it becomes unusable.
>
>I suppose it's the same
Christopher Faylor wrote:
I actually suspect that this is one of many cases where a FAQ entry
would be of little help and I'm always wary of adding so much verbiage
to the FAQ that it becomes unusable.
I suppose it's the same thought process that prompts people who install
3rd party products buil
At 01:41 PM 1/26/2004, Christopher Faylor you wrote:
>On Mon, Jan 26, 2004 at 06:34:29PM -, Dave Korn wrote:
>>>-Original Message-
>>>From: cygwin-owner On Behalf Of Larry Hall
>>
>>>Otherwise, adding what should be obvious to the FAQ isn't going to pass
>>>muster. The FAQ isn't the pl
On Mon, Jan 26, 2004 at 06:34:29PM -, Dave Korn wrote:
>>-Original Message-
>>From: cygwin-owner On Behalf Of Larry Hall
>
>>Otherwise, adding what should be obvious to the FAQ isn't going to pass
>>muster. The FAQ isn't the place for the obvious.
>
>AYS? The FAQ is the place for _fre
> -Original Message-
> From: cygwin-owner On Behalf Of Larry Hall
> Otherwise, adding what should be obvious to the FAQ isn't
> going to pass muster. The FAQ isn't the place for the obvious.
AYS? The FAQ is the place for _frequently_ asked questions, and I've always
assumed that f
At 12:21 PM 1/26/2004, Jose Gilberto Torres you wrote:
>>I feel like a broken record on this subject. If you followed the
>>instructions for setting up sshd under Cygwin from a different site,
>>why are you asking for help here on the Cygwin list when you are having
>>problems with instructions g
I feel like a broken record on this subject. If you followed the
instructions for setting up sshd under Cygwin from a different site,
why are you asking for help here on the Cygwin list when you are having
problems with instructions garnered from another site?
tech.erdelynet.com != cygwin.com.
In addition to making sure that the SYSTEM account is
in the /etc/passwd file, you can change the
permissions on a few directories (or check them to
make sure that they at least resemble the
following)before running the ssh-host-config routine:
chown -R 544:544 /var
chown -R 18:18 /var/log/sshd.lo
Hello,
I'm trying to setup sshd and I'm getting to success at all. Here's my
situation. I've followed the instructions at
http://tech.erdelynet.com/cygwin-sshd.html and when I run
*ssh-host-config -y* I get this error message.
To start the service, call `net start sshd' or `cygrunsrv -S sshd'
16 matches
Mail list logo
