carta
archive_entry_update_uname_utf8(3)

archive_entry_update_uname_utf83

Functions for manipulating ownership and permissions in archive entry descriptions

Part of archive_entry_copy_fflags_text(3).

Usage

gid_t

void

uid_t

void

mode_t

void

const char *

const char *

const wchar_t *

void

void

void

int

const char *

const wchar_t *

void

void

void

int

void

const char *

void

const char *

const wchar_t *

Library

Streaming Archive Library (libarchive, -larchive)

Overview

User id, group id and mode

The functions archive_entry_uid(), archive_entry_gid(), and archive_entry_perm() can be used to extract the user id, group id and permission from the given entry. The corresponding functions archive_entry_set_uid(), archive_entry_set_gid(), and archive_entry_set_perm() store the given user id, group id and permission in the entry. The permission is also set as a side effect of calling archive_entry_set_mode().

archive_entry_strmode() returns a string representation of the permission as used by the long mode of ls(1).

User and group name

User and group names can be provided in one of three different ways:

char *

Multibyte strings in the current locale.

wchar_t *

Wide character strings in the current locale. The accessor functions are named XXX_w().

UTF-8

Unicode strings encoded as UTF-8. These are convenience functions to update both the multibyte and wide character strings at the same time.

archive_entry_set_XXX() is an alias for archive_entry_copy_XXX(). The strings are copied, and don't need to outlive the call.

File Flags

File flags are transparently converted between a bitmap representation and a textual format. For example, if you set the bitmap and ask for text, the library will build a canonical text format. However, if you set a text format and request a text format, you will get back the same text, even if it is ill-formed. If you need to canonicalize a textual flags string, you should first set the text form, then request the bitmap form, then use that to set the bitmap form. Setting the bitmap format will clear the internal text representation and force it to be reconstructed when you next request the text form.

The bitmap format consists of two integers, one containing bits that should be set, the other specifying bits that should be cleared. Bits not mentioned in either bitmap will be ignored. Usually, the bitmap of bits to be cleared will be set to zero. In unusual circumstances, you can force a fully-specified set of file flags by setting the bitmap of flags to clear to the complement of the bitmap of flags to set. (This differs from fflagstostr(3), which only includes names for set bits.) Converting a bitmap to a textual string is a platform-specific operation; bits that are not meaningful on the current platform will be ignored.

The canonical text format is a comma-separated list of flag names. The archive_entry_copy_fflags_text() and archive_entry_copy_fflags_text_w() functions parse the provided text and set the internal bitmap values. This is a platform-specific operation; names that are not meaningful on the current platform will be ignored. The function returns a pointer to the start of the first name that was not recognized, or NULL if every name was recognized. Note that every name — including names that follow an unrecognized name — will be evaluated, and the bitmaps will be set to reflect every name that is recognized. (In particular, this differs from strtofflags(3), which stops parsing at the first unrecognized name.)

History

  • FreeBSD 16.0-CURRENT (2026-10-27): the text shown here
  • FreeBSD 15.1-RELEASE to FreeBSD 14.2-RELEASE
  • FreeBSD 14.1-RELEASE to FreeBSD 14.0-RELEASE
  • FreeBSD 13.5-RELEASE
  • FreeBSD 13.4-RELEASE to FreeBSD 12.2-RELEASE
  • FreeBSD 12.1-RELEASE to FreeBSD 12.0-RELEASE
  • FreeBSD 11.4-RELEASE
  • FreeBSD 11.3-RELEASE to FreeBSD 11.1-RELEASE
  • FreeBSD 11.0-RELEASE
  • FreeBSD 10.4-RELEASE
  • FreeBSD 10.3-RELEASE to FreeBSD 10.0-RELEASE

Bugs

The platform types uid_t and gid_t are often 16 or 32 bits wide. In this case it is possible that the ids can not be correctly restored from archives and get truncated.

From base 16.0-CURRENT-20261027-61c70dc16a79 in FreeBSD 16.0-CURRENT (2026-10-27). Parsed by carta from the page's mdoc source.