mark-wagner

Probably false analogy.

Where do you see that? To me it looks like bandwidth is plan-wide. For example, from the FAQ: "If you delete your instance early and create another one, the free data transfer allowance is shared between the two instances."

Also in the old days tools like sed and awk had more arbitrary limitations. E.g., line length was limited to something (reasonable) like 8192 bytes but input data I was processing was not reasonable.

GNU sed does not have that limit: https://www.gnu.org/software/sed/manual/html_node/Limitation...

The "curl | bash" usages I've seen from reputable sources avoid that by defining a single bash function f and then executing the the function as the final character, i.e.:

  function f {
          echo "hello world"
  }
  f

No, they were talking about marking glibc-2.22 as stable i.e., removing the tilde from the arches in the KEYWORDS of the ebuild.

glibc-2.22-r2 was released at the same time as glibc-2.21-r2 and it contains the fix for this issue. The Changelog merely says "misc upstream fixes" but I verified the relevant changes are there.

The GLSA is https://security.gentoo.org/glsa/201602-02