{
  "id": 18521043,
  "title": "Upgrading NetBSD from 11.0 to 11.1",
  "url": "https://urgent.news/2026/11/06/upgrading-netbsd-from-11-0-to-11-1",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-11-06T15:22:55.000Z",
  "source": {
    "name": "Lobsters",
    "slug": "lobsters",
    "url": "https://www.dwarmstrong.org/netbsd-upgrade/"
  },
  "original_language": "en",
  "account": "I upgraded my NetBSD amd64 system from version 11.0 to 11.1, encountering only one minor issue along the way. NetBSD offers two methods for upgrading: using install media and sysinst(8) or performing an in-place upgrade with sysupgrade(8). For major version changes, such as moving from 10.1 to 11.1, sysinst is recommended, while sysupgrade is a convenient option for minor version upgrades. I opted for sysupgrade.\n\nTo begin, I installed the necessary package, which downloaded the appropriate kernel and set it up for my computer. The package then unpacked the new files, prompting me to review and merge any configuration changes. There were only a few files that required manual editing, including passwd and sshd_config. I appreciated how NetBSD displayed the differences between the old and new files and managed the merging of differences. To resolve any issues, I deleted the legacy cache and allowed certctl(8) to handle the certificate updates by rehashing the certificates. I verified that certctl successfully populated the directory.\n\nI then manually re-ran the postinstall fix and confirmed that the system passed inspection. After rebooting the computer, I was pleased to experience the upgrade. It is also important to note that after the upgrade, one should edit /usr/pkg/etc/pkgin/repositories.conf and point pkgin to the new 11.1 repositories.",
  "summary": null,
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}