From: Eli Zaretskii Newsgroups: comp.os.msdos.djgpp Subject: Re: size of _text+_data Date: Sun, 3 Oct 1999 13:07:30 +0200 Organization: NetVision Israel Lines: 13 Message-ID: References: <7t58e3$csm AT cs DOT vu DOT nl> NNTP-Posting-Host: is.elta.co.il Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Trace: news.netvision.net.il 938948775 23427 199.203.121.2 (3 Oct 1999 11:06:15 GMT) X-Complaints-To: abuse AT netvision DOT net DOT il NNTP-Posting-Date: 3 Oct 1999 11:06:15 GMT X-Sender: eliz AT is In-Reply-To: <7t58e3$csm@cs.vu.nl> To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com X-Mailing-List: djgpp AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk On Sat, 2 Oct 1999 Fokkema DOT DBRA AT delorie DOT com wrote: > You helped me very much with my far pointer problem (thank you all) so here > is another question: for my os, I link a loader along with it at the start > of the binary image. So on booting the floppy, the loader takes over and has > to load the entire kernel from disc. But how can the loader know the size of > the entire kernel? The size of every section is usually recorded in the header of the binary file. Each binary file format has its own way of recording this information; check out the `size' program from GNU Binutils which reports the size of each section.