Re: openSUSE as small bussiness server

On Sep 30, 2:46 am, Vahis <waxb...@xxxxxxxxxxxxxxxxx> wrote:
On 2008-09-30, Artificer <eliezerfigue...@xxxxxxxxx> wrote:







According to my experience upgrading from 10.3 to 11.0 was like a couple
of hours at the beach :)

I've done several upgrades, even 10.0 to 10.2 was quite easy although there
was a version leap. That happened because I skipped 10.1 after trying it
for some time. That's the only version I've skipped after starting to
run Suse as my distro of choice.

This is probably, at least partially, due to my systems being close to
vanilla, only packman stuff added.

Coming from 10.3 to 11.0 was quite pleasant.
There you can change also packman and other extra repos on the fly
during the upgrading installation, so you miss all the "fun" of
temporary depency problems. These dependency problems used to be something
you had to deal with in upgrades prior to 11.0.

the 2 years of lifecycle for openSUSE what
really mean?

It means that after two years from publishing an openSUSE version Novell
stops security patching it.

Is Novell that provides the patches or opensuse.org? I mean is Novell
or the comunity the one that decided the 2-year lifecycle?

Novell sponsors the opanSUSE development team which administrates
openSUSE.

If I choose
to install openSUSE 11 and I dont want to upgrade every six months can
I just wait untill the end of the lifecycle and do upgrades only every
2 years? Will be hard to upgrade after two years of missing upgrades?

See my answer above. I have done both, as many others have and will.
First you need to know what you are using you system for, then you need
to maintain your goals. It obviously means installing and administrating
the current version as phase one.
In phases from there on you obviously install and test the upcoming new
versions on a test bed and decide whether you skip a version or upgrade
to that.

Just an example: I kept 10.0 as long as it lived because I didn't want
10.1 due to my testing period experiences.
I went from 10.0 to 10.2. I needed to because 10.0 was about to end.
10.2 was very good, but still I went to 10.3 due to my testring
experiences, I liked it and there was probably something I wanted then.
.
Then I changed to 64 bit HW. 11.0 was out, so I made a fresh install on
new HW. Now I'm on 11.0 and I've upgraded also the 32 bit machines.

Either way can be and has been done many, many times.

Great answer thanks. For your answers should I undertand that you are
using openSUSE on a production environment? Do you mind sharing what
are you using it for and how nice or wicked the experience has been?
.

Relevant Pages

  • Re: Fedora Core 6 ROCKS ! Salute to the developers !
    ... Upgrades leave rpmnew or rpmsave files, so short of losing out on technological changes, what would make one be better than the other. ... Merging config files from rpmsave or rpmnew files should serve the same function. ... After the install is done I try to figure out what needs to be changed and "bring forward" whatever I customized. ... Unsupported packages are even worse for a distro like Fedora or RHEL. ...
    (Fedora)
  • Re: Fedora Core 6 ROCKS ! Salute to the developers !
    ... Whenever I did my first clean install later on, ... Upgrades leave rpmnew or rpmsave files, so short of losing out on technological changes, what would make one be better than the other. ... So, on the laptop I mentioned, I edit /etc/sysconfig/iptables, /etc/fstab, etc. to bring them back to where I want while the various user rc and configuration files just get dropped into place. ... Unsupported packages are even worse for a distro like Fedora or RHEL. ...
    (Fedora)
  • Re: [opensuse] openSUSE (11.0) getting worse with the influence of KDE4 - Part #1: zypper
    ... Use either 11.0 or factory, ... If you add repos to 11.0, ... when I installed v11.0 (or after upgrades). ... But yast/zypper are just tools to install things. ...
    (SuSE)
  • Re: Upgrading to SBS2003 - realistic to do ourselves?
    ... the IT Pros because we are talking about a pretty long day of work. ... A scratch install of SBS remains on of the big lies of the business world. ... server is a typical 6 hr minimum process for scratch install. ... assumption that for an IT Pro...doing upgrades is a way to make money. ...
    (microsoft.public.backoffice.smallbiz2000)
  • Re: Warning: Beware of Office 2003 Service Pack 3
    ... that none of the reg keys that the upgrades were supposed to install and ... client has a bank that sends a credit-card account file to an internal ...
    (microsoft.public.windows.server.sbs)