From owner-freebsd-questions Wed Jan 16 17:44: 0 2002 Delivered-To: freebsd-questions@freebsd.org Received: from guru.mired.org (okc-65-31-201-166.mmcable.com [65.31.201.166]) by hub.freebsd.org (Postfix) with SMTP id 6311F37B41F for ; Wed, 16 Jan 2002 17:42:59 -0800 (PST) Received: (qmail 31706 invoked by uid 100); 17 Jan 2002 01:42:52 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15430.11292.89340.470262@guru.mired.org> Date: Wed, 16 Jan 2002 19:42:52 -0600 To: "Anthony Atkielski" Cc: "FreeBSD Questions" Subject: Re: USB CF reader (SanDisk) epilog In-Reply-To: <007201c19ed4$e98bc070$0a00000a@atkielski.com> References: <15428.34332.870130.2946@guru.mired.org> <00cc01c19e06$8dafddf0$0a00000a@atkielski.com> <15428.38970.224790.33804@guru.mired.org> <00ee01c19e0d$4c518960$0a00000a@atkielski.com> <15428.53337.168408.720031@guru.mired.org> <01b301c19e55$f11330a0$0a00000a@atkielski.com> <15429.45776.491932.646543@guru.mired.org> <007201c19ed4$e98bc070$0a00000a@atkielski.com> X-Mailer: VM 6.90 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ From: "Mike Meyer" X-Delivery-Agent: TMDA/0.44 (Python 2.2; freebsd-4.4-STABLE-i386) Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Anthony Atkielski types: > Mike writes: > > "fragmentary and incomplete" is redundant. > It's possible for something to be incomplete but contiguous (i.e., not > fragmentary). I don't feel like debating semantics now, but thanks for the offer. > > Often a series of guesses at the missing > > information is *faster* than trying to extract > > the information required to correctly diagnose > > the problem. > It is usually the _only_ way to diagnose the problem, and even then, it > usually isn't really a diagnosis. When dealing with users directly, yes. > > In extreme cases, it's faster to fly an > > expert to the spot so they can gather information > > than it is to try and extract it remotely. > You must be thinking of user information. I'm not talking about getting > information from users--although that is a problem, too. I'm talking about > just getting internal information on how the software works. Typically, no > such information is available. All the information on how the software works is contained in the code. It has to be - otherwise the code won't work. Other sources - that are sometimes easier to read - may exist, but they may not correctly reflect the code. If you can't read the code, you're handicapped in trying to solve problems from the first step. As to writing readable code, there are two approaches that have proven successful. See either "Object-Oriented Software Construction" by Bertrand Meyer, or "Literate Programming" by Donald Knuth. It should be obvious to anyone who's read why neither of these approaches has had much commercial success. > > So what have you done to figure out why it > > occured? > Looked for information on the Web, without success. The web is not the code. > > Have you checked LINT for debugging options > > for USB devices ... > I have now, after reading your suggestion. There are USB debugging options, > but no documentation as to what they produce. Yes there is. You can read it by replacing