Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Date:	Mon, 11 Oct 2004 12:00:31 -0400 (EDT)
From:	Igor Pechtchanski <pechtcha AT cs DOT nyu DOT edu>
Reply-To:	cygwin AT cygwin DOT com
To:	lex ein <lex_ein AT f-m DOT fm>
cc:	cygwin AT cygwin DOT com
Subject:	Re: Cygwin & openssh(d) & login without password
In-Reply-To:	<opsfkud1qltsbnf7@c500>
Message-ID:	<Pine.GSO.4.61.0410111156010.29807@slinky.cs.nyu.edu>
References:	<4162386A DOT 1080009 AT pastornet DOT net DOT au> <20041005084757 DOT GK6702 AT cygbert DOT vinschen DOT de> <opsfkud1qltsbnf7 AT c500>
MIME-Version:	1.0
X-Scanned-By:	MIMEDefang 2.39

On Fri, 8 Oct 2004, lex ein wrote:

> On Tue, 5 Oct 2004 10:47:57 +0200, Corinna Vinschen <corinna-cygwin AT XXXXXX DOT XXX> wrote:

<http://cygwin.com/acronyms/#PCYMTNQREAIYR>.

> > On Oct  5 16:00, David Campbell wrote:
> > > I've read lots of web pages about how to set it up, and I believe I've
> > > followed them, eg http://bumblebee.lcs.mit.edu/ssh2/ (for openssh to
> > > openssh):
> >
> > WHY DON'T YOU READ THE OFFICIAL DOCUMENTATION INSTEAD? [caps mine]
> > OpenSSH comes with a lot of man pages.  Then there's
> > /usr/share/doc/Cygwin/openssh.README.
> > Then you could have used ssh-host-config and ssh-user-config for the
> > basic configuration.
>
> BECAUSE in the case of openssh(and others), the "official documentation"
> is of little use to a new user: information is not gathered, stored, or
> presented in a orderly, logical, or sensible hierarchical manner, is not
> meaningfully cross-referenced, and is not reasonably searchable.
> There's just no usable thread to pull to unravel the mystery, either.
>
> Let's examine the steps a new user might pursue:
> [snip]
> 8. Let's say the user somehow finds openssh.README.
> [snip]
> To make the docs _easy_ to find would go against the dinosaur mentality
> of "Back in the day, I had to read all the docs before I could do
> anything, and now so do you."

It's been suggested before to make Cygwin-specific package README files
available on-line (off the package search/contents page).  Is this still
an acceptable solution?

Another proposal: add a "cygreadme" script, or even a "--readme/-R" option
to cygcheck, that would display the Cygwin-specific README file from a
given package...  Any takers? ;-)
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha AT cs DOT nyu DOT edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor AT watson DOT ibm DOT com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski, Ph.D.
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"Happiness lies in being privileged to work hard for long hours in doing
whatever you think is worth doing."  -- Dr. Jubal Harshaw

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -