cross-posted from: https://lemmy.dbzer0.com/post/66388621

transcript

A ^fake^ email. It reads: From: Linus Torvalds torvalds@linux-foundation.org To: linux-kernel@vger.kernel.org Subject: [RFC] Remove IPv4 support from kernel, effective next merge window Date: Sat, 15 Aug 2025 10:42:00 -0700 Message-ID: 20250815-drop-ipv4@linux-foundation.org

Hey folks,

After yet another deeply technical and entirely calm discussion about HRT (High-Resolution Timers) that somehow devolved into 200+ replies, personal insults, and at least one GIF of a raccoon, I have decided it’s time to take drastic measures.

Effective next merge window, we will be removing IPv4 support from the kernel. This will both (a) resolve the maintainers’ scheduling disputes, and (b) force the world into the IPV6 utopia we were promised back in 1998.

If you need IPv4 after this point, you can either:

run an ancient kernel from before the change (good luck with the bugs), or rewrite your applications to use IPv6 and learn to love colons in your addresses. Yes, I realize this will break roughly *everything *. No, I don’t care. I have already switched all my machines to IPv6-only, except for the toaster, which unfortunately still insists on using a 192. 168. x. x address. The toaster will be replaced.

If you disagree with this decision, I suggest you take it up with the HRT maintainers. But please keep it civil this time. (Or at least keep the raccoon GIFs under 1MB.)

  • Linus
From: Linus Torvalds <torvalds@linux-foundation.org> To: linux-kernel@vger.kernel.org Subject: [RFC] Remove IPv4 support from kernel, effective next merge window Date: Sat, 15 Aug 2025 10:42:00 -0700 Message-ID: <20250815-drop-ipv4@linux-foundation.org>  Hey folks,  After yet another deeply technical and entirely calm discussion about HRT (High-Resolution Timers) that somehow devolved into 200+ replies, personal insults, and at least one GIF of a raccoon, I have decided it’s time to take drastic measures.  Effective next merge window, we will be removing IPv4 support from the kernel. This will both (a) resolve the maintainers’ scheduling disputes, and (b) force the world into the IPV6 utopia we were promised back in 1998.  If you need IPv4 after this point, you can either:  run an ancient kernel from before the change (good luck with the bugs), or rewrite your applications to use IPv6 and learn to love colons in your addresses. Yes, I realize this will break roughly *everything *. No, I don’t care. I have already switched all my machines to IPv6-only, except for the toaster, which unfortunately still insists on using a 192. 168. x. x address. The toaster will be replaced.  If you disagree with this decision, I suggest you take it up with the HRT maintainers. But please keep it civil this time. (Or at least keep the raccoon GIFs under 1MB.)  - Linus

all 23 comments

sorted by: hot top controversial new old
[+] [S] 53 points 5 months ago* (last edited 2 days ago) (2 children)
  • [–] 28 points 5 months ago

    That's it, I'm deleting the internet

  • source
  • [–] 25 points 5 months ago

    I always knew Linus loves colons.

  • source
  • [–] 21 points 5 months ago

    Good, we should be by IPv9 already, but I can wait.

  • source
  • [–] 20 points 5 months ago (9 children)

    I'm so confused. It's april 1st ok but we're discussing an email from last august?

  • source
  • hideshow 9 child comments
  • [–] 22 points 5 months ago (5 children)

    Kinda like ipv6 adoption, huh?

  • source
  • parent
  • hideshow 5 child comments
  • [–] 7 points 5 months ago (4 children)

    Still confused. IPV6 when communicating externally, IPv4 on the local network because at least we can understand these addresses.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 3 points 5 months ago

    I was making a joke about how the email was dated back in August 2025, and how it’s being posted now (for April Fool’s Day). The comparison being that the email talked about waiting on IPv6 adoption since 1998.

    But you’re right that using IPv4 locally makes sense. Ain’t no way I’m trying to remember a 128-bit address.

  • source
  • parent
  • [–] 17 points 5 months ago

    This is all just a distraction for the real best option, IPv5

  • source
  • [–] 11 points 5 months ago

    cool, fuck half of the world

  • source
  • [–] 9 points 5 months ago

    PROTOCAL 7 LIVES

  • source
  • [–] 7 points 5 months ago

    Ok, yeah, late to the discussion, but that's because I used RFC2549

  • source
  • [–] 4 points 5 months ago

    ipv6 still sucks.

    Real solution to ipv4 problem- ipv4 but we add another triplet.

  • source
  • [–] 3 points 5 months ago

    loved being behind a triple nat and sharing the public IP with every customer in the county

  • source
  • [+] 2 points 5 months ago* (last edited 3 months ago)