3 ms·

The recent FreeBSD 14 release apparently failed to build for one of the platforms because a file "somehow ended up being full of NUL bytes" [0]. I wonder if tha

by ptx 3y ago

The recent FreeBSD 14 release apparently failed to build for one of the platforms because a file "somehow ended up being full of NUL bytes" [0]. I wonder if that's due to this bug? (Could be just a coincidence, of course.) OpenZFS 2.1.4 was included in FreeBSD 13.1, according to the release notes. [0] https://www.daemonology.net/blog/2023-11-21-late-breaking-FreeBSD-14-breakage.html https://www.daemonology.net/blog/2023-11-21-late-breaking-Fr...

inferiorhuman 3y ago
looks at the list looks at the FreeBSD 14.0 errata on freebsd.org This is precisely why I wouldn't run FreeBSD in production. Look at this shit. - You need to freebsd-update fetch install before you upgrade - EC2 AMIs can't handle binary user-data - FreeBSD Update reports 14.0-RELEASE approaching its EoL Two ways to break booting and one really stupid mistake and NONE of it is listed on freebsd.org. Sigh.
- wkat4242 3y ago
  freebsd-update fetch install is part of the normal upgrade process. So yeah of course that's necessary, it's how you upgrade. Not sure what #2 is about, I don't use cloud. And the EoL thing did not happen to me, I did hear of it happening though but it's not omnipresent.
  - inferiorhuman 3y ago
    freebsd-update fetch install is part of the normal upgrade process If the man page and literally every other piece of documentation about upgrading is correct: no, no it's not. If the intent of freebsd-update were only to allow migration from the latest patch level, it would fail instead of corrupting its state, no? The only caveat provided by the freebsd-update man page is the admonishment to read the release notes for special instructions, yet the release notes completely fail to mention this footgun. Or is your assertion that intuition should take the place of documentation?
    - wkat4242 3y ago
      When I upgraded I was sure it told me to be on the latest using this. I'll check where I read that, I don't think it was in the handbook but elsewhere on the site.
cperciva 3y ago
I wonder if that's due to this bug? It's definitely possible. Once we get this bug patched I'll definitely be updating the builders.

by ptx 3y ago

inferiorhuman 3y ago

looks at the list looks at the FreeBSD 14.0 errata on freebsd.org This is precisely why I wouldn't run FreeBSD in production. Look at this shit. - You need to freebsd-update fetch install before you upgrade - EC2 AMIs can't handle binary user-data - FreeBSD Update reports 14.0-RELEASE approaching its EoL Two ways to break booting and one really stupid mistake and NONE of it is listed on freebsd.org. Sigh.

wkat4242 3y ago
freebsd-update fetch install is part of the normal upgrade process. So yeah of course that's necessary, it's how you upgrade. Not sure what #2 is about, I don't use cloud. And the EoL thing did not happen to me, I did hear of it happening though but it's not omnipresent.
- inferiorhuman 3y ago
  freebsd-update fetch install is part of the normal upgrade process If the man page and literally every other piece of documentation about upgrading is correct: no, no it's not. If the intent of freebsd-update were only to allow migration from the latest patch level, it would fail instead of corrupting its state, no? The only caveat provided by the freebsd-update man page is the admonishment to read the release notes for special instructions, yet the release notes completely fail to mention this footgun. Or is your assertion that intuition should take the place of documentation?
  - wkat4242 3y ago
    When I upgraded I was sure it told me to be on the latest using this. I'll check where I read that, I don't think it was in the handbook but elsewhere on the site.

cperciva 3y ago

I wonder if that's due to this bug? It's definitely possible. Once we get this bug patched I'll definitely be updating the builders.