bin/129566: behavioral change of "read" builtin for sh on 8-CURRENT

Garrett Cooper yanefbsd at gmail.com
Sun Dec 14 02:40:14 PST 2008


The following reply was made to PR bin/129566; it has been noted by GNATS.

From: "Garrett Cooper" <yanefbsd at gmail.com>
To: bug-followup at freebsd.org
Cc:  
Subject: Re: bin/129566: behavioral change of "read" builtin for sh on 8-CURRENT
Date: Sun, 14 Dec 2008 02:34:13 -0800

 On Thu, Dec 11, 2008 at 12:52 AM, Garrett Cooper <yanefbsd at gmail.com> wrote:
 > On Wed, Dec 10, 2008 at 10:57 PM, Garrett Cooper <yanefbsd at gmail.com> wrote:
 >> On Wed, Dec 10, 2008 at 8:07 PM, Michael Proto <mike at jellydonut.org> wrote:
 >>
 >> That is indeed a problem. Usually one EOL char would terminate read
 >> but now it's two.
 >>
 >> I'm reproducing this issue on an older version of CURRENT (~2.5 weeks
 >> old). I'll try looking through the commit logs for anything fishy...
 >>
 >> -Garrett
 >
 >    None of the changes in .../src/bin/sh are causing this (I rolled
 > back all files individually changed in the past 2 years and I couldn't
 > find any problem files). It's most likely related to the MPSAFETTY
 > changes.
 >    It'd be nice to use a livefs CD from before the MPSAFETTY changes
 > were merged in to verify this.
 > -Garrett
 
 Cannot reach originator via email. Please change originator contact to
 my email address (gcooper@) until another one can be established as I
 can easily reproduce this issue.
 -Garrett


More information about the freebsd-bugs mailing list