Date: Sun, 08 Jul 2007 11:20:44 -0500 From: Tim Daneliuk <tundra@tundraware.com> To: Lowell Gilbert <freebsd-questions-local@be-well.ilk.org> Cc: freebsd-questions@freebsd.org Subject: Re: Enabling A Serial Port On 6.2 Message-ID: <46910EDC.10901@tundraware.com> In-Reply-To: <44hcof9dkm.fsf@Lowell-Desk.lan> References: <469056DE.40902@tundraware.com> <46908257.8060209@tundraware.com> <44hcof9dkm.fsf@Lowell-Desk.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
Lowell Gilbert wrote: > Tim Daneliuk <tundra@tundraware.com> 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/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?46910EDC.10901>