<p><br>
Den 07/01/2013 22.36 skrev "Jameson" <<a href="mailto:imntreal@gmail.com">imntreal@gmail.com</a>>:<br>
><br>
> On Sun, Jan 6, 2013 at 6:38 AM, Kenni Lund <<a href="mailto:kenni@kelu.dk">kenni@kelu.dk</a>> wrote:<br>
> > The issue with rolling release distributions on servers are that every<br>
> > application on the server suddenly can receive a major update which<br>
> > requires your attention. So when you perform a regular system update,<br>
> > which you expect to spend 5 minutes on, you'll end up spending 3<br>
> > hours, since you need to update some configuration file to be<br>
> > compatible with the new major release of some application which was<br>
> > updated. You can choose to avoid updating some of your applications,<br>
> > but it will only be a matter of time until other packages on the<br>
> > system becomes incompatible with your hold-back packages, and hence<br>
> > forcing you to update the packages anyway.<br>
><br>
> If updating config files for package updates is chewing up that much<br>
> of your time, you should check out pacdiff. It along with<br>
> systemd-delta has saved me plenty of time when running updates in<br>
> Arch.</p>
<p>That sentence contained some more examples, but I decided to strip it down before posting the message. Some other real-life examples, which definitely takes longer than doing a diff between two text files and reading the manual:<br>
Updates to the Arch Linux software RAID hook-system breaks assembly of software RAID and hence - in my case - the ability to boot. When the server is a headless server in a cupboard, that will be a PITA.<br>
Same thing applies when the userspace qemu-kvm fork was suddently replaced with the upstream qemu executable, just because some initial <br>
Den 07/01/2013 22.36 skrev "Jameson" <<a href="mailto:imntreal@gmail.com">imntreal@gmail.com</a>>:<br>
><br>
> On Sun, Jan 6, 2013 at 6:38 AM, Kenni Lund <<a href="mailto:kenni@kelu.dk">kenni@kelu.dk</a>> wrote:<br>
> > 2013/1/6 Nick Rout <<a href="mailto:nick.rout@gmail.com">nick.rout@gmail.com</a>>:<br>
> >> I really hate this 2 yearly cycle of updating ubuntu distros, even on LTS. I<br>
> >> thought maybe a rolling release like Arch would alleviate me from having to<br>
> >> do that.<br>
><br>
> I'm running Arch on my home server for just this reason. I probably<br>
> wouldn't recommend it for a commercial production environment where<br>
> applications may require specific patch levels for support, but at<br>
> home I really like it.<br>
><br>
> > The issue with rolling release distributions on servers are that every<br>
> > application on the server suddenly can receive a major update which<br>
> > requires your attention. So when you perform a regular system update,<br>
> > which you expect to spend 5 minutes on, you'll end up spending 3<br>
> > hours, since you need to update some configuration file to be<br>
> > compatible with the new major release of some application which was<br>
> > updated. You can choose to avoid updating some of your applications,<br>
> > but it will only be a matter of time until other packages on the<br>
> > system becomes incompatible with your hold-back packages, and hence<br>
> > forcing you to update the packages anyway.<br>
><br>
> If updating config files for package updates is chewing up that much<br>
> of your time, you should check out pacdiff. It along with<br>
> systemd-delta has saved me plenty of time when running updates in<br>
> Arch.<br>
><br>
> =-Jameson<br>
> _______________________________________________<br>
> mythtv-users mailing list<br>
> <a href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</a><br>
> <a href="http://www.mythtv.org/mailman/listinfo/mythtv-users">http://www.mythtv.org/mailman/listinfo/mythtv-users</a><br>
</p>