Linux 7.4 Removes the Obsolete UnixWare BFS Filesystem
Linux 7.4 is removing the legacy BFS filesystem driver, which was originally used by SCO UnixWare for its boot partition. The change removes roughly 1,200 lines of old kernel code as developers continue cleaning up obsolete and unmaintained filesystem implementations.
The removal is part of a broader effort to reduce the maintenance burden of supporting legacy filesystems that have little practical use on modern Linux systems. Importantly, the kernel change retains the BFS userspace API (UAPI) header, rather than removing every trace of the filesystem interface.
- Linux 7.4 removes the old UnixWare BFS filesystem driver.
- BFS was designed for UnixWare boot partitions containing kernels and bootloader settings.
- The filesystem supports contiguous files but has no subdirectories.
- Approximately 1,200 lines of legacy driver code are being removed.
- The BFS UAPI header is retained.
- This is not the removal of the BFS CPU scheduler, BeFS, or Btrfs.
What Is the BFS Filesystem?
BFS in this announcement refers to the UnixWare filesystem used for a boot partition. It is a legacy filesystem with a very limited design, intended to store a small collection of files needed during system startup.
According to the removal rationale discussed by Linux kernel developers, BFS supports contiguous files and does not provide subdirectories. Its intended contents were primarily operating-system kernels and bootloader settings rather than a general-purpose hierarchy of documents, applications, and user data.
Linux historically included a driver so that systems could access this filesystem. As modern Linux installations and storage formats evolved, however, the practical need for this particular driver became increasingly limited.
BFS is not Btrfs or BeFS
The name can cause confusion because several unrelated technologies use similar abbreviations.
| Name | What it means |
|---|---|
| BFS | The old UnixWare boot filesystem being removed from Linux 7.4. |
| Btrfs | A modern Linux filesystem with features such as snapshots, checksumming, and subvolumes. It is not being removed by this change. |
| BeFS | The filesystem associated with BeOS, distinct from UnixWare BFS. |
| BFS scheduler | A separate CPU scheduling project historically associated with Con Kolivas. It is unrelated to this filesystem-driver removal. |
This distinction is important: the Linux 7.4 change concerns a filesystem driver, not Linux’s general ability to schedule processes or its support for Btrfs.
Why Is Linux 7.4 Removing BFS?
The primary reason is that the old UnixWare filesystem has little remaining practical need within the mainline Linux kernel. Its limited feature set and specialized boot-partition role make it different from filesystems used for everyday Linux storage.
Christian Brauner, who argued for the removal in the patch, explained that the filesystem’s limited purpose and the nature of the data stored on it leave little reason for Linux to continue providing the driver.
The removal rationale also reflects a recurring kernel-maintenance challenge: every supported subsystem can require review, compatibility considerations, testing, and responses to reported bugs, even when the number of active users is very small.
Reducing legacy code and maintenance work
Removing an unused or obsolete driver reduces the amount of code maintained in the mainline kernel. The change eliminates roughly 1,200 lines associated with the BFS driver, making it a small but concrete example of ongoing kernel cleanup.
Less legacy code can reduce future maintenance work and avoid spending development time on components with little demonstrated demand. However, the removal alone should not be interpreted as a measurable performance improvement for normal Linux workloads.
What about bugs and security?
Kernel code can be difficult to maintain when it has few active users or regular contributors. Unmaintained code can still attract bug reports, fuzzing findings, and compatibility concerns.
Removing an obsolete driver can eliminate the need to maintain that code in the mainline kernel. It does not mean that the BFS driver was necessarily responsible for a specific security vulnerability, nor does it imply that all filesystem code is being reduced in the same way.
Linux Has Already Removed Other Legacy Filesystems
BFS is part of a broader series of legacy filesystem removals. Linux 7.3 also saw the removal of FreeVxFS and EFS, two older filesystem implementations that had become difficult to justify maintaining in the mainline kernel.
These changes illustrate the kernel community’s ongoing review of old filesystem drivers. The goal is not to remove every historical filesystem, but to assess whether continued in-tree support remains useful relative to the cost of maintenance.
For systems that still depend on an older filesystem, removal from mainline Linux can have practical consequences. Administrators should identify any real dependency before upgrading kernels on legacy infrastructure.
The BFS UAPI Header Will Remain
One important detail in the removal is that the BFS userspace API header remains in the kernel source tree.
A UAPI header defines interfaces intended to be visible to userspace programs. Retaining it can help preserve compatibility for code that references the relevant interface, even when the kernel’s filesystem driver is removed.
Keeping a header does not mean the filesystem remains mountable or that the removed driver continues to work. Users should distinguish between retaining an interface definition and retaining the kernel implementation that provided filesystem access.
Will This Affect Regular Linux Users?
For most Linux desktop and server users, the removal is unlikely to have a noticeable effect. Modern installations generally use filesystems such as ext4, XFS, Btrfs, or other supported storage formats rather than the old UnixWare boot filesystem.
Users who rely on standard Linux distributions for browsing, development, virtualization, gaming, or server workloads should not expect their normal filesystems to stop working because of this specific change.
Who should pay attention?
- Legacy UnixWare administrators: verify whether Linux-based tools or recovery environments need to read BFS partitions.
- Developers of storage and recovery tools: check for dependencies on the removed driver.
- Distribution maintainers: review downstream patches and any non-mainline use cases.
- Kernel developers: assess whether out-of-tree support is necessary for specialized environments.
For production systems, kernel upgrades should follow the distribution’s supported update process and testing policy. Legacy storage requirements should be checked before deploying a kernel that no longer contains a required driver.
Linux 7.4 BFS Removal at a Glance
| Item | Details |
|---|---|
| Kernel version | Linux 7.4 development cycle |
| Component | UnixWare BFS filesystem driver |
| Original purpose | UnixWare boot partition |
| Filesystem limitations | Contiguous files; no subdirectories |
| Code removed | Approximately 1,200 lines |
| UAPI header | Retained |
| Primary reason | Obsolete, specialized functionality with little remaining need |
| Expected impact | Minimal for typical modern Linux installations |
What This Means for the Linux Kernel
The removal of BFS is a small change in terms of the total Linux kernel, but it demonstrates how kernel development involves both adding new capabilities and retiring old implementations.
Modern Linux continues to add hardware support, filesystem improvements, performance optimizations, and security fixes. At the same time, developers must decide which older features still justify their ongoing maintenance costs.
For most users, the BFS removal will be a background change with no direct effect on everyday computing. For the people who still depend on the UnixWare filesystem, however, it is a reminder to verify storage compatibility before upgrading.
Final Thoughts
Linux 7.4 removes the obsolete UnixWare BFS filesystem driver as part of continued cleanup of legacy kernel code. The driver supported a specialized boot-partition filesystem with limited functionality, and kernel developers see little reason to keep it in the mainline tree.
The removal trims around 1,200 lines of code while retaining the BFS UAPI header. Most contemporary Linux users are unlikely to notice the change, but administrators and developers working with legacy UnixWare storage should confirm their requirements before upgrading.
Above all, remember that this announcement is about the UnixWare BFS filesystem. It does not mean Btrfs is being removed, and it has no connection to the similarly named BFS CPU scheduler.
Sources
- Phoronix: BFS Removed With Linux 7.4 As Old UnixWare File-System
- Phoronix: BFS File-System Being Removed for Linux 7.4
- The Linux Kernel Archives
