From mboxrd@z Thu Jan 1 00:00:00 1970 From: Harry Kalogirou Subject: Re: Adventure - the answer to what went wrong? Date: 12 Dec 2002 22:21:13 +0200 Sender: linux-8086-owner@vger.kernel.org Message-ID: <1039724471.2746.21.camel@cool> References: <200212121911.gBCJB75G012842@eddie.loc> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-/aIr67lSrGrVQqoJkGqO" Return-path: In-Reply-To: <200212121911.gBCJB75G012842@eddie.loc> List-Id: To: Richard Wallman Cc: Linux 8086 --=-/aIr67lSrGrVQqoJkGqO Content-Type: text/plain Content-Transfer-Encoding: quoted-printable > Gave it a bit of thought today, and I think I know what happened. >=20 > Looking at the libc sources, it looks like the strcmp and strncmp > functions assume that both strings are in the same 64Kb segment. (There > may be other functions that make this assumption as well, but I haven't > really looked). They assume right! In ELKS DS=3DSS=3DES. By the way, the CVS ELKS tree solves many memory problems but requires a patch to the linker that I posted here some time ago and never got in the linker tree... :( Harry --=-/aIr67lSrGrVQqoJkGqO Content-Type: application/pgp-signature; name=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQA9+O+3XrjIZPA34x8RAraoAKCtAnAtJzXpFtjAgQr1LrvT9NCEawCgoCiM N8pjay1ez01EJ5lK1nVd6Fs= =hZTR -----END PGP SIGNATURE----- --=-/aIr67lSrGrVQqoJkGqO--