Re: openSUSE as small bussiness server

On Mon, 29 Sep 2008, J G Miller wrote:-

Andreas Stieger wrote:
>>As uncounted posts here and in other places show the upgrade of a
>>community Linux is more or less a try and error procedure.

That is not the case with CentOS and Debian, and is not the policy,
unlike the attitude which *appears* to prevail with openSUSE.

I don't think it's either the policy or attitude of any of the
distributions, and certainly not openSUSE/Novell, that a version jump
should be a trial-and-error experience. The feelings of the users of the
various distributions may not hold the same attitudes though.

As for my own experience, on the times that I've started with vanilla
systems, I've never had problems where there's been a single version
jump, e.g. going from SuSE 9.1 -> 9.2 -> 9.3. Where I have had to do
some extra work, it's because I've added package from other sources,
including ones I've built myself. Even then, the extra work was quite
minimal.

*Almost* always these distributions can be upgraded from one
version to the next without any problems.

As I mentioned above, vanilla systems can be upgraded from one version
to the next. That's the only upgrade that is actually tested by
openSUSE/Novell to make sure it works.

Jumping over one, or many, releases can cause even more work to be
required. A jump from 10.3 to 11.1 will probably require some extra work
to be done, while even more would be needed when going from 10.2 or
10.1.

But as with everything, there is sometimes the exception to the rule --
but that has never meant installing from scratch.

That's something I'm going to have to do sometime in the future, but
it'll be 11.2 or 11.3 when I need do it. The reason for this fresh
install? The M/B on my 32bit 10.3 system died and so, as it's not easy
to get 32bit M/Bs, it was replaced by a new M/B with a 64bit CPU. After
sorting out things so the new kernel modules were loaded when booting,
the system was brought up and is running just fine[0]. When that system
gets upgraded, it will have to be a new install as I'll be moving it
over from a 32bit to a 64bit version.


[0] FSVO fine. I have to add a little extra cooling, since it's running
a little too warm for my liking when under full load.

Regards,
David Bolt

--
www.davjam.org/lifetype/ www.distributed.net: OGR@100Mnodes, RC5-72@15Mkeys
SUSE 10.1 32b | | openSUSE 10.3 32b | openSUSE 11.0 32b
| openSUSE 10.2 64b | openSUSE 10.3 64b | openSUSE 11.0 64b
RISC OS 3.6 | TOS 4.02 | openSUSE 10.3 PPC | RISC OS 3.11
.

Relevant Pages

  • Re: Upgrading to Snow Leopard
    ... Any time I upgrade the OS, I do a wipe clean and re-install too. ... So you like to waste your time. ... A little bit of extra work now often saves an awful lot of extra work ... who have had problems with an update install... ...
    (uk.comp.sys.mac)
  • Re: Using LoadCustomUI for Ribbons in 2007, but need to be able to compile in 2003
    ... You're already getting paid for the extra work (and some would argue getting ... paid for work you're not doing for the company who's paying but hasn't ... upgrade scheduled for 2010!! ...
    (comp.databases.ms-access)
  • Re: OpenVMS 7.2-1/Pathworks 6.0C NT4 Domain upgrade to Windows 2k3 Active Directory
    ... Currently the server pathworks server is configured ... your best bet is to upgrade VMS to 7.3-2 and upgrade from ... You could move the Alpha to its own domain (see above "extra work") ...
    (comp.os.vms)
  • Re: Upgrading 11 to 11i
    ... Upgrade itself is really easy. ... if you have separate file systems and /stand is too small you have some ... extra work. ... Paul ...
    (comp.sys.hp.hpux)
  • Re: Web vs. Desktop based systems
    ... provider with better privacy policy (perhaps Yahoo) also provides ... to other folder or reporting spam or changing the filter recipes. ... But how do you *really* know the important upgrade that keeps ... The alert-window doesn't exactly say *why* you need to install this ...
    (comp.programming)