XPost: comp.sys.mac.advocacy, alt.os.linux.mandrake, comp.os.linux.advocacy   
   XPost: alt.os.linux.redhat   
   From: nospam@nospam.com   
      
   "TravelinMan"  wrote in message   
   news:Nowhere-578CA3.09052827042005@news1.west.earthlink.net...   
   > In article ,   
   > "LawsonE"  wrote:   
   [...]   
   >> Apple has been known to ship box-specific versions of their OS, but I   
   >> don't   
   >> know if that was so much for optimization as for making sure that you   
   >> couldn't share your OS disk with just anyone.   
   >   
   > Actually, I don't remember that they ever did that.   
   >   
      
   If you receive it with the box, it may not work with another model than the   
   one it was packaged with, IIRC.   
      
   > Every version of OS X (or Classic Mac OS for that matter) that I've ever   
   > received worked on the system that it came with PLUS all earlier   
   > systems. I've never run into a circumstance where you couldn't take the   
   > newest version and install it on all previous versions.   
   >   
   > You can't use today's version on tomorrow's hardware, but that's to be   
   > expected.   
   >   
   >   
   > But to get back to the original comment, I don't think it would be that   
   > hard. Apple has plenty of experience with fat binaries going back over a   
   > decade. There's no reason that Tiger can't have specific G5   
   > optimizations.   
      
   Sure, depending on how big is "fat." I don't think you can have "fat"   
   binaries in the MacOS X sense until AFTER the OS is initialized, since   
   they're part of a higher-order layer. IOW, you can't have a fat system   
   binary. You have to have it preconfigured for the specific box you want it   
   optimized for.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)