I have a couple of hundreds of EL3, working with no issues. I've done the same with EL4 srpm, and I'm seriously considering using eh RH5 ruby (to avoid all of the ugly ruby warnings) and backport if also for RHEL3 and RHEL4.
so basically, you need to get ruby up and running, than facter and everything should work busybox is just a wrapper for shell and common binaries usually intended to save memory usage (e.g. embedded devices), so if you are short in memory, probably puppet is not the right tool for you. Cheers, Ohad On Fri, Apr 24, 2009 at 11:00 AM, Matthew Hyclak <hyc...@gmail.com> wrote: > > On Thu, Apr 23, 2009 at 11:51 AM, paul matthews > <paulsmatth...@googlemail.com> wrote: > > When I say busybox it's actually VMware ESX server which seems to use > > busybox (which I guess is the case a number of other software appliances) > . > > Reason for wanting to install puppet is to run the cli tools to create > > nightly vmware snapshots. > > I'm happy to give it a go (and add the docs to the wiki) but I'm not too > > sure at this stage how big a task this might be and what, if any, are the > > potential pitfalls > > We rebuilt ruby 1.8.1-7 from EL4 on EL3, as well as facter and puppet, > and used it within the service console of ESX 3.5, but not in any > serious fashion as of yet. It looks like vSphere 4 (with host > profiles) will alleviate much of our need for puppet, so we're holding > off rolling it out to more than just a test box or two. We're trying > to get rid of the remainder of our EL3 boxes anyway :-) > > Matt > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
