I'll bet your not running lilo after compiling your kernels...
This means you are in fact running your old kernel...I believe it's possible
that your running your old kernel even if you copied your new one on top,
and therefore, your old one no longer exists (at least as a file entry.)
The blocks are still on the disk, and lilo just points to those blocks.
Eventually the blocks will be used for something and you'll no longer be
able to boot.
So every time you switch your kernel, you must run lilo.
-Sam
On Thu, Mar 05, 1998 at 06:30:43PM -0600, David Mihm wrote:
> I've just updated gcc (2.7.2.3) and recompiled the kernel for the 7th time
> and just noticed that upon boot (and in dmesg) it reports:
>
> Linux version 2.0.33 ([EMAIL PROTECTED]) (gcc version 2.7.2.1) #3 Sun Jan
> 25 23:34:17 CST 1998
>
> I used a config file from a previous xconfig, made a few minor adjustments
> and recompiled it last night (Mar 5 01:31 /boot/vmlinuz). I'm very
> curious where the boor process gets this incorrect information about
> 1. the gcc version,
> 2. the incorrect # of times it's been recompiled, and
> 3. the 'far-from-right' date of which it was compiled.
>
> Anyone have any clues?
> TIA
--
Samuel Ockman | Work Linux? | VA Research
Director of Software | Work with us. | Proud Corporate
(650) 934-3666 ext. 133 | e-mail jobs@ | Sponsor of Guerilla
| varesearch.com | Linux Development
--
PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
http://www.redhat.com/RedHat-FAQ /RedHat-Errata /RedHat-Tips /mailing-lists
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject.
