linux-kernel - Re: [PATCH] Further update of the i386 boot documentation

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20070517164906.c7b96fe9.randy.dunlap@oracle.com>
Date:	Thu, 17 May 2007 16:49:06 -0700
From:	Randy Dunlap <randy.dunlap@...cle.com>
To:	Jeremy Fitzhardinge <jeremy@...p.org>
Cc:	"H. Peter Anvin" <hpa@...or.com>,
	Linux Torvalds <torvalds@...ux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] Further update of the i386 boot documentation

On Thu, 17 May 2007 16:30:44 -0700 Jeremy Fitzhardinge wrote:

> >>> +  If set to a nonzero value, contains a pointer to a null-terminated
> >>>   
> >>>       
> >> "nil-terminated"? "\0-terminated"?
> >>     
> >
> > Uh?  That seems more than a little silly.  Yes, I guess formally
> > speaking we're talking about "NUL-terminated", but the term
> > "null-terminated" has over 800,000 hits on Google -- 10 times as many as
> > "NUL-terminated" -- and is hardly an ambiguous term ("NUL-terminated" is
> > ugly, and "zero-terminated" is ambiguous.)
> >   
> 
> 0x00 or \0-terminated is idiomatic and unambigous.  Not a big deal
> either way.

I've mostly seen it as NUL-terminated.

---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/