search for: maillists0

I want to upgrade a 5.4 box with the 2.618 kernel to a shiny new 2.6.32 kernel. Anyone done it? Is it possible? Are there gotcha's to watch out for? Any advice is appreciated. A link to a decent howto would be awesome. -------------- next part -------------- An HTML attachment was scrubbed... URL:

I''ve followed the howto at virtuatopia.com<http://www.virtuatopia.com/index.php/Building_a_Xen_Virtual_Guest_Filesystem_on_a_Disk_Image_%28Cloning_Host_System%29>to clone existing machines, then create them as PV guests. It has worked a couple of times for me, but I''ve run into a problem I don''t understand. When I run "xm create name", I get an error that

I inherited an office with phones that are hosted off-site. Everything is skinny and G729. I see that the FreeBSD asterisk port comes with a G729 codec. I want to record everything. If I use port mirroring on my switch, is it possible to configure asterisk to record and assemble packets that it doesn't otherwise route? Is it insane to user asterisk for this purpose? Advice or a link to a howto

...sk-users at lists.digium.com> > Message-ID: > <b74751490711291928n692877c3w84c9d03f49b00bf8 at mail.gmail.com> > Content-Type: text/plain; charset="iso-8859-1" > > chan spy does the job i belive > > ram > > On Nov 30, 2007 7:37 AM, Jeff Adams <maillists0 at gmail.com> wrote: > > > I inherited an office with phones that are hosted off-site. Everything > is > > skinny and G729. I see that the FreeBSD asterisk port comes with a G729 > > codec. > > I want to record everything. If I use port mirroring on my switch, is it...

I'm running the 2.6 xen kernel on CentOS 5.3. My goal is to use larger-than-normal ramdisks. I can see that the rd module is statically compiled into this kernel, so I tried passing the option ramdisk_size=262144 during boot, but dmesg shows that it gets reset to 16384K. I can also see that this is the size stipulated in the kernel config. Do I have to rebuild the kernel to make this work? If

No answers to this? Sorry if it''s a stupid question, but I was hoping it would be dead easy for someone here to answer. I''ve edited in case it wasn''t clear enough. We upgraded to 2.6.3 and we''ve suddenly noticed two and sometimes three puppet processes frequently running on the clients. Is this normal? Is it new to this version or are we just noticing it for

New to puppet and I just don''t understand how to do this. Apologies in advance if it''s a dumb question. Let''s say I have a module called httpd and inside that is a class called httpd::service, which accepts a couple of parameters: class httpd::service ( $running = ''running'', $enabled = ''true'', ) { service {