public inbox for linux-8086@vger.kernel.org
 help / color / mirror / Atom feed
From: David Given <dg@cowlark.com>
To: Linux-8086 <linux-8086@vger.kernel.org>
Subject: Re: Regarding the Future of ELKS
Date: Sun, 06 May 2007 18:13:23 +0100	[thread overview]
Message-ID: <463E0CB3.30803@cowlark.com> (raw)
In-Reply-To: <20070506144640.2096fadc@the-village.bc.nu>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Alan Cox wrote:
[...]
> Not sure there is a spec per se but the ELKS system originally used minix
> format binaries (indeed I've used minix binaries on it). The later binary
> format fixes the minix 8086 design flaw where it puts the stack above the
> data. Instead ELKS puts the stack at the bottom of the data in a space
> size set at compile time. This allows brk() to work properly and avoids
> the chmem mess Minix has.

According to the ACK source, Minix uses PC/IX a.out files! I never even knew
the standard had a name. Minix i86 appears to use CPU 4, which matches the
ELKS a.out.h file.

Is there any way to distinguish between a Minix binary and an ELKS binary?

(Interestingly, putting the stack at the *bottom* of the data is exactly what
I did with the CP/M platform. In my case it was to make it easier for brk() to
tell where the end of the program area was. Strictly it shouldn't be necessary
for any platform to have a defined position for the stack; parameters can be
passed to the executable via registers, and then setting up the stack can be a
pure user-mode thing. I don't know if anyone actually does this, though.)

[...]
> If nobody ever did that fix to Minix it might be more useful to teach
> minix how to handle sane binary layouts and real memory allocation than
> ELKS hacking 8)

Can't comment on binary formats, but apparently someone is working on a real
VM for Minix 3, which should allow brk() to be actually useful. I'm hoping
that I can wait until then before porting the ACK's new build system...

- --
┌── dg@cowlark.com ─── http://www.cowlark.com ───────────────────
│ "Parents let children ride bicycles on the street. But parents do not
│ allow children to hear vulgar words. Therefore we can deduce that cursing
│ is more dangerous than being hit by a car." --- Scott Adams
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGPgyzf9E0noFvlzgRAhFCAKC6g/9TRkTvt8/Ed7a08LOyb7WbWACfetkH
wwapxf263425OWTpkevHxO8=
=pLwQ
-----END PGP SIGNATURE-----

-
To unsubscribe from this list: send the line "unsubscribe linux-8086" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2007-05-06 17:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-05 18:58 Regarding the Future of ELKS Jody
2007-05-05 22:10 ` Royce Williams
2007-05-05 22:14   ` NOTICE REGARDING SENDING MAIL TO THE ELKS LIST Jody
2007-05-06 10:08   ` Regarding the Future of ELKS Gábor Lénárt
2007-05-06 12:54   ` David Given
2007-05-06 13:46     ` Alan Cox
2007-05-06 17:13       ` David Given [this message]
2007-05-06 18:37         ` Alan Cox
2007-05-05 22:25 ` Mario Frasca
2007-05-06  9:23 ` Hans
2007-05-06 17:46 ` Luis A. Montes
2007-05-07 12:19 ` Mario Urban
  -- strict thread matches above, loose matches on Subject: below --
2007-05-07 18:12 chriscureau

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=463E0CB3.30803@cowlark.com \
    --to=dg@cowlark.com \
    --cc=linux-8086@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox