Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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, 1 Mar 2004 09:16:22 -0800 From: Yitzchak Scott-Thoennes To: cygwin AT cygwin DOT com Subject: Re: Problem with dd to raw disks Message-ID: <20040301171622.GA2832@efn.org> References: <20040301144712 DOT GN1587 AT cygbert DOT vinschen DOT de> <6 DOT 0 DOT 1 DOT 1 DOT 0 DOT 20040301113231 DOT 039dbec0 AT 127 DOT 0 DOT 0 DOT 1> <20040301164437 DOT GA18339 AT redhat DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040301164437.GA18339@redhat.com> User-Agent: Mutt/1.4i Organization: bs"d X-IsSubscribed: yes On Mon, Mar 01, 2004 at 11:44:38AM -0500, Christopher Faylor wrote: > On Mon, Mar 01, 2004 at 11:35:40AM -0500, Larry Hall wrote: > >Pah! The User's Guide. That's just a document full of useful > >information. Why would anyone want to read that? ;-) > > Maybe we need a howto on reading the user's guide. It should certainly > be in the FAQ that people should read the documentation. How would people > know that they should read the documentation unless it was spelled out > somewhere in black and white? You know, the thing that really bugs me about cygwin is the half-baked attempts at documentation. A FAQ entry suggesting reading the User's Guide is completely useless unless the User's Guide tells people to read the FAQ. -- 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/