From owner-freebsd-hackers@FreeBSD.ORG Mon May 16 21:15:03 2005 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 39EAD16A4CE for ; Mon, 16 May 2005 21:15:03 +0000 (GMT) Received: from priv-edtnes27.telusplanet.net (outbound04.telus.net [199.185.220.223]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7E8BE43D98 for ; Mon, 16 May 2005 21:15:02 +0000 (GMT) (envelope-from cpressey@catseye.mine.nu) Received: from catseye.biscuit.boo ([154.20.76.195]) by priv-edtnes27.telusplanet.netSMTP <20050516211459.UHPQ29154.priv-edtnes27.telusplanet.net@catseye.biscuit.boo> for ; Mon, 16 May 2005 15:14:59 -0600 Date: Mon, 16 May 2005 14:18:30 -0700 From: Chris Pressey To: freebsd-hackers@freebsd.org Message-Id: <20050516141830.6d0ea55e.cpressey@catseye.mine.nu> In-Reply-To: <20050516171143.GA19979@skatecity> References: <20050516171143.GA19979@skatecity> Organization: Cat's Eye Technologies X-Mailer: Sylpheed version 1.0.4 (GTK+ 1.2.10; i386-portbld-freebsd4.9) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: Console ASCII interpretation X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 May 2005 21:15:03 -0000 On Mon, 16 May 2005 19:11:44 +0200 alexander wrote: > Hi there. > > I'm using syscall number 4 write() to output data to stdout using x86 > assembly. When I try to output the following DWORD: 0x00003532 I get > the following output under Eterm and xterm: "25". Which is exactly > what I want. > > However when I do the very same under the console (using bash or sh. > It doesn't matter) I get this output: "25 ". > > I looked up the ASCII value for 00h and it says NUL. Doesn't that mean > that there shouldn't be any output at all? syscons and xterm implement different terminal emulations. xterm attempts to be compatible with a DEC VT102 and/or VT220, which treat NUL as non-printing. syscons doesn't aim to be compatible with anything in particular (so there is no standard to which it can be held to for rendering NUL as a blank space.) See the respective manual pages for more information. -Chris