8 ms·
In the ancient days, stuff the OS relied on was in /usr/sbin and stuff that was "yours" was in /usr/local/bin (or /opt) and stuff that no-one was quite sure who
by gaius 16y ago
In the ancient days, stuff the OS relied on was in /usr/sbin and stuff that was "yours" was in /usr/local/bin (or /opt) and stuff that no-one was quite sure whose it was was in /usr/bin. And lo, peace and harmony did reign upon the face of Unix. And the sysadmin did lie down with the developer, and it was good.
Who even knows how it works these days?
- nailer 16y agoStuff that belongs to the OS (but runnable by all users) is in /usr/bin. That's FHS. Stuff that's yours is wherever dir you specified when you ran: export WORKON_HOME=$HOME/.virtualenvs Seriously. Use virtualenv (and virtualenvwrapper). http://www.doughellmann.com/projects/virtualenvwrapper/ http://www.doughellmann.com/projects/virtualenvwrapper/
- dagw 16y agoWhat about stuff that belongs to me (the sysadmin) but runnable by all users? /usr/local/bin? /opt/bin? /my/homemade/solution/bin? There is a bunch of stuff that doesn't (shouldn't) belong to the OS, but still be runnable by all users without all of them needing a copy in their $HOME directory.
- munchhausen 16y agoYou answered your own question - /usr/local/bin. I don't know about MacOSX but on Linux, this is the solution to your problem - "stuff that belongs to me (the sysadmin) but runnable by all users".
- gaius 16y agoWell exactly. People who never learnt the old-skool ways always reinvent the wheel in an over-complex way. /usr/local/bin is stuff for the users, but which the sysadmin installs. So /usr/bin/python for the OS and /usr/local/bin/python for your users.
- nailer 16y ago> What about stuff that belongs to me (the sysadmin) but runnable by all users? If you're writing quick ad-hoc scripts and don't have time to package, /usr/local/bin. Per above, Python is used by your OS. It's installed by default, and not uninstallable, because the OS needs it. We can't and probably don't want to change that, so we'll need to live with it. Use virtualenv. if you need to to, install a quick Python 2.6 package that slots alongside your OS package rather than removing it - using RHEL 5 as an example, you'd install 'python26' alongside your existing 'python' package.
- uxp 16y agoNot to nitpick here, but I want to clarify something you said. > Per above, Python is used by your OS. It's installed by default, and not uninstallable, because the OS needs it. The OS doesn't need python. It is some package you have installed that needs python, like Gnome(py-gtk2) or KDE(py-qt), for your desktop environment or some application you decided you needed. If you don't understand what program on your server required python to be installed, then you shouldn't be administering a server. Having large numbers of language interpreters and compilers on a server can be considered a security risk, since after someone gains access, that provides him or her a large number of options of what kind of code he or she can run. Even having a C compiler is a risk, since code can then be compiled into programs already present on the system. Security should be first in mind when developing an application server. On the other hand for a development environment, there should be nothing stopping any distribution from installing multiple language interpreter versions. The default `/usr/bin/python` or `/usr/local/bin/python` can be a symlink to python25, python26 or python27, and when the user needs to run a different version, they explicitly call the binary with the version number. This whole virtualenv method just to parse a configuration file of a program not written in python seemed a little excessive.
- nailer 16y ago> The OS doesn't need python. It is some package you have installed that needs python No. The installer and packaging system need Python. Anaconda and Yum depend on it. Try removing it and see. You cannot install a minimal RHEL or Fedora system without Python. I am fairly sure this applies to other distros too.
- calloc 16y agoFreeBSD installs all packages in /usr/local/bin and /usr/local/sbin You can blow away your /usr/local and start from a new ports tree and build it all back up without adversely affecting the system. Everything system related is in /bin, /sbin, /usr/bin, /usr/sbin depending on whether it needs to be accessible when the system has just / mounted or when /usr is mounted as well. So in single user mode with just / mounted you have access to various different utilities. Mount /usr and you can expand upon that. Back in the old days when FreeBSD required perl in its base system switching to a newer version didn't break any of the base system tools (or maybe I just never noticed). There is something nice about a layout that is properly documented and makes sense: http://www.freebsd.org/cgi/man.cgi?query=hier&apropos=0&sektion=0&manpath=FreeBSD+8.1-RELEASE&format=html http://www.freebsd.org/cgi/man.cgi?query=hier&apropos=0&...
- zedshaw 16y agoPeople who don't do Python won't/can't use virtualenv. Also, you don't think that's a nasty workaround for something that should just be a non-issue? That's like you telling me to use NetBSD pkgsrc just to get around some ancient linux (which I have done).
- nailer 16y agoHi Zed. For the specific case of needing Python 2.6 on RHEL, ask your user to install the 'python26' package from EPEL. It's a semi official source of packages for RHEL including newer versions of OS tools that slot alongside those versions.
- zedshaw 16y agoOr, just rewrite in C and everyone except Python people will quit bitching. :-)
- nailer 16y agoIt seems nobody liked having a full language for default config file format anyway, so ditching it for something simpler may make people happier.
- bartl 16y agoThe problem with requiring an update to something like Python may break other programs. Not everything in Python (or Perl) is backward compatible.
- nailer 16y agoInstalling the 'python26' package doesn't update or change the installed Python in any way. That's why it was created. * 'python' remains installed, at version 2.4 * 'python26' is now installed, into separate folders.
- jacquesm 16y agoIf there is one thing that ticks me off about modern unix it is that to install <insert minor package here> I end up having to install / upgrade half the rest of the system because of all the interdependencies between packages.
- fauigerzigerk 16y agoExactly, and the baroqueness of package managers and the excentric configuration ideas of package writers are a symptom of that.
- gaius 16y agoTell me about it! I just wanted to install folding-mode for Emacs the other day, dselect wanted to install a new sodding IM client as well! (Something in emacs-goodies-el depended on it). About 50M it came to! So I just did it by hand, more like 50k...
- jacquesm 16y agoThat's an even more extreme example than the one that I just ran in to. Wow.
- johnzabroski 16y agoThat is a pretty wild example, but it is common in software today. Microsoft does stuff like this all the time, deprecating good .NET libraries for stupid ones just because of God knows what reasons (none of them intelligible to non-political folk).
- chousuke 16y agoThat sounds weird. Are you sure it wasn't a "Recommends" instead of a dependecy? If it really was a dependency, I think a bug should be filed against the package. :/
- statictype 16y agoI think that's more symptomatic of the open source culture around most Unix systems than Unix itself. Being able to share and depend on other people's libraries is great for the developers as long as they're not tied to providing support for when users can't compile or run their software.
- alexkay 16y agoIt's still like that in all BSDs.