From owner-freebsd-questions@FreeBSD.ORG Sun Jul 8 16:21:02 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 BD6DD16A400 for ; Sun, 8 Jul 2007 16:21:02 +0000 (UTC) (envelope-from tundra@tundraware.com) Received: from eskimo.tundraware.com (eskimo.tundraware.com [66.92.130.161]) by mx1.freebsd.org (Postfix) with ESMTP id 750BA13C45A for ; Sun, 8 Jul 2007 16:20:57 +0000 (UTC) (envelope-from tundra@tundraware.com) Received: from [192.168.0.2] (ozzie.tundraware.com [66.92.130.199]) (authenticated bits=0) by eskimo.tundraware.com (8.14.1/8.14.1) with ESMTP id l68GKltv029580 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=NO); Sun, 8 Jul 2007 11:20:48 -0500 (CDT) (envelope-from tundra@tundraware.com) Message-ID: <46910EDC.10901@tundraware.com> Date: Sun, 08 Jul 2007 11:20:44 -0500 From: Tim Daneliuk Organization: TundraWare Inc. User-Agent: Thunderbird 1.5.0.12 (Windows/20070509) MIME-Version: 1.0 To: Lowell Gilbert References: <469056DE.40902@tundraware.com> <46908257.8060209@tundraware.com> <44hcof9dkm.fsf@Lowell-Desk.lan> In-Reply-To: <44hcof9dkm.fsf@Lowell-Desk.lan> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-tundraware.com-MailScanner-Information: Please contact the ISP for more information X-tundraware.com-MailScanner: Found to be clean X-tundraware.com-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-4.399, required 1, autolearn=not spam, ALL_TRUSTED -1.80, BAYES_00 -2.60) X-tundraware.com-MailScanner-From: tundra@tundraware.com X-Spam-Status: No Cc: freebsd-questions@freebsd.org Subject: Re: Enabling A Serial Port On 6.2 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: tundra@tundraware.com List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Jul 2007 16:21:02 -0000 Lowell Gilbert wrote: > Tim Daneliuk writes: > >> But ... the entry did not end with a newline and init apparently thus didn't >> recognize it. Ending the line made everything happy. I am submitting >> this as a (very minor) bug, since I do not believe this to be correct >> behavior (but what do I know ;) ... > > That's perfectly normal and age-old behaviour. Part of the definition > of a "line" of text is that it ends in a newline... Hmm - while I acknowledge that I've seen this problem before (I've used some variant of Unix since the late 1970s and FreeBSD since 2.x), whether it is "perfectly normal" is arguable. I suspect that there are a great many places - shell scripts and C source code leap to mind - where the lack of a terminating newline at the end of a file does not cause the line to be ignored altogether. I rather think this is an "age-old" bug that never got fixed because of its minor importance. In any case, i've authored a PR to make note of it. If I ever get the time, I'll dig into the source myself and see if I can figure out where the wheels are coming off... -- ---------------------------------------------------------------------------- Tim Daneliuk tundra@tundraware.com PGP Key: http://www.tundraware.com/PGP/