On Fri, 25.01.13 08:58, Simo Sorce (simo@xxxxxxxxxx) wrote:
> On Fri, 2013-01-25 at 05:42 +0000, Matthew Garrett wrote:
> > On Thu, Jan 24, 2013 at 11:46:24PM -0500, Simo Sorce wrote:
> >
> > > We are all grown up enough to decide for our own, just give the
> > > information and let the admin take care of that.
> >
> > Well, that's the problem. Most of our users (including many of the
> > professional sysadmins) are *not* able to make a fully informed choice
> > about whether an online upgrade will ensure that they're no longer
> > running any code with known security issues. That's not a criticism of
> > them - it's just a much harder problem than almost everyone realises.
> >
> > Nobody's suggesting making it impossible to use yum, but blessing it as
> > a first-class distribution upgrade mechanism is a bad idea. There's far
> > too many corner cases, and we can't justify the effort it'd take to fix
> > all of them.
>
> Nonsense, for a distribution upgrade you just recommend the admin to
> reboot the system when done.
> Everybody expects to reboot after a big distro-sync anyway as there is a
> new kernel and basically new-everything.
Ah, so you have to reboot anyway, so where is the difference between
your approach and proper offline updates then? Either way you have to
interrupt your work to reboot the machine. One just takes a slight bit
longer for rebooting...
Lennart
--
Lennart Poettering - Red Hat, Inc.
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
> On Fri, 25.01.13 08:58, Simo Sorce (simo@xxxxxxxxxx) wrote: > > > On Fri, 2013-01-25 at 05:42 +0000, Matthew Garrett wrote: > > > On Thu, Jan 24, 2013 at 11:46:24PM -0500, Simo Sorce wrote: > > > > > > > We are all grown up enough to decide for our own, just give the > > > > information and let the admin take care of that. > > > > > > Well, that's the problem. Most of our users (including many of the > > > professional sysadmins) are *not* able to make a fully informed choice > > > about whether an online upgrade will ensure that they're no longer > > > running any code with known security issues. That's not a criticism of > > > them - it's just a much harder problem than almost everyone realises. > > > > > > Nobody's suggesting making it impossible to use yum, but blessing it as > > > a first-class distribution upgrade mechanism is a bad idea. There's far > > > too many corner cases, and we can't justify the effort it'd take to fix > > > all of them. > > > > Nonsense, for a distribution upgrade you just recommend the admin to > > reboot the system when done. > > Everybody expects to reboot after a big distro-sync anyway as there is a > > new kernel and basically new-everything. > > Ah, so you have to reboot anyway, so where is the difference between > your approach and proper offline updates then? Either way you have to > interrupt your work to reboot the machine. One just takes a slight bit > longer for rebooting... > > Lennart > > -- > Lennart Poettering - Red Hat, Inc. > -- > devel mailing list > devel@xxxxxxxxxxxxxxxxxxxxxxx > https://admin.fedoraproject.org/mailman/listinfo/devel >
-- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
