On Sat, Jun 7, 2014 at 10:31 AM, J.B. Nicholson-Owens <[email protected]> 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. Thanks. -- To unsubscribe e-mail to: [email protected] Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/users/ All messages sent to this list will be publicly archived and cannot be deleted
