Console ASCII interpretation
cpressey at catseye.mine.nu
Mon May 16 21:15:03 GMT 2005
On Mon, 16 May 2005 19:11:44 +0200
alexander <arundel at h3c.de> 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 about the freebsd-hackers