From 1b332461529851b16ccc725807abb3cdd069ba82 Mon Sep 17 00:00:00 2001 From: Elara Musayelyan Date: Mon, 23 Oct 2023 14:19:57 -0700 Subject: [PATCH] Clarify README --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index f070875..8503f08 100644 --- a/README.md +++ b/README.md @@ -12,6 +12,6 @@ Instead of injecting custom libc functions, this library uses Linux's user names ### Why? -Fakeroot is very useful for building packages, as various utilities depend on file permissions and users. For example, the `tar` command that creates tar archives. It creates files inside the tar archive with the same permissions as the original files. That means if the files were owned by a particular user, they will still be owned by that user when the tar archive is extracted. This is problematic for package building because it means you can end up with system files in a package, owned by non-root users. Fakeroot is used to trick utilities like `tar` into making files owned as root. +Fakeroot is very useful for building packages, as various utilities depend on file permissions and users. For example, the `tar` command. It creates files inside the tar archive with the same permissions as the original files. That means if the files were owned by a particular user, they will still be owned by that user when the tar archive is extracted. This is problematic for package building because it means you can end up with system files in a package, owned by non-root users. Fakeroot is used to trick utilities like `tar` into making files owned as root. Many utilities require root privileges for some operations but return errors even if the specific thing you're doing doesn't require them. Fakeroot can also be used to execute these programs without actually giving them root privileges, which provides extra security.