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.
John Groves 277e777fe8 lib: Add simple crc32c() function 5 years ago
Documentation docs: update TODO 5 years ago
bash-completion bash-completion: Exclude /dev/fd from fsck find 5 years ago
config build-sys: inform gtk-doc about __ul_attribute__ 10 years ago
disk-utils blockdev: be more explicit for BLKSSZ in blockdev.8 5 years ago
include lib: Add simple crc32c() function 5 years ago
lib lib: Add simple crc32c() function 5 years ago
libblkid libblkid: udf: Fix parsing LVID location 5 years ago
libfdisk libfdisk: (gpt) move backup header after device resize 5 years ago
libmount libmount: fix access() utab write test 5 years ago
libsmartcols libsmartcols: (sample) cleanup line separator usage 5 years ago
libuuid misc: cleanup UUID_STR_LEN definitions 5 years ago
login-utils lib/timeutils: add common ISO timestamp masks 5 years ago
m4 build-sys: add libtinfow check 5 years ago
misc-utils cal: simplify leap year rule 5 years ago
po po: merge changes 5 years ago
schedutils misc: consolidate macro style USAGE_HELP_OPTIONS 5 years ago
sys-utils mount: add more details about UUIDs and LABELs to the man page 5 years ago
term-utils lib/timeutils: add common ISO timestamp masks 5 years ago
tests tests: GPT device resize test 5 years ago
text-utils column: allow to hide unnamed columns 5 years ago
tools tools: add segfault detection for 5 years ago
.editorconfig add .editorconfig 7 years ago
.gitignore rfkill: make command to build in util-linux project 5 years ago travis: add make checkusage 5 years ago
.travis.yml travis: minor cosmetics 5 years ago
AUTHORS docs: update AUTHORS file 5 years ago
COPYING docs: corrections to FSF license files, and postal address 11 years ago
ChangeLog build-sys: use AUTOMAKE_OPTIONS = gnu 12 years ago build: use --runstatedir instead of --localstatedir 5 years ago
NEWS build-sys: release++ (v2.31) 5 years ago
README docs: add information about mailing list rejection 5 years ago
README.licensing COPYING: fix grammar of referring phrase, and indicate location better 9 years ago build-sys: add parse-date.y 6 years ago libmount: use eacess() rather than open() to check mtab/utab 5 years ago
util-linux.doap docs: replace FTP by HTTPS in URLs 6 years ago



util-linux is a random collection of Linux utilities

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



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.



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:

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.