Updating kernel using aptitude
Updating kernel using aptitude - celebrating 100 days of dating
I do not see such separate packaging in the repositories for my Ubuntu 12.04, but perhaps the way the kernel and the modules are packaged is to be changed for Ubuntu 12.10, and there will be separate packages for modules, and my concern will be legitimate then.
Also, replacing the package by a newer version is usually not something we want for kernels.
I have a machine running Debian stable, and I'd like to update the stock kernel to the latest kernel available in the backports repository.
There are many kernel-related packages and virtual packages--what is the right way to do this and get the appropriate packages upgraded? This is so that if the real package name changes (which is very often), you won't lag behind.
Ubuntu releases a new distribution every 6 months, they do not support intermediate upgrades except for grave bugs.
But there are separate packages for modules listed on launchpad.net/ubuntu/ source/linux-ac100/3.0.27-1.1 and launchpad.net/ubuntu/ source/linux-ac100/3.1.10-4.5 .
This particular PPA is managed by the Ubuntu kernel team, so it's pretty close to official.
However, you link to the page for quantal, which is Ubuntu 12.10, currently alpha.There are now two ways to upgrade, a safe one (conservative, if an update needs to add or remove dependencies, it won't update) and a full one (it will always upgrade even though it impacts other packages by adding them or removing them, previously called 'dist-upgrade').The actions are now 'safe-upgrade' or 'full-upgrade'.If you believe it's important to stay up to date with the latest security patches, then you should follow this simple tutorial.Recently (since Ubuntu 7.10), the aptitude action 'upgrade' is deprecated.To determine which meta package to use, have a look at the name of the kernel package you are running.