Berkeley CSUA MOTD:Entry 12920
Berkeley CSUA MOTD
 
WIKI | FAQ | Tech FAQ
http://csua.com/feed/
2025/04/07 [General] UID:1000 Activity:popular
4/7     

2004/3/29-30 [Computer/SW/OS/FreeBSD, Computer/SW/OS/OsX] UID:12920 Activity:high
3/29    I'm installing binaries for both OsX and Linux and I'd like all the
        users to have /usr/bin/<files> to be accessible. I thought about
        /usr/bin/<files> for generic stuff (like scripts) and
        /usr/bin/<platform>/<files> for platform specific things.
        What is the correct approach to this?
        \_ there are obviously several ways to do this, and "correct" is mostly
           relative. what you describe is probably the most typical way to
           do it though.
        \_ FreeBSD way: put all the base stuff in /usr/bin.  Platform supported
           stuff goes in /usr/local/bin (eg, ports and pkgs).  If you're not
           using the provided pkg management stuff, put it in /opt.
        \_ multiplatform support is a sysadm nightmare. Enjoy patching?
           Upgrading Perl/CPAN/emacs and all that crap? Now you've got
           2X the problem. There is only one correct way to deal with this.
           One OS, nothing else. The correct OS to use is FreeBSD.
           \- while the above post begs the question, i think there is
              a lot to be said for not worrying about having a shared
              dir for "sharable" codes. disk is cheap so i'd just ask to
              a lot of be said for not worrying about having a shared
              dir for "sharable" codes. disk is cheep so i'd just ask soon
              have disjoint os specific trees and not worry about duplication
              or keeping them in sync. --psb
        \_ Why would you want to do that?  Darwin and Linux do not have RW
           compatible drivers except for old fashioned HFS (no +).