Re: [reiserfs-dev] Re: [ANNOUNCE] reiser4 snaphots

[Todd Lyons <todd@mrball.net>]

[-- Attachment #1: Type: text/plain, Size: 1618 bytes --]

Valdis.Kletnieks@vt.edu wanted us to know:
>> Todd Lyons wrote:
>> Maybe my understanding is a little off, but I thought that I could
>> just rebuild the modules and install them and run depmod and the new
>> module symbols would be in effect.  But that didn't work (same
>> error).
>> So then I tried also a make bzImage and make install (which updates the
>> System.map, something that didn't get done with make modules_install).
>> It still would not load (same error).
>> Finally, I rebooted loading the new kernel and that fixed it.  No
>> comments needed, unless they are "what you did should have worked."
>I've seen similar issues when the /boot/System.map file doesn't match
>the kernel in use (this is particularly an issue for 'depmod' - the
>standard 'make modules_install' target passes a -F flag to depmod to
>use the just-created System.map file.

That I get.  You're saying that my make install step which updated the
System.map in /boot was nullfied because it didn't exactly match the
running kernel version.  And you're also saying that -F makes it ignore
what /proc/ksyms has.

But then that leads to the next problem.  That System.map doesn't match
the /proc/ksyms, so I'm still left with a reboot as my only option.  

Thinking out loud.  But I didn't change the way that the kernel was
compiled.  Reiser4 is _still_ a module.  What am I missing?

Blue skies...			Todd

P.S. Valdis, I think this sig originally came from somebody's NANOG
post.  :)
-- 
A: No
Q: Should I quote at the end of the message?
   Linux kernel 2.5.45-3   load average: 0.00, 0.00, 0.00

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]