On Mon, 2004-01-12 at 23:36, Don wrote: > With MS Windows, it seems a reboot is required after nearly every > software update. > > One of the things I like about UNIX/Linux is the overall design of > things such that reboots are not really part of the "problem > resolution process". > But, how do I know what needs to be restarted/rebooted when updates to > things like cron or glibc are installed? To "be safe" I could always > reboot the machine after installing updates, but that seems > unnecessary and certainly unwanted. In principle, the only update for which a reboot is needed is Linux (since it is the most common kernel of the GNU system), but even this may change in the future. However, some updates might imply a reboot both to make sure everything starts up properly in case an accidental reboot happens (like a power loss), or to make sure every software running uses the updated libs (RedHat used to advice a reboot on glibc updates). Hugs, Rui -- + No matter how much you do, you never do enough -- unknown + Whatever you do will be insignificant, | but it is very important that you do it -- Gandhi + So let's do it...? Please AVOID sending me WORD, EXCEL or POWERPOINT attachments. See http://www.fsf.org/philosophy/no-word-attachments.html
Attachment:
signature.asc
Description: This is a digitally signed message part
