From: Nigel Roles ngr@symbionics.co.uk
Subject: 386 maximum segment size of 16Mb
Date: Fri, 3 Nov 1995 03:33:51 -0500 [thread overview]
Message-ID: <19951103083351.UMjPUBYiu1_PR8nixX-DXJ77LDfezINUDVnggAreg_s@z> (raw)
>
> changing SEGMAPSIZE works fine.
> It incurs overhead allocated Segment structures
> so 16 seemed reasonable for a terminal. We really
> dont use PC's to compile.
>
>
Well, wouldn't you know. I was going to post all this yesterday, and
as we get up earlier in the morning this side of the pond, I would
have got there first. I fixed SEGMAPSIZE to 32, so must be half a
woos (?sp).
What you have to watch is the linker! It gets to 14 meg doing
9pcdisk; it gets to 20mb doing ghostscript, even without any useful
printer drivers added in (which was what I was doing). Anyone else
tried compiling in, say, HP deskjet support?
next reply other threads:[~1995-11-03 8:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-11-03 8:33 Nigel [this message]
-- strict thread matches above, loose matches on Subject: below --
1995-11-02 18:38 philw
1995-11-02 18:28 G.David
1995-11-02 17:14 G.David
1995-11-02 16:21 G.David
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=19951103083351.UMjPUBYiu1_PR8nixX-DXJ77LDfezINUDVnggAreg_s@z \
--to=9fans@9fans.net \
/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 NNTP newsgroup(s).