Originally Posted by TFB
Well that stinks. I guess I'll need to pay attention to updates.
Not really, if you update in console you'll get output that generally will give you big clues. Like when you get output that tells you (summed up) that a service won't restart until next reboot, you know you need to reboot. It's all real easy, and obvious. Like a kernel update, if you get one you'll know it won't be ran until next reboot. Though IMO your best off compiling your own kernel in something like Arch, where you have all the tools. It's even better with Quad Cores, where it takes literally 5 minutes to build. Once you have a base .config made, or use your running one, it's a real quick and easy process these days. Doing that allows you to ignore all kernel updates, cause you won't be running those kernels anyways. =P You also get more up to date, I actually really like the 2.6.37 kernel atm.
 Another obvious is something like Xorg, if Xorg updates you need to restart it. It's more "no brainer" situations, most won't be real secret "you need to restart but I won't tell you" type of things.Edited by mushroomboy - 1/15/11 at 2:05pm