{
  "@context":[
    "https://www.w3.org/ns/activitystreams",
    {"Hashtag":"as:Hashtag"}
  ],
  "published":"2025-02-23T03:01:42.903Z",
  "attributedTo":"https://fedi.weebyte.com/actors/gizmo",
  "replies":"https://fedi.weebyte.com/objects/5iLwa0tISwo/replies",
  "to":["https://www.w3.org/ns/activitystreams#Public"],
  "cc":["https://fedi.weebyte.com/actors/gizmo/followers"],
  "content":"<p>I occasionally revisit my Proxmox VM of FreeBSD to see if it can change my current opinion of it, which is that it is barely fit for purpose. But no, it reinforced my opinion today.</p><p>The VM has 14.1-RELEASE installed, reasonably recent you might say. So I attempt to run `freebsd-update fetch` and get as response \"Fetching 2 metadata files... failed\". I try this several times with the same result. Scanning the forums produces nothing useful, but on a whim I try modifying ServerName in `/etc/freebsd-update.conf` from `update.FreeBSD.org` to `update1.FreeBSD.org`.</p><p>No go, same result. OK, try `update2.FreeBSD.org`. It works and my system gets updated! This is a fundamental tool for maintaining a FreeBSD system and it cannot even work its way through the mirrors when it encounters one that fails.</p><p>I have had similar issues in the past, where an upgrade broke my BastilleBSD jails sufficiently to require a fresh install of the latest version of the OS. These issues never seem to plague me on Linux which is why I keep abandoning my experiments with BSD. It really does feel more like someone's hobby project than something \"that just works\".</p><p>I guess I will try again in a few releases' time... </p><p><a href=\"https://fedi.weebyte.com/tags/freebsd\" class=\"hashtag\" rel=\"tag\">#freebsd</a></p>",
  "mediaType":"text/html",
  "attachment":[],
  "tag":[
      {"type":"Hashtag","name":"#freebsd","href":"https://fedi.weebyte.com/tags/freebsd"}
  ],
  "type":"Note",
  "id":"https://fedi.weebyte.com/objects/5iLwa0tISwo"
}