On Wed, 23 Jan 2013 22:06:17 +1100, Gregory Shearman wrote: > > That's fine if you see the message, which you should, and the system > > does not suffer an unplanned reboot, which it shouldn't. But leaving a > > system in a state that won't reboot following a crash or power > > failure is not particularly clever, making the warnings fatal sounds > > a safe default to me. As this is Gentoo there will always be a way to > > turn the airbags off and even disable the brakes :)
> I have all update messages emailed to me using: > > PORTAGE_ELOG_*=<blah> As do I. > After every update I read every message that portage sends me and I act > appropriately upon them. As do I. > BTW, My udev update went without a hitch. I had a revdep-rebuild to do > for a libudev update and that was about it. As did mine, but none of that has any real relevance to my previous point. What if you have an unintentional reboot before you have had a chance to read on and act on the message. The point is that this update can render your machine unbootable, until you take remedial action that you are only informed about after the update. Effectively, that elog message is saying "I have just broken your computer, you'd better fix it before you reboot!". > Even if you didn't see the message and your system didn't boot then you > could still fix things by using your Minimal Install CD to start up, > then chroot into your normal system and rebuild your kernel. That remedy should be reserved for unforseen circumstances, not used as an excuse for casual breakage. -- Neil Bothwick why do kamikazee pilots wear helmets?
signature.asc
Description: PGP signature
