> In message <jum-1309982136490001@anubis.han.de>, Jens-Uwe Mager writes:
> +-----
> | Earlier (e.g 68k Macs) also stored code segments there, but nowadays most
> | code fragments reside in the data fork as one would expect with other
> | OS's.
> +--->8
>
> Ah, so they did change it to something rational.
>
> (Actually, the resources trick made sense with the way Apple's memory
> management worked on 68000s, where demand paging couldn't work --- but it
> was a hindrance to proper memory management on a 68020.)
This approach has one useful (sorta) side-effect: PowerPC code is stored
in the data fork, and 68K code is stored in the resource fork, so that
"fat" binaries are easy to make.
-- Kenneth Albanowski (kjahds@kjahds.com, CIS: 70705,126)
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/faq.html