Date: Sun, 14 Dec 2008 10:40:14 GMT From: "Garrett Cooper" <yanefbsd@gmail.com> To: freebsd-bugs@FreeBSD.org Subject: Re: bin/129566: behavioral change of "read" builtin for sh on 8-CURRENT Message-ID: <200812141040.mBEAeEBC091647@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR bin/129566; it has been noted by GNATS. From: "Garrett Cooper" <yanefbsd@gmail.com> To: bug-followup@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@gmail.com> wrote: > On Wed, Dec 10, 2008 at 10:57 PM, Garrett Cooper <yanefbsd@gmail.com> wrote: >> On Wed, Dec 10, 2008 at 8:07 PM, Michael Proto <mike@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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200812141040.mBEAeEBC091647>