Date: 6 Apr 96 09:03:47 GMT From: peter@jhome.DIALix.COM (Peter Wemm) To: freebsd-questions@freebsd.org Subject: Re: Stop^H^H^H^HRecofi^H^Hnfiguring tgo ^H^H^Ho gt^Hreater than 16Mbyte Tex^H^H^HProces ^Hs Text Segments Message-ID: <peter.828781427@jhome.DIALix.COM> References: <9604012138.AA24116@lazarus.nrtc.northrop.com>, <199604020051.RAA14857@phaeton.artisoft.com>
next in thread | previous in thread | raw e-mail | index | archive | help
terry@lambert.org (Terry Lambert) writes: >> >> Hi Folks, >> >> What's the majgic to reconfigure 2.FreeBSD 2.1 to support larger than >> 16Mbyte Text Segments? >stty erase >Just joking... >I assume you mean data size or something? We don't have user space >visible segments, we're a real OS... 8-). >Use the "limit" or "ulimit" command (it depends on your shell). No, this wont work above 16MB of text size, as the executable loaders have a limit on it. You *might* be able to get away with changing the MAXTSIZ in src/sys/i386/vmaram.h. Some other things may depend on this setting, I dont know. It's currently hardwired at 16MB and cannot be changed. IMHO, this sucks. MAXDSIZ and MAXSSIZ (for data and stack segments) can be overridden at config time. They are: 128MB data, 64MB stack. Those are rock solid limits and override the ulimit values. -Peter > Terry Lambert > terry@lambert.org >--- >Any opinions in this posting are my own and not those of my present >or previous employers.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?peter.828781427>