[ipxe-devel] [1c838002] memtest86+.bin vs. memtest86.bin?

Ivan Shmakov oneingray at gmail.com
Sat Aug 18 18:48:13 BST 2012

>>>>> Michael Brown writes:
>>>>> On Friday 17 Aug 2012 21:44:41 Ivan Shmakov wrote:


 >> chain /diskless/memtest86+.0
 >> # deal with the exit code here somehow?
 >> goto menu

 > In full, something like:

 >   chain memtest.0 && goto memtest_ok || goto memtest_${errno}

	ACK, thanks!  Somehow, I fail to find any mention of this
	“setting” on http://ipxe.org/.  (I've tried registering and
	logging in, but it hasn't allowed me to create the corresponding
	page myself, either.)

 >   :memtest_ok
 >   echo Memory test passed
 >   exit

 >   :memtest_0x1

	… Or, one can use ${errno:int32} and get somewhat simpler labels
	(:memtest_1, :memtest_2; hopefully there're no implications for
	errno's greater or equal to 0x80000000.)

	Now, with all these features in place, aren't we headed towards
	designing one more fully-featured programming language?  And if
	there's some chance that we are, wouldn't it be possible to stop
	and implement some language already in existence instead?  (Or
	are we doomed to repeat the history?)


 > Note in particular that ${errno} is set only when an error occurs.

	ACK, thanks.  (Just like in C.)


 >> … At the closer view, I don't seem to see any build options for
 >> Memtest86+ other than the .bin and ELF formats (or what was meant by
 >> “default memtest.bin” above?)


 > Check out the "pxe" branch from my memtest repository:

 > http://git.ipxe.org/people/mcb30/memtest.git/shortlog/refs/heads/pxe

 > Type "make" and you should get memtest.0 built alongside the usual
 > targets.

	ACK.  (Indeed, I've carried all my experiments with it so far
	using a PXE version I've built.  It's at [1], if anyone's
	interested.  Check also [2] for why I've put it there.)

[1] http://ritic.am-1.org/diskless/bin/memtest86+-1345195845.0
[2] news:868vdc1kyb.fsf_-_ at gray.siamics.net

FSF associate member #7257	http://sf-day.org/

More information about the ipxe-devel mailing list