Michael Mansour wrote:
...
I don't use, and have never used, up2date on an SL server, so I am unsure why
these errors are coming up.
I've checked cron's and cannot find anywhere where up2date is being kicked off.
Any ideas how I can trouble-shoot this and stop up2date from running?
...
I
The scenario you are saying might work, but it will be a lot
less maintenance hassle for you if you bite the bullet and
yum upgrade your machines to the latest version of 4.x and 5.x
respectively, then you would only have to maintain 2 directories
rather than five.
Steve
On Tue, 10 Nov
FRANCHISSEUR Robert writes:
as long ago I enabled dag.repo and I had a lot of trouble
because yum and yum-conf were updated with dag'ones which are
completely different than SL ones.
The situation has improved now, been using daq without problems. I
suspect that the
After reading a lot of the failure reports and noise.
Are the available distributions what we are going to live with for the
immediate future?
When I read the release notes for SL 5.4 there is no mention of the S ATA
problem or it being fixed.
NVidea problems I had with SL 5.3 can be taken
Larry J. Linder wrote:
After reading a lot of the failure reports and noise.
We had some problems with one of the download servers. This has been fixed.
Where people were able to get a good download and DVD burn, there
haven't been install problems.
Are the available distributions what we
A colleague here is trying to build a 64-bit network boot image, but he
is creating it on a 32-bit host. We can't figure out how to make yum
grab the 64-bit packages in this case.
Any idea what we can do to force yum to grab 64-bit packages while
running on a 32-bit host? We tried specifying
Hi Larry,
After reading a lot of the failure reports and noise.
I agree you'll read a lot of problems people are having on this list, but
that's typical as people wouldn't email noise to the list saying things work
fine.
For me, I had SL5.3 i386 crash the server (kernel panic) when running a
Hi Troy,
Michael Mansour wrote:
...
I don't use, and have never used, up2date on an SL server, so I am unsure
why
these errors are coming up.
I've checked cron's and cannot find anywhere where up2date is being kicked
off.
Any ideas how I can trouble-shoot this and stop up2date
