In searching for solutions to some problems with our OES2 SP2 NCS
cluster, i came across this document:
More details here:
http://www.novell.com/support/php/search.do?cmd=displayKC&docType=kc&externalId=InfoDocument-patchbuilder-readme5067744&sliceId=&docTypeID=DT_SUSESDB_PSDB_1_1&dialogID=120652101&stateId=0%200%20120650093
http://www.novell.com/support/php/search.do?cmd=displayKC&docType=kc&externalId=InfoDocument-patchbuilder-readme5067745&sliceId=&docTypeID=DT_SUSESDB_PSDB_1_1&dialogID=120652101&stateId=0%200%20120650093
My main questions:
1. The patch document states that all OES2 users should apply this
"scheduled maintenance". This seems to be something like a Service Pack
or Hot Patch - why isn't it called one of those things instead of
introducing a new, confusing term for it? I have seen no gossip about a
new patching strategy in Cool Solutions or the forums - is this just bad
patch release co-ordination by Novell?
2. The same versions referred to in the download page seem to be
available in yast online update. Why is this special in that it has a
separate download page? If i patch via yast, am i getting all the right
patches?
Thanks in advance,
Paul
I can't you answer your Questions, but a lot of my Cluster and Backup
Problems are resolved with this and a brand new "Cluster Stability Pack"
in OES2 Support Channel.
And i think, this is new Support Direction of Novell.
Only when you pay, you get Patches for buggy Products who are "brand
new" via Update Channels.
This is bad Time to doing it now, because most People have to go the new
Way. This let us Customer feeling only like a CashCow!
I understand Novell to get Money (they should).
This is one Way they can go. But they should have 2 Eyes! to not
overprized here Products now!
It is become hard, to argument with Management to pay now every Year
Maintenance to Novell when Microsoft put Updates for here Products out
for less.
And when i take a look at the Quality from actually Novell and Microsoft
Products seem to be going comparable.
I hold Novell so long as i can to avoid a complete Vendor Locking to
Microsoft, but this become harder and harder.
Ok, stopping crying now (or whe going in Chat) ;-)
Thomas
> In searching for solutions to some problems with our OES2 SP2 NCS
> cluster, i came across this document:
>
> http://www.novell.com/support/php/search.do?cmd=displayKC&docType=kc&externalId=7005280&sliceId=1&docTypeID=DT_TID_1_1&dialogID=120652101&stateId=0%200%20120650093
>
> More details here:
>
> http://www.novell.com/support/php/search.do?cmd=displayKC&docType=kc&externalId=InfoDocument-patchbuilder-readme5067744&sliceId=&docTypeID=DT_SUSESDB_PSDB_1_1&dialogID=120652101&stateId=0%200%20120650093
> http://www.novell.com/support/php/search.do?cmd=displayKC&docType=kc&externalId=InfoDocument-patchbuilder-readme5067745&sliceId=&docTypeID=DT_SUSESDB_PSDB_1_1&dialogID=120652101&stateId=0%200%20120650093
>
> My main questions:
>
> 1. The patch document states that all OES2 users should apply this
> "scheduled maintenance". This seems to be something like a Service Pack
> or Hot Patch - why isn't it called one of those things instead of
> introducing a new, confusing term for it? I have seen no gossip about a
> new patching strategy in Cool Solutions or the forums - is this just bad
> patch release co-ordination by Novell?
As far as I can tell this is just a round-up of all (or most) patches
that have been released up to that date, just bundled for convenience.
> 2. The same versions referred to in the download page seem to be
> available in yast online update. Why is this special in that it has a
> separate download page? If i patch via yast, am i getting all the right
> patches?
If you patch via YaST then yes you are getting all the right patches.
By having them available for download it's possible to grab them for
off-line servers.
HTH.
--
Simon
Novell Knowledge Partner (NKP)
------------------------------------------------------------------------
Do you work with Novell technologies at a university, college or school?
If so, your campus could benefit from joining the Novell Technology
Transfer Partners (TTP) group. See www.novell.com/ttp for more details.
------------------------------------------------------------------------
I think it was in November last year that Novell started bundling patches
end issue them in batches once amonth rather than making them available
individually. I don't know what was Novell's official reason for this, but
I can see 2 advanatages in this approach:
- it makes it more predictable to customers when patches become available
(like path Tuesday at MS) and customers can schedule a monthly patch session
- it probably makes it easier for Novell to test patches. In the past,
Novell had some serious quality problems with OES2 patches. This bundling
of patches probably allows Novell to "pool" test resources and potentially
allow better testing of the patches
The patches between support packs have existed ever since the realease of
OES. The only new thing is the monthly patch bundling.
--
Marcel Cox
http://support.novell.com/forums
------------------------------------------------------------------------
Marcel Cox's Profile: http://forums.novell.com/member.php?userid=8