site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com Not a linux fan ;) I prefer the BSD's. Though Solaris, AIX, and z/OS are quite interesting. -Juan On Jul 30, 2009, at 10:00 PM, Bill Northcott wrote: Horror horror horror: Darwin/MacOS is NOT Linux. Get used to it! ;-) So you see jails are not there, because you don't need them. Hope that helps you not to go off on some wild goose chase. Bill Northcott _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... I'm talking about running for example apache PHP, Perl in its own jailed environment so they think they are in their on box. Jails duplicate the root or specified directory structure and isolates whatever is running in it from everything else and I can assign resources to it Unless there's another way to replicate this. I'm going to just use FreeBSD. On 31/07/2009, at 5:03 AM, Juan wrote: I need to set up multiple development environments on my Macbook Pro and don't want to trash the default Mac OS X installs of apache etc... A Jail would simplify things considerably. I hope Mac OS X ports over FreeBSD Jails or Solaris Zones as soon as possible! Its sorely needed. Parallels or VMWare is over kill and resource intensive. Jails are lightweight. I really can't believe Jails aren't in Mac OS X. What a shock! That does not mean you cannot do what you you are trying to do. It just means you might need to think different. The big difference between Darwin and all the other UNIXen that I have used: Linux, Solaris, HP-UX, True64..., is in the shared library arrangement. At runtime other systems search some sort of shared library path to find an appropriate library to link. Darwin is different. The path to the linked shared libraries is written into an executable at static link time. At runtime, dyld (the launcher) will always look at that path first. It only uses the DYLD_LIBRARY_PATH if the library is not found at the right path. (do an 'otool -L' on any library or executable) So you can have as many virtual systems as you like, build and run using them and almost the only thing they need in common is the kernel (and maybe some GUI stuff if you use it). Look at the way Xcode uses SDKs and the systemroot and other useful compiler and linker options. (the linker is very different RTFM) This email sent to site_archiver@lists.apple.com