Red Hat Enterprise Linux 5.5 patching

[Matty Sarro]

To be honest I suppose it isn't. However with Solaris you have the
option of downloading a rollup for any given day. You cannot do this
with yum, at least not running yum update (unless the downloadonly
plugin does that, i'm not familiar with it). You can then take this
rollup and apply it to any server and be assured that they are exactly
the same both in the lab and in production.

It's been hell trying to get servers updated initially, and then
keeping that as a baseline. I'll need to look into this downloadonly
plugin. Also, does it avoid the problem of yum refusing to install the
packages because they're signed? I've had a terrible time trying to
get updates installed on boxes, even when i disable the signature
check in the repo settings.

On Tue, Mar 8, 2011 at 9:09 AM, Paul M. Whitney <paul.whitney at me.com> wrote:
> I would consider building an identical "development" baseline so that you
> can connect to the Internet.  Register that system, then install the
> yum-downloadonly plugin. Once that is installed, you download all of the
> updates applicable to your system and then burn to CD and transfer to the
> "disconnected" box.  The only caveat is that "legally" you would need two
> subscriptions.
> Paul M. Whitney
> paul.whitney at me.com
>
> "Can't is the cancer of happen." - Charlie Sheen
>
>
> On Mar 08, 2011, at 03:49 AM, Dean Thompson <dnt07 at yahoo.co.uk> wrote:
>
>> Thanks. The system currently needing packages is not connected to the
>> internet.
>> I have an RHN account but I don't have any systems to register on there.
>> Can you
>> recommend any websites from which I can download rpm packages from?
>>
>>
>>
>>
>> ________________________________
>> From: Paul M. Whitney <paul.whitney at me.com>
>> To: General Red Hat Linux discussion list <redhat-list at redhat.com>
>> Sent: Mon, 7 March, 2011 15:53:47
>> Subject: Re: Red Hat Enterprise Linux 5.5 patching
>>
>> I believe Red Hat releases updates when one is warranted for either a bug
>> fix,
>> vulnerability, etc. The beauty with RHN is that the updates are available
>> quickly for you to most importantly mitigate vulnerabilities and you are
>> notified when these updates are available. I typically like to download
>> the
>> updates and test first in my "non-production" environment to ensure
>> nothing
>> breaks and then apply to production systems once I am certain the updates
>> do not
>> disrupt anything.
>>
>> Depending on the risk your customer is willing to accept on their systems,
>> quarterly might work, but I would suggest at a minimum monthly updates be
>> applied to the systems.
>>
>> Paul M. Whitney
>> 
>> "Can't is the cancer of happen." - Charlie Sheen
>>
>>
>> On Mar 07, 2011, at 07:26 AM, Dean Thompson <dnt07 at yahoo.co.uk> wrote:
>>
>> > Hi all
>> >
>> > A client wants to explore the different patching options we have for Red
>> > Hat
>> EL
>> > 5.5. The preference from the client's side would be to not connect to
>> > the RHN
>> > and rather have patching done once a quarter with officially released
>> > patches.
>> >
>> > Can you please tell me whether Red Hat releases quarterly patches
>> > similar to
>> >the
>> > way Solaris does it with the EIS dvd's?
>> >
>> >
>> > Regards
>> > Dean
>> >
>> >
>> >
>> >
>> > --
>> > redhat-list mailing list
>> > unsubscribe mailto:redhat-list-request at redhat.com?subject=unsubscribe
>> > https://www.redhat.com/mailman/listinfo/redhat-list
>> --
>> redhat-list mailing list
>> unsubscribe mailto:redhat-list-request at redhat.com?subject=unsubscribe
>> https://www.redhat.com/mailman/listinfo/redhat-list
>>
>>
>>
>> --
>> redhat-list mailing list
>> unsubscribe mailto:redhat-list-request at redhat.com?subject=unsubscribe
>> https://www.redhat.com/mailman/listinfo/redhat-list
>>
>
> --
> redhat-list mailing list
> unsubscribe mailto:redhat-list-request at redhat.com?subject=unsubscribe
> https://www.redhat.com/mailman/listinfo/redhat-list