nyuuzyou/wikis huggingface dataset:
Glpi

GLPI is the Information Resource-Manager with an additional Administration- Interface. You can use it to build up a database with an inventory for your company (computer, software, printers...). It has enhanced functions to make the daily life for the administrators easier, like a job-tracking-system with mail-notification and methods to build a database with basic information about your network-topology.
The principal functionalities of the application are :
1) the precise inventory of all the technical resources. All their characteristics will be stored in a database.
2) management and the history of the maintenance actions and the bound procedures. This application is dynamic and is directly connected to the users who can post requests to the technicians. An interface thus authorizes the latter with if required preventing the service of maintenance and indexing a problem encountered with one of the technical resources to which they have access.
== Install lighttpd, PHP, and MySql ==
== Install Mysql server packages ==
== Configuring MySql ==
 /usr/bin/mysql_install_db --user=mysql
 rc-service mariadb start && rc-update add mariadb default
 /usr/bin/mysqladmin -u root password 'password'
Create the GLPI database
Note: you can create the database from command line or from the GLPI web page later.
== Installing GLPI ==
Create a folder named 
Download the source code archive 
Unpack and delete tar file
Change the folder permissions
Create a symlink to the folder
== Configuring GLPI ==
Browse to: http://WEBSERVER_IP_ADDRESS/glpi and install GLPI by completing the information as appropriate from the web browser.
GLPI Installation steps:
GLPI SETUP
* Select your language
* Licence
: I have read and ACCEPT the terms of the license written above.
* Beginning of the installation - Installation or update of GLPI
:* Choose 'Install' for a completely new installation of GLPI.
:* Select 'Update' to update your version of GLPI from an earlier version
* Checking of the compatibility of your environment with the execution of GLPI
:* Continue ?
* Database connection setup
:* Mysql server: localhost
:* Mysql user: root
:* Mysql password : password
* Test of the connection at the database
: Database connection successful
: Create a new database or use an existing one: glpi
* Database created
OK - database was initialized
Default values have been entered, feel free to delete them if you want
Upon first connection you can use the login glpi and the password glpi in order to access the application with administrator rights
After click on "continue" you will see The installation is finished.
Congratulations, you installed GLPI!
You can delete or modify these accounts as well as the first entries in the database. Use GLPI.
Browse to http://WEBSERVER_IP_ADDRESS/glpi now
Category:SQL
Graphics driver

Many desktop environments need a graphics driver to work properly. Install Mesa drivers for all graphics cards before installing a desktop. Mesa-gallium is an open-source OpenGL implementation that supports a variety of hardware and software drivers, including Intel, AMD, NVIDIA, and more. 
* : Mesa drivers for all Graphics cards.
* : Mesa vaapi drivers for all video decoding acceleration.
Graphics cards of recent vintage need a driver to work. Install additional graphics drivers from the below depending on your hardware. If you are unsure about your graphics card, use lspci from package to identify the graphics card: 
Then, install an appropriate driver. 
* For Intel video chipsets, see Intel Video
* For AMD Radeon Chipsets, see Radeon Video
* For Nvidia Chipsets, see Nvidia Video
For details on legacy Xorg drivers refer Xorg page.
category:Graphics
category: Drivers
category: Desktop
Greetd

greetd is a minimal and flexible login manager daemon that makes no assumptions about what you want to launch. Greetd needs to be combined with a greeter. You can find a list of available greeters: . 
== Text based greeter ==
Text based greeter like can log you into a normal terminal session. Make sure that vt is set in:
Remember to activate greetd service. 
== Graphical greeter - gtkgreet ==
The following section details the steps for using the graphical greeter gtkgreet which is packaged as . 
# Install the main package and the greeter:
# Install a lightweight wayland compositor to be used with greetd login session.(If using Sway, no need for ).
# Graphical greeters like gtkgreet require either seatd or elogind. If using seatd, follow the additional steps for using seatd with greetd.
# Gtkgreet reads desktop sessions from the file , So create the file with the list of login environments/desktop sessions. Instead of listing <Code>sway</Code> a wrapper script like <Code>sway-run</Code> can be used.
# If using cage, do not skip the -s option and the config file appears as follows:
# Instead of , any other wayland compositor like sway can be used by setting the greetd config file: 
# If sway is used, create a dedicated sway config file that runs the greeter and terminates when it dies: 
# Remember to activate greetd service.
== Using seatd with greetd ==
 
When seatd is used, following additional configuration is required.
# For graphical greeters like gtkgreet, the user greetd needs the seatd group: 
# Append rc_need=seatd in the following file:
== Activate greetd service ==
Once you have completed the above configuration i.e text or graphical greeter, enable and start greetd:
== Auto-login ==
Follow greetd wiki for auto-login instructions. No alpine Linux specific changes are required.
== See also ==
* greetd wiki
* Arch wiki
Category:Display Managers
Category:Desktop
Category:Services
HAProxy

HAProxy is a free, very fast, and reliable reverse-proxy offering high availability, load balancing, and proxying for TCP and HTTP-based applications.
A unique feature is that HAProxy can be configured for TLS termination to occur locally on the HAProxy server or it can be configured to pass through TLS termination at the backend via SNI.
== Installation ==
HAProxy package is available in the Alpine Linux repositories. To install it run:
=== System scripts ===
If you are running OpenRC, then you can install with:
If you are running runit, s6, or dinit, (or other), then there are no scripts packaged for your init systems yet. Please feel free to contribute a package with them.
=== Local Documentation ===
If you want local documenation, then you can install that with:
== See Also ==
* HAProxy Homepage
Category:Web Server
Hardened linux

== Why Linux-Hardened Kernel? ==
You may want to get a more security focused kernel, custom private syscalls (only if you compile it for yourself and is not publicly shown), apply Grsecurity/KSPP/GrapheneOS kernel hardening suggestions and remove attack surface from the kernel (with the kernel-hardening-checker APK package).
== Developing Linux-hardened kernel with hardened patch ==
Make a custom linux kernel using this guide [1]. Once you have setup the linux kernel from there, in your current directory ($YOUR_WORK_DIR/aports/main/linux-lts), gather linux hardened patches via these two CLI commands (Replace "$VERSION" with the current latest version in the releases):
In the "APKBUILD" file, change this "source" line to this:
In "APKBUILD" file again, change "pkgver" and "pkgrel" to the same as the releases patch file's "$VERSION"
You may change the pkg name's flavor (if you do that, replace all words "lts" with your preferred flavor name (for example "hardened"), and, for example, change the file lts.x86_64.config to hardened.x86_64.config), but for this wiki it'll just be LTS
There is some need to remove "-hardened1" in the patch file (not the sig file):
== Developing Linux-hardened kernel with hardened config ==
OPTIONAL: Before compiling the kernel, in the Alpine Linux custom kernel guide [1], you must do some kernel module configurations (do this by abuild -rK for a few seconds, then exiting by Ctrl-C, and then go to src/linux-$VERSION/, download this Arch_hardened_x86_64.config:
And do make menuconfig, and select "load", and input the downloaded .config file's name: Arch_hardened_x86_64.config, preferably shorten the amount of kernel modules in the .config files where possible, to reduce compilation times. You may use the just-downloaded Arch_hardened_x86_64.config as a base for configuration simplicity sake. (Use the apk package "kernel-hardening-checker" for configuring .config file as securely as possible, as it contains some grsecurity and kspp kernel configuration suggestions and more.)
After applying this, you may do cd $YOUR_WORK_DIR/aports/main/linux-lts and abuild checksum && abuild -r to start compiling the kernel.
When the compile has successfully completed, you should see ~/packages/main/$ARCH/linux-lts-$VERSION.apk and may install by apk add linux-lts=$VERSION(make sure to do apk update, and that /etc/apk/repositories contains $YOUR_USERS_HOME_DIR/packages/main.
== External Links: ==
==== Custom Kernel (AlpineWiki): ====
* Custom_Kernel [1]
==== EFIStub (Secure Boot) (AlpineWiki): ====
* UEFI_Secure_Boot [2]
==== Releases page: ====
* https://github.com/anthraxx/linux-hardened/releases [3]
==== Some resources for help creating this page: ====
* https://strfry.github.io/blog/building-alpine-kernel.html [4]
==== Arch Linux linux-hardened package repo (to decompress and aquire its .config) ====
* https://archlinux.org/packages/?sort=&q=hardened&packager=anthraxx&flagged= [5]
Category:Security Category:Kernel
Hardened malloc

=== What is it? ===
An excerpt on github [1]:
This is a security-focused general purpose memory allocator providing the malloc API along with various extensions. It provides substantial hardening against heap corruption vulnerabilities.
=== How to use ===
Then you can set LD_PRELOAD="/usr/lib/libhardened_malloc.so" while launching individual applications or before your window manager starts if you prefer. For a more global setting placing the LD_PRELOAD reference into or might help, as well as for PAM-based systems.
=== External sources ===
Hardened malloc github
* https://github.com/GrapheneOS/hardened_malloc [1]
Category:Security
Himitsu

Himitsu is a secret storage manager for Linux.
== Installation ==
You need to install the "himitsu" package, as well as a prompter. The default prompter that is recommended is hiprompt-gtk-py. This prompter is in the testing repository.
Run to create a key store. The daemon, himitsud, needs to be running in order to access the key store. How you start it up depends on your system configuration; your desktop environment or service manager may offer a means of running it on startup.
=== Additional integrations ===
Various packages are available which add support for new protocols and integrations to Himitsu.
* : SSH integration
* : Firefox add-on
== Documentation ==
Consult the man pages. Start with himitsu(7).
== See also ==
* Himitsu - ArchWiki
Category:Security
Hosting services on Alpine

= Introduction =
Alpine is well suited for hosting email, web or other network services.
Your biggest task is to figure out what you want your system to do.
== Preparing Alpine ==
First you need to get alpine up and running.
Follow the Installation instructions on how to get your Alpine booted.
If nothing else is mentioned in the below instructions, you should use the latest stable release:
== Mail ==
We split the 'Mail' section into various tasks.
One task is to gather and process mail. Some other task would be to prevent spam and virus etc.
Finally we need to make sure the user can fetch/read his mail.
=== Receive mail ===
* Setting up postfix with virtual domains | Postfix can be configured in multiple ways - Here we do it with virtual domains
=== Processing mail - Virus protection ===
* Setting up ClamAV for Postfix | Refers to Setting_up_postfix_with_virtual_domains instructions
=== Processing mail - Spam protection ===
* Setting up Gross for Postfix | Refers to Setting up postfix with virtual domains instructions
* Setting up ClamSMTP | Use ClamSMTP to provide advanced content and virus filtering for spam
* Setting up SaneSecurity & MSRBL extra definitions | Another good way of catching SPAM is Sanesecurity and MSRBL definitions
=== Delivering mail to the user ===
* Setting up dovecot with imap and tls | Secure way to fetch you mail from the mailer daemon
=== Other Mail-related documents ===
* Hosting Web/Email services on Alpine | Describes multiple services on same document
* Protecting your email server with Alpine | Describes multiple services on same document
* ISP Mail Server 3.x HowTo
== Web ==
* Setting up trac wiki | A ticket/wiki system
* Lighttpd | Lighttpd web server
* Apache | Apache web server
* Darkhttpd | Darkhttpd web server
* Nginx | Nginx web server
== SSH ==
* Setting up a SSH server | OpenSSH and Dropbear SSH servers
== DNS ==
* Setting up unbound DNS server | A validating, recursive, and caching DNS resolver that supports DNSSEC
* Setting up nsd DNS server | An authoritative-only DNS server
== Proxy ==
* Setting up Explicit Squid Proxy | Configuring an explicit Squid proxy server
* Setting up Transparent Squid Proxy | Configuring a transparent Squid proxy server
= Also see =
You'll probably also want to look at Tutorials and Howtos
Category:Server
Category:Mail
How to build the Alpine Linux kernel

== How to build the Alpine Linux kernel ==
This Howto quickly demonstrates building/compiling the default Alpine Linux kernels "LTS" and "virt". Alpine kernels extend the standard Linux kernel and build within a few minutes to a few hours (depending on the speed of your system) using abuild, aports, and alpine-sdk.
Kernel customizations (not covered here) allow you to experiment by adding/removing kernel modules/features. Alpine releases multiple downloads which contain kernels that vary in features and file sizes.
== Before you start ==
A running instance of Alpine Linux and a non-root user with doas privileges (i.e. sudo, wheel group) are required to use abuild.
== Build & install the kernel ==
=== Build ===
doas apk add alpine-sdk
doas addgroup USERNAME abuild # your non-root user
git clone --depth 1 https://gitlab.alpinelinux.org/alpine/aports.git
abuild-keygen --append --install
doas chmod a+r /etc/apk/keys/* # ensure new keys are readable
cd aports/main/linux-lts/
time abuild -crK
=== Identify backup ===
Identify the package name of your current kernel (e.g. linux-lts, linux-virt). This example shows that linux-lts is the current package that we would revert to as a backup.
echo "kernel: $(uname -r)"
apk list --installed linux-*
=== Install ===
Find the newly-built kernel file to install. This example shows how to install a newly-built x86_64 LTS kernel:
ls -r ~/packages/main/*
doas apk add FILENAME
doas reboot
After rebooting, verify the newly-installed kernel version:
echo "kernel: $(uname -r)"
=== Revert ===
If needed, revert to the previous backup kernel package we identified earlier. This example shows how to revert to the previous "alpine-lts" package after removing the newly-installed "alpine-lts" (both are named "alpine-lts" yet refer to different versions/locations):
apk list linux-lts # newly-compiled kernel installed
doas apk del linux-lts # newly-compiled kernel from file
doas apk add linux-lts # previous kernel from Alpine repo
apk list linux-lts # previous kernel installed
doas reboot
== See Also ==
* Kernels
* Custom Kernel (2018-present)
How to configure static routes

This document describes how to configure persistent static routes in Alpine Linux so the route definitions survive server reboots. 
This process was tested with release 2.1.4, dated 2011-01-07.
First, set the staticroute service to start automatically on boot by entering the following command:
You can now define your static routes in one of three ways:
==Option 1: Edit /etc/conf.d/staticroute==
Routes are added as a parameter value - the staticroute file has header information that explains the syntax - for example:
 staticroute="net 10.200.200.0 netmask 255.255.255.0 gw 192.168.202.12"
If you need to add multiple static routes, just add additional routes to the end of the text between the quotes with each route separated by a semicolon or a line break (press ENTER).
==Option 2: Create /etc/route.conf==
Use nano, vi, or your favourite editor to create the file /etc/route.conf 
Add each static route on a separate line - for example:
 net 10.200.200.0 netmask 255.255.255.0 gw 192.168.200.12
 net 10.200.201.0 netmask 255.255.255.0 gw 192.168.200.13
==Option 3: Set up routes in /etc/network/interfaces==
If you have static network configuration in /etc/network/interfaces, you can add a static route that gets activated when an interface is brought up:
 auto eth0
 iface eth0 inet static
 address 192.168.0.1
 netmask 255.255.255.0
 up ip route add 10.14.0.0/16 via 192.168.0.2
 up ip route add 192.168.100.0/23 via 192.168.0.3
Once editing is complete, remember to save your changes if you are running the OS in RAM (eg: booting from a USB stick) - if you are not sure how to do this, see this article: How to Boot Alpine Linux and Save Settings on a USB Stick or Alpine_local_backup
You can verify your settings by restarting the server, or by issuing the following commands:
To add your defined static routes manually (for testing):
To remove your defined static routes:
There is a 'restart' option to do an automatic stop/start, but it seems less reliable than using the two above.
Category:Networking
How to get regular stuff working

Alpine Linux is built around Musl libc and BusyBox. This makes it small and very resource efficient. The utilities in BusyBox generally have fewer options and hence missing some functionality when used to daily drive. This page explains how to get the regular utilities working as found in other Linux distributions.
== Core utilities ==
Most of the basic file, shell and text manipulation utilities commonly grouped under Core Utilities are provided by BusyBox. To replace it with original package:
== Util-linux ==
A set of approximately 100 basic Linux system utilities not included in GNU Core Utilities, such as mount, cfdisk, more, lsblk and kill are maintained under Util-linux. To have the complete package:
The full featured file pager utility less can be installed from the package.
== Search utilities ==
Standard search tools grep and find can be installed by installing the packages and as follows:
== Bash shell == 
The default shell used by Alpine Linux is the busybox variant of the ash shell. To install shell: 
== Hardware Management ==
Install and for identifying and configuring PCI and USB hardware using the full featured version of lspci and lsusb commands respectively. 
The packages and are dependencies for the above utilities and they are installed automatically. These packages can be removed once the hardware configuration has been completed.
== Disk Management ==
Managing (removable) disks is much easier with udisks. 
To see the mounted disks:
== Network Management ==
For network, you may want to install . 
== Subpackages and missing functionality ==
In Alpine Linux, binary packages are thinned out and split into subpackages to give more control over what features are installed and keeps the installation as small and efficient as possible. When a package is installed in Alpine Linux, no assumption is made on what features the user wants, so the user might get a false impression of missing functionality.
For eg: NetworkManager, a popular network configuration tool is split into 20+ subpackages based on features. If the user installs package or only the NetworkManager utility and the applet will get installed. To manage Wifi networks or to use commands like <Code>nmcli</Code> and <Code>nmtui</Code> the user is expected to add the required subpackages , and respectively. In other Linux distributions when NetworkManager is installed, all the above features plus bluetooth, adsl, wwan, vpn, l2tp, ppp etc are automatically installed along with their dependencies. 
Use package database or to find subpackages related to a package.
== Development environment ==
Compiling in Alpine Linux may be more challenging because it uses musl-libc instead of glibc. The meta package provides regular compiler stuff such as , , , etc..
The meta package is provided to build packages for Alpine Linux. It includes , , and .
To install CMake:
 and a lot other tools are also available in Alpine Linux. 
Category:Installation
category: System Administration
How to make a custom ISO image

== ISO remastering ==
There are third party scripts to re-build completely custom images, like alpine-make-vm-image
(works to only make a disk based VM image) and there is Alpine's original
mkimg. 
(creates a diskless ISO file - usually what you want for QEMU and Proxmox)
== An alternative ==
It's also possible to commit and load ISO image customizations to and from a writable partition when booting in Diskless Mode.
== See also ==
* Directly booting an ISO file
* How to make a custom ISO image with mkimage
Category:Package Manager
Category:ISO
How to setup a wireless access point

== Install needed packages ==
== Check that the card is detected ==
Run cat /proc/net/dev to see which cards are detected.
If no cards are available, check what driver the card uses and modprobe it.
Check that the card is in master mode.
== Setup Bridge ==
Setup the bridge by editing /etc/network/interfaces. Assuming you wish to bridge the access point to the ethernet device eth0, you can add something like this:
auto br0
iface br0 inet dhcp
 hostname alpine
 bridge-ports eth0
Comment out any existing lines configuring eth0 as this should now be handled via the bridge configuration. It is not necessary to mention wlan0 here, as hostapd will take care of adding the device to the bridge later.
Please see Bridge for more information on network bridges.
== Setup Encryption ==
Edit /etc/hostapd/hostapd.wpa_psk and insert the following, replacing PASSPHRASE with the WPA_PSK key you would like to use (remove keys that you don't want to use):
 00:00:00:00:00:00 PASSPHRASE
== Setup hostapd ==
Edit /etc/hostapd/hostapd.conf and make the necessary changes such as interface, bridge, driver, ssid, etc.
Example file below:
 interface=wlan0
 bridge=br0
 driver=hostap
 logger_syslog=-1
 logger_syslog_level=2
 logger_stdout=-1
 logger_stdout_level=2
 debug=0
 dump_file=/tmp/hostapd.dump
 ctrl_interface=/var/run/hostapd
 ctrl_interface_group=0
 ssid=SecureSSID
 #macaddr_acl=1
 #accept_mac_file=/etc/hostapd/accept
 auth_algs=3
 eapol_key_index_workaround=0
 eap_server=0
 wpa=3
 wpa_psk_file=/etc/hostapd/hostapd.wpa_psk
 wpa_key_mgmt=WPA-PSK
 wpa_pairwise=CCMP
If you wish to use MAC address filtering, uncomment the lines starting with macaddr_acl and accept_mac_file, create /etc/hostapd/accept (with permissions set to 600) and add the allowed clients' MAC address to the file.
Start hostapd.
== Associate clients ==
Associate a few clients to test.
== See also ==
* Wireless AP with udhcpd and NAT
* Raspberry Pi 3 - Configuring it as wireless access point -AP Mode
Category:Networking
How to use xdelta and download only differential update files

For those having a slow connection, it is possible to download a smaller differential file that contains only the new Alpine Linux version changes. If you have an ISO file of the version immediately prior to the latest version, you can then use the downloaded xdelta file to update to the latest ISO. You will still need to download the new ISO checksum file and test the integrity of the newly built ISO file. For xdelta to work you should have the three files on the same directory level, i.e.: alpine-1.10.3-1.10.4.xdelta, alpine-1.10.3-x86.iso (previous release) and the alpine-1.10.4-x86.iso.sha1
 
 wget -c http://www.alpinelinux.org/cgi-bin/dl.cgi/v1.10/releases/alpine-1.10.3-1.10.4.xdelta
 wget http://www.alpinelinux.org/cgi-bin/dl.cgi/v1.10/releases/alpine-1.10.4-x86.iso.sha1
Make sure you have xdelta3 installed and build the new ISO:
 apk add xdelta3
 xdelta3 -d alpine-1.10.3-1.10.4.xdelta
Check the integrity of the file:
 sha1sum -c alpine-1.10.4-x86.iso.sha1
If checking the integrity of the file shows: alpine-1.10.4-x86.iso: OK then you are ready to continue.