On Sun, 26 Oct 2014 13:13:24 +0100 Håkon Alstadheim <ha...@alstadheim.priv.no> wrote:
> On 26. okt. 2014 00:18, Brian wrote: > > On Sat 25 Oct 2014 at 22:46:43 +0200, Pascal Hambourg wrote: > > > >> I have seen at least two stable kernel > >> updates which changed the ABI without changing the version in the > >> kernel package name and resulted in some new modules not being > >> compatible with the previous kernel image or modules. > > If it is a matter of exchanging anecdotal experiences I've never > > experienced any problem booting a new kernel in nearly twenty years. > > > > I'm unsure what it is you are recommending the OP to do. > > > > > > The point is that loading kernel modules after a kernel update will > not always work, so a reboot is in my experience advisable before > you do any configuration changes involving module loading. > > Such config changes might e.g. be firewall changes or new hardware. > > I don't know if Pascal's description of the condition is accurate, > the effect has been real on kernel updates in the past. > > There was a time when a kernel upgrade always triggered a message which urged a reboot as soon as possible. I'm not sure when it stopped happening, a quick Google suggests that it disappeared after lenny. -- Joe -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141026124631.0c940...@jresid.jretrading.com