Chris Grau wrote:
If I had some file in my directory, let's say
packages.i.found.which.match.g++, and I ran an unescaped yum command:
$ yum provides *g++
The command would then actually be,
$ yum provides packages.i.found.which.match.g++
Which probably isn't what I want.
This probably explains why after some usage, I start to have problems with:
yum update tre* tra* sel* per* ...
¿Would this be a simple matter of doing this:
yum update 'tre* tra* sel* per* ...'
('...' merely shorthand for many more, not a literal, just to be clear)
It seems that over time, yum starts accumulating files that apparently
start giving me false matches and then yum bombs. When this starts to
happen, I always do a 'yum clean all'. I figure I should probably do
that once in a while anyway, right?
--
Ralph
--------------------
The spelling of words is subordinate. Morbidness for nice spelling and tenacity
for or against one letter or so means dandyism and impotence in literature.
--Walt Whitman
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
