Alpine Linux - User contributions [en]

Setting up lm sensors

2012-05-12T15:27:48Z

Jrthomerson:

This document is a short note on how to set up lm_sensors in Alpine.

Install the neccessary packages. You will need perl to run the sensors-detect script.
{{Cmd|apk_add lm_sensors lm_sensors-detect perl}}

Load the i2c-dev module:
{{Cmd|<nowiki>echo i2c-dev >> /etc/modules
modprobe i2c-dev</nowiki>}}

'''Note:''' If you already know the name of the sensor module, you can modprobe it now, and skip the sensors-detect and perl install.

Run sensors detect:
{{Cmd|sensors-detect}}

There are multiple types of sensors that you must skip scanning for (answer "no" to the prompt) because grsec will not allow you to access /proc/port. If you encounter an error that says something like "/dev/port: no such file..", re-run the script and answer "no" to that question on the next attempt. Examples of ones that you must enter "no" for: ISA bus, other Super I/O sensors, and IPMI.

Be sure to enter "yes" (non-default) for the question "Do you want to generate /etc/conf.d/lm_sensors?"

You will not need perl anymore. Remove it before you forget.
{{Cmd|apk_del lm_sensors-detect perl}}

Make services start during next reboot.
{{Cmd|rc-update add lm_sensors default
rc-update add sensord default}}

Start services:
{{Cmd|/etc/init.d/lm_sensors start && /etc/init.d/sensord start}}

Don't forget to save your new server configuration using {{Cmd|lbu commit}}.

[[Category:Monitoring]]

Alpine Package Keeper

2011-05-14T21:59:14Z

Jrthomerson:

= Alpine Linux Package Management =

Because Alpine Linux is designed to run from RAM, package management involves two phases:
* Installing / Upgrading / Deleting packages on a running system
* Restoring a system to a previously configured state (e.g. after reboot), including all previously installed packages and locally modified configuration files. '''(RAM-Based Installs Only)'''

'''apk''' is the tool used to install, upgrade, or delete software on a running sytem<br />
'''lbu''' is the tool used to capture the data necessary to restore a system to a previously configured state.

This page documents the apk tool - See the [[Alpine_local_backup|Alpine Local Backup page]] for the lbu tool.

The '''apk''' tool has the following applets:

{|
| [[#Add a Package|add]]
| Add new packages to the running system
|-
| [[#Remove a Package|del]]
| Delete packages from the running system
|-
| fix
| Attempt to repair or upgrade an installed package
|-
| [[#Update the Package list|update]]
| Update the index of available packages
|-
| [[#Info on Packages|info]]
| Prints information about installed or available packages
|-
| [[#Search for Packages|search]]
| Search for packages or descriptions with wildcard patterns
|-
| [[#Upgrade a Running System|upgrade]]
| Upgrade the currently installed packages
|-
| [[#Cache Maintenance|cache]]
| Maintenance operations for locally cached package repository
|-
| version
| Compare version differences between installed and available packages
|-
| index
| create a repository index from a list of packages
|-
| fetch
| download (but not install) packages
|-
| audit
| List changes to the file system from pristine package install state
|-
| verify
| Verify a package signature
|}

== Quickstart Guide ==

=== Packages and Repositories ===

Software packages for Alpine Linux are digitally signed tar.gz archives containing the programs, configuration files, and dependency metadata. They have the extension "*.apk", and are often called "a-packs"

The packages are stored in one or more ''repositories'' A repository is simply a directory with a collection of *.apk files. The directory must include a special index file, named APKINDEX.tar.gz to be considered a repository.

The '''apk''' utility can install packages from multiple repositories. The list of repositories to check is stored in <tt>/etc/apk/repositories</tt>, one repository per line. If you booted from USB stick (<tt>/media/sda1</tt>) or CD-ROM (<tt>/media/cdrom</tt>), your repository file probably looks like this:

<pre>
/media/sda1/apks/
</pre>

In addition to local repositories, the '''apk''' utility uses '''busybox wget''' to fetch packages using ''http:'', ''https:'' or ''ftp:'' protocols. The following is a valid repository file:

<pre>
/media/sda1/apks
http://dl-3.alpinelinux.org/alpine/v2.1/main
https://dl-3.alpinelinux.org/alpine/v2.1/main
ftp://dl-3.alpinelinux.org/alpine/v2.1/main
</pre>

{{note|Currently there are no public https or ftp repositories. The protocols are available for local repositories}}

=== Update the Package list ===

Remote repositories change as packages are added and upgraded. To get the latest list of available packages, use the ''update'' command. The command downloads the APKINDEX.tar.gz from each repository and stores it in the local cache, typically <tt>/var/lib/apk</tt> or <tt>/etc/apk/cache</tt>.

{{Cmd|apk update}}
<pre>
fetch http://dl-3.alpinelinux.org/alpine/v2.1/main/APKINDEX.tar.gz
</pre>

{{Tip|If using remote repositories, it is a good idea to do an '''update''' just before doing an '''add''' or '''upgrade''' command. That way you know you are using the latest software available}}

=== Add a Package ===

Use '''add''' to install packages from a repository. Any necessary dependencies are also installed. If you have multiple repositories, the '''add''' command installs the newest package.

{{cmd|apk add openssh
apk add openssh openntp vim}}

=== Remove a Package ===

Use '''del''' to remove a package (and dependencies that are no longer needed.)

{{cmd|apk del openssh
apk del openssh openntp vim}}

=== Upgrade a Running System ===

To upgrade ''all'' the packages of a running system, use '''upgrade'''

{{cmd|apk update
apk upgrade
}}

To upgrade only a few packages, use the '''add''' command with the ''-u'' parameter:

{{cmd|apk update
apk add -u busybox
}}

{{Note|Remember that when you reboot your machine, the remote repository will not be available until after networking is started. This means packages newer than your local boot media will likely not be installed after a reboot. To make an "upgrade" persist over a reboot, use a [[#Local Cache|local cache]].}}

=== Search for Packages ===

The '''search''' command searches the repository Index files for installable packages.

Examples:
* To list all packages available, along with their descriptions: {{cmd|apk search -v}}
* To list all packages are part of the ACF system: {{cmd|apk search -v 'acf*' }}
* To list all packages that list NTP as part of their description: {{cmd|apk search -v -d 'NTP' }}

=== Info on Packages ===

The '''info''' command provides information on the contents of packages, their dependencies, and which files belong to a package.

For a given package, each element can be chosen (for example, ''-w'' to show just the webpage information); or all information is displayed with the ''-a'' command.

Example: {{cmd|apk info -a zlib}}

'''zlib-1.2.5-r1 description:'''
A compression/decompression Library

'''zlib-1.2.5-r1 webpage:'''
<nowiki>http://zlib.net</nowiki>

'''zlib-1.2.5-r1 installed size:'''
94208

'''zlib-1.2.5-r1 depends on:'''
libc0.9.32

'''zlib-1.2.5-r1 is required by:'''
libcrypto1.0-1.0.0-r0
apk-tools-2.0.2-r4
openssh-client-5.4_p1-r2
openssh-5.4_p1-r2
libssl1.0-1.0.0-r0
freeswitch-1.0.6-r6
atop-1.25-r0

'''zlib-1.2.5-r1 contains:'''
lib/libz.so.1.2.5
lib/libz.so.1
lib/libz.so

'''zlib-1.2.5-r1 triggers:'''

As shown in the example you can determine
* The '''description''' of the package
* The '''webpage''' where the application is hosted
* The '''size''' the package will require once installed (in bytes)
* What packages are required to use this one ('''depends''')
* What packages require this one to be installed ('''required by''')
* The '''contents''' of the package
* Any '''triggers''' this package sets. Listed here are directories that are watched; if a change happens to the directory, then the trigger script is run at the end of the apk add/delete. For example, doing a depmod once after installing all packages that add kernel modules.

{{Tip|The '''info''' command is also useful to determine which package a file belongs to. For example: {{cmd|apk info --who-owns /sbin/lbu}} will display

/sbin/lbu is owned by alpine-conf-x.x-rx
}}
== Additional apk Commands ==

In progress...

== Local Cache ==

Alpine Linux needs to be able to pull packages from local media on boot. (You can't download packages from the net before you have a network connection.) Using remote repositories presents a problem. If the config files have been modified for a newer version of a package, and the older package is on local media, all sorts of fun can result.

The solution is a local cache of updated packages. This cache can be stored on any r/w media, typically the same location as the apkovl.

=== To Enable Local Cache ===

# Create a '''cache''' directory on the device you store your lbu backups (typically, <code>/dev/sda1</code>.) {{Cmd| mkdir /media/sda1/cache }}
{{Tip|If you get an error that says "mkdir: can't create directory '/media/usbdisk/cache': Read-only file system", then you probably need to remount your disk read-write temporarily. Try {{Cmd|mount -o remount,rw /media/sda1}} and then don't forget to run {{Cmd|mount -o remount,ro /media/sda1}} when you are done with the following commands}}
# Create a symlink to this directory from <code>/etc/apk/cache</code>. {{Cmd|ln -s /media/sda1/cache /etc/apk/cache}}
# Run an lbu commit to save the change (<code>/etc/apk/cache</code> is in <code>/etc</code> and is automatically backed up.) {{Cmd|lbu commit}}
# Done. Now whenever you run an apk command that pulls a new package from a remote repository, The package is stored on your local media. On startup, Alpine Linux will check the local cache for new packages, and will install them in preference.

So you now have a run-from-RAM distro that can do a '''yum upgrade''' or '''apt-get dist-upgrade'''

=== Cache Maintenance ===

Over time, newer packages will replace older ones; the cache directory will contain all older versions of packages.

==== Delete Old Packages ====
To clean out older versions of packages, run the '''clean''' command. {{cmd|apk cache clean}} or to see what is deleted {{cmd|apk -v cache clean}}

==== Download Missing Packages ====
If you accidentally delete packages from the cache directory, you can make sure they are there with the '''download''' command, {{cmd|apk cache download}}

==== Delete and Download In One Step ====
You can combine the two steps into one with the '''sync''' command - this cleans out old packages and downloads missing packages. {{cmd|apk cache -v sync}}

==== Automatically Cleaning Cache on Reboot ====
To automatically attempt to validate your cache on reboot, you can add the above command to the <code>/etc/conf.d/local</code> script, in the <code>stop</code> stanza:

local_stop() {
# This is a good place to unload any misc.
# programs you started above.

# verify the local cache on shutdown
apk cache -v sync

# We should always return 0
return 0
}

{{Tip|Usually the only time you need to reboot is when things have gone horribly wrong; so this is a "best effort" to cover forgetting to sync the cache; It is much better to run '''sync''' immediately after adding or upgrading packages.}}

== Advanced APK Usage ==

=== Holding a specific package back ===

In certain cases, you may want to upgrade a system, but keep a specific package at a back level. It is possible to add "sticky" or versioned dependencies. For instance, to hold the ''asterisk'' package to the 1.6.2 level or lower:
{{cmd|1=apk add asterisk=1.6.0.21-r0}}
or
{{cmd|apk add 'asterisk<1.6.1'}}

after which a {{cmd|apk upgrade}}

will upgrade the entire system, keeping the asterisk package at the 1.6.0 or lower level

To later upgrade to the current version,

{{cmd|apk add 'asterisk>1.6.1'}}

Installing Alpine on a virtual machine

2009-08-04T05:10:47Z

Jrthomerson: Created page with '= Installing Alpine on a VMWare Server virtual machine = # create a virtual machine (linux, other 2.6 32 bit) ## the vm doesn't need a hard drive ## add a cdrom to the vm that p...'

= Installing Alpine on a VMWare Server virtual machine =

# create a virtual machine (linux, other 2.6 32 bit)
## the vm doesn't need a hard drive
## add a cdrom to the vm that points to the alpine iso you downloaded
## add a floppy (choose new floppy image and give it a file name to create a fake floppy image on your machine)
# boot into the vm
# press f2 on boot to enter the BIOS
## warning: this can be a real timing trick. I had to disconnect the cd and floppy and try several times to get into the bios screen before it started trying to network boot
## change the boot order so that it boots from cd, then hd, then floppy (or whatever - as long as cd is first)
# boot the machine
# now run the following commands:
## mkfs.vfat /dev/fd0
## mount /dev/fd0 /media/floppy
## setup-alpine
## lbu ci floppy

Now you should be able to reboot and it should retain your settings because they were saved to your floppy.

Alpine Linux:Documentation

2009-08-04T05:10:04Z

Jrthomerson: /* Developer Documentation */

== User Documentation ==
Documentation how to install and use the Alpine distro.

* [[Installing Alpine on CD]]
* [[Installing Alpine on USB]]
* [[Installing Alpine on Compact Flash]]
* [[Upgrading Alpine]]
* [[Alpine package management]] ''(How to add/remove packages on your Alpine)''
* [[Alpine boot services]] ''(Configure a service to automatically boot at next reboot)''
* [[Alpine local backup]] ''(Permanently store your modifications in case your box needs reboot)''
* [[Comparison with Gentoo and Debian]]
* Submitting [http://bugs.alpinelinux.org Problem Reports]

=== HOWTOS ===

==== Installation ====
* [[Bootstrapping Alpine on Soekris net4xxx]]
* [[Bootstrapping Alpine on PC Engines ALIX.3]]
* [[Setting up a software raid1 array]]
* [[Setting up Logical Volumes with LVM]]
* [[Setting up a /var partition on software IDE raid1]]
* [[Native Harddisk Install]]
* [[Installing XUbuntu using Alpine boot floppy]]

==== Networking ====
* [[Setting up a OpenVPN-server with Alpine]]
* [[Setting up traffic monitoring using rrdtool (and snmp)]]
* [[Setting up Zaptel/Asterisk on Alpine]]
* [[Using HSDPA modem]]
* [[Using Alpine on Windows domain with IPSEC isolation]]
* [[Using Racoon for Remote Sites]]

==== Misc ====
* [[Setting up lm_sensors]]
* [[Setting up Satellite Internet Connection]]
* [[Setting up Streaming an Asterisk Channel]]
* [[Formatting HD/Floppy/Other]]
* [[Setting up Transmission (bittorrent) with Clutch WebUI]]
* [[Hosting_services_on_Alpine]] ''(This applies to hosting mail, webservices and other services)''
** [[Setting_up_postfix_with_virtual_domains]]
** [[Protecting your email server with Alpine]]
** [[Hosting Web/Email services on Alpine]]
** [[Setting_up_trac_wiki]]
* [[Running Alpinelinux As a QEMU networked Guest ]]
* [[Screen on console]]
* [[Using espeak on AlpineLinux]]
* [[Generating SSL certs with ACF]]
* [[Setting up a ssh-server]]
* [[Changing passwords]]

==== iSCSI ====
* [[iSCSI Target and Initiator Configuration]]
* [[iSCSI Raid and Clustered File Systems]]

=== Vserver ===
* [[Setting up a basic vserver]]

== Developer Documentation ==
Documentation how to build and modify the Alpine distro.

* [[Alpine Package Testing Suite]]
* [[Alpine Configuration Framework Design]] (Why ACF is the way it is)
* [[Development using git]]
* [[Installing Alpine on a virtual machine]]

=== Alpine 1.9.x build system ===
After Alpine 1.8 is released we will switch to a new build system. Those docs here below is for bulding packages in Alpine 1.9 and later.

* [[Setting up the build environment]]
* [[Creating an Alpine package]]
* [[Creating_an_Alpine_1.9_iso]] (This page is experimental and might go away or move in the future)

=== Obsolete docs ===
* [[Setting up the build environment 1.7]]
* [[Newbie Guide to Building an apk]]
* [[Creating patches]]

== Misc. References ==
Other useful references.

* http://www.metoffice.gov.uk/research/nwp/external/fcm/doc/user_guide/working_practices.html - Some guidelines on use of Trac and SVN