From tmattox at gmail.com  Thu Jul  1 17:35:49 2004
From: tmattox at gmail.com (Tim Mattox)
Date: Thu, 1 Jul 2004 20:35:49 -0400
Subject: [cAos] FW: [Warewulf] cAos certified installed but doesn't boot
In-Reply-To: <380C0AED4D502940A061BFD92C0EDD3E412DAC@ccc2003.4cd.net>
References: <380C0AED4D502940A061BFD92C0EDD3E412DAC@ccc2003.4cd.net>
Message-ID: <ea86ce22040701173543833cb5@mail.gmail.com>

Hello Milen,

On Thu, 1 Jul 2004 10:57:04 -0700, Fong, Milen <mfong at contracosta.edu> wrote:
[snip]
>Problem is that when I try to have other nodes PXE boot I get the
following message on the slave node. I followed the steps from the
HowTo from www.warewulf-cluster.org site.
> 
> Client IP: 10.1.0.1 Mask: 255.252.0.0
> DHCP IP: 10.0.0.1
> Gateway IP: 10.0.0.1
> TFTP.
> PXE-T02: Access Denied
> PXE-E3c: TFTP Error - Access Violation
> PXE-M0F: Exiting Broadcom PXE ROM

Hmm, it looks like either the tftpd isn't configured correctly, the
eb-[whatever].zpxe file isn't globally readable, or maybe the dell's
PXE is one of the "broken" ones that I've heard about.
Can you post an "ls -laR /tftpboot" from the server,
as well as "chkconfig --list tftp"

Are there any relevant error messages in the server's
/var/log/messages pertaining to the tftp?  Please post a snippet
including every line from the DHCPDISCOVER onwards.

> Is there some access privileges I need to assign?

The wwmaster.initiate script should have taken care of
setting up the tftp, so the likely thing is that your eb-[whatever].zpxe
file isn't readable.
--
Tim Mattox - tmattox at gmail.com - http://homepage.mac.com/tmattox/


From geoff at galitz.org  Fri Jul  2 11:43:58 2004
From: geoff at galitz.org (Geoff Galitz)
Date: Fri, 2 Jul 2004 11:43:58 -0700
Subject: [cAos] FW: [Warewulf] cAos certified installed but doesn't boot
In-Reply-To: <ea86ce22040701173543833cb5@mail.gmail.com>
References: <380C0AED4D502940A061BFD92C0EDD3E412DAC@ccc2003.4cd.net> <ea86ce22040701173543833cb5@mail.gmail.com>
Message-ID: <C76CEC7C-CC57-11D8-8930-000A95A5025C@galitz.org>


Greetings,

The error below is indicative of incorrect file permissions
on the tftpboot directory or files therein.

-geoff


On Jul 1, 2004, at 5:35 PM, Tim Mattox wrote:

> Hello Milen,
>
> On Thu, 1 Jul 2004 10:57:04 -0700, Fong, Milen <mfong at contracosta.edu> 
> wrote:
> [snip]
>> Problem is that when I try to have other nodes PXE boot I get the
> following message on the slave node. I followed the steps from the
> HowTo from www.warewulf-cluster.org site.
>>
>> Client IP: 10.1.0.1 Mask: 255.252.0.0
>> DHCP IP: 10.0.0.1
>> Gateway IP: 10.0.0.1
>> TFTP.
>> PXE-T02: Access Denied
>> PXE-E3c: TFTP Error - Access Violation
>> PXE-M0F: Exiting Broadcom PXE ROM
>
> Hmm, it looks like either the tftpd isn't configured correctly, the
> eb-[whatever].zpxe file isn't globally readable, or maybe the dell's
> PXE is one of the "broken" ones that I've heard about.
> Can you post an "ls -laR /tftpboot" from the server,
> as well as "chkconfig --list tftp"
>
> Are there any relevant error messages in the server's
> /var/log/messages pertaining to the tftp?  Please post a snippet
> including every line from the DHCPDISCOVER onwards.
>
>> Is there some access privileges I need to assign?
>
> The wwmaster.initiate script should have taken care of
> setting up the tftp, so the likely thing is that your 
> eb-[whatever].zpxe
> file isn't readable.
> --
> Tim Mattox - tmattox at gmail.com - http://homepage.mac.com/tmattox/
> _______________________________________________
> cAos mailing list
> cAos at caosity.org
> http://www.caosity.org/mailman/listinfo/caos
>
>
http://www.galitz.org



From gravesricharde at yahoo.com  Mon Jul  5 15:30:47 2004
From: gravesricharde at yahoo.com (Rick Graves)
Date: Mon, 5 Jul 2004 15:30:47 -0700 (PDT)
Subject: [cAos] Re: YUM updates
In-Reply-To: <20040705120001.12950.87001.Mailman@caos1.caosity.org>
Message-ID: <20040705223047.89079.qmail@web14713.mail.yahoo.com>

Hey,

> The easy way to make sure you are up to date with
> all the latest patches is to run:
> # yum update

There is an even easier way -- tell cron to apply YUM
updates every day.  

There is a HowTo on the cAos site here:

http://www.caosity.org/index.php?option=displaypage&Itemid=102&op=page&SubMenu=

Rick


From jn at it.swin.edu.au  Mon Jul  5 16:08:40 2004
From: jn at it.swin.edu.au (John Newbigin)
Date: Tue, 06 Jul 2004 09:08:40 +1000
Subject: [cAos] Re: [Centos] Re: YUM updates
In-Reply-To: <1089067652.24871.4.camel@binkley>
References: <20040705223047.89079.qmail@web14713.mail.yahoo.com> <1089067652.24871.4.camel@binkley>
Message-ID: <40E9DF78.9090608@it.swin.edu.au>

seth vidal wrote:

> On Mon, 2004-07-05 at 15:30 -0700, Rick Graves wrote:
> 
>>Hey,
>>
>>
>>>The easy way to make sure you are up to date with
>>>all the latest patches is to run:
>>># yum update
>>
>>There is an even easier way -- tell cron to apply YUM
>>updates every day.  
>>
>>There is a HowTo on the cAos site here:
>>
>>http://www.caosity.org/index.php?option=displaypage&Itemid=102&op=page&SubMenu=
>>
> 
> 
> and for the paranoid among you.
> 
> you can use yum check-update to display the updates that should take
> place from cron, if there are no updates, nothing will be outputted.
check-update sounds better than putting yum update in a cron job.  Only 
a mad man would do that!  Much better to run a daily cron which rsyncs 
your local patch repository.  That way you get an email which indicates 
the new packages and you can then test & deploy at your leisure.  When 
it comes time to install on your other machines, the patches are already 
local.

John.

> 
> -sv
> 
> 
> _______________________________________________
> CentOS mailing list
> CentOS at caosity.org
> http://www.caosity.org/mailman/listinfo/centos
> 
> 
> 


-- 
John Newbigin - Computer Systems Officer
School of Information Technology
Swinburne University of Technology
Melbourne, Australia
http://www.it.swin.edu.au/staff/jnewbigin



From gravesricharde at yahoo.com  Tue Jul  6 05:59:47 2004
From: gravesricharde at yahoo.com (Rick Graves)
Date: Tue, 6 Jul 2004 05:59:47 -0700 (PDT)
Subject: [cAos] Re: cron job madness
In-Reply-To: <20040706120001.24086.82769.Mailman@caos1.caosity.org>
Message-ID: <20040706125947.42245.qmail@web14712.mail.yahoo.com>

Hey,  

> check-update sounds better than putting yum update
in a cron job.  Only a mad man would do that!  

Are the cAos and CentOS releases THAT BAD?

> Much better to run a daily cron which rsyncs your
local patch repository.

So must one have your own local repository to avoid
being labeled as a madman?  

In which one of the RedHad reference books can I find
this?

Just curious.

Rick


From jn at it.swin.edu.au  Tue Jul  6 18:38:57 2004
From: jn at it.swin.edu.au (John Newbigin)
Date: Wed, 07 Jul 2004 11:38:57 +1000
Subject: [cAos] Re: [Centos] Re: cron job madness
In-Reply-To: <20040706125806.46352.qmail@web14704.mail.yahoo.com>
References: <20040706125806.46352.qmail@web14704.mail.yahoo.com>
Message-ID: <40EB5431.1060304@it.swin.edu.au>

I am not trying to start a flame war here, just share my thoughts on 
what I think a responsible system administrator should do before 
installing new software on a live server.

Rick Graves wrote:

> Hey,  
> 
> 
>>check-update sounds better than putting yum update
> 
> in a cron job.  Only a mad man would do that!  
> 
> Are the cAos and CentOS releases THAT BAD?
I am not sure what you mean by THAT BAD.  yum in centos-2 comes with a 
cron script which, when enabled will run "yum update" every day.  This 
IMHO is bad so I made sure that it is not enabled by default.
> 
> 
>>Much better to run a daily cron which rsyncs your
> 
> local patch repository.
> 
> So must one have your own local repository to avoid
> being labeled as a madman?  
I said better, not must.  I recommend a local repository if you have 
more than one machine which will require the patches installed.  I 
recommend having more that one machine so you can test the patches on a 
test box and not your live server.
> 
> In which one of the RedHad reference books can I find
> this?
Just because RedHat did not write a book about it, does not make it bad. 
  RedHat actually wrote a product "Proxy and Satellite Servers".

And here are some of the reasons for not installing rpm updates without 
testing:
1. back up your config files.  Even the best spec files can have 
mistakes.  If you have modified a file which is not flagged as a config 
file then you might lose all your changes.  Spend 10 seconds and tar up 
/etc (and perhaps run rpm -V and see if there is anything else which 
might have changed)
2. unwanted side effects.  Some packages can create annoying side 
effects, particularly ones which have cron jobs.  sa and mrtg have been 
known to do this.
3. bugs.  Many redhat packages contain buggy software.  Often the 
updates introduce more bugs than they fix.  stunnel 3.26 for example 
appears to work at first but does not work reliably.  Mozilla has 
cosmetic bugs which means that some users lose their mozilla icons. 
Small but can still cause users to ring and complain at 2:00 in the morning.

Of course, the thing which makes a good administrator (or any other 
role) is the ability to evaluate other peoples suggestions and decide 
for themselves what they should do.

John.

> 
> Just curious.
> 
> Rick
> _______________________________________________
> CentOS mailing list
> CentOS at caosity.org
> http://www.caosity.org/mailman/listinfo/centos
> 
> 
> 


-- 
John Newbigin - Computer Systems Officer
School of Information Technology
Swinburne University of Technology
Melbourne, Australia
http://www.it.swin.edu.au/staff/jnewbigin



From mailing-lists at hughesjr.com  Tue Jul  6 20:13:30 2004
From: mailing-lists at hughesjr.com (Johnny Hughes)
Date: Tue, 06 Jul 2004 22:13:30 -0500
Subject: [cAos] Re: [Centos] Re: cron job madness
In-Reply-To: <40EB5431.1060304@it.swin.edu.au>
References: <20040706125806.46352.qmail@web14704.mail.yahoo.com>
	 <40EB5431.1060304@it.swin.edu.au>
Message-ID: <1089170010.8072.47.camel@Myth.home.local>

I think what John is really trying to express is that applying patches
from a cron job automatically to your production servers (without
testing them first on a test platform) is a bad idea.  I absolutely
agree with him.

What is a good idea is to test your updates on a test machine ... verify
that everything works exactly like you want / expect ... then update a
local yum Mirror with the patches.  Since you only put tested updates on
the local mirror ... you can run an automated yum on your production
machines that do their updates from the local mirror ... and you then
get tested only software automatically installed on your production
machines.

Exactly how I do it, and exactly how I recommend updates be pushed to
production machines.

I think to push untested patches from a public mirror to production
machines is absolutely silly :). But I could be wrong.


Johnny Hughes
HughesJR.com
 
On Tue, 2004-07-06 at 20:38, John Newbigin wrote:

> I am not trying to start a flame war here, just share my thoughts on 
> what I think a responsible system administrator should do before 
> installing new software on a live server.
> 
> Rick Graves wrote:
> 
> > Hey,  
> > 
> > 
> >>check-update sounds better than putting yum update
> > 
> > in a cron job.  Only a mad man would do that!  
> > 
> > Are the cAos and CentOS releases THAT BAD?
> I am not sure what you mean by THAT BAD.  yum in centos-2 comes with a 
> cron script which, when enabled will run "yum update" every day.  This 
> IMHO is bad so I made sure that it is not enabled by default.
> > 
> > 
> >>Much better to run a daily cron which rsyncs your
> > 
> > local patch repository.
> > 
> > So must one have your own local repository to avoid
> > being labeled as a madman?  
> I said better, not must.  I recommend a local repository if you have 
> more than one machine which will require the patches installed.  I 
> recommend having more that one machine so you can test the patches on a 
> test box and not your live server.
> > 
> > In which one of the RedHad reference books can I find
> > this?
> Just because RedHat did not write a book about it, does not make it bad. 
>   RedHat actually wrote a product "Proxy and Satellite Servers".
> 
> And here are some of the reasons for not installing rpm updates without 
> testing:
> 1. back up your config files.  Even the best spec files can have 
> mistakes.  If you have modified a file which is not flagged as a config 
> file then you might lose all your changes.  Spend 10 seconds and tar up 
> /etc (and perhaps run rpm -V and see if there is anything else which 
> might have changed)
> 2. unwanted side effects.  Some packages can create annoying side 
> effects, particularly ones which have cron jobs.  sa and mrtg have been 
> known to do this.
> 3. bugs.  Many redhat packages contain buggy software.  Often the 
> updates introduce more bugs than they fix.  stunnel 3.26 for example 
> appears to work at first but does not work reliably.  Mozilla has 
> cosmetic bugs which means that some users lose their mozilla icons. 
> Small but can still cause users to ring and complain at 2:00 in the morning.
> 
> Of course, the thing which makes a good administrator (or any other 
> role) is the ability to evaluate other peoples suggestions and decide 
> for themselves what they should do.
> 
> John.
> 
> > 
> > Just curious.
> > 
> > Rick
> > _______________________________________________
> > CentOS mailing list
> > CentOS at caosity.org
> > http://www.caosity.org/mailman/listinfo/centos
> > 
> > 
> > 


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.infiscale.org/pipermail/caos/attachments/20040706/e958520b/attachment.html 

From caosity at tomseeley.co.uk  Wed Jul  7 09:18:02 2004
From: caosity at tomseeley.co.uk (Tom Seeley)
Date: Wed,  7 Jul 2004 17:18:02 +0100
Subject: [cAos] Re: [Centos] Re: cron job madness
In-Reply-To: <1089170010.8072.47.camel@Myth.home.local>
References: <20040706125806.46352.qmail@web14704.mail.yahoo.com>  <40EB5431.1060304@it.swin.edu.au> <1089170010.8072.47.camel@Myth.home.local>
Message-ID: <1089217082.40ec223a8d115@www.karenhudson.co.uk>

In such scenarios, what do the members of this list normally do about restarts?
 ie I would normally restart apache if I were upgrading it or any of its
componants.  Unless I'm missing something, yum doesn't provide the logic to auto
restart affected services, which is why I personally don't turn on auto-updating
facilities.  

Thoughts/comments/suggestions?

Tom.

Quoting Johnny Hughes <mailing-lists at hughesjr.com>:

> I think what John is really trying to express is that applying patches
> from a cron job automatically to your production servers (without
> testing them first on a test platform) is a bad idea.  I absolutely
> agree with him.
> 
> What is a good idea is to test your updates on a test machine ... verify
> that everything works exactly like you want / expect ... then update a
> local yum Mirror with the patches.  Since you only put tested updates on
> the local mirror ... you can run an automated yum on your production
> machines that do their updates from the local mirror ... and you then
> get tested only software automatically installed on your production
> machines.
> 
> Exactly how I do it, and exactly how I recommend updates be pushed to
> production machines.
> 
> I think to push untested patches from a public mirror to production
> machines is absolutely silly :). But I could be wrong.
> 
> 
> Johnny Hughes
> HughesJR.com
>  
> On Tue, 2004-07-06 at 20:38, John Newbigin wrote:
> 
> > I am not trying to start a flame war here, just share my thoughts on 
> > what I think a responsible system administrator should do before 
> > installing new software on a live server.
> > 
> > Rick Graves wrote:
> > 
> > > Hey,  
> > > 
> > > 
> > >>check-update sounds better than putting yum update
> > > 
> > > in a cron job.  Only a mad man would do that!  
> > > 
> > > Are the cAos and CentOS releases THAT BAD?
> > I am not sure what you mean by THAT BAD.  yum in centos-2 comes with a 
> > cron script which, when enabled will run "yum update" every day.  This 
> > IMHO is bad so I made sure that it is not enabled by default.
> > > 
> > > 
> > >>Much better to run a daily cron which rsyncs your
> > > 
> > > local patch repository.
> > > 
> > > So must one have your own local repository to avoid
> > > being labeled as a madman?  
> > I said better, not must.  I recommend a local repository if you have 
> > more than one machine which will require the patches installed.  I 
> > recommend having more that one machine so you can test the patches on a 
> > test box and not your live server.
> > > 
> > > In which one of the RedHad reference books can I find
> > > this?
> > Just because RedHat did not write a book about it, does not make it bad. 
> >   RedHat actually wrote a product "Proxy and Satellite Servers".
> > 
> > And here are some of the reasons for not installing rpm updates without 
> > testing:
> > 1. back up your config files.  Even the best spec files can have 
> > mistakes.  If you have modified a file which is not flagged as a config 
> > file then you might lose all your changes.  Spend 10 seconds and tar up 
> > /etc (and perhaps run rpm -V and see if there is anything else which 
> > might have changed)
> > 2. unwanted side effects.  Some packages can create annoying side 
> > effects, particularly ones which have cron jobs.  sa and mrtg have been 
> > known to do this.
> > 3. bugs.  Many redhat packages contain buggy software.  Often the 
> > updates introduce more bugs than they fix.  stunnel 3.26 for example 
> > appears to work at first but does not work reliably.  Mozilla has 
> > cosmetic bugs which means that some users lose their mozilla icons. 
> > Small but can still cause users to ring and complain at 2:00 in the
> morning.
> > 
> > Of course, the thing which makes a good administrator (or any other 
> > role) is the ability to evaluate other peoples suggestions and decide 
> > for themselves what they should do.
> > 
> > John.
> > 
> > > 
> > > Just curious.
> > > 
> > > Rick
> > > _______________________________________________
> > > CentOS mailing list
> > > CentOS at caosity.org
> > > http://www.caosity.org/mailman/listinfo/centos
> > > 
> > > 
> > > 
> 
> 
> 


-- 
Tom Seeley


From mickw at mbwcomputing.net  Thu Jul  8 03:37:01 2004
From: mickw at mbwcomputing.net (Michael Watson)
Date: Thu, 8 Jul 2004 20:37:01 +1000
Subject: [cAos] Cinch SATA Problem
Message-ID: <200407081037.i68AbNO23608@mail.mbwcomputing.net>

 
Using the current Build of Cinch (2.0.3)
 
Trying to install cAos-1.0 onto an Intel D865G Motherboard.  ICH5 SATA
Support.
 
Cinch Boot disk boot successfully until it starts detecting IDE devices.
Halts on detection of HDE  (SATA Seagate Hard Drive).
CentOS 3.0 Detects Device as sda and boots / installs successfully.  
 
 
Michael Watson
 
 
 

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.716 / Virus Database: 472 - Release Date: 5/07/2004
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.infiscale.org/pipermail/caos/attachments/20040708/80575b6c/attachment.html 

From gravesricharde at yahoo.com  Thu Jul  8 08:20:08 2004
From: gravesricharde at yahoo.com (Rick Graves)
Date: Thu, 8 Jul 2004 08:20:08 -0700 (PDT)
Subject: [cAos] Re: more cron job madness
In-Reply-To: <20040708120001.15087.21102.Mailman@caos1.caosity.org>
Message-ID: <20040708152008.41858.qmail@web14707.mail.yahoo.com>

Hey,

UNCLE!  

I added a warning to the YUM HowTo.  I will also look
into this further, and may be back with one or more
proposed solutions.

Rick


From mailing-lists at hughesjr.com  Thu Jul  8 11:12:21 2004
From: mailing-lists at hughesjr.com (Johnny Hughes)
Date: Thu, 08 Jul 2004 13:12:21 -0500
Subject: [cAos] Re: [Centos] Re: cron job madness
In-Reply-To: <1089217082.40ec223a8d115@www.karenhudson.co.uk>
References: <20040706125806.46352.qmail@web14704.mail.yahoo.com>
	 <40EB5431.1060304@it.swin.edu.au>
	 <1089170010.8072.47.camel@Myth.home.local>
	 <1089217082.40ec223a8d115@www.karenhudson.co.uk>
Message-ID: <1089310341.28592.5.camel@Myth.home.local>

On Wed, 2004-07-07 at 11:18, Tom Seeley wrote:

> In such scenarios, what do the members of this list normally do about restarts?
>  ie I would normally restart apache if I were upgrading it or any of its
> componants.  Unless I'm missing something, yum doesn't provide the logic to auto
> restart affected services, which is why I personally don't turn on auto-updating
> facilities.  

I read the log and then restart services manually.  (For workstations, I
just reboot .... for servers I manually restart services).   Most items
are not services/daemons ... some are.


Johnny Hughes
HughesJR.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.infiscale.org/pipermail/caos/attachments/20040708/7777ed14/attachment.html 

From greg at runlevelzero.net  Thu Jul  8 12:52:03 2004
From: greg at runlevelzero.net (Greg Kurtzer)
Date: Thu, 8 Jul 2004 12:52:03 -0700
Subject: [cAos] Cinch SATA Problem
In-Reply-To: <200407081037.i68AbNO23608@mail.mbwcomputing.net>
References: <200407081037.i68AbNO23608@mail.mbwcomputing.net>
Message-ID: <20040708195203.GA5297@runlevelzero.net>

cAos-1 uses the 2.4 kernel, and the stock 2.4 kernel (as of 2.4.25 IIRC) does
not incorporate libata, thus cAos-1 and cinch does not support SATA.

cAos-2 should support it just fine when it gets released because it uses the
2.6 kernel.

BTW, RHEL3 (and thus Centos3) has the SATA back-ports.


On Thu, Jul 08, 2004 at 08:37:01PM +1000, Michael Watson told me:
>  
> Using the current Build of Cinch (2.0.3)
>  
> Trying to install cAos-1.0 onto an Intel D865G Motherboard.  ICH5 SATA
> Support.
>  
> Cinch Boot disk boot successfully until it starts detecting IDE devices.
> Halts on detection of HDE  (SATA Seagate Hard Drive).
> CentOS 3.0 Detects Device as sda and boots / installs successfully.  
>  
>  
> Michael Watson
>  
>  
>  
> 
> ---
> Outgoing mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.716 / Virus Database: 472 - Release Date: 5/07/2004
>  

-- 
Greg M. Kurtzer
http://runlevelzero.net/
http://caosity.org/
http://warewulf-cluster.org/


From rick at linuxmafia.com  Thu Jul  8 13:04:44 2004
From: rick at linuxmafia.com (Rick Moen)
Date: Thu, 8 Jul 2004 13:04:44 -0700
Subject: [cAos] Cinch SATA Problem
In-Reply-To: <20040708195203.GA5297@runlevelzero.net>
References: <200407081037.i68AbNO23608@mail.mbwcomputing.net> <20040708195203.GA5297@runlevelzero.net>
Message-ID: <20040708200444.GT25508@linuxmafia.com>

Quoting Greg Kurtzer (greg at runlevelzero.net):

> cAos-1 uses the 2.4 kernel, and the stock 2.4 kernel (as of 2.4.25 IIRC) does
> not incorporate libata, thus cAos-1 and cinch does not support SATA.

FYI:  libata is very helpful for SATA support, but not essential for all
SATA chipsets.  Some people are able to get by on Intel ICH5 chipsets
using some 2.4.x kernels' piix drivers (from the regular drivers/ide
set), for example.

More at:  "Serial ATA" on http://linuxmafia.com/kb/Hardware/

-- 
Cheers,
Rick Moen                          Ban the Bomb.  
rick at linuxmafia.com                Save the world for conventional warfare.


From hamid at use-trade.com  Sun Jul 11 03:25:24 2004
From: hamid at use-trade.com (Abd El-Hameed Mohammed  (Use-trade.com))
Date: Sun, 11 Jul 2004 13:25:24 +0300
Subject: [cAos] php-mcal
Message-ID: <044e01c46731$62367110$2e0a0a51@hamid>

Hi,
    How to add mcrypt and mcal support to php-4.3.2-11.ent?
I am running CentOS 3.1

Hameed
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.infiscale.org/pipermail/caos/attachments/20040711/23bf0dd1/attachment.html 

From mej at caosity.org  Thu Jul 15 12:05:12 2004
From: mej at caosity.org (Michael Jennings)
Date: Thu, 15 Jul 2004 15:05:12 -0400
Subject: [cAos] Package Maintainers
Message-ID: <20040715190512.GD15433@kainx.org>

For those who may not have heard, package maintainers for caos 2.x
will require an account on our CVS server.  In order to create an
account for you, I will need you to provide the following:

  1.  Your preferred userid (8 char max please)
  2.  Your ssh public key file
  3.  $20 USD (just making sure you're paying attention)

Please send these items directly to "mej at caosity.org" and not the
list.  Also, you must have an existing temple account; if you don't
have one, get one. :)

Instructions on how to import your packages into CVS will be
forthcoming.

Thanks,
Michael

-- 
Michael Jennings (a.k.a. KainX)  http://www.kainx.org/  <mej at kainx.org>
n + 1, Inc., http://www.nplus1.net/       Author, Eterm (www.eterm.org)
-----------------------------------------------------------------------
 "[Heather Graham] is the new I-would-run-over-my-best-friend-in-a-
  hummer-to-get-next-to-her girl."                    -- Claude Nobler


From jmyost at ameritech.net  Thu Jul 15 15:59:34 2004
From: jmyost at ameritech.net (Joshua Yost)
Date: Thu, 15 Jul 2004 17:59:34 -0500
Subject: [cAos] centOS 3.0 and Cold Fusion
Message-ID: <A3E2E8C6-D6B2-11D8-8EB6-000A958D5BFA@ameritech.net>

I am considering 3.0 for a server I will be running that requires cold 
fusion MX - the tech specs say CFMX is all good for RH AS 3.0 - since I 
am newer to this - is there any reason the installer and server should 
have any problems then with CentOS 3? - I'm trying to save 1500.00 here 
on a non mission critical server and if I can avoid RH I will. Any help 
would be appreciated.

Thanks!



From charlieb-caos at budge.apana.org.au  Thu Jul 15 18:18:31 2004
From: charlieb-caos at budge.apana.org.au (Charlie Brady)
Date: Thu, 15 Jul 2004 21:18:31 -0400 (EDT)
Subject: [cAos] centOS 3.0 and Cold Fusion
In-Reply-To: <A3E2E8C6-D6B2-11D8-8EB6-000A958D5BFA@ameritech.net>
Message-ID: <Pine.LNX.4.44.0407152114550.3069-100000@e-smith.charlieb.ott.istop.com>

On Thu, 15 Jul 2004, Joshua Yost wrote:

> I am considering 3.0 for a server I will be running that requires cold 
> fusion MX - the tech specs say CFMX is all good for RH AS 3.0 - since I 
> am newer to this - is there any reason the installer and server should 
> have any problems then with CentOS 3? - I'm trying to save 1500.00 here 
> on a non mission critical server and if I can avoid RH I will.

If you wish to save money, why are you using Cold Fusion MX?  (Have you 
looked at Apache::ASP? Mason?)

Anyway, if you need to lie to a software installer, I'm sure you can. Most 
likely thing you'd need to do would be to adjust contents of 
/etc/redhat-release.

---
Charlie