Just recently I found again that openSUSE is not really positioned for some usecases. In my personal case that is especially the usage as a web/mail/dns/etc server on hosted environments. IMHO it just doesn’t make sense to roll out a distribution which is supported for only 18 months to a hosted system with limited access to it. I still have been doing that with previous openSUSE releases but it’s so annoying that I really regret it. Also the possibility to zypper dup doesn’t really fix that issue for different reasons. Anyway this post is not about whining about that fact or to explain why I don’t like to update these type of systems remotely every <= 18 months.
A possible solution?
Sometime last year there was a discussion about options for something like an “openSLE” or “openSUSE LTS” distribution. There is an external page where some outcome was documented here. The dicussions stopped mainly because of health issues of the main initiator. There was done some planning and voting on the different options but no real results ever happened (as far as I know). So I’m trying to resurrect that topic a bit once again:
The amount of work related to such a project is the critical part and therefore my proposal is to try to start off with a “lightweight” approach.
This would be something like an openSUSE LTS version. That means that the community would take over (security) maintenance after Novell as main contributor drops it out of official maintenance after around 18 months. This will likely only work for a subset of packages which were delivered with the original distribution but the focus might be on server services anyway. Using the openSUSE release which also is the base for SLE could help us a bit as the work is done anyway (some of the Novell employees who are also openSUSE community members would hopefully help us here?). There are quite some details to work out still but it could be doable.
While I think we wouldn’t need a lot of people we at least need some and the more the better. We will bring that topic up again on opensuse-project@o.o as well. The main intention of this post is to get feedback if there is enough interest and contributors to do further planning. I’m very interested in hearing from you via comments, mailing lists or personal mail.
It is something that is missing from opensuse and will add a bonus.
If such a thing occurs i’m willing to help as a package maintainer. I haven’t any experience in packaging but i’m willing to learn.
A version of openSUSE with LTS would indeed be great. With apparmor and other nice features it is otherwise well-suited to servers, but these days I can only use openSUSE in VMs, where I have snapshots as well as VNC and consoles to access it in case of trouble with a dist-upgrade.
It’s a long long long idea I have, because most customers of that kind of distribution have a 3-5 years rolling IT process.
Someone tell me that it could be possible to do a SLES/D Ã la centos. If some subscription are take for getting the srpms from Novell and successors.
That could do the trick, because it will very light to maintain, and publish. With a rock solid base.
There’s so much to talk about. Ping me if you restart that project.
You could start at once. 🙂
I am still using OpenSuse 11.1 with a lot of SLES11 software from the build service.
OpenSuse 11.1 and SLES 11 seem to be binary compatible. Although I do not know whether this binary compatibility is 100% or not, OpenSuse 11.1 would be a nice place to start with this project: After almost two years of updates and very good support OpenSuse 11.1 can be considered as rock-solid and stable.
Opensuse 11.0 with KDE 3-5 desktop works so damn well on my desktop PC that I am very reluctant to change anything.
Now I have a bad problem this version is no longer maintained and all the Repositories in my Yast list are invalid. I am thus forced to upgrade but live in fear of messing up a sytem that works perfectly for me NOW.
I am most gratefull that your project will save me from having this same head ache in the future. This is good news Thanks.
PS I am just an enthusiatic user not a developer.
The OpenSuse 11.0 standard repositories are still available and can be used as online repos with Yast.
The update repo can be found here:
http://download.opensuse.org/update/11.0/
or
ftp://ftp5.gwdg.de/pub/opensuse/discontinued/update/11.0/
The OSS repo is here:
ftp://ftp5.gwdg.de/pub/opensuse/discontinued/distribution/11.0/repo/oss/
The Non-OSS repo also:
ftp://ftp5.gwdg.de/pub/opensuse/discontinued/distribution/11.0/repo/non-oss/
Even the ISO-Media are still provided:
ftp://ftp5.gwdg.de/pub/opensuse/discontinued/distribution/11.0/iso/
Most software from openSuse 11.1 works on OpenSuse 11.0, e.g. almost all software in the KDE 3.5-OpenSuse 11.1 buildservice repo.
Most OpenSuse 11.1 updates can be rebuild on OpenSuse 11.0 with the simple command:
rpmbuild –rebuild OpenSuse11.1packagename*src.rpm
Moreover, all modern browsers in their newest versions from their respective websites work well with OpenSuse 11.0 as well as Kernel 2.6.27.57 from kernel.org.
In this regard, OpenSuse 11.0 is still “safe”.
PS: I am not a developer, too.
Pingback: openSUSE 11.1 , a fi sau a nu fi LTS ? « Linux pentru incepatori
Pingback: Zombie Lizards! Evergreen brings 11.1 back from the dead | Daringsearch