Thu, 16 Nov 2006
It took me a while to figure out that
my executable files and libraries yesterday, and that RPM is now
prelink-aware. Vašek added an interesting comment to which I want to reply in this blog post:
Yes, prelink. It shoud be written at the top of rpm man page (maybe also bold and red) that prelink modifies binaries and RPM knows about it. Most people find differences and then hunt ghosts - just like you. I only wonder how a guru like you do not know this. :-)
Well, the simple answer is that I am by no means a guru :-)
The more complicated answer is that I learned RPM long ago (pretty indepth,
I even wrote a series of
articles about it), when it did not have a
This is a general problem with the IT knowledge: it is often not so hard to gain the knowledge, but it is much harder to keep up with ongoing changes. I think it is because there are manuals and tutorials for beginners, but almost nothing about what has changed in - for example - last two years. I don't count Changelogs, because they are clogged with changes at the micro-architectural level, which are of no interest after a year or two.
It is hard to keep the knowledge up-to-date even when you actually still use
the system in question: I build RPM packages occasionally, yet this was
the first time I came into the
prelink support of RPM.
It is the same with Perl, for example.
I use Perl almost daily, yet many features used in Perl Best Practices
were new for me (such as using "
instead of "
use vars qw($var);").
Also, in this particular case it would not probably helped to have a big fat
warning near the top of the
rpm(1) manpage - I think I would
not consult this manpage in this situation. Using
more general :-). Keeping the knowledge up-to-date
is pretty hard - for example, I skip most of content of the
Linux Journal, because it in a
lengthy ways repeats what I already know, and should there be anything new
for me, it is deeply buried in facts I already know.
How do you keep up with the current development in IT, my dear lazyweb?