You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
ThomasKaiser 7076703b52 lscpu: Add Kryo 3XX Gold core 3 days ago
.github/workflows Merge branch 'patch-1' of 3 days ago
Documentation docs: update v2.38-ReleaseNotes 6 months ago
bash-completion lsblk: introduce 'MQ' column 4 months ago
config build-sys: gtkdoc-fixxref v1.27 requires module option 5 years ago
disk-utils sfdisk: inform about failed fsync() [coverity scan] 2 months ago
include Merge branch 'luks/checksum' of 3 weeks ago
lib lib/path: ul_path_cpuparse: fix parsing of empty sysfs files 6 days ago
libblkid Merge branch 'xfs/checksum' of 3 days ago
libfdisk libfdisk: (gpt) don't ignore fsync() errors 2 months ago
libmount libmount: remove mtab locking 4 months ago
libsmartcols libsmartcols: (sample) remove hidden variable [CodeQL scan] 2 weeks ago
libuuid libuuid: check clock value from LIBUUID_CLOCK_FILE 1 month ago
login-utils lslogins: support more password methods 1 month ago
m4 build-sys: use $LIBS rather than LDFLAGS 1 year ago
man-common colors.adoc: format command name bold 8 months ago
misc-utils lsfd: (man) write about UNIX-STREAM and UNIX sockets 1 week ago
po meson: don't build po if no gettext 5 months ago
po-man Add pipesz.1.adoc to po4a configuration 4 months ago
schedutils taskset: warn if affinity is not settable 2 months ago
sys-utils lscpu: Add Kryo 3XX Gold core 3 days ago
term-utils write: (man) fix history section 2 weeks ago
tests tests: (lsfd) add a case for testing SOCKNETNS column 1 week ago
text-utils column: fix greedy mode on -l 2 months ago
tools tools: add git-tp-sync-man 7 months ago
.editorconfig add .editorconfig 7 years ago
.gitignore pipesz: add the pipesz utility 5 months ago
AUTHORS docs: update AUTHORS file 6 months ago
COPYING docs: corrections to FSF license files, and postal address 11 years ago
ChangeLog docs: Correct ChangeLog URL to history log. 2 years ago build-sys: distribute Meson files 7 months ago
NEWS build-sys: release++ (v2.38) 6 months ago
README docs: update IRC address 11 months ago
README.licensing docs: add GPLv3 text 3 years ago build-sys: use set +e before patch --try in ./ 12 months ago build-sys: make pipesz optional 1 month ago meson: enable nls support 3 weeks ago
meson_options.txt meson: enable nls support 3 weeks ago
util-linux.doap docs: update github URL 11 months ago



util-linux is a random collection of Linux utilities

Note: for the years 2006-2010 this project was named "util-linux-ng".


See Documentation/howto-compilation.txt.



The mailing list will reject email messages that contain:
- more than 100K characters
- html
- spam phrases/keywords


#util-linux at


The IRC channel and Mailing list are for developers and project
maintainers. For end users it is recommended to utilize the
distribution's support system.



Bug reports with sensitive or private information: Karel Zak <>

This project has no resources to provide support for distribution specific
issues. For end users it is recommended to utilize the distribution's
support system.


PO files are maintained by:


Standard releases:
major = fatal and deep changes
minor = typical release with new features
maint = maintenance releases; bug fixes only

Development releases:


Download archive:

See also:

SCM (Source Code Management) Repository:

Primary repository:
git clone git://

Backup repository:
git clone git://

Web interfaces:

Note: the GitHub repository may contain temporary development branches too.

The repository contains master (current development) and stable/*
(maintenance) branches only. All master or stable/* changes are always pushed
to both repositories at the same time.

Repository Branches: 'git branch -a'
master branch
- current development
- the source for stable releases when deemed ready.
- day-to-day status is: 'it works for me'. This means that its
normal state is useful but not well tested.
- long-term development or invasive changes in active development are
forked into separate 'topic' branches from the tip of 'master'.

stable/ branches
- public releases
- branch name: stable/v<major>.<minor>.
- created from the 'master' branch after two or more release
candidates and the final public release. This means that the stable
releases are committed, tagged, and reachable in 'master'.
- these branches then become forked development branches. This means
that any changes made to them diverge from the 'master' branch.
- maintenance releases are part of, and belong to, their respective
stable branch. As such, they are tags(<major>.<minor>.<maint>) and
not branches of their own. They are not part of, visible in, or
have anything to do with the 'master' development branch. In git
terminology: maintenance releases are not reachable from 'master'.
- when initially cloned (as with the 'git clone' command given above)
these branches are created as 'remote tracking branches' and are
only visible by using the -a or -r options to 'git branch'. To
create a local branch use the desired tag with this command:
'git checkout -b v2.29.2 v2.29.2'

Tags: 'git tag'
- a new tag object is created for every release.
- tag name: v<version>.
- all tags are signed by the maintainer's PGP key.

Known Bugs:
- don't use tag v2.13.1 (created and published by mistake),
use v2.13.1-REAL instead.


1) development (branch: <master>)

2) master release (tags: v2.29-rc1, v2.29-rc2, v2.29, branch: <master>)

3) development (work on v2.30, branch: <master>)

4) fork -- create a new branch <stable/v2.29> based on tag v2.29

4a) new patches or cherry-pick patches from <master> (branch: <stable/v2.29>)

4b) stable release (tag: v2.29.1, branch: <stable/v2.29>)

4c) more patches; another release (tag: v2.29.2, branch: <stable/v2.29>)

5) master release v2.30 (branch: <master>)

where 3) and 4) happen simultaneously.