OpenSUSE considers dropping reiserfs
As Jeff Mahoney notes in this message to the openSUSE
factory list, the reiserfs filesystem has been unmaintained for years and lacks
many of the features that users have come to expect. He has thus proposed
removing reiserfs from openSUSE Tumbleweed immediately.
I recognize
that there may be people out there with disks containing reiserfs file
systems. If these are in active use, I would seriously encourage
migrating to something actively maintained.
[$] 6.0 Merge window, part 1
The merge window for the kernel that will probably be
called "6.0" has gotten off to a strong start, with 6,820 non-merge changesets
pulled into the mainline repository in the first few days. The work pulled so
far makes changes all over the kernel tree; read on for a summary of what has
happened in the first half of this merge window.
Security updates for Friday
Security updates have been issued by CentOS (firefox,
thunderbird, and xorg-x11-server), Debian (xorg-server), Gentoo (Babel, go,
icingaweb2, lib3mf, and libmcpp), Oracle (389-ds:1.4, go-toolset:ol8, httpd,
mariadb:10.5, microcode_ctl, and ruby:2.5), Red Hat (xorg-x11-server),
Scientific Linux (xorg-x11-server), SUSE (buildah, go1.17, go1.18, harfbuzz,
python-ujson, qpdf, u-boot, and wavpack), and Ubuntu (gnutls28, libxml2, mod-
wsgi, openjdk-8, openjdk-8, openjdk-lts, openjdk-17, openjdk-18, and python-
django).
GitLab plans to delete dormant projects in free accounts (Register)
The Register reports that GitLab is planning to start
deleting repositories belonging to free accounts if they have been inactive for
at least a year.
GitLab is aware of the potential for angry
opposition to the plan, and will therefore give users weeks or months of
warning before deleting their work. A single comment, commit, or new
issue posted to a project during a 12-month period will be sufficient to
keep the project alive.
[$] A security-module hook for user-namespace creation
The Linux Security Module (LSM) subsystem works by way of
an extensive set of hooks placed strategically throughout the kernel. Any
specific security module can attach to the hooks for the behavior it intends to
govern and be consulted whenever a decision needs to be made. The placement of
LSM hooks often comes with a bit of controversy; developers have been known to
object to the performance cost of hooks in hot code paths, and sometimes there
are misunderstandings over how integration with LSMs should be handled. The
disagreement over a security hook for the creation of user namespaces, though,
is based on a different sort of concern.
