From owner-cvs-src@FreeBSD.ORG  Sat Nov 15 23:22:47 2003
Return-Path: <owner-cvs-src@FreeBSD.ORG>
Delivered-To: cvs-src@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 4FAD116A4CE; Sat, 15 Nov 2003 23:22:47 -0800 (PST)
Received: from smtp.omnis.com (smtp.omnis.com [216.239.128.26])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 5ACB443FB1; Sat, 15 Nov 2003 23:22:46 -0800 (PST)
	(envelope-from wes@softweyr.com)
Received: from softweyr.homeunix.net (66-91-236-204.san.rr.com
	[66.91.236.204])	by smtp-relay.omnis.com (Postfix) with ESMTP
	id 1965A9BE81; Sat, 15 Nov 2003 23:22:32 -0800 (PST)
From: Wes Peters <wes@softweyr.com>
Organization: Softweyr
To: Wes Peters <wes@FreeBSD.org>, src-committers@FreeBSD.org,
	cvs-src@FreeBSD.org, cvs-all@FreeBSD.org
Date: Sat, 15 Nov 2003 23:22:45 -0800
User-Agent: KMail/1.5.4
References: <200311160710.hAG7AtRR047311@repoman.freebsd.org>
In-Reply-To: <200311160710.hAG7AtRR047311@repoman.freebsd.org>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200311152322.45260.wes@softweyr.com>
Subject: Re: cvs commit: src/sbin/fsck_ffs setup.c
X-BeenThere: cvs-src@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: CVS commit messages for the src tree <cvs-src.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/cvs-src>,
	<mailto:cvs-src-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/cvs-src>
List-Post: <mailto:cvs-src@freebsd.org>
List-Help: <mailto:cvs-src-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/cvs-src>,
	<mailto:cvs-src-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Nov 2003 07:22:47 -0000

On Saturday 15 November 2003 11:10 pm, Wes Peters wrote:
> wes         2003/11/15 23:10:55 PST
>
>   FreeBSD src repository
>
>   Modified files:
>     sbin/fsck_ffs        setup.c
>   Log:
>   Catch and report on filesystems that were interrupted during newfs,
>   sporting the new 'BAD' magic number.  Exit with a unique error code
>   (11) so callers who care about this can respond appropriately.

I expect someone will soon follow up with (perhaps several) better ways to 
code the BAD_MAGIC_MSG when the code is indented that far to the right.  
Thanks in advance for the help.  ;^)

-- 

        Where am I, and what am I doing in this handbasket?

Wes Peters                                               wes@softweyr.com