Skip to content

src/xbps/troubleshooting/static.md: Improve wording and formatting #644

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Vaelatern merged 1 commit into from
Jan 14, 2022
Merged

src/xbps/troubleshooting/static.md: Improve wording and formatting #644

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 9 additions & 9 deletions src/xbps/troubleshooting/static.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,9 +15,9 @@ compiled copy of XBPS.

## Obtaining static XBPS

Statically compiled versions of XBPS are available in all mirrors in the static/
directory. The link below points to the static copies on the primary mirror in
Germany:
Statically compiled versions of XBPS are available on all mirrors in the
`static/` directory. The link below points to the static copies on the primary
mirror in the EU:

<https://alpha.de.repo.voidlinux.org/static>

Expand All @@ -27,9 +27,9 @@ copy on your system (with a preference for the latest copy).
## Using static XBPS

The tools in the static set are identical to the normal ones found on most
systems. The only distinction is that these tools are statically linked to the
musl C library, and should work on systems where nothing else does. In systems
where the platform can no longer boot, it is recommended to chroot in with Void
installation media and use the static tools from there, as it is unlikely that
even a shell will work correctly on the target system. When using static XBPS
with glibc installation, environmental variable `XBPS_ARCH` need to be set.
systems. The only difference is that these tools are statically linked to the
musl C library, and should work on systems where nothing else does. On systems
that can no longer boot, it is recommended to chroot in using a Void
installation medium and use the static tools from there, as it is unlikely that
even a shell will work correctly on those systems. When using static XBPS with a
glibc installation, the environment variable `XBPS_ARCH` needs to be set.