The topic of packages is one part of Linux I don't have much experience with. Could some else explain why the apt-get packages are frequently very outdated? I can understand not having the absolute latest version and not wanting to update immediately, but being months behind seems like a terrible idea.
Basically there are different ways to solve the problem, but as users install one version of a distribution, packages available for that version are built towards the libraries and other packages available.
Thus, any new updates to a package will impact all users that have version x of the system--without them necessarily wanting undesired changes--as well as potentially being dependant on newer libraries and other system packages. These dependencies can in some cases make it tricky to update just one package, as it'll require more -- and then you might want to test all of these packages to make sure everything else dependant on the same thing is still equally stable.
There are other approaches, like rolling distributions, but here you are aware of the risks and responsibilities you have as a user if you wish to keep your system stable.
I use it at home because it's fun and has the latest stuff. Never would use it for a server, though. For those and my own machine at work I like to use Debian Stable, although we use Ubuntu Server LTS at work.
Arch seems interesting for development, but sounds scary from a deployment standpoint. Even for a dev box it could get annoying to constantly worry about packages changing.
But occasionally something will randomly break, and it'll just drive you nuts.
One day I found that the touchpad on my laptop just wouldn't work. Another time I updated the kernel, and found that sound no longer worked at all.
I have been using it for over five years, and not had many problems, nor can I even claim that I have had fewer than when I upgraded between different Fedora versions... But upgrading a distro like fedora, you are prepared for something to break. With a rolling release, you never know when it may come.
All things considered though, I love it. At my job they have CentOS 6, where the system python is 2.6. The system tar doesn't understand what an xzip file is.
I vastly prefer Arch to that, although it is more stable, which is nice as a sysadmin.
There's a thing I've been wondering about for some time... isn't this "you can't update an package because that would require newer versions of library dependencies, which would require updates to other packages that rely on them..." approach an equivalent of an "DLL Hell" in Windows, if not worse?
In the case of Debian-stable, the whole point of it is that it doesn't change, except for fixes for security vulnerabilities and serious bugs, which get backported. New versions mean new features that might affect how your server functions, and require manual testing and recertification, which can be a lot of work. In an environment where you have a working server, you generally don't want to change anything unless you have to.
Taken to the extreme, consider RHEL. Their support lifetimes are enormous. RHEL4 for example shipped in February 2005, and is available under Extended Lifecycle support (at extra cost) until March 2017. There are companies that will conceivably be using gcc 3.4, Python 2.3, PHP 4.3, Apache 2.0, etc. in 2017 because those are all what were current when the distribution was stabilized leading up to that February 2005 release. The current release, RHEL7, will likely be available under Extended Lifecycle support until at least 2027, possibly later. (The official end of production is ten years after release, which is June 2024, and then after that for paying customers the extended phase has generally lasted 3 to 5 years.)
Generally speaking, if you're running a whole load of servers you don't want to have to test every single package that comes out to ensure it still works nicely with your configuration files, maintains backwards compatibility etc before updating. Debian (and to a slightly lesser extent Ubuntu) do this in the main repositories by basically locking packages to whatever the most recent tested version is at the time of that version of the OS being released. They do take any security updates and backport them to these earlier releases (while the OS itself is still supported), so that you're not running insecure software, but you won't get any significant new features and such until a newer version of the OS comes out, because they can't guarantee backwards compatibility between major release versions. It does mean, however, that you can pretty safely run an apt-get upgrade and not break stuff.
If you're not using the official distribution repositories, of course, anything goes. I run a network monitoring system called OpenNMS. It is available in the official repos, but it's an ancient version, and I needed newer features. So I have a repo configured that is run by the OpenNMS developers themselves. They test and run on older (but still supported) versions of Debian and Ubuntu, so I know it'll work, but I do have to check all the release notes and edit configuration files pretty much every time I do an update.
Your actually safe. NTFS uses capitalization but the windows virtual file system ignores this. So NTFS on linux shouldn't exhibit the same error NTFS on windows does.
Well, I enjoy writing @ instead of HEAD, for example. It sounds minor, but it’s really quite pleasant, and I imagine I’d be annoyed if I had to go back to a version without it.
You can use sub modules in a fruitful way if you’re on git 1.8.2 or later. Very useful when you have repository whose code is used in more than one of your other development projects.
0
u/[deleted] Feb 06 '15
[deleted]