Anonymous_User Absent Member.
Absent Member.
1066 views

Updates and Patches for OES Linux

Hi all!
What's the diference betwen Updates and Patches? Both appears in the Red
Carpet update manager in OES Linux. And is there anyway to do automatic
updates in one server and all the other OES Linux Server can get the updates
from this server? Is there anyway to do this?

Tks,
Alan Cota.


Labels (2)
0 Likes
6 Replies
Anonymous_User Absent Member.
Absent Member.

Re: Updates and Patches for OES Linux

An update is a new version of the package, a patch is a new revision to
an existing package to fix an issue... Of course there are some updates
that will fix issues with an older package but im sure you get the idea...

Yes, there is a way to setup a red-carpet server... The explanation is
a bit lengthly for me to describe but here is the red-carpet
administrators guide...
http://support.novell.com/docs/ProductDoc/ximian/rcserver/rcserver.html

Hope that helps!

-scz

Alan Cota wrote:
> Hi all!
> What's the diference betwen Updates and Patches? Both appears in the Red
> Carpet update manager in OES Linux. And is there anyway to do automatic
> updates in one server and all the other OES Linux Server can get the updates
> from this server? Is there anyway to do this?
>
> Tks,
> Alan Cota.
>
>

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Updates and Patches for OES Linux

Scott Zentz wrote:
> Yes, there is a way to setup a red-carpet server... The explanation
> is a bit lengthly for me to describe but here is the red-carpet
> administrators guide...
> http://support.novell.com/docs/ProductDoc/ximian/rcserver/rcserver.html


Note that this requires purchasing RCE (now known as Zenworks 7). There
used to be a great free alternative called open-carpet done by one of
the Red Carpet devs, but the domain seems to have gone offline:

http://www.open-carpet.org

Fortunately, I still have an rpm for OES Linux that I built that should
work fine on SLES9 or any SuSE platform for that matter (its python based):

http://packages.jwgnetworks.com/novell/oes/9/i586/open-carpet-0.3-jwg.1.i586.rpm


--
Justin Grote
Novell Support Connection Sysop
Network Architect
JWG Networks
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Updates and Patches for OES Linux

If an update fix a path issue will the patch show as installed in Red Carpet
? Also, I've saw a post smewhere that said not to use the Red Carpet GUI. Is
this still valid ? Whats the différence between Yast Online Update and Red
Carpet ? Finaly, how can I tell if a patch is pre- or post an update ?

Thanks a lot,

Louis-Steve Desjardins


"Justin Grote [SysOp]" <jgrote@jwgnetworks.com> a écrit dans le message de
news: 7ETog.12547$tN4.5425@prv-forum2.provo.novell.com...
> Scott Zentz wrote:
>> Yes, there is a way to setup a red-carpet server... The explanation
>> is a bit lengthly for me to describe but here is the red-carpet
>> administrators guide...
>> http://support.novell.com/docs/ProductDoc/ximian/rcserver/rcserver.html

>
> Note that this requires purchasing RCE (now known as Zenworks 7). There
> used to be a great free alternative called open-carpet done by one of
> the Red Carpet devs, but the domain seems to have gone offline:
>
> http://www.open-carpet.org
>
> Fortunately, I still have an rpm for OES Linux that I built that should
> work fine on SLES9 or any SuSE platform for that matter (its python
> based):
>
> http://packages.jwgnetworks.com/novell/oes/9/i586/open-carpet-0.3-jwg.1.i586.rpm
>
>
> --
> Justin Grote
> Novell Support Connection Sysop
> Network Architect
> JWG Networks



0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Updates and Patches for OES Linux

Louis-Steve Desjardins wrote:
> If an update fix a path issue will the patch show as installed in Red Carpet
> ?


No. The update will be shown as installed in the RPM system, but the
patch won't be listed as installed unless you use rug pin.

This is only a cosmetic difference, as if you attempt to rug pin a
package afterwards, it will download the package, attempt to install it
with rpm -Fvh (which will not install the update if it is already
present) and then mark the patch as installed.


> Also, I've saw a post smewhere that said not to use the Red Carpet GUI. Is
> this still valid ?


Post-SP2, it should be OK to use the Red Carpet GUI.

> Whats the différence between Yast Online Update and Red
> Carpet ?


Yast Online Update is the old system, Rug is the new system after Novell
bought Ximian 🙂

It's kind of a mess in OESv1, but sles10 (and the forthcoming OESv2)
fixes all this by introducing a revamped package management system and a
new version of red carpet (now called Zenworks Linux management) that
integrates all this together. Try out the SLES10 prerelease to see it in
action:

http://www.novell.com/linux/prerelease.html

It's quite slick and pushes all of the SLES9 confusion out of the way.


> Finaly, how can I tell if a patch is pre- or post an update ?


Officially, you should not use rug update, and only use rug pin to apply
patches. Rug update is a "side effect" of the patching process.

http://tinyurl.com/ajtdk

In reality, rug pin is basically the grafting of the YoU patch process
into red carpet, with mixed success. It works, but it downloads all the
patches even if you don't have the products installed, finding
individual patches is obtuse, it doesn't do dependency checking, and you
can't apply package locks.

Rug update is the original and native red carpet function, does pretty
much the exact same thing as rug pin and provides all the same updates
as rug pin, only provides more features and is more reliable IMHO.

Use rug pin if you want to make sure your system will stay "supported"
so you can call Novell and get help, but if you don't care about that,
use rug update. I use it on all my servers and it works just fine.

--
Justin Grote
Novell Support Connection Sysop
Network Architect
JWG Networks
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Updates and Patches for OES Linux

Hi all. Thank you for the help but I still have some questions to do.
For sample, I did't understood how to create a OES Linux patch server were
all of my other OES Linux server will get updates from this server. I need
to use ZenWorks 7.0 and I must install the product in my environment or I
can use Red Carpet to update all of the servers from single point?

Tks again!

Best regards,
Alan Cota.


"Justin Grote [SysOp]" <jgrote@jwgnetworks.com> wrote in message
news:FAVog.12694$tN4.2545@prv-forum2.provo.novell.com...
> Louis-Steve Desjardins wrote:
>> If an update fix a path issue will the patch show as installed in Red
>> Carpet
>> ?

>
> No. The update will be shown as installed in the RPM system, but the
> patch won't be listed as installed unless you use rug pin.
>
> This is only a cosmetic difference, as if you attempt to rug pin a
> package afterwards, it will download the package, attempt to install it
> with rpm -Fvh (which will not install the update if it is already
> present) and then mark the patch as installed.
>
>
>> Also, I've saw a post smewhere that said not to use the Red Carpet GUI.
>> Is
>> this still valid ?

>
> Post-SP2, it should be OK to use the Red Carpet GUI.
>
>> Whats the différence between Yast Online Update and Red
>> Carpet ?

>
> Yast Online Update is the old system, Rug is the new system after Novell
> bought Ximian 🙂
>
> It's kind of a mess in OESv1, but sles10 (and the forthcoming OESv2)
> fixes all this by introducing a revamped package management system and a
> new version of red carpet (now called Zenworks Linux management) that
> integrates all this together. Try out the SLES10 prerelease to see it in
> action:
>
> http://www.novell.com/linux/prerelease.html
>
> It's quite slick and pushes all of the SLES9 confusion out of the way.
>
>
>> Finaly, how can I tell if a patch is pre- or post an update ?

>
> Officially, you should not use rug update, and only use rug pin to apply
> patches. Rug update is a "side effect" of the patching process.
>
> http://tinyurl.com/ajtdk
>
> In reality, rug pin is basically the grafting of the YoU patch process
> into red carpet, with mixed success. It works, but it downloads all the
> patches even if you don't have the products installed, finding
> individual patches is obtuse, it doesn't do dependency checking, and you
> can't apply package locks.
>
> Rug update is the original and native red carpet function, does pretty
> much the exact same thing as rug pin and provides all the same updates
> as rug pin, only provides more features and is more reliable IMHO.
>
> Use rug pin if you want to make sure your system will stay "supported"
> so you can call Novell and get help, but if you don't care about that,
> use rug update. I use it on all my servers and it works just fine.
>
> --
> Justin Grote
> Novell Support Connection Sysop
> Network Architect
> JWG Networks



0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Updates and Patches for OES Linux

Alan Cota wrote:
> Hi all. Thank you for the help but I still have some questions to do.
> For sample, I did't understood how to create a OES Linux patch server were
> all of my other OES Linux server will get updates from this server. I need
> to use ZenWorks 7.0 and I must install the product in my environment or I
> can use Red Carpet to update all of the servers from single point?


Officially, yes, you need Zenworks, and use the rug mirror feature.
http://www.novell.com/coolsolutions/feature/15523.html

Unofficially, all the updates are just RPMs, so you can use open-carpet
to build your own red carpet server like the one I run at
packages.jwgnetworks.com and my undisclosed red carpet server for my
clients :). Unfortunately the opencarpet.org site is offline, but I
provide an RPM for OES:

http://packages.jwgnetworks.com/novell/oes/9/i586/open-carpet-0.3-jwg.1.i586.rpm

Alternatively, all packages are cached at /var/cache/rcd/packages if you
use the rug update method, and /var/cache/rcd/patch-data if you use the
rug pin method, so you can simply make an NFS mount on either of these
directories to a local server. That way when servers update, they pull
all the updates from your local NFS server. This is the way I usually
recommend to my clients, just make sure you make it a "soft" mount, or
you might hang your server if your NFS goes offline.


--
Justin Grote
Novell Support Connection Sysop
Network Architect
JWG Networks
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.