4 ms·
OS X apps that 'shell out' to the BSD under-pinnings could be an issue. The CLI options can differ between Linux and BSD/Darwin.
by pyre 14y ago
OS X apps that 'shell out' to the BSD under-pinnings could be an issue. The CLI options can differ between Linux and BSD/Darwin.
- adamzegelin 14y agoA shim to handle common tools and remap the options would be feasible.
- chimeracoder 14y agoThat would seem to me to be the least of the problems. Just as you can install GNU coreutils on OS X, you can compile the BSD utilities to run on Linux as well.
- stcredzero 14y agochroot!
- pyre 14y agoI wasn't saying that it was impossible to run them. I'm just commenting on an issue that was immediately apparent to me. If a program calls '/usr/bin/nc' and expect BSD options, it's not going to get them. "Replace GNU coreutils with BSD coreutils" is an option, but not one that everyone would be ready to jump at, because now things running on your Linux system that expect GNU options won't be getting them.
- chimeracoder 14y agoYou can use chroot to solve this problem.
- pretoriusB 14y agoYou can use chroot, or you can have the OS X porting layer delegate those calls to the BSD tools transparently.
- deleted 14y ago[deleted]