{"id":314,"date":"2009-10-19T01:49:27","date_gmt":"2009-10-19T06:49:27","guid":{"rendered":"http:\/\/yourlinuxguy.com\/?p=314"},"modified":"2009-10-23T17:23:33","modified_gmt":"2009-10-23T22:23:33","slug":"have-oes2sp1-on-linux-watch-out-for-sles10sp3","status":"publish","type":"post","link":"https:\/\/yourLinuxGuy.com\/?p=314","title":{"rendered":"Have OES2sp1 on Linux? Watch out for SLES10sp3…"},"content":{"rendered":"

While working with a customer today, we were solving some silly problems that cropped up while patching his OES2sp1 Linux servers.\u00a0 Some nonsense about Mozilla dependencies on 64-bit servers (see Novell TID 7004278<\/a> for details on that). But that’s not what I’m here to discuss today…<\/p>\n

Anyway, since SLES10sp3 came out in the past few days, a simple behavior has come to my attention.\u00a0 If you run “zypper up<\/code>” on a standard SLES server, for instance, it will perform the “move-to-sles10-sp3<\/code>” patch and do what it sounds like it will do.\u00a0 This is a good thing on a SLES server as far as I can tell so far.\u00a0 Even my iFolder 3.7.2 seems to love sp3.<\/p>\n

Also, I’ve patched a small handful of OES2sp1 servers using the command “rug up -t patch OES2-SP1-Updates SLES10-SP2-Updates<\/code>“.\u00a0 And (until today) by default, they did *not* perform the “move-to-sles10-sp3<\/code>” as one would expect them not to, since it might break the OES2sp1 install in some ways that I don’t know or want to know.<\/p>\n

So today, the third OES2sp1 server we were patching today suddenly prompted me with the *warning* (to which I must agree to continue) that it was going to do the migration to sp3!\u00a0 Argh! I scrolled back up to see the list of patches, and it did even have the “move-to-sles10-sp3<\/code>” patch in the list.\u00a0 Hmm… Okay, that scared me enough.\u00a0 A quick “rug lu<\/code>” shows that it is still listed as an optional patch…\u00a0 Hmm…<\/p>\n

Honestly, I’m not sure what is going on here, but I wanted to make sure my regular readers\/customers\/friends are aware of this (if you’re an enemy of mine, go ahead and install it and tell me how it goes…), and warn that as far as I can tell, running sp3 underneath OES2sp1 is not a good (or supported) thing. Not until OES2sp2, from what I understand.<\/p>\n

So I want to update the recommendation I’ve made here in the past<\/a>.\u00a0 My new preferred method of patching OESsp2-Linux servers is this:<\/p>\n

rug up -t patch -g security -g recommended<\/code><\/p>\n

…or optionally specify the channels too…<\/p>\n

rug up -t patch -g security -g recommended OES2-SP1-Updates SLES10-SP2-Updates<\/code><\/p>\n

By specifying the “security<\/code>” and “recommended<\/code>” types, you avoid the “optional<\/code>” type, which is where the “move-to-sles10-sp3<\/code>” update resides.<\/p>\n

In the end, no matter what we did with this one server, it still tried to do the “move-to-sles10-sp3<\/code>“.\u00a0\u00a0 So we kinda’ threw in the towel and ran the “Desktop Updater” from the GUI, which is Novell’s only other recommend method of installing updates.\u00a0 And *it* did not prompt us to accept the sp3 update, just standard kernel warnings.\u00a0 Phew!<\/p>\n

If you know more about this, please share with us.\u00a0 Also, I’ll update this post as discover more… Good luck out there…<\/p>\n

\ud83d\ude1b<\/p>\n

Updates:\u00a0 SLES10SP3 Release notes<\/a>, Press Release<\/a>, …<\/p>\n","protected":false},"excerpt":{"rendered":"

While working with a customer today, we were solving some silly problems that cropped up while patching his OES2sp1 Linux servers.\u00a0 Some nonsense about Mozilla dependencies on 64-bit servers (see Novell TID 7004278 for details on that). But that’s not…
Read more<\/a><\/p>\n","protected":false},"author":5,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[11,13,72],"tags":[],"class_list":["post-314","post","type-post","status-publish","format-standard","hentry","category-intermediate","category-oeslinux","category-rug"],"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/pnjn1-54","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/yourLinuxGuy.com\/index.php?rest_route=\/wp\/v2\/posts\/314","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/yourLinuxGuy.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/yourLinuxGuy.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/yourLinuxGuy.com\/index.php?rest_route=\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"https:\/\/yourLinuxGuy.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=314"}],"version-history":[{"count":7,"href":"https:\/\/yourLinuxGuy.com\/index.php?rest_route=\/wp\/v2\/posts\/314\/revisions"}],"predecessor-version":[{"id":317,"href":"https:\/\/yourLinuxGuy.com\/index.php?rest_route=\/wp\/v2\/posts\/314\/revisions\/317"}],"wp:attachment":[{"href":"https:\/\/yourLinuxGuy.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=314"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/yourLinuxGuy.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=314"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/yourLinuxGuy.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=314"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}