From owner-freebsd-current@FreeBSD.ORG Fri Nov 5 10:06:29 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7B76A16A4CE for ; Fri, 5 Nov 2004 10:06:29 +0000 (GMT) Received: from smtp01.syd.iprimus.net.au (smtp01.syd.iprimus.net.au [210.50.30.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4577A43D5C for ; Fri, 5 Nov 2004 10:06:29 +0000 (GMT) (envelope-from tim@robbins.dropbear.id.au) Received: from robbins.dropbear.id.au (210.50.32.6) by smtp01.syd.iprimus.net.au (7.0.031.3) id 416A467C00B27656; Fri, 5 Nov 2004 21:06:27 +1100 Received: by robbins.dropbear.id.au (Postfix, from userid 1000) id 861B1425E; Fri, 5 Nov 2004 21:07:11 +1100 (EST) Date: Fri, 5 Nov 2004 21:07:11 +1100 From: Tim Robbins To: Dmitry Frolov Message-ID: <20041105100711.GA81646@cat.robbins.dropbear.id.au> References: <20041104175805.GA69815@nerve.riss-telecom.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041104175805.GA69815@nerve.riss-telecom.ru> User-Agent: Mutt/1.4.1i cc: freebsd-current@freebsd.org Subject: Re: cut(1) behaviour changed since 5.2.1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Nov 2004 10:06:29 -0000 On Thu, Nov 04, 2004 at 11:58:05PM +0600, Dmitry Frolov wrote: > [ Cc'ing tjr@ because he is the comitter of the change in question ] > > I'm experiencing a minor problem with cut(1) while trying to run shell > script (installer), written for FreeBSD 5.2.1, on 5.3-RC1 system. > > I don't know if it's really a bug, but if it is someone may want look > at it. The problem is that on 5.3 cut returns 'Illegal byte sequence' > (EILSEQ) error while parsing files without trailing newline, while on > 5.2.1 it doesn't. It looks like the behaviour was changed with the > revision 1.27 of the cut.c (about handling of multibyte characters). [...] I see the problem and I'll have this fixed soon. Tim