Slashdot Mirror
OpenSUSE To Offer a Rolling Release Repository
dkd903 writes "While the rumors of Ubuntu moving to a rolling release have been brought to a halt, another major Linux distribution is looking to provide a rolling release. In a message to the opensuse-project mailing list, openSUSE developer Greg Kroah-Hartman announced a new project – openSUSE Tumbleweed. OpenSUSE Tumbleweed will provide a rolling release for those openSUSE users who wishes to have a rolling release. It will essentially be a repo containing the latest stable versions of the applications."
For those who want a Debian based distro Linux Mint Debian will be a rolling release. http://blog.linuxmint.com/?p=1527
by TheSpoom (715771) Uncaring Linux user here. I have nothing to add to this but please continue. *munches popcorn*
What I like about rolling releases is you get to deal with application incompatabilities one at a time as they come up, rather than having to spend a week or few all at once when upgrading a distro.
I think it's also probably better for security, as you get the latest patches for the software. (I know the security patches get applied to downlevel releases as well by distributors, but that seems so cumbersome compared to following the application's software releases.)
I do not fail; I succeed at finding out what does not work.
Please provide reliable market share statistics, I can't find any.
Change is certain; progress is not obligatory.
This is basically what Gentoo does. The only numbered releases they have are the annualish install discs. And if you go with the minimal install, even that doesn't draw much from the install medium, you download all the current packages.
I have to admit however that this is an issue of virtually all linux distros.
They confuse system software with user software
Ideally the system software should be fixed for a period to serve as a platform for developers, while user software would be constantly upgraded.
But alas, until this confusion is cleared you have to choose between having a stable platform or updated user software.
Rolling releases make horrible targets for 3rd party developers, specially shrink wrap software vendors.
On the other hand it is not true as you say that you don't know what release you are running or that you can't stay on that release.
When you are on a rolling distro you are effectively staying on a fixed and well know platform known as the current release . That's all you have to know when you ask for help in forums so it's not like you are lost in a limbo.
But... the future refused to change.
Yup, and in BSD land it works well. You update the system periodically, either just tracking security updates or updating to get new features, and you update third-party software independently. With FreeBSD, you have a choice of following the cutting edge branch (-CURRENT), which is not recommended for anyone except developers, the mostly-tested (-STABLE) branch, which is fine for people who want to play with new stuff, or a release branch (-RELENG) that has had some extra testing and generally only incorporates bug fixes between releases. Each port / package is flagged with the versions of the base system that it supports and can be updated individually. You never need to upgrade the kernel or core userland to get a new version of something like KDE or GNOME (unless it actually depends on a newer feature in the base system, which is very rare).
The problem for Linux distributions is that everything is a third-party package, aside from some distro-specific management tools. Most of the time, these tools are relatively unimportant - you can easily work without them. It gets even worse when you try to do back-ports, because some things like glibc and Linux are very closely tied - for example, the RHEL kernel contains a couple of back-ported system calls that don't have the their glibc wrappers, so you can only get at them by making the system call directly, rather than via the libc interface.
I am TheRaven on Soylent News
any stats will be very rough estimates and completely depend on what B.S. methodology you wish to use. I took distrowatches distro popularity page, took the top 23 which included everything I care about, and normalized Ubuntu 10%
Mint 8.6
Fedora 8.6
openSUSE 6.7
Debian 6.4
Sabayon 5.1
PCLinuxOS 4.3
Arch 4.1
Ultimate 3.5
CentOS 3.5
Puppy 3.5
Mandriva 3.2
MEPIS 3.1
Red Hat 3.0
Unity 2.8
Slackware 2.8
Chakra 2.7
Macpup 2.6
Tiny Core 2.5
Pinguy 2.4
BackTrack 2.2
FreeBSD 2.2
Gentoo 2.1
should have mentioned that's hit for last month (not the 12 month column they also have), and kept the FreeBSD in there for relative comparison purposes, since I care about BSD though not that particular one.
> Support for new hardware.
Removal of old, but still used hardware.
> New features.
More unneeded and unwanted API changes.
> Easier to contribute to development.
Harder to develop own applications for a faster movin target.
> Less obsolete versions of software.
More forced upgrades, more forced training costs, less bug fixes for older, but mission critical versions.
> No need to wait months or years to see stable released improvements on your system.
No way to avoid bad "improvements".
All in all, for commercial usage and development, this makes the situation even less predicatble and manageable than it is now. The target now moves even faster.
As somebody else already said, it is crucial for the Linux ecosystem to stop bundling applications and the base systems, and to unpredictably couple application updates to system updates. This unpredictability and instability is killing Linux in the enterprise. It needs a stable, very stable base companies can develop for without fear that they'll obsolete in 5 years or having to adapt to wild unpredictable API changes every 6 months.
Linux software may be "stable" in terems of performance, but it is the exact opposite in terms of development and long term planing, and this is killing it in the industry.