From owner-freebsd-bugs Wed May 17 14:37: 0 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from uran.kharkiv.net (uran.kharkiv.net [194.44.156.30]) by hub.freebsd.org (Postfix) with ESMTP id C010F37B8B0; Wed, 17 May 2000 14:36:42 -0700 (PDT) (envelope-from vvc@kharkiv.net) Received: from localhost (vvc@localhost) by uran.kharkiv.net (8.9.3/8.9.3/uran) with ESMTP id AAA20075; Thu, 18 May 2000 00:36:35 +0300 (EEST) (envelope-from vvc@kharkiv.net) Date: Thu, 18 May 2000 00:36:35 +0300 (EEST) From: "Vadym V. Chepkov" To: hoek@FreeBSD.org Cc: freebsd-bugs@FreeBSD.org Subject: Re: Re: bin/17077 Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-2087214696-958599395=:19644" Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-2087214696-958599395=:19644 Content-Type: TEXT/PLAIN; charset=US-ASCII Hello! >Sorry, for this type of bug it's necessary to send a sample file >showing the problem or we simply don't know where to start (I couldn't >duplicate the problem). >The write() syscall certainly works correctly and is not what caused >you to see long lines that wrapped as-if they only had a \r terminating >character and no \n terminator. I already send example in send-pr report. There is another example.txt in attachment. You could duplicate problem just exec command 'cat example.txt' and 'more example.txt' and see difference I also send you ALL my `env` in env.txt if it will be usefull. Kind regards, Vadim V. Chepkov --0-2087214696-958599395=:19644 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="env.txt" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename="env.txt" UFdEPS91c3IvaG9tZS92dmMNClBBR0VSPWxlc3MNCkhPU1ROQU1FPXVyYW4u a2hhcmtpdi5uZXQNCkJMT0NLU0laRT1LDQpVU0VSPXZ2Yw0KTUFDSFRZUEU9 aTM4Ni1wYy1mcmVlYnNkMy4xDQpNQUlMPS92YXIvbWFpbC92dmMNCkVESVRP Uj12aQ0KU1NIX0NMSUVOVD0xOTQuNDQuMTU2Ljk5IDEwMDYgMjINCkxPR05B TUU9dnZjDQpTSExWTD0xDQpTSEVMTD0vdXNyL2xvY2FsL2Jpbi9iYXNoDQpI T1NUVFlQRT1pMzg2DQpPU1RZUEU9ZnJlZWJzZDMuMQ0KVEVSTT1jb25zMjUN CkhPTUU9L3Vzci9ob21lL3Z2Yw0KUEFUSD0vc2JpbjovYmluOi91c3Ivc2Jp bjovdXNyL2JpbjovdXNyL2xvY2FsL2JpbjovdXNyL2hvbWUvdnZjL2Jpbg0K U1NIX1RUWT0vZGV2L3R0eXAxDQpfPS91c3IvYmluL2Vudg0K --0-2087214696-958599395=:19644 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="example.txt" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename="example.txt" aHViLmZyZWVic2Qub3JnIWZyZWVic2Qub3JnIW93bmVyLWZyZWVic2QtcXVl c3Rpb25zCUxPQ0FMIVBST0dSQU1NCTE3OTcJMDA6MTQ6NDkgMTguMDUuMDAN Cg== --0-2087214696-958599395=:19644-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message