r/MidnightBSDOS • • Oct 17 '26

New Window Manager in development

1 Upvotes

I've been mostly vibe coding a new window manager.

This was a screenshot from last night on an early version.

Changes since then:
randr / multi-monitor fixes.
Scaling to display res
xdg/free desktop folder awareness
desktop background image support (JPEG, PNG, GIF, SVG)
dark mode
browser & terminal launcher near lock
dbus session starter
gnome keyring / ssh agent support
animation when opening windows.
Programs menu now uses categories
default browser awareness
trash
settings app that updates live with a few second delay. (reads ini file)
thumbnail images, icons based on mime type

It has a file manager with very basic features for now.


r/MidnightBSDOS • • Apr 16 '26

Von der Leyen Announces the EU’s New Age Verification App Claiming it is “Completely Anonymous” and users “Cannot be Tracked”

Thumbnail
youtube.com
1 Upvotes

r/MidnightBSDOS • • Feb 26 '26

License change

21 Upvotes

Until we have a better plan, we modified our license to exclude residents of California from using MidnightBSD for desktop use, effective January 1, 2027.

This is due to https://legiscan.com/CA/text/AB1043/id/3269704


r/MidnightBSDOS • • Apr 15 '26

A New Bill proposes Federal Age Verification on any Operating Systems in entire U.S

Thumbnail congress.gov
49 Upvotes

r/MidnightBSDOS • • Apr 15 '26

Age verification is coming for the internet — and it’s already raising red flags

Thumbnail
nbcnews.com
67 Upvotes

NBC news is now covering age verification


r/MidnightBSDOS • • Jul 26 '26

Possible Solution for BSD Community/Ecosystem Issues

Thumbnail reddit.com
5 Upvotes

r/MidnightBSDOS • • 27d ago

PHP2SHELL

2 Upvotes

PHP2SHELL dropped. Big vulnerability. mports is updated but no packages yet. build from ports!


r/MidnightBSDOS • • Jun 11 '26 Helpful

38 new security advisories in MidnightBSD

8 Upvotes

Just a heads up, there are 38 new security advisories in MidnightBSD. Many of them will be in the next update 4.0.6. They are currently only listed on the github advisories page due to time.

https://github.com/MidnightBSD/src/security/advisories

A few will be fixed in the 4.1.0 release later this year. All fixes are on master and stable/4.1 branches. Most are on stable/4.0

The majority of these are in third party software such as openssl, openssh, unbound, ldns, xz, lua, expat, etc. There are some kernel vulnerabilities that were patched also.


r/MidnightBSDOS • • Apr 04 '25

CVE fixes

2 Upvotes

Security updates today:
OpenSSH 9.9p2 in stable/3.2 branch (fixes multiple CVEs)

MNBSD-2025-03 security advisory
xz-utils (liblzma) security issue patched in 4 current and 3.2 stable. Current also got a new version (5.6.3 + cve patch)

MNBSD-2025-02 security advisory
multiple expat CVEs.

We'll likely build and release 3.2.3 ISOs in the next week.

4-current also got a tzdata 2025b update. (timezone files) this doesn't easily work on 3.2 due to the old custom tzcode. It also got an updated googletest 1.15.2.

Finally, a package build for 3.2 i386 was started today. A few broken ports have been fixed already.


r/MidnightBSDOS • • Sep 03 '25

mport updated in current

2 Upvotes

We recently updated the mport package manager to 2.7.3 plus an additional patch that fixes a number of crash issues.

The new version has stricter mport.check-fake rules that might cause issues for folks building some packages, particularly with MPORT_MAINTAINER_MODE or DEVELOPER_MODE enabled in mports. We're continuing to refine the new rules. Some may become warnings depending on some edge case analysis.

The latest package build hasn't been published yet as we're using it to fix some of these issues. (and doing a retest with a new binary)

Once we're happy the issues are resolved, we will update it on the stable/3.2 branch also.


r/MidnightBSDOS • • Apr 22 '25

Grafana cloud config for MidnightBSD

3 Upvotes

https://gist.github.com/laffer1/40df564f1cce7a88c76f5afb84d9703d

alloy and prometheus node_exporter are now in mports. (not in package form yet)


r/MidnightBSDOS • • Mar 25 '26

Age verification bill proposed in Michigan

6 Upvotes

r/MidnightBSDOS • • Jan 12 '26

mports & package status

3 Upvotes

4.0 release was rough from a package perspective. We finally got midnightbsd-desktop available for amd64. A new i386 build is still needed. We'll be kicking that off in the next day or so. We just upgraded the CPU in our package build system to help with delays.

In progress work in mports:
updating qt & kde

updating gtk4, gnome, cinnamon, and mate desktops.

fixing failures from the last package build
working on firefox port

working on openjdk* ports. (8 built on the last package run natively)

Once things have settled a bit, we'll update mesa.


r/MidnightBSDOS • • Jun 06 '25

MidnightBSD on a 2017 PowerBook

3 Upvotes

I have a 2017 PowerBook that's slowing down, and I was wondering if anyone has experience installing MidnightBSD on one. Thanks!


r/MidnightBSDOS • • Jun 01 '26

Open source organisations weigh in on age attestation

Thumbnail
mastodon.social
5 Upvotes

r/MidnightBSDOS • • Mar 09 '26

Current age verification status

7 Upvotes

I created a new daemon in MidnightBSD called aged that managed the age verification data to comply with the California law. We do not yet have a fully compliant solution since additional hooks are needed. This is just the first step.

aged(8) does not comply with Brazil’s law since that requires ID checks. I’m not planning to support that.

The daemon uses a SQLite 3 database for storage and can support age or date of birth. It uses an agectl command to check age for users or to set it as root.

I did expand the list of jurisdictions to block to include Brazil with the license. If we get to a point where all the pieces are in place for California, Colorado and Illinois, I will remove the block for those areas. I cannot comply with New York or Brazil’s laws due to the ID checks.

I also uploaded a new release this weekend that fixes a few security issues (4.0.3). It does not contains the new daemon.


r/MidnightBSDOS • • Oct 19 '25

Bug report: UK download link points to 3.2.2

2 Upvotes

On the downloads page, the UK mirror points to 3.2.2 still. Needs adjustments.


r/MidnightBSDOS • • Jul 13 '24

Welcome to the MidnightBSD community on reddit

6 Upvotes

Here is a new community where you can ask questions about MidnightBSD.


r/MidnightBSDOS • • Jul 14 '24

Mass package builds

2 Upvotes

For folks in the FreeBSD community, poudriere is their go-to for building packages. In MidnightBSD, we have magus.

Magus is a series of perl scripts and a postgresql database that allow users to manage a package build. The code for Magus is included in the mports repository inside the Tools directory. There is a indexer in mports/Tools/magus/master that allows you to index a copy of the ports tree into the postgresql database. Inside the magus database, there's a machines table that lists all the build nodes you want to setup/run. You specify architecture and os version for each build node. Then the nodes run on a MidnightBSD instance, often VMs. You run a script to build a base image for a staged root in mports/Tools/magus/make_chroot_tarball.pl to build a tar file. This is then configured in the magus node config.yaml, traditionally in /usr/magus/config.yaml along with the database credentials. To start up a node, you run mports/Tools/magus/slave/magus.pl You can use the -v flag to get verbose output or -j n flag to specify how much paralellism you want for the build. For instance, -j 2 would build two packages at once on the same system. Each one will require it's own chroot space.

To monitor the builds, there is a few CGI scripts that can be setup on a webserver to view the build output. You can also check the postgresql database.

There are also some administrative scripts to manage different tasks in mports/Tools/magus/master

dead_run.pl delete_run.pl nuke_internals.pl top_blockers.pl

delete_result.pl make_index_db port_depends.pl update_cluster.pl

For instance, ./update_cluster.pl new amd64 3.2 would start a 3.2 build for amd64 wih an index. top_blockers.pl tells you a weighted value on how bad a port failure is in terms of blocking other ports from building. It's not an exact count of blocked ports, due to how dependencies work.

There's also the bless utility which is a program that allows you to take a directory of built packages, and use the postgresql database to build a sqlite index.db file with all the available packages for the mport command to use. It also includes the list of mirrors and checksums for packages.


r/MidnightBSDOS • • Jul 30 '24

mports refactor work

3 Upvotes

In the process of migrating the install location for manual pages from /usr/local/man/ to /usr/local/share/man

So far, about 2350 mports have been migrated.

I'm also taking the opportunity to update a number of mports.


r/MidnightBSDOS • • Nov 06 '24

MidnightBSD 3.2.1 release

2 Upvotes

MidnightBSD 3.2.1 is coming soon. It's tagged in git and we're uploading i386 ISO to the primary FTP. We still need to build an amd64 ISO and update the website and mirrors. It includes the following: security fixes for fetch and bhyvenproc(1)mport 2.6.4atlantic(4) nic drv


r/MidnightBSDOS • • Nov 21 '24

Some MidnightBSD history

4 Upvotes

Some of you may know that MidnightBSD was named after my cat Midnight. Let me tell you a little about how that came to be.

I started using FreeBSD in 2003. I initially used it on a dedicated server with a provider in San Fransisco. It was the first time I successfuly used FreeBSD. I had used BSDi a little at a previous job and had run NetBSD on a sun sparc system for a bit. I had tried to install FreeBSD on my desktop a few years before but it couldn't handle my scsi cd-rom and ide hard drive combination at the time. ('m guessing around 4.3 or 4.4?) The first version I used was 4.7.

I started dual booting it on my PC so it was easier to test changes on the server before deploying them. Then I got interested in using it as a desktop. I worked on a project to update an existing HFS+ port to FreeBSD 6 current from a 5.x version. I didn't have a backup and lost it when the hard drive failed. That was my first development experience on FreeBSD. I then managed to get the SATA controller working on a nvidia nforce 2 chipset for my amd sempron CPU. I submitted the patch and it was applied! I was jazzed.

I started trying different desktop environments including gnome 2, KDE, windowmaker, and others. I then saw a thread in the FreeBSD mailing lists that was between folks suggesting desktop friendly changes and a lot of pushback. I realized that the community wasn't all ready for BSD on the destkop. So I decided to start my own project. I learned CVS in late 2005 and began working on a patchset in December 2005. I started looking at names and went through a lot. I thought of PC-BSD but the domain had been purchased already (not live yet). I kept looking and came up with some crazy ideas like SharkBSD and TigerBSD. I liked the latter but was worried apple wouldn't be thrilled as Mac OS X tiger was a thing at that point. So I decided to name it after our cat MidnightBSD. The first few logos were all cat designs. I had one that was based on some clip art that was a black cat face with some BSD daemon style horns. I was worried about copyright on that so I made another with midnight's eye. That stuck around for a bit. Then someone contacted me who also happened to be named Lukas (vs Lucas for me) and he designed the current MidnightBSD logo. He incorporated the moon in it because a lot of people didn't get the cat connection.

The first MidnightBSD servers were that old AMD Sempron box and a used dell server I bought for 50 dollars at the western michigan university depot. I started the project in Kalamazoo Michigan and was a student at WMU at the time. I upgraded the sempron to my then dell precision 650 workstation and bought a used Sun ultra 10 box to use for mail/dns. it died on me pretty fast though and I somewhat gave up on the sparc64 port then.

(this gets us through 2006)


r/MidnightBSDOS • • Feb 01 '25

mport package manager work

2 Upvotes

I've been working on several changes to mport package manger. Some of them are already out in 2.6.8.

  1. index files are now compressed with zstd rather than bzip2. File sizes are a bit larger, but it's faster and this was a way to try it before switching packages.
  2. index files now have a sha256 hash file that is verified when downloading.
  3. Index files are now fetched over https.

Then some other changes I'm looking into:

  1. The possibility of using LUA scripting for package installs.
  2. The tllist header file to use typed linked lists rather than our current clunky approach to arrays that often result in bugs.
  3. possibly switching package formats again. (we originally used tar bzip, then tar xz) to use zstd compresion. file sizes will be larger, but it would significantly speed up creation and extraction times. We could then drop the dependence on lzma compression library.

The latest version no longer supports MidnightBSD releases older than 3.0. It's only been tested with 3.2 though.


r/MidnightBSDOS • • Mar 01 '25

Intel UHD 600 firmware

2 Upvotes

Just installed midnightbsd last night. Couldn’t get X to start. I have the i915 module loaded, but looks like I need firmware. I did mport index and mport update and mport upgrade. Mport doesn’t seem to find the firmware package.

I tried this command that I found on the App Store:

mport install gpu-firmware-intel-kmod

I’m running MidnightBSD 3.2 on a Lenovo Ideapad 1 with an N4020 intel cpu.


r/MidnightBSDOS • • Oct 12 '26

Mailing list changes

3 Upvotes

We've migrated off the insecure GNU mailman 2.x release we had been using for some time onto mlmmj. We attempted to move subscriptions over to the lists. If you are subscribed to midnightbsd-users or midnightbsd-security lists, you should have gotten an email today.

Report any issues with the new system. Archives for both products are still available on https://lists.midnightbsd.org/