on 15:38 Wed 02 Mar, Steven VanDevender (ste...@uoregon.edu) wrote:
> Dr. Ed Morbius writes:
> > In the specific pathological case I'm thinking of (Dell's iSCSI
> > management tools), the net end result is rather poorly defined and spans
> > a significant chunk of the filesystem -- mostly under
Dr. Ed Morbius writes:
> In the specific pathological case I'm thinking of (Dell's iSCSI
> management tools), the net end result is rather poorly defined and spans
> a significant chunk of the filesystem -- mostly under /opt/dell, but
> some stray (and largely undocumented) bits, mostly under /
on 15:20 Wed 02 Mar, Steven VanDevender (ste...@uoregon.edu) wrote:
> Dr. Ed Morbius writes:
> > While you're considering providers, another case we encounter fairly
> > frequently are just general crap ISV or HW vendor-provided blob shell
> > installers. Usually a self-unpacking shell script,
Dr. Ed Morbius writes:
> While you're considering providers, another case we encounter fairly
> frequently are just general crap ISV or HW vendor-provided blob shell
> installers. Usually a self-unpacking shell script, which may itself
> include various internal packaging formats (tarballs, RP
on 10:54 Wed 02 Mar, Nigel Kersten (ni...@puppetlabs.com) wrote:
> On Wed, Mar 2, 2011 at 7:18 AM, Mike Lococo wrote:
>
> > So Russell, the short of it is that Puppet doesn't provide much to help you
> > manage source-installed software. You can apply puppet's features to other
> > software-mana
On Wed, Mar 2, 2011 at 7:18 AM, Mike Lococo wrote:
> So Russell, the short of it is that Puppet doesn't provide much to help you
> manage source-installed software. You can apply puppet's features to other
> software-management tools to roll something yourself, you can package the
> software, or
I am managing a fairly small set of machines (network security
monitors) and some of these packages are being installed on just two
or three boxes so spending a lot of time building packages is simply
not worth it. The apps are also updated fairly frequently and I need
to stay on the bleeding edge
russell.fulton wrote:
> I'll repeat the question from my previous post: Is there a straight
> forward way to have a local rpm repository on the puppet server
> rather than relying on yum and the RHE channels?
It's trivial to run createrepo /path/to/rpms to create the yum
metadata. You can then s
On Tue, Mar 1, 2011 at 8:13 PM, russell.fulton wrote:
>
> I'll repeat the question from my previous post: Is there a straight
> forward way to have a local rpm
> repository on the puppet server rather than relying on yum and the RHE
> channels?
Check out mrepo if you want to mirror another repos
On 3/1/2011 9:32 PM, Nigel Kersten wrote:
On Tue, Mar 1, 2011 at 5:40 PM, russell.fulton wrote:
I am managing a fairly small set of machines (network security
monitors) and some of these packages are being installed on just two
or three boxes so spending a lot of time building packages is simp
On Tue, Mar 1, 2011 at 5:40 PM, russell.fulton wrote:
> I am managing a fairly small set of machines (network security
> monitors) and some of these packages are being installed on just two
> or three boxes so spending a lot of time building packages is simply
> not worth it. The apps are also
11 matches
Mail list logo
