John Hinton wrote:
> I haven't disabled Kudzu on most of my systems, but I really do wonder
> if there is really any reason to keep it running after the initial
> system install. These servers might get a new drive from time to time,
> only replacing a drive in the array with a like drive. Maybe s
On Thu, Jan 24, 2008 at 06:26:46PM -0500, John Hinton alleged:
> Can anybody give a good reason to keep it running in a server non-gui
> environment?
>
> I guess Kudzu is still very weak in this area. maybe getting worse.
*shrug* I've been disabling it for years.
pgpY4hbvR88U2.pgp
Descri
Garrick Staples wrote:
On Wed, Jan 23, 2008 at 09:39:09PM -0500, Michael Semcheski alleged:
So I have a CentOS 5 machine, which I recently did a 'yum update' on.
Everything went fine, but I rebooted as a precaution (just to confront
any problems which might arise the first time after an updat
On Wed, Jan 23, 2008 at 09:39:09PM -0500, Michael Semcheski alleged:
> So I have a CentOS 5 machine, which I recently did a 'yum update' on.
> Everything went fine, but I rebooted as a precaution (just to confront
> any problems which might arise the first time after an update).
>
> And sure enoug
A little birdy told me that Michael A. Peters said:
] Michael Semcheski wrote:
] > So I have a CentOS 5 machine, which I recently did a 'yum update' on.
] > Everything went fine, but I rebooted as a precaution (just to confront
] > any problems which might arise the first time after an update).
]
On Jan 23, 2008 9:59 PM, Michael A. Peters <[EMAIL PROTECTED]> wrote:
> I don't know but I always disable kudzu after initial install on
> machines that don't change hardware because I've had similar things
> happen to me in pre-fedora redhat. I leave it on my laptop though.
The machine in questio
On Jan 23, 2008 10:02 PM, John R Pierce <[EMAIL PROTECTED]> wrote:
> I'd probably have diff'd the files before overwriting to see wtf was hosed.
That was my first thought.
There was no ifcfg-eth0, only ifcfg-eth0.bak.
___
CentOS mailing list
CentOS@cent
Michael Semcheski wrote:
So I have a CentOS 5 machine, which I recently did a 'yum update' on.
Everything went fine, but I rebooted as a precaution (just to confront
any problems which might arise the first time after an update).
And sure enough, when the machine came back up, the network didn't
Michael Semcheski wrote:
So I have a CentOS 5 machine, which I recently did a 'yum update' on.
Everything went fine, but I rebooted as a precaution (just to confront
any problems which might arise the first time after an update).
And sure enough, when the machine came back up, the network didn't
So I have a CentOS 5 machine, which I recently did a 'yum update' on.
Everything went fine, but I rebooted as a precaution (just to confront
any problems which might arise the first time after an update).
And sure enough, when the machine came back up, the network didn't
work. Luckilly, someone s
10 matches
Mail list logo
