Prev: qtparted and kernel disagree about partitions
Next: useradd: Problem joining into a Samba domain
From: Marc Auslander on 4 Mar 2010 12:10
having installed the bigmem kernel package, should I then remove the
regular kernel package?

my concern is that if I don't, the next update to it will replace vmlinuz
with the regular kernel.

or are the installers smart enough to avoid that?

From: Mihamina Rakotomandimby on 4 Mar 2010 12:20
> "Marc Auslander" <marcausl(a)gmail.com> :
> having installed the bigmem kernel package, should I then remove the
> regular kernel package?
>
> my concern is that if I don't, the next update to it will replace
> vmlinuz with the regular kernel.

- How did you install your bigmem kernel?
- What is your bootloader configuration
- List your existing "vmlinuz"

--
Architecte Informatique chez Blueline/Gulfsat:
Administration Systeme, Recherche & Developpement
+261 34 29 155 34 / +261 33 11 207 36


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/20100304201534.5d674cea(a)pbmiha.malagasy.com
From: Stephen Powell on 4 Mar 2010 12:30
On Thu, 4 Mar 2010 11:46:06 -0500 (EST), Marc Auslander wrote:
>
> having installed the bigmem kernel package, should I then remove the
> regular kernel package?
>
> my concern is that if I don't, the next update to it will replace vmlinuz
> with the regular kernel.
>
> or are the installers smart enough to avoid that?

There are two issues here: the kernels themselves and the symbolic links
used by bootloaders such as lilo.

If the kernel image package names are different, then the package
management system will keep them straight. You don't need to worry
about a "bigmem" kernel getting updates from a non-bigmem kernel.
The vmlinuz symbolic link generally points to the most recently installed
kernel image. Its companion symbolic link, initrd.img, points to
the initial RAM filesystem image that goes with it. vmlinuz.old
generally points to the next most recently installed kernel, and its
companion symbolic link, initrd.img.old, generally points to the initial
RAM filesystem image that goes with it. It is a good
idea to check them manually to make sure they point where you want
them to point after applying maintenance. If in doubt, manually run
lilo too. Then shutdown and reboot. If you have more than two
kernels installed, only two are generally bootable through a bootloader
such as lilo which uses symbolic links. You might as well purge
the non-bootable ones, since all they're doing is taking up space.


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/296220991.16763271267723545136.JavaMail.root(a)md01.wow.synacor.com
From: Olaf Reitmaier Veracierta on 4 Mar 2010 23:00


On 04/03/10 12:16, Marc Auslander wrote:
>
> having installed the bigmem kernel package, should I then remove the
> regular kernel package?
No.
>
> my concern is that if I don't, the next update to it will replace
> vmlinuz with the regular kernel.
>
False, the active kernel is update instead of second options.
> or are the installers smart enough to avoid that?
>
No as smart as you think, but they update the runing kernel version
(first on GRUB).

--
---------------------------------------------------------------------
"You don't know where your shadow will fall",
Somebody.-
---------------------------------------------------------------------
Ing. Olaf Reitmaier Veracierta<olafrv(a)gmail.com>
---------------------------------------------------------------------
Personal Web Page -- http://olafrv.com -- info(a)olafrv.com
---------------------------------------------------------------------

From: Marc Auslander on 5 Mar 2010 10:20
Olaf Reitmaier Veracierta <olafrv(a)gmail.com> writes:

> On 04/03/10 12:16, Marc Auslander wrote:
>
> having installed the bigmem kernel package, should I then remove
the
> regular kernel package?
>
> No.
>
> my concern is that if I don't, the next update to it will replace
> vmlinuz with the regular kernel.
>
> False, the active kernel is update instead of second options.
>
> or are the installers smart enough to avoid that?
>
> No as smart as you think, but they update the runing kernel version
> (first on GRUB).
> --

I am confused by this and the other explainations.

To be clear - I am only concerned about the vmlinuz symlink. I know
package management works.

When I installed bigmen, it swung vmlinuz to the newly installed
kernel, just as every other kernel install/update I've done has.

So what happens if the normal kernel package is updated. I fear the
update would swing vmlinuz to the latest version of the normal
kernel. If this is not going to happen, what rule would prevent it?

Marc Auslander
 |  Next  |  Last
Pages: 1 2
Prev: qtparted and kernel disagree about partitions
Next: useradd: Problem joining into a Samba domain