Futureweb

Software

Linux 7.4 drops the UnixWare BFS driver. The header in the user API stays. BeFS is a different name.

Linux 7.4 drops the UnixWare BFS driver and keeps the user API header. BeFS is a different filesystem. This is not the 7.3 release. The pull is the record.

The short version

Phoronix, citing a pull Linus took for Linux 7.4, says the UnixWare BFS driver is gone. The pull says the filesystem only supported contiguous files and had no subdirectories, and that the user API header stays. BeFS, the BeOS filesystem, is a different driver.

A driver that left during the 7.4 pulls

Phoronix's October 20, 2026 item says Linus Torvalds began taking pulls for Linux 7.4 overnight, and that one of them removes BFS, the filesystem UnixWare used for its boot partition. The same item quotes Christian Brauner: the filesystem supports contiguous files and has no subdirectories, the only data on such a partition are kernels and bootloader settings, and the user API header stays. The kernel commit Phoronix links is 355da270c1700db892b8d1c9e0eb76a801e4549a. The document named in the sources is the record this page will keep.Linux 7.3 without the rc suffix.

Not the BeOS filesystem

The September patch that led here, which Phoronix's earlier item quotes, says BFS is not BeFS. Be, Inc. called the BeOS filesystem BFS. Linux named that driver befs because UnixWare's boot filesystem was already called bfs. The October removal is the UnixWare driver. A reader who still mounts BeOS disks is in a different directory. Asked directly, Is Linux 7.4 a released tarball? Not on this page's sources. Phoronix describes pulls entering the 7.4 merge window, including this removal. The 7.3 tarball, filed yesterday, is a different tag.the 7.3 release candidate.

What the diff is willing to count

The September patch Phoronix and the mailing list carried deletes the driver, its documentation, and the build lines, and it says the user API header is retained. The patch stat in that message is about 1,275 lines removed across 20 files. That is the patch's count of the deletion, not a measure of how many machines mounted the filesystem. Asked directly, Does removing the driver delete a UnixWare disk? No. It removes Linux's ability to mount that filesystem in the mainline tree. A disk that still uses it is unchanged. The note says the only data on such a partition was likely kernels and bootloader settings.BeamFS is still a request.

The pull is the October document

An LKML copy of the vfs bfs pull is labeled for v7.4 and dated in the October window. Phoronix's October 20 story is that the pull was honored. Yesterday's brief filed Linux 7.3 as the tarball that had already dropped the release-candidate suffix. A removal inside the next merge window is a later fact. It does not reopen 7.3. The document named in the sources is the record this page will keep. The document named in the sources is the record this page will keep.the software desk.

Why the maintainers said it could go

The quoted argument is narrow: no subdirectories, contiguous files only, no known reason to read that partition from Linux, and a pattern of removing other unmaintained Unix filesystems such as EFS and FreeVxFS in 7.3. Phoronix adds that recent patches against such drivers have been noise. This page will not treat that characterization as a user census. Asked directly, Who asked for the removal? Phoronix attributes the argument to Christian Brauner's pull and, in an earlier September item, to a patch by Ethan Nelson-Moore. Jan Kara acked that patch. The October 20 story is that the pull landed.

What this page will not flatten

It will not say every old filesystem left in the same pull. It will not say UnixWare itself stopped booting. It will not paste the driver's old mount path as an instruction. The record is a mainline deletion, a kept header, and a name that is easy to confuse with BeFS. Asked directly, What does the driver removal keep? The user API header. Phoronix quotes the pull: the driver goes, and the uapi header stays. The document named in the sources is the record this page will keep.

What would put the driver back

A later commit that restores fs/bfs would change this page. A distribution that still ships the driver out of tree would be a different sentence, and this page does not have that packaging note. The user API header remaining means a program that includes the header still compiles against the numbers. It does not mean the kernel will mount the volume. The document named in the sources is the record this page will keep. The document named in the sources is the record this page will keep.the open-source desk.

A September patch and an October merge

The removal was proposed in early September and acked then. October 20 is the day Phoronix reported the pull entering 7.4. Those are two dates. The proposal is not the merge, and the merge window is not a stable tarball. Asked directly, Which filesystem left, and which name is easy to confuse with it? BFS, the UnixWare boot-partition filesystem. BeFS is the BeOS filesystem, and the removal note says Linux already called that one befs because the names collided. The document named in the sources is the record this page will keep.

What stays on the record

UnixWare BFS, not BeFS. Contiguous files, no subdirectories, user API header retained, commit 355da270c1700db892b8d1c9e0eb76a801e4549a, reported as taken for Linux 7.4. The 7.3 release remains the previous brief. The short answer this page will stand on is this: Phoronix, citing a pull Linus took for Linux 7.4, says the UnixWare BFS driver is gone. The pull says the filesystem only supported contiguous files and had no subdirectories, and that the user API header stays. BeFS, the BeOS filesystem, is a different driver. The document named in the sources is the record this page will keep.

Sources

The reports this brief is filing. Futureweb did not republish them.

  1. Phoronix, BFS removed with Linux 7.4
  2. Linux kernel commit 355da270c170
  3. LKML, vfs bfs pull for v7.4

Questions

Which filesystem left, and which name is easy to confuse with it?

BFS, the UnixWare boot-partition filesystem. BeFS is the BeOS filesystem, and the removal note says Linux already called that one befs because the names collided.

What does the driver removal keep?

The user API header. Phoronix quotes the pull: the driver goes, and the uapi header stays.

Is Linux 7.4 a released tarball?

Not on this page's sources. Phoronix describes pulls entering the 7.4 merge window, including this removal. The 7.3 tarball, filed yesterday, is a different tag.

Who asked for the removal?

Phoronix attributes the argument to Christian Brauner's pull and, in an earlier September item, to a patch by Ethan Nelson-Moore. Jan Kara acked that patch. The October 20 story is that the pull landed.

Does removing the driver delete a UnixWare disk?

No. It removes Linux's ability to mount that filesystem in the mainline tree. A disk that still uses it is unchanged. The note says the only data on such a partition was likely kernels and bootloader settings.