linux-8086.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
To: Georg Potthast 2 <nospam@georgpotthast.de>
Cc: Linux-8086@vger.kernel.org
Subject: Re: Elks networking
Date: Thu, 2 Feb 2017 16:47:29 +0000	[thread overview]
Message-ID: <20170202164729.4d145d4f@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <990587541.474117.1485858768986@com4.strato.de>

> So I recommend to modify the loader to use just 2k as the stack size limit (a configurable option). Should this turn out to be insufficient for a program it will terminate with "stack overflow" and one could reconfigure this limit. With currently available programs for ELKS I do not think this will happen though.

No they'll crash the machine generally unless you are in 286 protected
mode. Most of the ELKS tools do build with their stack size set.

Alan

  reply	other threads:[~2017-02-02 16:47 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-28 20:17 Elks networking Derek Johansen
2016-05-29  6:31 ` Jody Bruchon
2016-05-31  9:15   ` Marc-François LUCCA-DANIAU
2016-05-31 10:50     ` Alan
2017-01-22 10:37       ` Marc-F. LUCCA-DANIAU
2017-01-22 13:23         ` Marc-François LUCCA-DANIAU
2017-01-23 19:48           ` Marc-F. LUCCA-DANIAU
     [not found]             ` <CAMXth7QD+jMbeTx9YOvQnwd2FLvyvZ8F9Y-mjmdw5wLU6VHtuQ@mail.gmail.com>
2017-01-28  7:50               ` Marc-François LUCCA-DANIAU
     [not found]                 ` <CAMXth7SJWiuq7z4wgMNrL+dEhG40s=q9QrkMThOv3voj+6uh-Q@mail.gmail.com>
2017-01-29 13:43                   ` Fwd: " Marc-François LUCCA-DANIAU
2017-01-29 14:01                     ` Alan Cox
2017-01-29 19:51                 ` Georg Potthast
2017-01-30 12:13                   ` Georg Potthast 2
2017-01-30 20:08                   ` Marc-François LUCCA-DANIAU
2017-01-30 21:59                     ` Alan Cox
2017-01-31 10:32                       ` Georg Potthast 2
2017-02-02 16:47                         ` One Thousand Gnomes [this message]
2016-05-31 10:07   ` Alan

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=20170202164729.4d145d4f@lxorguk.ukuu.org.uk \
    --to=gnomes@lxorguk.ukuu.org.uk \
    --cc=Linux-8086@vger.kernel.org \
    --cc=nospam@georgpotthast.de \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).