🚀 go-pugleaf

>	What are you talking about?
>
>			-Matt

HE REPLIES:
> Jim Budler                                   X   X
>
>Try the command `size /bin/*sh' sometime. This will display something like:
>text	data	bss	dec	hex
>65536	2048	19836	87420	1557c	/bin/csh
>18432	3072	16844	38348	95cc	/bin/sh
>The command `ls -l /bin/sh' gives:
>-rwxr-xr-x  1 root        68608 Jul 10  1983 /bin/csh
>-rwxr-xr-x  1 root        22528 Jul 10  1983 /bin/sh
>
>As you'll note, text + data is approx. file size.
>bss is `buffered storage space'.  This is preallocated space. The program
>will take a minimum of text + data + bss memory to run (although paging
>on a vmunix system can allow programs totaling more than physical
>memory, echh!)
>
>My point is that Unix systems store the file with one directory entry,
>then within an application, the first portion of the file ( the a.out
>header) defines where the text and data portions begin. On a mac
>there are two directory entries, one for the data fork, one for the
>resource fork.

	Foolish person, that is simply the executable format that someone
made up.  Object files have the same sort of format.  Fonts have different
formats.  Some backup programs use a vitual hierarchy format.  That has
nothing to do with the MAC's filesystem.  Try applying my last example to
the MAC's file format (NOT directory structure... single-file format).  You
can't.  Unix Files are exactly ONE contiguous stream, period.  Certainly the
executable format is similar, in a remote way, to the macs file format, but
the difference is that you are BOUND by the mac's file format for the entire
system, not just the executable.

				-Matt