title really says it all.
Ask HN: Does CopyFail make a stronger case for rolling releases such as Arch?
1–5 of 5 posts
Re: Ask HN: Does CopyFail make a stronger case for rolling releases such as Arch?
#2Good distros should backport updates like this - the patch has been merged into several downstreams. Whilst I prefer a rolling release, this isn't the reason to do it. You could even be on a rolling release that is behind (like arch - my Gentoo box was patched for this vuln before I even understood what it was, and I could run the exploit on my arch machine days laterz until eventually the update came). Speed of response by the upstream here is more important than anything else.
Re: Ask HN: Does CopyFail make a stronger case for rolling releases such as Arch?
#3Good distros should backport updates like this - the patch has been merged into several downstreams. Whilst I prefer a rolling release, this isn't the reason to do it. You could even be on a rolling release that is behind (like arch - my Gentoo box was patched for this vuln before I even understood what it was, and I could run the exploit on my arch machine days laterz until eventually the update came). Speed of resp…
I meant from a software architecture / maintenance standpoint. I assume its that much more work to backport vs just pushing the next change, I also assume this type of issue is only going to happen more thus more backporting / hotpatches ect.
Re: Ask HN: Does CopyFail make a stronger case for rolling releases such as Arch?
#4Good distros should backport updates like this - the patch has been merged into several downstreams. Whilst I prefer a rolling release, this isn't the reason to do it. You could even be on a rolling release that is behind (like arch - my Gentoo box was patched for this vuln before I even understood what it was, and I could run the exploit on my arch machine days laterz until eventually the update came). Speed of resp…
I meant from a software architecture / maintenance standpoint. I assume its that much more work to backport vs just pushing the next change, I also assume this type of issue is only going to happen more thus more backporting / hotpatches ect.
Many users will never accept rolling releases so it doesn't matter if that's easier for the distro developers.
Re: Ask HN: Does CopyFail make a stronger case for rolling releases such as Arch?
#5[dead]