Date: prev next · Thread: first prev next last
2014 Archives by date, by thread · List index

On Sat, Jun 7, 2014 at 10:31 AM, J.B. Nicholson-Owens
<> wrote:

On most OSes (including GNU/Linux) I doubt one can update (in other words,
change) something as low-level as an operating system's kernel and continue
to run the system normally. After the update and before the reboot, the new
kernel is updated on the primary storage medium and the old kernel is still
running in memory. I'd imagine that there are all sorts of kernel
dependencies where the currently-running kernel and newly-installed kernel
differ. Therefore you'll see lots of adverse effects for the currently
running system which are resolved by getting everything rebased on the
updated kernel. Hence kernel update packages are marked to require a reboot
as soon as possible.

I've never seen that happen before, but it makes sense.

Now if I knew why the update got stuck running depmod for more than
ten minutes, I'd feel more comfortable.  Oh, well.


To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.