Unfortunately the information to 'suggest a reboot' is not tied to a 'package', but to a 'patch'. A 'patch' describes the minimal versions of a bunch of packages which need to be installed in order to fix the issue addressed by the 'patch'. "zypper patch" is the operation which evaluates the patch metadata and which is able to suggest a reboot in the summary, if patch providing this hint was applied (i.e. all mentioned packages were updated accordingly). "zypper up" however is a pure package based operation trying to update each package individually to a higher version. The final result might be similar to "zypper patch", but the approach is different and the patch hints are not available here. @ the "old" kernel is left lying around in /boot Well, it's usually a bad idea to remove the running kernel from disk. That's why obsolete kernel packages are usually removed after reboot. The definition which kernel packages too keep is found in /etc/zypp/zypp.conf (see multiversion.kernels). Default is to keep the latest 2 kernel versions (and the booted one). I'll keep this open as 'enhancement' request. maybe we can teach 'up' to sneak into the patch matadata looking for reboot hints.