On Wed, Jul 27, 2016 at 8:56 PM, Josh Boyer <jwboyer@xxxxxxxxxxxxxxxxx> wrote: > How does the reboot-required package get installed in the first place? > I was assuming something during the update process would install it, > which means something has to Require it or install it in some manner. I haven't figured that part out yet, one reason I started this discussion. For now I think leaving it up to the adminstrator is best, just like unattended-upgrades in Debian. > > (As an aside, I've never heard of /etc/kerne/postinst.d until now. I > have no idea if anything even looks in there in Fedora.) Neither did I. /usr/sbin/new-kernel-pkg is the one executing the scripts in there. At one point it looks like mkinitrd owned that directory: https://bugzilla.redhat.com/441111 dracut drops scripts in there, but it doesn't own it either. > >>>>> Also, I think "recommended" is really the appropriate terminology >>>>> here. There is very little that _requires_ a reboot to be done after >>>>> it is installed. >>>> >>>> It's that little part I care very much about ;) >>> >>> For what purpose though? Do you care because you want to make sure >>> your software is running with all security fixes? Do you care because >>> you want to simply be running the latest and greatest at all times? >> >> Primarily security fixes. > > OK. It might be beneficial to look at the update metadata anyway in > that case, to see what is labeled as a security fix. I will do that. > >>> Checking the update metadata could probably be done in dnf itself if >>> it isn't already. I believe Software already looks at this flag if >>> you are using that to apply your updates. If you simply want to >>> always be running the latest, then 'dnf update && reboot' solves that >>> need. >> >> In the case I've been thinking of the updates are done by us, or >> puppet, but the reboots are scheduled >> by our customers at a time which suits them. We don't always know if >> they've rebooted already >> and checking /var/run/reboot-required would be an easy way to remind them. >> >> For Debian / Ubuntu motd also lets them know as soon as they login, which helps. > > I think what you're trying to accomplish is certainly possible. I'm > not sure the exact implementation of having it done as a separate > package is the best method, but it's a possibility I guess. I'll get started on it, and I'm certain other people will prove me wrong ;) Thank you for your comments, Ruben -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://lists.fedoraproject.org/admin/lists/devel@xxxxxxxxxxxxxxxxxxxxxxx
