Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email email@example.com
From: Michal Jaegermann (michalellpspace.math.ualberta.ca)
Date: Sat Mar 23 2002 - 11:51:54 CST
On Fri, Mar 22, 2002 at 09:10:41AM -0800, Rajiv Prasad wrote:
> 1. there are a lot of update files for 7.1 (I downloaded all rpms, it is
> worth 301MB). How do I figure out the inter-dependencies for these rpms? Or
> is just a brute-force "rpm --force --install *.rpm" okay? Don't want to mess
> up *this* installation.
NO! First principle - do not use '--force' on rpm unless there is truly
no other way to install and you are truly convinced that you know what
you are doing. Not a second earlier. An indiscriminate use of
'--force' is a sure way to mess up a system.
Start from typing 'rpm --help | less' and looking over that and rpm
If you have "alternative architectures" (like glibc for alpha and
alphaev6) then leave in a directory with stuff to install only those
which you want to install and not others.
Once you did that try 'rpm -Fvh *.rpm' ('-F' is an alternative for
'--freshen' and installs updates only to things which you have
installed). If this will get back with complaints, as it could be when
some packages were split or aquired new unsatisfied dependencies, do
'rpm -Uvh ...' _only_ to resolve these complaints and repeat 'rpm -Fvh
*.rpm'. For example in updates for 7.2 Intel (I do not remember now
what, if any, will cause such problems in updates to 7.1) there is few
perl packages which depend on each other. You do than
'rpm -Uvh perl*.rpm' so they are installed as one group and you _know_
that you need a perl update. If you do not need it (you do) then you
will not see any bitching.
> 2. I am a little unclear about the layout of /boot. What do System.map and
> modules.info files do? They are symlinks to System.map-2.4.3-12 and
> module.info-2.4.3-12. Do I have to put System.map and module.info from my
> 2.4.19-pre3 build in /boot, and modify the symlinks?
You do not have module.info-2.4.19-pre3 (this is Red Hat invention and
do not worry about it) and you add /boot/System.map-2.4.19-pre3.
Suffix is really the same as a name of a directory with your modules.
Links will be updated automatically on boot. Later there is no point
if you do not understand what they are for.
> 2.4.19-pre3 boots
> without these files.
> So why are they there?
When in doubt check your logs. There is a lot of information there
and for a reason. This map is needed but only in time of troubles.
> BTW, I could not find
> module.info in my 2.4.19-pre3 build tree. Where is it?
> 3. dhcp: while I was installing, the hostname was set to dhcp-102-6, and it
> is sticking even now. When I was using RH6.1, I used to get hostname and
> domainname from dhcp. Why not in 7.1:
Because you set it that way. Reconfigure your network information.
Buying a boxed set has its uses. Printed manuals are there.
Axp-list mailing list