I don't understand: Re: unresolved symbols

[Zacarias ecumberri Sanchez zacals]

From:"Mary Christie Generalao" <[EMAIL PROTECTED]>

>Thanks a lot. Really im starting to feel the difficulties of
>administering
>remote machines (with no tech support onsite).
>
>Mary Christie

>----- Original Message -----
>From: Ray Olszewski <[EMAIL PROTECTED]>
>To: Mary Christie Generalao <[EMAIL PROTECTED]>;
><[EMAIL PROTECTED]>
>Sent: Saturday, June 03, 2000 10:30 PM
>Subject: Re: unresolved symbols

>> It sounded like you compiled a new (for example) 2.2.13 kernel on
>> a system that had an old 2.2.13 kernel, and you did not extend the
>> version number to distinguish them.
Well, that extend is something like sub-sub-version, isn't it?
>> As a result, when you did "make modules_install", you overwrote
>> the old kernel's modules with the new ones. (Unless you previously
>> did something like "mv /lib/modules/2.2.13
>> /lib/modules/2.2.13-old", thus making the modules backup that the
>> standard kernel-compile README file recommends; then you have them
>> safely tucked aside and you can put them back quite easily.)
And now I don't understand a shit,... You state she compiled a new
kernel so then I think there are two kernels the 2.2.13new and the
2.2.13old (the active one before compile(kernel,modules)/reboot) or
only one (if it is also overwriten given the fact that they are not
distingued. Then she overwrites old modules. So: what's wrong with
that? She hasn't distinguished among them and overwrite occurs, but
after this, she has the matching 2.2.13new kernel and 2.2.13new
modules, so all should be ok when booting. Then, how did she came
up with those unresolved symbols?
She might had lost the old modules and maybe the image, but she should
have the new ones.
But, hey, I think now there might be old modules in the directory if
they weren't removed. Is it what I'm missing? I cannot think of
another.
I have not had experience with different equal-version kernels.
Where may I find information on that extend-def and equal-versions?
I would be glad if someone explains me all that mess I have.
>>
>> If you and the machine are not co-located, this is tough to fix.
>> You need to reload the kernel-image file for your default kernel
>> or compile a new kernel that works. You might have a config file
>> for your default kernel in /boot; some distributions include one
>> with the image, but others don't.
I know nothing about that, do you do remote administering by Telnet?

Oh well, TIA.
Sorry about the final line (this is "webmail")


Consigue tu direcci�n de email gratis y permanente en http://WWW.LETTERA.NET

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.linux-learn.org/faqs