From owner-freebsd-questions@FreeBSD.ORG Mon Jul 2 20:11:57 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 151BA16A400 for ; Mon, 2 Jul 2007 20:11:57 +0000 (UTC) (envelope-from martin@dc.cis.okstate.edu) Received: from dc.cis.okstate.edu (dc.cis.okstate.edu [139.78.100.219]) by mx1.freebsd.org (Postfix) with ESMTP id DD55113C45E for ; Mon, 2 Jul 2007 20:11:56 +0000 (UTC) (envelope-from martin@dc.cis.okstate.edu) Received: from dc.cis.okstate.edu (localhost.cis.okstate.edu [127.0.0.1]) by dc.cis.okstate.edu (8.13.8/8.13.8) with ESMTP id l62KBu8I039211 for ; Mon, 2 Jul 2007 15:11:56 -0500 (CDT) (envelope-from martin@dc.cis.okstate.edu) Message-Id: <200707022011.l62KBu8I039211@dc.cis.okstate.edu> To: freebsd-questions@freebsd.org Date: Mon, 02 Jul 2007 15:11:56 -0500 From: Martin McCormick Subject: Re: The worst error message in history belongs to... BIND9! X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jul 2007 20:11:57 -0000 Jeffrey Goldberg writes: > I still remember as a newcomer to Unix a long long time ago getting > > "Bad magic number" > > > In retrospect, I suspect that I'd typed "ld" where I'd meant to type "ls". I have been doing things on Unix systems since about 1990 and the thing I run across that makes me ready to split a brick with my bare hands to this very day is the "not found" message one can get in a badly written shell script such as the following: #! /bin/sh a = 5 that's enough to make it happen. Run that, and you get: a: not found Interestingly enough, if you run that same script in a Debian Linux environment, you get: ./testfile: line 2: a: command not found Most of you will probably instantly see what I did wrong in that there shouldn't be any spaces between the variable name, the = sign and the 5 which could be anything else. I just picked a 5 for the heck of it. If you are in a big messy shell script, just seeing a: not found Doesn't tell me much except I know it's not working. The problem could be either that there is a typo or it could be that $a is null. I usually find that I snuck a space in and didn't even think about it at the time. I don't know if error messages from other OS's are off limits, but some of the ones from the most widely-used OS on Earth are treasures. How about running a gigantic piece of commercial software that does God knows what on your computer, and getting an error like: The software has performed an illegal operation. I bet there is a second line that they had to print in text using the same forground and background color so as to keep from getting fired that reads: "Now, try and find it. Ha ha ha ha!" Then, there is the ultimate, the "Check engine." light on the modern car. It would be so nice if it said some indication as to the seriousness of the problem so that one knows whether to get it fixed now and maybe save $5,000 worth of repair costs or let it slide a few days until a better time. I like the quotation I read once that said that Unix is a user-friendly operating system. It is just particular about who it makes friends with. Martin McCormick WB5AGZ Stillwater, OK Systems Engineer OSU Information Technology Department Network Operations Group