At 11:48 22.10.2002, Emmanuel Seyman and Nick Lindsell said:
[snip]
>You don't.
>You have a vmlinux-2.4.18-17.7.xsmp file and a vmlinuz-2.4.18-17.7.xsmp
>one (same as the previous one but compressed).
>You can't have two files with the same name in the same
At 11:33 22/10/2002 +0200, you wrote:
Hmm - I failed to visit /etc/grub.conf... sorry for the noise before, of
course grub.conf points to the correct images.
One question remains though - how come that I have 2 (!)
vmlinuz-2.4.18-17.7.xsmp files in /boot?
One is vmlinuX, the other is vmlinuZ -
On Tue, Oct 22, 2002 at 11:33:31AM +0200, Ernest E Vogelsinger wrote:
>
> One question remains though - how come that I have 2 (!)
> vmlinuz-2.4.18-17.7.xsmp files in /boot?
You don't.
You have a vmlinux-2.4.18-17.7.xsmp file and a vmlinuz-2.4.18-17.7.xsmp
one (same as the previous one but compre
Hmm - I failed to visit /etc/grub.conf... sorry for the noise before, of
course grub.conf points to the correct images.
One question remains though - how come that I have 2 (!)
vmlinuz-2.4.18-17.7.xsmp files in /boot?
Thx,
>O Ernest E. Vogelsinger
(\)ICQ# 13394035
^
-
Hi list,
maybe some kernel guru can shed a light on this.
Yesterday night I ran up2date for the new kernel patch on our dual
processor machine. Now, the System.map points to the new kernel map, I have
2 (!) entries for vmlinuz-2.4.18-17.7.xsmp, and module-info and vmlinuz are
still linked to 2.4.
