table of contents
- bookworm 252.31-1~deb12u1
- bookworm-backports 254.16-1~bpo12+1
- testing 257-2
- unstable 257.1-4
SYSTEMD-ID128(1) | systemd-id128 | SYSTEMD-ID128(1) |
NAME¶
systemd-id128 - Generate and print sd-128 identifiers
SYNOPSIS¶
systemd-id128 [OPTIONS...] new
systemd-id128 [OPTIONS...] machine-id
systemd-id128 [OPTIONS...] boot-id
systemd-id128 [OPTIONS...] invocation-id
DESCRIPTION¶
id128 may be used to conveniently print sd-id128(3) UUIDs. What identifier is printed depends on the specific verb.
With new, a new random identifier will be generated.
With machine-id, the identifier of the current machine will be printed. See machine-id(5).
With boot-id, the identifier of the current boot will be printed.
Both machine-id and boot-id may be combined with the --app-specific=app-id switch to generate application-specific IDs. See sd_id128_get_machine(3) for the discussion when this is useful.
With invocation-id, the identifier of the current service invocation will be printed. This is available in systemd services. See systemd.exec(5).
With show, well-known IDs are printed (for now, only GPT partition type UUIDs), along with brief identifier strings. When no arguments are specified, all known IDs are shown. When arguments are specified, they must be the identifiers or ID values of one or more known IDs, which are then printed. Combine with --uuid to list the IDs in UUID style, i.e. the way GPT partition type UUIDs are usually shown.
OPTIONS¶
The following options are understood:
-p, --pretty
-a app-id, --app-specific=app-id
-u, --uuid
-h, --help
--version
EXIT STATUS¶
On success, 0 is returned, a non-zero failure code otherwise.
SEE ALSO¶
NOTES¶
- 1.
- wikipedia
systemd 252 |