On Sun, Nov 28, 2004 at 01:22:44AM -0500, Dave Jones wrote: > > For example if someone rebuilds a kernel with the same name/number outside > > of RPM. > > But, y'know, Don't Do That. > If someone is building their own kernel, they should know what they're doing. > Folks building their own kernels get to turn on /proc/config.gz for themselves > anyway if they really want it. This discussion is about the packaging of > the kernel RPMs used by those who don't recompile. I'm thinking of a situation where there's more than one person involved, which often happens in real world sysadmin catastrop^H^H^H^H^H^H^H^H^H experience. Someone who doesn't really know the rules rebuilds the kernel to fix some "urgent problem", doesn't turn that on, doesn't make a new name (or even goes out of their way to match the RPM packages name, for some reason that seems like a good idea at the time). The next person who comes along and looks at /boot/config-`uname -r` will be confused, and it might take them a while to think to verify that the running kernel is actually the RPM version. Maybe this is far-fetched -- and probably "have good sysadmin policies" is a better fix than the /proc option. -- Matthew Miller mattdm@xxxxxxxxxx <http://www.mattdm.org/> Boston University Linux ------> <http://linux.bu.edu/>
