MidnightBSD
@midnightbsd
Followers
1K
Following
168
Media
48
Statuses
3K
The official MidnightBSD twitter feed for the open source operating system.
Ypsilanti, MI
Joined November 2011
Update on 4.0 release status: i386 packages are still building. Release notes done Two CVEs came out right after the release. We'll do a 4.0.1 ISO with fixes soon; already in git stable/4.0 branch 4.0.1 will also include a fix for diff3, and zfs ashift setting in installer
0
0
4
Users can help with testing. If you are building from mports rather than using packages, it's OK to start using it. We are actively working on failed mports on the last magus build too.
0
0
1
We're in the middle of preparing the 4.0 release. At this point, we have: ISOs on the FTP A draft of the release notes up. TODO: packages! (i386 is building right now) amd64 has packages, but is missing some critical ones, so it needs another rebuild.
1
0
2
We've fixed a number of ports on 4.0 and current over the last few days. There's also been some updates. The 4.0 package build for amd64 is almost done. We're trending toward at least 100 more packages that passed. A few failed due to our memory disk size
1
0
1
Companies that seem to be trying to do the right thing with robots.txt include: claude, google, amazon, openai, Microsoft, and Apple. Companies that suck include: Baidu, Alibaba, semrush (not ai), and a few that don't even send a proper user agent.
0
0
1
At least once a week, we have some outage due to AI scraping activities. It's becoming a time consuming process when we want to work on the OS. Some AI bots are honoring robots.txt now. Others just plow through the site and cripple it.
1
0
1
We scaled up our package cluster website backend a bit. This includes improvements to our PostgreSQL db running it, and multiple instances of the app to handle more load. This has been causing a lot of 500/503 errors on our site because of AI indexing.
1
0
1
the 64bit package build was delayed by the outage. We've restarted it where it left off.
0
0
2
1. 32bit still needs package build 2. 64bit package build in progress 3. 64bit iso not built yet 4. Release notes neede to be written 5. both ISOs will need to go through testing
1
0
2
Last night, we had a power outage that impacted services. (And OpenAI wants a data center nearby!) Services should be mostly restored at this point. Additionally, we have a possible release ISO for 4.0 32bit on the FTP. There are several caveats...
1
0
3
The rust186 port has been fixed for 4.0/current. Don't use lang/rust only lang/rust186
0
0
2
Feels like we've been fixing or upgrading infra for the last few months. This past weekend, we replaced our two UPS setups with a single larger UPS. We've also recently replaced multiple switches, setup vlans, and moved to a new NAS for package builds.
0
0
3
We put up some new documentation on setting up various ntpd options in MidnightBSD. https://t.co/bd0s8JGGjo
0
0
0
For those using current or stable 4.0 branches, run make check-old and make delete-old with the latest changes in git. This should fix some C++ build issues for a few ports. (old C++ include files from previous version were missed)
0
0
2
For anyone that has issues with zfs pools not mounting after updating to current. force the new cache location! zpool set cachefile=/etc/zfs/zpool.cache tank
0
0
2
To complicate matters, our backups were messed up and the latest backup we had was from early June.
0
0
1
We had some data loss recently with the package build cluster software. This wiped out the in progress magus run for 4.0 and all historical magus runs for 4.0. Other data is fine. We've started a fresh 4.0 amd64 run to get packages refreshed on that branch.
1
0
1
mports updates: OpenSSL 3.0.18 duo unix 2.0.4 (issues with 2.1.0+) libressl libretls zaproxy 2.16.1 tailscale 1.84.0 sshguard 2.5.1
0
0
5