[chef] Re: Re: Re: RHL 4

["steve ." < >]

It might actually be less of a headache to stand up CI on a RHEL4 host and try to get chef-omnibus working on that platform.  That would give you a single versioned package to install that would yield a modern, patched Ruby and all gem dependencies.

I remember doing this on RHEL5 without omnibus in the bad old days, so I'm sure it's possible with RHEL4... but I didn't have a great time doing it that way and omnibus seems like a better way to go.  If I were in your shoes now, I'd investigate that first.

Good luck!

On Tue, Jul 23, 2013 at 1:29 PM, Damien Roche < " target="_blank"> > wrote:

Thanks eric appreciate the info.  rhl4 is in our supported os roadmap for at least the short term.

On 15 Jul 2013 21:59, "Wolfe, Eric G" < " target="_blank"> > wrote:

Best bet is a Rubygem install of Chef.  You also need yum on the RHEL4 machine to satisfy the Chef yum provider.

I have 3 remaining RHEL4 machines.  Automating those legacy machines will accelerate migration to RHEL6 in my case.

Something to consider, will Chef accelerate a migration in the future, or could you forgo automating your legacy system and just rebuild the application faster on a newer release of RHEL?

I would go with the least amount of effort.  It is worth it to automate the legacy if it will save time/effort down the road.

" " target="_blank"> " < " target="_blank"> > wrote:


Hi All,

New to the lists here. I've recently discovered that I need to support RHL-4 at least in a deprecation phase.

Has any one experience installing the client on RHL-4?
What's needed to get the chef-client installer working for RHL-4 ?

Thanks
D.