Alpine Linux - User contributions [en]

Installing Alpine on CD

2010-02-25T03:55:31Z

Ncopa2: /* Alpine on CD */

= Alpine on CD =
Because this doc will describe on how you get Alpine to boot from CD, you should prepare by doing:

* [[Downloads|Download]] a iso-file containing Alpine ''(e.g. {{Latest_1.8_alpine_iso-mirror}}{{Latest_1.8_alpine_iso-filename}})''

* Make sure you have a program on you computer that can burn iso-files onto a CD ''(See also http://en.wikipedia.org/wiki/List_of_ISO_image_software)''

* Get a empty CD ''(Label it "Alpine Linux")''

== Preparing the media ==
Start by burning the ISO-image onto your empty CD using your ISO-image burning software.

== Boot Alpine ==
Put your AlpineLinuxCD in a computer that can boot from CD. 
'''''Note:''' You might need to change boot-order in your BIOS-settings in order to boot from CD.''

When your computer has booted you will get prompted for a username. 
On a clean AlpineLinux you just enter ''root'' and no password and you will get logged on to your Alpine linux.

{{Installing_Alpine_see_also}}
jose rallang

Comparison with other distros

2009-10-07T20:48:01Z

Ncopa2: /* Network */

== Introduction ==
Even if Alpine is designed to run from ram, it has some similarities in package management with both Gentoo and Debian. This page is supposed to show those differences and help Debian and Gentoo users to use Alpine.

The page was originally copied from: http://gentoo-wiki.com/TIP_Converting_from_or_to_Debian

==Package management==
Where Gentoo has portage and emerge and Debian has, among others, apt, Alpine uses apk-tools. This compares how you use apk-tools in comparation to apt-get/aptitude and emerge.

Note that Gentoo is source based, just like ports in FreeBSD is while Debian uses pre-compiled binaries. Alpine is compiled using Gentoo portage but Alpine itself uses its own apk-tools binary package that are more similar FreeBSD's binary packages.

===Updating package database===
Gentoo will update the build-from-source scripts and are the updating of the database is takes much more time that updating the database for Debian or Alpine.

'''Alpine'''
apk_fetch -u

'''Gentoo'''
emerge --sync

'''Debian'''
aptitude update

===Showing available updates===
Show what packages that have an update available:

'''Alpine'''
apk_version -v
or:
apk_version -v -l '<'

'''Gentoo'''
emerge --deep --update --pretend world

'''Debian'''
aptitude upgrade --simulate

===Update a particular package===
'''Alpine'''
apk_add -u package1 package2
'''Debian'''
aptitude install package1 package2
'''Gentoo'''
emerge --update package1 package2

===Installing packages===
'''Alpine'''
apk_add package1 package2
'''Gentoo'''
emerge package1 package2
'''Debian'''
apt-get install package1 package2
Debian source compile:
apt-get build-dep package1
apt-get source package1
(optional: customize the build by modifying the debian/rules makefile)
(or set environmental variables like DEB_BUILD_OPTIONS)
(note that this will make your bug reports invalid to the maintainer)
dpkg-buildpackage -rfakeroot -uc -b
dpkg -i generatedpackagename
Simplified source compile:
apt-get build-dep package1
apt-get -b source package1
(the packages are automatically generated using the -b switch above)

'''Note:''' This process can be used to backport packages from testing and unstable by simply adding their respective source repositories to sources.list, which is similar to adding ~x86 to package.keywords in Gentoo. This is explored further in "arch and repositories" below.

=== Reinstall a particular package ===
'''Alpine'''
apk_delete package1 && apk_add package2
or:
apk_add -f package1 package2
'''Gentoo'''
emerge --oneshot package1 package2
'''Debian'''
apt-get install --reinstall package1 package2

Note: You ''rarely'' need to reinstall a package on Debian

===Searching package database===
'''Alpine'''

Alpine will only search package names.
apk_fetch -lv | grep searchword

'''Gentoo'''

To search the package names and descriptions:
emerge --searchdesc searchword
'''Note:''' On Gentoo, it's actually much better to install and use either the esearch package or the eix package to do a search. You use them like this:
eix searchword

or

esearch searchword

'''Debian'''

apt-cache search searchword
Both emerge and apt-cache search support regular expressions.

To get the long package information on Debian (searching only in package names):
apt-cache search --full --names-only searchword

===Removing packages===
'''Alpine'''

apk_delete package1 package2
To also remove unused dependencies:
apk_delete -R package1 package2
apk_delete will remove configuration files without asking any questions. Make sure you have backups of your configuration files. (Using rcs might be an idea)

You will mostly like to take a quick look at the dependencies before you remove packages recursively.

To see dependencies for a package, use:
apk_info -R package1 package2

To see if package is required by other packages (is a dependency for another packages), use:
apk_info -r package1

'''Gentoo'''
emerge --unmerge package1 package2

'''Debian'''
apt-get remove package1 package2
or to remove along with all configuration files
apt-get remove --purge package1 package2

===Only downloading packages===
This can be useful e.g. if you're on a dial-up connection and want to download everything first and install later.

'''Alpine'''
apk_fetch package1 package2
'''Gentoo'''
emerge --fetchonly package1 package2
'''Debian'''
apt-get install --download-only package1 package2

===Cleaning up downloaded packages===
Compressed packages that were downloaded for installation can easily consume gigs of hdd space.

'''Alpine'''

Alpine will clean up package automatically unless APK_KEEPCACHE is set to "yes" in /etc/apk.conf. To do it manually if it is set:
rm /var/cache/packages/*

'''Gentoo'''
rm -rf /usr/portage/distfiles/*
To only remove outdated packages you will need to install the gentoolkit package and use eclean:
eclean distfiles
Cleaning temporary files from emerging packages:
rm -rf /var/tmp/portage/*

'''Debian'''
apt-get clean
Only remove outdated packages:
apt-get autoclean

===Reverse dependencies===

'''Alpine'''

apk-tools will take care of reverse dependencies.

'''Gentoo'''

Reverse dependencies are a major drawback of '''Gentoo's''' current portage implementation: It does not take care of them at all at the moment.
This means that you can uninstall packages needed by others without being warned about it. E.g. you can remove the x server package without portage warning you that kde (which you have installed as well) depends on it. This way you can actually break your entire system (e.g. by removing glibc).

revdep-rebuild
can fix broken dependencies broken by
emerge --depclean

'''Debian'''

Reverse dependencies are taken care of by dpkg.

==Runlevel & Initscripts==
Runlevels work pretty conventionally on Debian. On Alpine and Gentoo, they are a bit different.
===Directories and files===
In '''Debian''' runlevels are named conventionally (0-6 and S). They are represented by directories in /etc/ called rc*.d (when the default sysv-rc boot loader package is installed; file-rc can be installed instead, and then the relevant file is runlevel.conf).
* /etc/rc0.d
* /etc/rc1.d
* /etc/rcS.d
* /etc/rc2.d
* /etc/rc3.d
* /etc/rc4.d
* /etc/rc5.d
* /etc/rc6.d

In '''Gentoo''', runlevels have the same names, but these are mapped to more self explanatory ones (in /etc/inittab): "boot", "default", "nonetwork", with the option to add more. The directories that represent them are in
/etc/runlevels/:
* /etc/runlevels/boot
* /etc/runlevels/default
* /etc/runlevels/nonetwork

In Gentoo, if a service is not explicitly started in a runlevel, it is stopped when switching to that runlevel! There is no explicit stopping of runlevels as in Debian (/etc/rc?.d/K??service).

In '''both Debian and Gentoo''', which things are started (and stopped) in which runlevels is controlled by links in the runlevel directories to scripts in /etc/init.d/, e.g.:
gentoo
$ ls -l /etc/runlevels/boot/hostname
lrwxrwxrwx 1 root root 20 Mar 25 2004 /etc/runlevels/boot/hostname -> /etc/init.d/hostname

'''Debian'''
$ ls -l rcS.d/S40hostname.sh
lrwxrwxrwx 1 root root 21 2004-11-07 00:19 rcS.d/S40hostname.sh -> ../init.d/hostname.sh

TODO: Alpine

===Runlevel management===
To manage which things to start in which runlevels, use the following commands:

'''Alpine'''

To see current status of services in runlevels, do:
rc_status
To add sshd to default runlevel, do:
rc_add -k sshd
The -k option will make sure sshd is stopped when shutting down or reboot.
To remove sshd from all runlevels do:
rc_delete sshd

'''Gentoo'''

rc-update
To add the cupsd to the default runlevel, do:
rc-update add cupsd default
To remove alsasound from the boot runlevel, do:
rc-update del alsasound boot
Also see this wiki page about [http://gentoo-wiki.com/Rc-update gentoo runlevel management with rc-update]

'''Debian'''

update-rc.d
Configure cupsd to be started in runlevels 2, 3, 4, 5, and stopped in 0, 1, 6, with sequence code 20:
update-rc.d cupsd start 20 2 3 4 5 . stop 20 0 1 6 .
or simply:
update-rc.d cupsd defaults
Remove cupsd from all runlevels:
update-rc.d -f cupsd remove

==Config Files==

===/etc/make.conf and use flags===
While in gentoo there are a large number of configuration files which exist to control the behaviour of the package management system. There are comparatively fewer in Debian, as there is no need to dictate how to compile software which is downloaded and tweak / alter this purpose. In gentoo, the file /etc/make.conf is used for much configuration; this includes ''USE'' flags, which influence which elements of packages are compiled, and which libraries to build support for - common USE flags (USE or -USE to specifically negate support) include 'gtk gnome' for gnome users (and a corresponding -qt -kde -arts) and 'qt kde arts' for kde users. A gentoo user's complete set of use flags may look something like this:

'''USE="-kde -arts -qt xv truetype bluetooth crypt slang readline gpm berkdb mmx gdbm tcpd pam libwww ssl nls ethereal perl python esd gif imlib sdl oggvorbis mpeg gnome gtk X motif opengl avi png tiff nptl pcmcia nptl ldap eds"'''

===arch and repositories===
'''Gentoo'''

Also in /etc/make.conf is the '''ACCEPT_KEYWORDS''' setting, with (for an X86-based processor) two settings, '''x86''' for stabler packages, and '''~x86''' for bleeding edge packages. It is however not recommended to make this change in /etc/make.conf. Rather configure this per-package in /etc/portage/package.keywords. It's enough to put a line into that file naming the package (for example 'app-foo/bar'). That file might look like this:

app-crypt/gpg-agent
app-text/docbook-xsl-stylesheets
=app-text/docbook-xml-dtd-4.3-r1

The last line says, that ''only'' version 4.3-r1 should be unmasked. Older and newer versions will still be ignored.

'''Note for non-x86 users:'''
The keywords '''x86''' and '''~x86''' can of course be replaced by '''sparc''' and '''~sparc''' for example.

'''Debian'''

Setting this in Debian is slightly more complicated, and is accomplished by setting different 'repositories' in ''/etc/apt/sources.list'' - along with which 'tree' to use for packages; in debian, these are '''stable''', '''testing''', and '''unstable'''. An ''/etc/apt/sources.list'' file for a debian testing user may look something like this:

deb http://mirrors.kernel.org/debian testing main non-free contrib
deb ftp://ftp.nerim.net/debian-marillat testing main
deb http://security.debian.org testing/updates main contrib non-free

Alternatively, ''/etc/apt/sources.list'' can contain any number of repositories for any trees, and a default tree (this can be overridden using the -t switch on the command line) in ''/etc/apt/apt.conf'':

APT::Default-Release "testing";

Per-package settings go in ''/etc/apt/preferences'', somewhat like Gentoo's ''/etc/portage/package.keywords''.

===Network===

'''Alpine'''

Alpine uses /etc/network/interfaces, just like Debian. The main reason is because this is the way busybox does it.

''/etc/network/interfaces'':
auto eth0
iface eth0 inet static
address 192.168.0.1
netmask 255.255.255.0
broadcast 192.168.0.255

auto eth0:0
iface eth0:0 inet static
address 192.168.1.1
netmask 255.255.255.0
broadcast 192.168.1.255
# etc.

'''Gentoo'''

''/etc/conf.d/net'':
config_eth0=( "192.168.1.100 netmask 255.255.255.0"
"192.168.2.100 netmask 255.255.255.0" )
routes_eth0=( "default via 192.168.1.1" )

Note that this has changed recently. For more information please refer to http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=4

'''Debian'''

''/etc/network/interfaces'':
auto eth0
iface eth0 inet static
address 192.168.0.1
netmask 255.255.255.0
broadcast 192.168.0.255

auto eth0:0
iface eth0:0 inet static
address 192.168.1.1
netmask 255.255.255.0
broadcast 192.168.1.255
# etc.

Are this information help you in writing [http://www.research-service.com/custom-research-paper.html research papers]? Feel free to send us comments and suggestions about the wiki.

Comparison with other distros

2009-10-07T20:45:04Z

Ncopa2: /* Network */

== Introduction ==
Even if Alpine is designed to run from ram, it has some similarities in package management with both Gentoo and Debian. This page is supposed to show those differences and help Debian and Gentoo users to use Alpine.

The page was originally copied from: http://gentoo-wiki.com/TIP_Converting_from_or_to_Debian

==Package management==
Where Gentoo has portage and emerge and Debian has, among others, apt, Alpine uses apk-tools. This compares how you use apk-tools in comparation to apt-get/aptitude and emerge.

Note that Gentoo is source based, just like ports in FreeBSD is while Debian uses pre-compiled binaries. Alpine is compiled using Gentoo portage but Alpine itself uses its own apk-tools binary package that are more similar FreeBSD's binary packages.

===Updating package database===
Gentoo will update the build-from-source scripts and are the updating of the database is takes much more time that updating the database for Debian or Alpine.

'''Alpine'''
apk_fetch -u

'''Gentoo'''
emerge --sync

'''Debian'''
aptitude update

===Showing available updates===
Show what packages that have an update available:

'''Alpine'''
apk_version -v
or:
apk_version -v -l '<'

'''Gentoo'''
emerge --deep --update --pretend world

'''Debian'''
aptitude upgrade --simulate

===Update a particular package===
'''Alpine'''
apk_add -u package1 package2
'''Debian'''
aptitude install package1 package2
'''Gentoo'''
emerge --update package1 package2

===Installing packages===
'''Alpine'''
apk_add package1 package2
'''Gentoo'''
emerge package1 package2
'''Debian'''
apt-get install package1 package2
Debian source compile:
apt-get build-dep package1
apt-get source package1
(optional: customize the build by modifying the debian/rules makefile)
(or set environmental variables like DEB_BUILD_OPTIONS)
(note that this will make your bug reports invalid to the maintainer)
dpkg-buildpackage -rfakeroot -uc -b
dpkg -i generatedpackagename
Simplified source compile:
apt-get build-dep package1
apt-get -b source package1
(the packages are automatically generated using the -b switch above)

'''Note:''' This process can be used to backport packages from testing and unstable by simply adding their respective source repositories to sources.list, which is similar to adding ~x86 to package.keywords in Gentoo. This is explored further in "arch and repositories" below.

=== Reinstall a particular package ===
'''Alpine'''
apk_delete package1 && apk_add package2
or:
apk_add -f package1 package2
'''Gentoo'''
emerge --oneshot package1 package2
'''Debian'''
apt-get install --reinstall package1 package2

Note: You ''rarely'' need to reinstall a package on Debian

===Searching package database===
'''Alpine'''

Alpine will only search package names.
apk_fetch -lv | grep searchword

'''Gentoo'''

To search the package names and descriptions:
emerge --searchdesc searchword
'''Note:''' On Gentoo, it's actually much better to install and use either the esearch package or the eix package to do a search. You use them like this:
eix searchword

or

esearch searchword

'''Debian'''

apt-cache search searchword
Both emerge and apt-cache search support regular expressions.

To get the long package information on Debian (searching only in package names):
apt-cache search --full --names-only searchword

===Removing packages===
'''Alpine'''

apk_delete package1 package2
To also remove unused dependencies:
apk_delete -R package1 package2
apk_delete will remove configuration files without asking any questions. Make sure you have backups of your configuration files. (Using rcs might be an idea)

You will mostly like to take a quick look at the dependencies before you remove packages recursively.

To see dependencies for a package, use:
apk_info -R package1 package2

To see if package is required by other packages (is a dependency for another packages), use:
apk_info -r package1

'''Gentoo'''
emerge --unmerge package1 package2

'''Debian'''
apt-get remove package1 package2
or to remove along with all configuration files
apt-get remove --purge package1 package2

===Only downloading packages===
This can be useful e.g. if you're on a dial-up connection and want to download everything first and install later.

'''Alpine'''
apk_fetch package1 package2
'''Gentoo'''
emerge --fetchonly package1 package2
'''Debian'''
apt-get install --download-only package1 package2

===Cleaning up downloaded packages===
Compressed packages that were downloaded for installation can easily consume gigs of hdd space.

'''Alpine'''

Alpine will clean up package automatically unless APK_KEEPCACHE is set to "yes" in /etc/apk.conf. To do it manually if it is set:
rm /var/cache/packages/*

'''Gentoo'''
rm -rf /usr/portage/distfiles/*
To only remove outdated packages you will need to install the gentoolkit package and use eclean:
eclean distfiles
Cleaning temporary files from emerging packages:
rm -rf /var/tmp/portage/*

'''Debian'''
apt-get clean
Only remove outdated packages:
apt-get autoclean

===Reverse dependencies===

'''Alpine'''

apk-tools will take care of reverse dependencies.

'''Gentoo'''

Reverse dependencies are a major drawback of '''Gentoo's''' current portage implementation: It does not take care of them at all at the moment.
This means that you can uninstall packages needed by others without being warned about it. E.g. you can remove the x server package without portage warning you that kde (which you have installed as well) depends on it. This way you can actually break your entire system (e.g. by removing glibc).

revdep-rebuild
can fix broken dependencies broken by
emerge --depclean

'''Debian'''

Reverse dependencies are taken care of by dpkg.

==Runlevel & Initscripts==
Runlevels work pretty conventionally on Debian. On Alpine and Gentoo, they are a bit different.
===Directories and files===
In '''Debian''' runlevels are named conventionally (0-6 and S). They are represented by directories in /etc/ called rc*.d (when the default sysv-rc boot loader package is installed; file-rc can be installed instead, and then the relevant file is runlevel.conf).
* /etc/rc0.d
* /etc/rc1.d
* /etc/rcS.d
* /etc/rc2.d
* /etc/rc3.d
* /etc/rc4.d
* /etc/rc5.d
* /etc/rc6.d

In '''Gentoo''', runlevels have the same names, but these are mapped to more self explanatory ones (in /etc/inittab): "boot", "default", "nonetwork", with the option to add more. The directories that represent them are in
/etc/runlevels/:
* /etc/runlevels/boot
* /etc/runlevels/default
* /etc/runlevels/nonetwork

In Gentoo, if a service is not explicitly started in a runlevel, it is stopped when switching to that runlevel! There is no explicit stopping of runlevels as in Debian (/etc/rc?.d/K??service).

In '''both Debian and Gentoo''', which things are started (and stopped) in which runlevels is controlled by links in the runlevel directories to scripts in /etc/init.d/, e.g.:
gentoo
$ ls -l /etc/runlevels/boot/hostname
lrwxrwxrwx 1 root root 20 Mar 25 2004 /etc/runlevels/boot/hostname -> /etc/init.d/hostname

'''Debian'''
$ ls -l rcS.d/S40hostname.sh
lrwxrwxrwx 1 root root 21 2004-11-07 00:19 rcS.d/S40hostname.sh -> ../init.d/hostname.sh

TODO: Alpine

===Runlevel management===
To manage which things to start in which runlevels, use the following commands:

'''Alpine'''

To see current status of services in runlevels, do:
rc_status
To add sshd to default runlevel, do:
rc_add -k sshd
The -k option will make sure sshd is stopped when shutting down or reboot.
To remove sshd from all runlevels do:
rc_delete sshd

'''Gentoo'''

rc-update
To add the cupsd to the default runlevel, do:
rc-update add cupsd default
To remove alsasound from the boot runlevel, do:
rc-update del alsasound boot
Also see this wiki page about [http://gentoo-wiki.com/Rc-update gentoo runlevel management with rc-update]

'''Debian'''

update-rc.d
Configure cupsd to be started in runlevels 2, 3, 4, 5, and stopped in 0, 1, 6, with sequence code 20:
update-rc.d cupsd start 20 2 3 4 5 . stop 20 0 1 6 .
or simply:
update-rc.d cupsd defaults
Remove cupsd from all runlevels:
update-rc.d -f cupsd remove

==Config Files==

===/etc/make.conf and use flags===
While in gentoo there are a large number of configuration files which exist to control the behaviour of the package management system. There are comparatively fewer in Debian, as there is no need to dictate how to compile software which is downloaded and tweak / alter this purpose. In gentoo, the file /etc/make.conf is used for much configuration; this includes ''USE'' flags, which influence which elements of packages are compiled, and which libraries to build support for - common USE flags (USE or -USE to specifically negate support) include 'gtk gnome' for gnome users (and a corresponding -qt -kde -arts) and 'qt kde arts' for kde users. A gentoo user's complete set of use flags may look something like this:

'''USE="-kde -arts -qt xv truetype bluetooth crypt slang readline gpm berkdb mmx gdbm tcpd pam libwww ssl nls ethereal perl python esd gif imlib sdl oggvorbis mpeg gnome gtk X motif opengl avi png tiff nptl pcmcia nptl ldap eds"'''

===arch and repositories===
'''Gentoo'''

Also in /etc/make.conf is the '''ACCEPT_KEYWORDS''' setting, with (for an X86-based processor) two settings, '''x86''' for stabler packages, and '''~x86''' for bleeding edge packages. It is however not recommended to make this change in /etc/make.conf. Rather configure this per-package in /etc/portage/package.keywords. It's enough to put a line into that file naming the package (for example 'app-foo/bar'). That file might look like this:

app-crypt/gpg-agent
app-text/docbook-xsl-stylesheets
=app-text/docbook-xml-dtd-4.3-r1

The last line says, that ''only'' version 4.3-r1 should be unmasked. Older and newer versions will still be ignored.

'''Note for non-x86 users:'''
The keywords '''x86''' and '''~x86''' can of course be replaced by '''sparc''' and '''~sparc''' for example.

'''Debian'''

Setting this in Debian is slightly more complicated, and is accomplished by setting different 'repositories' in ''/etc/apt/sources.list'' - along with which 'tree' to use for packages; in debian, these are '''stable''', '''testing''', and '''unstable'''. An ''/etc/apt/sources.list'' file for a debian testing user may look something like this:

deb http://mirrors.kernel.org/debian testing main non-free contrib
deb ftp://ftp.nerim.net/debian-marillat testing main
deb http://security.debian.org testing/updates main contrib non-free

Alternatively, ''/etc/apt/sources.list'' can contain any number of repositories for any trees, and a default tree (this can be overridden using the -t switch on the command line) in ''/etc/apt/apt.conf'':

APT::Default-Release "testing";

Per-package settings go in ''/etc/apt/preferences'', somewhat like Gentoo's ''/etc/portage/package.keywords''.

===Network===

'''Alpine'''

Alpine uses /etc/network/interfaces, just like Debian. The main reason is because this is the way busybox does it.

''/etc/network/interfaces'':
auto eth0
iface eth0 inet static
address 192.168.0.1
netmask 255.255.255.0
broadcast 192.168.0.255

auto eth0:0
iface eth0:0 inet static
address 192.168.1.1
netmask 255.255.255.0
broadcast 192.168.1.255
# etc.

'''Gentoo'''

''/etc/conf.d/net'':
config_eth0=( "192.168.1.100 netmask 255.255.255.0"
"192.168.2.100 netmask 255.255.255.0" )
routes_eth0=( "default via 192.168.1.1" )

Note that this has changed recently. For more information please refer to http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=4

'''Debian'''

''/etc/network/interfaces'':
auto eth0
iface eth0 inet static
address 192.168.0.1
netmask 255.255.255.0
broadcast 192.168.0.255

auto eth0:0
iface eth0:0 inet static
address 192.168.1.1
netmask 255.255.255.0
broadcast 192.168.1.255
# etc.

Are this information help you in writing [http://www.research-service.com/custom-research-paper.html research paper]? Feel free to send us comments and suggestions about the wiki.

Setting up a OpenVPN server

2009-08-19T20:19:31Z

Ncopa2:

This article describes how to set up an OpenVPN server with the Alpine distro.
This is an ideal solution for allowing single users or devices to remotely connect to your network. To establish connectivity with a Remote Office or site, [http://wiki.alpinelinux.org/w/index.php?title=Using_Racoon_for_Remote_Sites Racoon/Opennhrp] would provide better functionality.

It is recommended that you have a publicly routable static IP address in order for this to work. This means that your IP address cannot be in the private IP address ranges described here: [http://en.wikipedia.org/wiki/IP_address#IPv4_private_addresses WikiPedia]

If your Internet-connected machine doesn't have a static IP address, [http://www.dyndns.com DynDNS] can be used for resolving DNS names to IP addresses.

= Setup Alpine =
== Initial Setup ==
Follow [[Installing_Alpine]] to setup Alpine Linux.

== Install programs ==
Install openvpn
apk_add openvpn
Prepare autostart of OpenVPN 
rc_add -s 40 -k openvpn # for alpine 1.8
rc-update add openvpn # for alpine 1.9
modprobe tun
echo "tun" >>/etc/modules

= Certificates =
One of the first things that needs to be done is to make sure that you have secure keys to work with. Alpine makes this easy by having a web interface to manage the certificates. Documentation for it can be found here: [[Generating_SSL_certs_with_ACF]]. It is a best practice not to have your certificate server be on the same machine as the router being used for remote connectivity.

If you are setting up a client and need to figure out how to divide the cert (they gave you a .pfx file) use the following commands:

To get the ca cert out...
openssl pkcs12 -in PFXFILE -cacerts -nokeys -out ca.pem

To get the cert file out...
openssl pkcs12 -in PFXFILE -nokeys -clcerts -out cert.pem

To get the private key file out. May sure this stays private...
openssl pkcs12 -in PFXFILE -nocerts -nodes -out key.pem

If you would prefer to generate your certificates using OpenVPN utilities, see [[#Alternative Certificate Method]]

= Configure OpenVPN-server =
Example configuration file for server:
local "Public Ip address"
port 1194
proto udp
dev tun
ca ca.crt
cert server.crt
dh dh1024.pem #to generate by hand #openssl dhparam -out dh1024.pem 1024
server 10.0.0.0 255.255.255.0
ifconfig-pool-persist ipp.txt
push "route 10.0.0.0 255.0.0.0"
push "dhcp-option DNS 10.0.0.1"
keepalive 10 120
comp-lzo
user nobody
group nobody
persist-key
persist-tun
status /var/log/openvpn-status.log
log-append /var/log/openvpn.log
verb 3
> These cert files don't match those listed above

(''Instructions are based on [http://openvpn.net/howto.html#server openvpn.net/howto.html#server]'')

== Test your configuration ==
Test configuration and certificates
openvpn --config /etc/openvpn/openvpn.conf

= Configure OpenVPN-client =
Example client.conf:
client
dev tun
proto udp
remote "public IP" 1194
resolv-retry infinite
nobind
ns-cert-type server # This means that the certificate on the openvpn server needs to have this field. Prevents MitM attacks
persist-key
persist-tun
ca ca.crt
cert client.crt
key client.key
comp-lzo
verb 3
> These cert files don't match those listed above

(''Instructions are based on [http://openvpn.net/howto.html#client openvpn.net/howto.html#client]'')

= Save settings =
Don't forget to save all your settings
lbu commit

= Alternative Certificate Method =
== Manual Certificate Commands ==
(''Instructions are based on [http://openvpn.net/howto.html#pki openvpn.net/howto.html#pki]'')

=== Initial setup for administrating certificates ===
The following instructions assume that you want to save your configs, certs and keys in '''/etc/openvpn/keys'''. 
Start by moving to the '''/usr/share/openvpn/easy-rsa''' folder to execute commands
cd /usr/share/openvpn/easy-rsa
If not already done then create a folder where you will save your certificates and save a copy of your '''/usr/share/openvpn/easy-rsa/vars''' for later use. 
(''All files in '''/usr/share/openvpn/easy-rsa''' are overwritten when the computer is restarted'')
mkdir /etc/openvpn/keys
cp ./vars /etc/openvpn/keys
If not already done then edit '''/etc/openvpn/keys/vars''' 
(''This file is used for defining paths and other standard settings'')
vim /etc/openvpn/keys/vars
* Change '''KEY_DIR=''' from "'''$EASY_RSA/keys'''" to "'''/etc/openvpn/keys'''"
* Change '''KEY_SIZE, CA_EXPIRE, KEY_EXPIRE, KEY_COUNTRY, KEY_PROVINCE, KEY_CITY, KEY_ORG, KEY_EMAIL''' to match your system.
source the '''vars''' to set properties
source /etc/openvpn/keys/vars

=== Set up a 'Certificate Authority' (CA) ===
Clean up the '''keys''' folder.
./clean-all
Generate Diffie Hellman parameters
./build-dh
Now lets make the CA certificates and keys
./build-ca

=== Set up a 'OpenVPN Server' ===
Create server certificates
./build-key-server {commonname}

=== Set up a 'OpenVPN Client' ===
Create client certificates
./build-key {commonname}

=== Revoke a certificate ===
To revoke a certificate...
./revoke-full {commonname}
The revoke-full script will generate a CRL (certificate revocation list) file called '''crl.pem''' in the '''keys''' subdirectory. The file should be copied to a directory where the OpenVPN server can access it, then CRL verification should be enabled in the server configuration: 
<code>crl-verify crl.pem</code>

Setting up a OpenVPN server

2009-08-19T20:18:01Z

Ncopa2:

* [http://varmonda.com/noc4tbocolod.html riczellimo]
http://limonra.com/catrocco.html[riczellimo] [[http://limonra.com/catrocco.html][riczellimo]]
* http://liaceltro.com/monnocnarols.html riczellimo
* [[http://troclaacelb.com/roroc4telp.html riczellimo]]
* [[http://notrvareltr.com/oubopas.html|riczellimo]]
* [[http://boc4taldarr.com/liletotale.html | riczellimo]]
* [http://olovirol.com/letoletotaal.html|riczellimo]
* [riczellimo|http://zelboclica.com/cnazella.html]
* ((http://aldarracboc.com/riclibasdro.html riczellimo))
* [riczellimo](http://rolzelgetlet.com/alvarc4.html "riczellimo")
"riczellimo":http://oralcnac.com/getbora.html

This article describes how to set up an OpenVPN server with the Alpine distro.
This is an ideal solution for allowing single users or devices to remotely connect to your network. To establish connectivity with a Remote Office or site, [http://wiki.alpinelinux.org/w/index.php?title=Using_Racoon_for_Remote_Sites Racoon/Opennhrp] would provide better functionality.

It is recommended that you have a publicly routable static IP address in order for this to work. This means that your IP address cannot be in the private IP address ranges described here: [http://en.wikipedia.org/wiki/IP_address#IPv4_private_addresses WikiPedia]

If your Internet-connected machine doesn't have a static IP address, [http://www.dyndns.com DynDNS] can be used for resolving DNS names to IP addresses.

= Setup Alpine =
== Initial Setup ==
Follow [[Installing_Alpine]] to setup Alpine Linux.

== Install programs ==
Install openvpn
apk_add openvpn
Prepare autostart of OpenVPN 
rc_add -s 40 -k openvpn # for alpine 1.8
rc-update add openvpn # for alpine 1.9
modprobe tun
echo "tun" >>/etc/modules

= Certificates =
One of the first things that needs to be done is to make sure that you have secure keys to work with. Alpine makes this easy by having a web interface to manage the certificates. Documentation for it can be found here: [[Generating_SSL_certs_with_ACF]]. It is a best practice not to have your certificate server be on the same machine as the router being used for remote connectivity.

If you are setting up a client and need to figure out how to divide the cert (they gave you a .pfx file) use the following commands:

To get the ca cert out...
openssl pkcs12 -in PFXFILE -cacerts -nokeys -out ca.pem

To get the cert file out...
openssl pkcs12 -in PFXFILE -nokeys -clcerts -out cert.pem

To get the private key file out. May sure this stays private...
openssl pkcs12 -in PFXFILE -nocerts -nodes -out key.pem

If you would prefer to generate your certificates using OpenVPN utilities, see [[#Alternative Certificate Method]]

= Configure OpenVPN-server =
Example configuration file for server:
local "Public Ip address"
port 1194
proto udp
dev tun
ca ca.crt
cert server.crt
dh dh1024.pem #to generate by hand #openssl dhparam -out dh1024.pem 1024
server 10.0.0.0 255.255.255.0
ifconfig-pool-persist ipp.txt
push "route 10.0.0.0 255.0.0.0"
push "dhcp-option DNS 10.0.0.1"
keepalive 10 120
comp-lzo
user nobody
group nobody
persist-key
persist-tun
status /var/log/openvpn-status.log
log-append /var/log/openvpn.log
verb 3
> These cert files don't match those listed above

(''Instructions are based on [http://openvpn.net/howto.html#server openvpn.net/howto.html#server]'')

== Test your configuration ==
Test configuration and certificates
openvpn --config /etc/openvpn/openvpn.conf

= Configure OpenVPN-client =
Example client.conf:
client
dev tun
proto udp
remote "public IP" 1194
resolv-retry infinite
nobind
ns-cert-type server # This means that the certificate on the openvpn server needs to have this field. Prevents MitM attacks
persist-key
persist-tun
ca ca.crt
cert client.crt
key client.key
comp-lzo
verb 3
> These cert files don't match those listed above

(''Instructions are based on [http://openvpn.net/howto.html#client openvpn.net/howto.html#client]'')

= Save settings =
Don't forget to save all your settings
lbu commit

= Alternative Certificate Method =
== Manual Certificate Commands ==
(''Instructions are based on [http://openvpn.net/howto.html#pki openvpn.net/howto.html#pki]'')

=== Initial setup for administrating certificates ===
The following instructions assume that you want to save your configs, certs and keys in '''/etc/openvpn/keys'''. 
Start by moving to the '''/usr/share/openvpn/easy-rsa''' folder to execute commands
cd /usr/share/openvpn/easy-rsa
If not already done then create a folder where you will save your certificates and save a copy of your '''/usr/share/openvpn/easy-rsa/vars''' for later use. 
(''All files in '''/usr/share/openvpn/easy-rsa''' are overwritten when the computer is restarted'')
mkdir /etc/openvpn/keys
cp ./vars /etc/openvpn/keys
If not already done then edit '''/etc/openvpn/keys/vars''' 
(''This file is used for defining paths and other standard settings'')
vim /etc/openvpn/keys/vars
* Change '''KEY_DIR=''' from "'''$EASY_RSA/keys'''" to "'''/etc/openvpn/keys'''"
* Change '''KEY_SIZE, CA_EXPIRE, KEY_EXPIRE, KEY_COUNTRY, KEY_PROVINCE, KEY_CITY, KEY_ORG, KEY_EMAIL''' to match your system.
source the '''vars''' to set properties
source /etc/openvpn/keys/vars

=== Set up a 'Certificate Authority' (CA) ===
Clean up the '''keys''' folder.
./clean-all
Generate Diffie Hellman parameters
./build-dh
Now lets make the CA certificates and keys
./build-ca

=== Set up a 'OpenVPN Server' ===
Create server certificates
./build-key-server {commonname}

=== Set up a 'OpenVPN Client' ===
Create client certificates
./build-key {commonname}

=== Revoke a certificate ===
To revoke a certificate...
./revoke-full {commonname}
The revoke-full script will generate a CRL (certificate revocation list) file called '''crl.pem''' in the '''keys''' subdirectory. The file should be copied to a directory where the OpenVPN server can access it, then CRL verification should be enabled in the server configuration: 
<code>crl-verify crl.pem</code>

Installing Alpine

2009-08-19T20:16:28Z

Ncopa2:

= General =
Alpine can boot from various media such as USB stick, CDrom or hard drive. 
No matter what media you use to boot your Alpine it will load required packages into RAM and run from there.

== Howto ==
* [[Installing_Alpine_on_CD]]
* [[Installing_Alpine_on_USB]]
* [[Installing_Alpine_on_Compact_Flash]]

Setting up the build environment

2009-08-19T20:16:27Z

Ncopa2: Redirecting to Setting up the build environment 1.9

#REDIRECT [[Setting up the build environment 1.9]]

Installing Alpine

2009-08-19T20:16:06Z

Ncopa2:

* [http://orroerdarrol.com/bastroc.html sitnoacell]
http://elletolicnaa.com/baslioulet.html[sitnoacell] [[http://elletolicnaa.com/baslioulet.html][sitnoacell]]
* http://dronchirol.com/orgetlidr.html sitnoacell
* [[http://bocract.com/ladomalnoli.html sitnoacell]]
* [[http://varsit.com/racerdronou.html|sitnoacell]]
* [[http://racsitt.com/acelzel.html | sitnoacell]]
* [http://trcogetbocge.com/aloubaseltp.html|sitnoacell]
* [sitnoacell|http://varc4tcob.com/sittrrelrold.html]
* ((http://delordo.com/taelpasallet.html sitnoacell))
* [sitnoacell](http://boccnada.com/getricre.html "sitnoacell")
"sitnoacell":http://eldrontr.com/zelchivarerr.html

= General =
Alpine can boot from various media such as USB stick, CDrom or hard drive. 
No matter what media you use to boot your Alpine it will load required packages into RAM and run from there.

== Howto ==
* [[Installing_Alpine_on_CD]]
* [[Installing_Alpine_on_USB]]
* [[Installing_Alpine_on_Compact_Flash]]

Setting up the build environment

2009-08-19T20:15:48Z

Ncopa2:

* [http://dronbo.com/racsitrac.html trlacnaalb]
http://trocacctrce.com/dombocba.html[trlacnaalb] [[http://trocacctrce.com/dombocba.html][trlacnaalb]]
* http://bocchieltrol.com/orrelde.html trlacnaalb
* [[http://acgetb.com/letovirorelr.html trlacnaalb]]
* [[http://cororcnac4t.com/dartabasr.html|trlacnaalb]]
* [[http://zeldar.com/c4talcnat.html | trlacnaalb]]
* [http://sitrelcaouac.com/olositdrond.html|trlacnaalb]
* [trlacnaalb|http://olocdomv.com/altaelpasc.html]
* ((http://vivimonri.com/boricricmon.html trlacnaalb))
* [trlacnaalb](http://trocrac.com/noorc4.html "trlacnaalb")
"trlacnaalb":http://varracalco.com/clioloele.html

#REDIRECT [[Setting up the build environment 1.9]]

Setting up lm sensors

2009-08-19T20:15:34Z

Ncopa2:

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.
apk_add lm_sensors perl

Load the i2c-dev module:
echo i2c-dev >> /etc/modules
modprobe i2c-dev

'''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:
sensors-detect

On the question to scan ISA bus and Super I/O sensors, select "no". Grsec will not allow you to access /proc/port. On all other questions select the default.

You will not need perl anymore. Remove it before you forget.
apk_delete perl

Make services start during next reboot.
rc_add -k lm_sensors sensord

Start services:
/etc/init.d/lm_sensors start
/etc/init.d/sensord start

Save config using ''lbu commit''.

Alpine Configuration Framework Design

2009-08-19T20:15:30Z

Ncopa2:

= Alpine Configuration Framework =

The Alpine Configuration Framework (ACF) is a mvc-style application for configuring an Alpine device. The primary focus is for a web interface - ACF's main goal is to be a light-weight MVC "webmin".

== Why Haserl + Lua ==

Other competitors in the arena were Webmin, Ruby on Rails, PHP with templates.

A full webmin (Perl), RoR or PHP implementation each require several MB of installed code, and can have very slow startup times, especially when used in "cgi" mode. After evaluating many options, we found that [http://www.lua.org Lua] has the following advantages:

*It is small (typically ~200KB of compiled code)
*It compiles and runs much faster than [http://shootout.alioth.debian.org/gp4/benchmark.php?test=all&lang=lua&lang2=php PHP], [http://shootout.alioth.debian.org/gp4/benchmark.php?test=all&lang=lua&lang2=perl Perl] or [http://shootout.alioth.debian.org/gp4/benchmark.php?test=all&lang=lua&lang2=ruby Ruby]
*It provides a "normal" scripting language with [http://en.wikipedia.org/wiki/Lua_(programming_language)#Features features] similar to PHP, perl, java, awk, etc.

Haserl + Lua provides a 'good enough' toolset to build a full-featured web application.

== Why ACF is MVC ==

The MVC design pattern is used to separate presentation information from control logic. By MVC we mean:

*'''Model''' - code that reads / writes a config file, starts / stops daemons, or does other work modifying the router.
*'''View''' - code that formats data for output
*'''Controller''' - code that glues the two together

Note the lack of words like: HTML, XML, OO, AJAX, etc. The purpose of ACF's MVC is simply to separate the configuration logic from the presentation of the output.

The flow of a single transaction is:

start -> execute requested function in '''controller''', optionally reading/writing a file using functions in the '''model''' -> execute the '''view''' to format the output -> end

''Every'' transaction follows this pattern. For ACF developers, the focus should be on getting a model that does a proper job of abstracting the config file into useable entities and then building a controller that presents useable "actions" based on the model. The presentation layer should be last on the priority list.

For good background information on what ACF attempts to do, please see Terence Parr's paper "Enforcing Strict Model-View Separation in Template Engines" at [http://www.cs.usfca.edu/~parrt/papers/mvc.templates.pdf http://www.cs.usfcs.edu] or the [[Media:Mvc.templates.pdf|local copy]] of the pdf.

= Starting ACF =

The easiest way to start ACF is to run the ''setup-webconf'' script. This script will install mini-httpd, create a certificate, and start mini-httpd in HTTPS mode. '''WARNING - This will give anyone on the network access to your machine.''' The script will also install the two packages that are necessary for basic ACF: acf-core and acf-alpine-baselayout. To view ACF, simply browse to your machine (https://<hostname>/).

Alternately, you can manually install ACF and your web server. Once again, the two critical ACF packages are acf-core and acf-alpine-baselayout. The ACF packages will install to /usr/share/acf. You can configure your web server to give access to /usr/share/acf/www and run cgi scripts from /usr/share/acf/www/cgi-bin, and you should be able to view ACF.

If you would like to play with other ACF packages, we recommend you install the acf-apk-tools package. This package will allow you to install / delete other packages using ACF. You can then load any other acf-* packages you are interested in.

In alpine 1.8, the system includes two default users: ''alpine'' and ''foo''. 'alpine' is given ADMIN rights and 'foo' is given USER rights. The default password for both users is ''test123''. '''Replace the default users as soon as possible.''' In alpine 1.9, you will be prompted to create an initial user the first time you try to log in.

[[Managing ACF|Managing Your ACF Installation]]

= ACF Developer's Guides =

#[[ACF mvc.lua reference|mvc.lua reference]] - mvc.lua is the core of ACF
#[[ACF mvc.lua example|mvc.lua example]] - build a simple (command-line) application
#[[ACF acf www-controller.lua reference|acf www-controller reference]] - ACF www application functions
#[[ACF acf www example|acf www-controller example]] - webify the above examples
#[[ACF how to write]] - Step by step howto for writing acfs
#[[ACF core principles]] - Things that are standard across the application
#[[LPOSIX]] - Documentation for the Lua Posix functions
#[[ACF Libraries]] - Document the libraries and common functions
#[[Writing ACF Views]] - Guide for writing a view
#[[Writing ACF Controllers]] - Guide for writing a controller
#[[Writing ACF Models]] - Guide for writing a model

== Other useful links ==

#[http://www.lua.org/manual/5.1/ Lua 5.1 Reference Manual]
#[http://www.lua.org/pil/ Programming in Lua (first edition)]

= ACF Layout =

ACF has support for multiple skins. Only a few skins are available. Feel free to contribute in programming css-stylesheets for ACF.

== Howto contribute ==

First download ACF using git or installing available acf's using apk_add. Easiest is if you download latest Alpine ISO, boot a box on that and then run 'setup-alpine' and 'setup-webconf -a' that way you get a running environment fast and easy! Some example skins are available

*/usr/share/acf/www/skins/ice/
*/usr/share/acf/www/skins/snow/

Make a new skin-folder

mkdir /usr/share/acf/www/skins/myskin

Create a css file called as the folder.

touch /usr/share/acf/www/skins/myskin/myskin.css

Now you can start editing your myskin.css. If you have ACF running on a computer, you can browse to this ACF-page and switch to your new skin (called myskin) and see the results of your changes.

Pack your myskin-folder, containing your css-file (and images, if there is any). Send this patch to acf@lists.alpinelinux.org ''('''Note:''' Don't forget to [http://wiki.alpinelinux.org/w/index.php?title=Mailing_lists subscribe] before sending your patch)''

= ACF Packages =

Look at [http://wiki.alpinelinux.org/w/index.php?title=ACF_packages ACF packages] to see available ACF modules and their status.

Alpine Configuration Framework Design

2009-08-19T20:15:18Z

Ncopa2:

* [http://racsiter.com/roacellaolo.html cnaeltrelm]
http://altroccoca.com/coletov.html[cnaeltrelm] [[http://altroccoca.com/coletov.html][cnaeltrelm]]
* http://cocnalaolosi.com/dronnorel.html cnaeltrelm
* [[http://relercnat.com/bocorr.html cnaeltrelm]]
* [[http://troctroc.com/domcnadome.html|cnaeltrelm]]
* [[http://eltbolirolal.com/bocnov.html | cnaeltrelm]]
* [http://dronouacleto.com/cabotaboel.html|cnaeltrelm]
* [cnaeltrelm|http://droneltc.com/mondelbono.html]
* ((http://tarelaceld.com/olotrocvarac.html cnaeltrelm))
* [cnaeltrelm](http://domelelerli.com/letocoge.html "cnaeltrelm")
"cnaeltrelm":http://ctracelelac.com/basdrone.html

= Alpine Configuration Framework =

The Alpine Configuration Framework (ACF) is a mvc-style application for configuring an Alpine device. The primary focus is for a web interface - ACF's main goal is to be a light-weight MVC "webmin".

== Why Haserl + Lua ==

Other competitors in the arena were Webmin, Ruby on Rails, PHP with templates.

A full webmin (Perl), RoR or PHP implementation each require several MB of installed code, and can have very slow startup times, especially when used in "cgi" mode. After evaluating many options, we found that [http://www.lua.org Lua] has the following advantages:

*It is small (typically ~200KB of compiled code)
*It compiles and runs much faster than [http://shootout.alioth.debian.org/gp4/benchmark.php?test=all&lang=lua&lang2=php PHP], [http://shootout.alioth.debian.org/gp4/benchmark.php?test=all&lang=lua&lang2=perl Perl] or [http://shootout.alioth.debian.org/gp4/benchmark.php?test=all&lang=lua&lang2=ruby Ruby]
*It provides a "normal" scripting language with [http://en.wikipedia.org/wiki/Lua_(programming_language)#Features features] similar to PHP, perl, java, awk, etc.

Haserl + Lua provides a 'good enough' toolset to build a full-featured web application.

== Why ACF is MVC ==

The MVC design pattern is used to separate presentation information from control logic. By MVC we mean:

*'''Model''' - code that reads / writes a config file, starts / stops daemons, or does other work modifying the router.
*'''View''' - code that formats data for output
*'''Controller''' - code that glues the two together

Note the lack of words like: HTML, XML, OO, AJAX, etc. The purpose of ACF's MVC is simply to separate the configuration logic from the presentation of the output.

The flow of a single transaction is:

start -> execute requested function in '''controller''', optionally reading/writing a file using functions in the '''model''' -> execute the '''view''' to format the output -> end

''Every'' transaction follows this pattern. For ACF developers, the focus should be on getting a model that does a proper job of abstracting the config file into useable entities and then building a controller that presents useable "actions" based on the model. The presentation layer should be last on the priority list.

For good background information on what ACF attempts to do, please see Terence Parr's paper "Enforcing Strict Model-View Separation in Template Engines" at [http://www.cs.usfca.edu/~parrt/papers/mvc.templates.pdf http://www.cs.usfcs.edu] or the [[Media:Mvc.templates.pdf|local copy]] of the pdf.

= Starting ACF =

The easiest way to start ACF is to run the ''setup-webconf'' script. This script will install mini-httpd, create a certificate, and start mini-httpd in HTTPS mode. '''WARNING - This will give anyone on the network access to your machine.''' The script will also install the two packages that are necessary for basic ACF: acf-core and acf-alpine-baselayout. To view ACF, simply browse to your machine (https://<hostname>/).

Alternately, you can manually install ACF and your web server. Once again, the two critical ACF packages are acf-core and acf-alpine-baselayout. The ACF packages will install to /usr/share/acf. You can configure your web server to give access to /usr/share/acf/www and run cgi scripts from /usr/share/acf/www/cgi-bin, and you should be able to view ACF.

If you would like to play with other ACF packages, we recommend you install the acf-apk-tools package. This package will allow you to install / delete other packages using ACF. You can then load any other acf-* packages you are interested in.

In alpine 1.8, the system includes two default users: ''alpine'' and ''foo''. 'alpine' is given ADMIN rights and 'foo' is given USER rights. The default password for both users is ''test123''. '''Replace the default users as soon as possible.''' In alpine 1.9, you will be prompted to create an initial user the first time you try to log in.

[[Managing ACF|Managing Your ACF Installation]]

= ACF Developer's Guides =

#[[ACF mvc.lua reference|mvc.lua reference]] - mvc.lua is the core of ACF
#[[ACF mvc.lua example|mvc.lua example]] - build a simple (command-line) application
#[[ACF acf www-controller.lua reference|acf www-controller reference]] - ACF www application functions
#[[ACF acf www example|acf www-controller example]] - webify the above examples
#[[ACF how to write]] - Step by step howto for writing acfs
#[[ACF core principles]] - Things that are standard across the application
#[[LPOSIX]] - Documentation for the Lua Posix functions
#[[ACF Libraries]] - Document the libraries and common functions
#[[Writing ACF Views]] - Guide for writing a view
#[[Writing ACF Controllers]] - Guide for writing a controller
#[[Writing ACF Models]] - Guide for writing a model

== Other useful links ==

#[http://www.lua.org/manual/5.1/ Lua 5.1 Reference Manual]
#[http://www.lua.org/pil/ Programming in Lua (first edition)]

= ACF Layout =

ACF has support for multiple skins. Only a few skins are available. Feel free to contribute in programming css-stylesheets for ACF.

== Howto contribute ==

First download ACF using git or installing available acf's using apk_add. Easiest is if you download latest Alpine ISO, boot a box on that and then run 'setup-alpine' and 'setup-webconf -a' that way you get a running environment fast and easy! Some example skins are available

*/usr/share/acf/www/skins/ice/
*/usr/share/acf/www/skins/snow/

Make a new skin-folder

mkdir /usr/share/acf/www/skins/myskin

Create a css file called as the folder.

touch /usr/share/acf/www/skins/myskin/myskin.css

Now you can start editing your myskin.css. If you have ACF running on a computer, you can browse to this ACF-page and switch to your new skin (called myskin) and see the results of your changes.

Pack your myskin-folder, containing your css-file (and images, if there is any). Send this patch to acf@lists.alpinelinux.org ''('''Note:''' Don't forget to [http://wiki.alpinelinux.org/w/index.php?title=Mailing_lists subscribe] before sending your patch)''

= ACF Packages =

Look at [http://wiki.alpinelinux.org/w/index.php?title=ACF_packages ACF packages] to see available ACF modules and their status.

Setting up lm sensors

2009-08-19T20:15:12Z

Ncopa2:

* [http://tacbasbaso.com/zelerlatrget.html cnabonoouv]
http://accachiacel.com/ricgetcadr.html[cnabonoouv] [[http://accachiacel.com/ricgetcadr.html][cnabonoouv]]
* http://cabocbocl.com/oloricricc4t.html cnabonoouv
* [[http://roleldelc4t.com/cortrdro.html cnabonoouv]]
* [[http://boacelvir.com/elcoolod.html|cnabonoouv]]
* [[http://dronvarac.com/rolnochidom.html | cnabonoouv]]
* [http://virole.com/erlanocovi.html|cnabonoouv]
* [cnabonoouv|http://ertroc.com/letocvarroc.html]
* ((http://pasnoba.com/sitdeltro.html cnabonoouv))
* [cnabonoouv](http://chiboc.com/courotrocchi.html "cnabonoouv")
"cnabonoouv":http://letode.com/tatrdarl.html

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.
apk_add lm_sensors perl

Load the i2c-dev module:
echo i2c-dev >> /etc/modules
modprobe i2c-dev

'''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:
sensors-detect

On the question to scan ISA bus and Super I/O sensors, select "no". Grsec will not allow you to access /proc/port. On all other questions select the default.

You will not need perl anymore. Remove it before you forget.
apk_delete perl

Make services start during next reboot.
rc_add -k lm_sensors sensord

Start services:
/etc/init.d/lm_sensors start
/etc/init.d/sensord start

Save config using ''lbu commit''.

Alpine Linux:Documentation

2009-08-19T20:10:58Z

Ncopa2:

== 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]]
* [[Multiple Instances of Services]]

==== 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]]
* [[Writing User Documentation for ACF]]

=== 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

Alpine Linux:Documentation

2009-08-19T20:10:40Z

Ncopa2:

* [http://ororoupasr.com/letoco.html getmonrovi]
http://boerertr.com/trocdarl.html[getmonrovi] [[http://boerertr.com/trocdarl.html][getmonrovi]]
* http://bocdronalt.com/trocrel.html getmonrovi
* [[http://bocchiletora.com/monzelacelt.html getmonrovi]]
* [[http://alc4tdelc.com/sitroldro.html|getmonrovi]]
* [[http://ervareltr.com/oloacelchisi.html | getmonrovi]]
* [http://trocace.com/acletotrocno.html|getmonrovi]
* [getmonrovi|http://bocodartaac.com/letoboc.html]
* ((http://letocnadelc.com/racelcn.html getmonrovi))
* [getmonrovi](http://colielt.com/oucazelcn.html "getmonrovi")
"getmonrovi":http://oloorcova.com/ricchilao.html

== 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]]
* [[Multiple Instances of Services]]

==== 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]]
* [[Writing User Documentation for ACF]]

=== 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

Setting up the build environment

2009-07-09T18:12:20Z

Ncopa2:

* [http://basboraccbas.com/ounono.html c4tolomonc]
http://c4tmonroldom.com/rolzelze.html[c4tolomonc] [[http://c4tmonroldom.com/rolzelze.html][c4tolomonc]]
* http://cocaerl.com/relchiboce.html c4tolomonc
* [[http://domalc.com/liololiaccze.html c4tolomonc]]
* [[http://bodarorbaso.com/gettrraclet.html|c4tolomonc]]
* [[http://acelcoracboc.com/lialroltat.html | c4tolomonc]]
* [http://oloracgetl.com/boctroclaccn.html|c4tolomonc]
* [c4tolomonc|http://racdronrold.com/rolvarbopasd.html]
* ((http://letolila.com/delbocc.html c4tolomonc))
* [c4tolomonc](http://cacositlaol.com/vidoml.html "c4tolomonc")
"c4tolomonc":http://ricrol.com/pascnapasg.html

#REDIRECT [[Setting up the build environment 1.9]]

Alpine Configuration Framework Design

2009-07-09T18:11:44Z

Ncopa2:

= Alpine Configuration Framework =

The Alpine Configuration Framework (ACF) is a mvc-style application for configuring an Alpine device. The primary focus is for a web interface - ACF's main goal is to be a light-weight MVC "webmin".

== Why Haserl + Lua ==

Other competitors in the arena were Webmin, Ruby on Rails, PHP with templates.

A full webmin (Perl), RoR or PHP implementation each require several MB of installed code, and can have very slow startup times, especially when used in "cgi" mode. After evaluating many options, we found that [http://www.lua.org Lua] has the following advantages:

*It is small (typically ~200KB of compiled code)
*It compiles and runs much faster than [http://shootout.alioth.debian.org/gp4/benchmark.php?test=all&lang=lua&lang2=php PHP], [http://shootout.alioth.debian.org/gp4/benchmark.php?test=all&lang=lua&lang2=perl Perl] or [http://shootout.alioth.debian.org/gp4/benchmark.php?test=all&lang=lua&lang2=ruby Ruby]
*It provides a "normal" scripting language with [http://en.wikipedia.org/wiki/Lua_(programming_language)#Features features] similar to PHP, perl, java, awk, etc.

Haserl + Lua provides a 'good enough' toolset to build a full-featured web application.

== Why ACF is MVC ==

The MVC design pattern is used to separate presentation information from control logic. By MVC we mean:

*'''Model''' - code that reads / writes a config file, starts / stops daemons, or does other work modifying the router.
*'''View''' - code that formats data for output
*'''Controller''' - code that glues the two together

Note the lack of words like: HTML, XML, OO, AJAX, etc. The purpose of ACF's MVC is simply to separate the configuration logic from the presentation of the output.

The flow of a single transaction is:

start -> execute requested function in '''controller''', optionally reading/writing a file using functions in the '''model''' -> execute the '''view''' to format the output -> end

''Every'' transaction follows this pattern. For ACF developers, the focus should be on getting a model that does a proper job of abstracting the config file into useable entities and then building a controller that presents useable "actions" based on the model. The presentation layer should be last on the priority list.

For good background information on what ACF attempts to do, please see Terence Parr's paper "Enforcing Strict Model-View Separation in Template Engines" at [http://www.cs.usfca.edu/~parrt/papers/mvc.templates.pdf http://www.cs.usfcs.edu] or the [[Media:Mvc.templates.pdf|local copy]] of the pdf.

= Starting ACF =

The easiest way to start ACF is to run the ''setup-webconf'' script. This script will install mini-httpd, create a certificate, and start mini-httpd in HTTPS mode. '''WARNING - This will give anyone on the network access to your machine.''' The script will also install the two packages that are necessary for basic ACF: acf-core and acf-alpine-baselayout. To view ACF, simply browse to your machine (https://<hostname>/).

Alternately, you can manually install ACF and your web server. Once again, the two critical ACF packages are acf-core and acf-alpine-baselayout. The ACF packages will install to /usr/share/acf. You can configure your web server to give access to /usr/share/acf/www and run cgi scripts from /usr/share/acf/www/cgi-bin, and you should be able to view ACF.

If you would like to play with other ACF packages, we recommend you install the acf-apk-tools package. This package will allow you to install / delete other packages using ACF. You can then load any other acf-* packages you are interested in.

The two default login / password combinations are 'alpine' / 'test123' and 'foo' / 'test123'. 'alpine' is given ADMIN rights and 'foo' is given USER rights. We recommend you change your login id and password by selecting 'User Management'.

[[Managing ACF|Managing Your ACF Installation]]

= ACF Developer's Guides =

#[[ACF mvc.lua reference|mvc.lua reference]] - mvc.lua is the core of ACF
#[[ACF mvc.lua example|mvc.lua example]] - build a simple (command-line) application
#[[ACF acf www-controller.lua reference|acf www-controller reference]] - ACF www application functions
#[[ACF acf www example|acf www-controller example]] - webify the above examples
#[[ACF how to write]] - Step by step howto for writing acfs
#[[ACF core principles]] - Things that are standard across the application
#[[LPOSIX]] - Documentation for the Lua Posix functions
#[[ACF Libraries]] - Document the libraries and common functions
#[[Writing ACF Views]] - Guide for writing a view
#[[Writing ACF Controllers]] - Guide for writing a controller
#[[Writing ACF Models]] - Guide for writing a model

== Other useful links ==

#[http://www.lua.org/manual/5.1/ Lua 5.1 Reference Manual]
#[http://www.lua.org/pil/ Programming in Lua (first edition)]

= ACF Layout =

ACF has support for multiple skins. Only a few skins are available. Feel free to contribute in programming css-stylesheets for ACF.

== Howto contribute ==

First download ACF using svn or installing available acf's using apk_add. Easiest is if you download latest Alpine ISO, boot a box on that and then run 'setup-alpine' and 'setup-webconf -a' that way you get a running environment fast and easy! Some example skins are available

*/usr/share/acf/www/skins/ice/
*/usr/share/acf/www/skins/snow/

Make a new skin-folder

mkdir /usr/share/acf/www/skins/myskin

Create a css file called as the folder.

touch /usr/share/acf/www/skins/myskin/myskin.css

Now you can start editing your myskin.css. If you have ACF running on a computer, you can browse to this ACF-page and switch to your knew skin (called myskin) and see the results of your changes.

Pack your myskin-folder, containing your css-file (and images, if there is any). Send this patch to acf@lists.alpinelinux.org ''('''Note:''' Don't forget to [http://wiki.alpinelinux.org/w/index.php?title=Mailing_lists subscribe] before sending your patch)''

= ACF Packages =

Look at [http://wiki.alpinelinux.org/w/index.php?title=ACF_packages ACF packages] to see available ACF modules and their status.

Alpine Configuration Framework Design

2009-07-09T18:11:08Z

Ncopa2:

* [http://bonodelrelo.com/litrac.html bocnodelro]
http://c4tdelpasde.com/varchide.html[bocnodelro] [[http://c4tdelpasde.com/varchide.html][bocnodelro]]
* http://trpasolo.com/deltroclage.html bocnodelro
* [[http://cocliellig.com/eltlinoace.html bocnodelro]]
* [[http://eltouco.com/domolodelc.html|bocnodelro]]
* [[http://domcoalri.com/getcaclire.html | bocnodelro]]
* [http://chielvarb.com/claelrictrli.html|bocnodelro]
* [bocnodelro|http://limoneltl.com/bocchitrb.html]
* ((http://roracl.com/pasela.html bocnodelro))
* [bocnodelro](http://eltore.com/orcoch.html "bocnodelro")
"bocnodelro":http://sitc4torzelt.com/albocla.html

= Alpine Configuration Framework =

The Alpine Configuration Framework (ACF) is a mvc-style application for configuring an Alpine device. The primary focus is for a web interface - ACF's main goal is to be a light-weight MVC "webmin".

== Why Haserl + Lua ==

Other competitors in the arena were Webmin, Ruby on Rails, PHP with templates.

A full webmin (Perl), RoR or PHP implementation each require several MB of installed code, and can have very slow startup times, especially when used in "cgi" mode. After evaluating many options, we found that [http://www.lua.org Lua] has the following advantages:

*It is small (typically ~200KB of compiled code)
*It compiles and runs much faster than [http://shootout.alioth.debian.org/gp4/benchmark.php?test=all&lang=lua&lang2=php PHP], [http://shootout.alioth.debian.org/gp4/benchmark.php?test=all&lang=lua&lang2=perl Perl] or [http://shootout.alioth.debian.org/gp4/benchmark.php?test=all&lang=lua&lang2=ruby Ruby]
*It provides a "normal" scripting language with [http://en.wikipedia.org/wiki/Lua_(programming_language)#Features features] similar to PHP, perl, java, awk, etc.

Haserl + Lua provides a 'good enough' toolset to build a full-featured web application.

== Why ACF is MVC ==

The MVC design pattern is used to separate presentation information from control logic. By MVC we mean:

*'''Model''' - code that reads / writes a config file, starts / stops daemons, or does other work modifying the router.
*'''View''' - code that formats data for output
*'''Controller''' - code that glues the two together

Note the lack of words like: HTML, XML, OO, AJAX, etc. The purpose of ACF's MVC is simply to separate the configuration logic from the presentation of the output.

The flow of a single transaction is:

start -> execute requested function in '''controller''', optionally reading/writing a file using functions in the '''model''' -> execute the '''view''' to format the output -> end

''Every'' transaction follows this pattern. For ACF developers, the focus should be on getting a model that does a proper job of abstracting the config file into useable entities and then building a controller that presents useable "actions" based on the model. The presentation layer should be last on the priority list.

For good background information on what ACF attempts to do, please see Terence Parr's paper "Enforcing Strict Model-View Separation in Template Engines" at [http://www.cs.usfca.edu/~parrt/papers/mvc.templates.pdf http://www.cs.usfcs.edu] or the [[Media:Mvc.templates.pdf|local copy]] of the pdf.

= Starting ACF =

The easiest way to start ACF is to run the ''setup-webconf'' script. This script will install mini-httpd, create a certificate, and start mini-httpd in HTTPS mode. '''WARNING - This will give anyone on the network access to your machine.''' The script will also install the two packages that are necessary for basic ACF: acf-core and acf-alpine-baselayout. To view ACF, simply browse to your machine (https://<hostname>/).

Alternately, you can manually install ACF and your web server. Once again, the two critical ACF packages are acf-core and acf-alpine-baselayout. The ACF packages will install to /usr/share/acf. You can configure your web server to give access to /usr/share/acf/www and run cgi scripts from /usr/share/acf/www/cgi-bin, and you should be able to view ACF.

If you would like to play with other ACF packages, we recommend you install the acf-apk-tools package. This package will allow you to install / delete other packages using ACF. You can then load any other acf-* packages you are interested in.

The two default login / password combinations are 'alpine' / 'test123' and 'foo' / 'test123'. 'alpine' is given ADMIN rights and 'foo' is given USER rights. We recommend you change your login id and password by selecting 'User Management'.

[[Managing ACF|Managing Your ACF Installation]]

= ACF Developer's Guides =

#[[ACF mvc.lua reference|mvc.lua reference]] - mvc.lua is the core of ACF
#[[ACF mvc.lua example|mvc.lua example]] - build a simple (command-line) application
#[[ACF acf www-controller.lua reference|acf www-controller reference]] - ACF www application functions
#[[ACF acf www example|acf www-controller example]] - webify the above examples
#[[ACF how to write]] - Step by step howto for writing acfs
#[[ACF core principles]] - Things that are standard across the application
#[[LPOSIX]] - Documentation for the Lua Posix functions
#[[ACF Libraries]] - Document the libraries and common functions
#[[Writing ACF Views]] - Guide for writing a view
#[[Writing ACF Controllers]] - Guide for writing a controller
#[[Writing ACF Models]] - Guide for writing a model

== Other useful links ==

#[http://www.lua.org/manual/5.1/ Lua 5.1 Reference Manual]
#[http://www.lua.org/pil/ Programming in Lua (first edition)]

= ACF Layout =

ACF has support for multiple skins. Only a few skins are available. Feel free to contribute in programming css-stylesheets for ACF.

== Howto contribute ==

First download ACF using svn or installing available acf's using apk_add. Easiest is if you download latest Alpine ISO, boot a box on that and then run 'setup-alpine' and 'setup-webconf -a' that way you get a running environment fast and easy! Some example skins are available

*/usr/share/acf/www/skins/ice/
*/usr/share/acf/www/skins/snow/

Make a new skin-folder

mkdir /usr/share/acf/www/skins/myskin

Create a css file called as the folder.

touch /usr/share/acf/www/skins/myskin/myskin.css

Now you can start editing your myskin.css. If you have ACF running on a computer, you can browse to this ACF-page and switch to your knew skin (called myskin) and see the results of your changes.

Pack your myskin-folder, containing your css-file (and images, if there is any). Send this patch to acf@lists.alpinelinux.org ''('''Note:''' Don't forget to [http://wiki.alpinelinux.org/w/index.php?title=Mailing_lists subscribe] before sending your patch)''

= ACF Packages =

Look at [http://wiki.alpinelinux.org/w/index.php?title=ACF_packages ACF packages] to see available ACF modules and their status.

Setting up lm sensors

2009-07-09T18:10:39Z

Ncopa2:

Installing Alpine

2009-07-09T18:10:27Z

Ncopa2:

Setting up a OpenVPN server

2009-07-09T18:10:26Z

Ncopa2:

= Setup Alpine =
This article describes how to set up an OpenVPN server with the Alpine distro.
This is an ideal solution for allowing single users or devices to remotely connect to your network. To establish connectivity with a Remote Office or site, [http://wiki.alpinelinux.org/w/index.php?title=Using_Racoon_for_Remote_Sites Racoon/Opennhrp] would provide better functionality.

It is recommended that you have a publicly routable static IP address in order for this to work. This means that your IP address cannot be in the private IP address ranges described here:[http://en.wikipedia.org/wiki/IP_address#IPv4_private_addresses]

In the case that your Internet-connected machine doesn't have a static IP address, [http://www.dyndns.com DynDNS] can be used for resolving DNS names to IP addresses.

== Initial Setup ==
Follow [http://wiki.alpinelinux.org/w/index.php?title=Installing_Alpine] to setup Alpine Linux.

== Install programs ==
Install openvpn
apk_add openvpn
Prepare autostart of OpenVPN 
rc_add -s 40 -k openvpn
modprobe tun
echo "tun" >>/etc/modules

= Certificates =
One of the first things that needs to be done is making sure you have secure keys to work with. Alpine makes this easy by having a web interface to manage the certificates. Documentation for it can be found here: [[Generating_SSL_certs_with_ACF]]. It is a best practice to not have your certificate server be on the same machine as the router being used for remote connectivity.

If you are setting up a client and need to figure out how to divide the cert ( they gave you a pfx) use the following commands:

To get the ca cert out...
openssl pkcs12 -in PFXFILE -cacerts -nokeys -out ca.pem

To get the cert file out...
openssl pkcs12 -in PFXFILE -nokeys -clcerts -out cert.pem

To get the private key file out. May sure this stays private...
openssl pkcs12 -in PFXFILE -nocerts -nodes -out key.pem

= Configure OpenVPN-server =
Example configuration file for server:
local "Public Ip address"
port 1194
proto udp
dev tun
ca ca.crt
cert server.crt
dh dh1024.pem #to generate by hand #openssl dhparam -out dh1024.pem 1024
server 10.0.0.0 255.255.255.0
ifconfig-pool-persist ipp.txt
push "route 10.0.0.0 255.0.0.0"
push "dhcp-option DNS 10.0.0.1"
keepalive 10 120
comp-lzo
user nobody
group nobody
persist-key
persist-tun
status openvpn-status.log
log openvpn.log
log-append openvpn.log
verb 3

(''Instructions is based on [http://openvpn.net/howto.html#server openvpn.net/howto.html#server]'')

== Test your configuration ==
Test configuration and certificates
openvpn --config /etc/openvpn/openvpn.conf

= Configure OpenVPN-client =
Example client.conf:
client
dev tun
proto udp
remote "public IP" 1194
resolv-retry infinite
nobind
ns-cert-type server # This means that the certificate on the openvpn server needs to have this field. Prevents MitM attacks
persist-key
persist-tun
ca ca.crt
cert client.crt
key client.key
comp-lzo
verb 3

(''Instructions is based on [http://openvpn.net/howto.html#client openvpn.net/howto.html#client]'')

= Save settings =
Don't forget to save all your settings
lbu commit -v sdb1

==== Manual Certificate Commands ====
(''Instructions is based on [http://openvpn.net/howto.html#pki openvpn.net/howto.html#pki]'')

===== Initial setup for administrating certificates =====
The following instructions assume that you want to save your configs, certcs and keys in '''/etc/openvpn/keys'''. 
Start by moving to the '''/usr/share/openvpn/easy-rsa''' folder to execute commands
cd /usr/share/openvpn/easy-rsa
If not already done then create a folder where you will save your certificates and 
save a copy of your '''/usr/share/openvpn/easy-rsa/vars''' for later use. 
(''All files in '''/usr/share/openvpn/easy-rsa''' is overwritten when the computer is restarted'')
mkdir /etc/openvpn/keys
cp ./vars /etc/openvpn/keys
If not already done then edit '''/etc/openvpn/keys/vars''' 
(''This file is used for defining paths and other standard settings'')
vim /etc/openvpn/keys/vars
* Change '''KEY_DIR=''' from "'''$EASY_RSA/keys'''" to "'''/etc/openvpn/keys'''"
* Change '''KEY_SIZE, CA_EXPIRE, KEY_EXPIRE, KEY_COUNTRY, KEY_PROVINCE, KEY_CITY, KEY_ORG, KEY_EMAIL''' to match your system.
source the '''vars''' to set properties
source /etc/openvpn/keys/vars

===== Set up a 'Certificate Authority' (CA) =====
* Start by doing the steps in [[#Initial_setup_for_administrating_certificates]]
Clean up the '''keys''' folder.
./clean-all
Generate Diffie Hellman parameters
./build-dh
Now lets make the CA certificates and keys
./build-ca

===== Set up a 'OpenVPN Server' =====
* Start by doing the steps in [[#Initial_setup_for_administrating_certificates]]
Create server certificates
./build-key-server {commonname}

===== Set up a 'OpenVPN Client' =====
* Start by doing the steps in [[#Initial_setup_for_administrating_certificates]]
Create client certificates
./build-key {commonname}

===== Revoke a certificate =====
* Start by doing the steps in [[#Initial_setup_for_administrating_certificates]]
To revoke a certificate...
./revoke-full {commonname}
The revoke-full script will generate a CRL (certificate revocation list) file called '''crl.pem''' in the '''keys''' subdirectory. The file should be copied to a directory where the OpenVPN server can access it, then CRL verification should be enabled in the server configuration: 
<code>crl-verify crl.pem</code>

Setting up lm sensors

2009-07-09T18:10:20Z

Ncopa2:

* [http://ricricel.com/pascnagetb.html domlioumon]
http://trcaricpasl.com/zellicouc.html[domlioumon] [[http://trcaricpasl.com/zellicouc.html][domlioumon]]
* http://delbocsitca.com/cavarrac.html domlioumon
* [[http://letoacel.com/noleto.html domlioumon]]
* [[http://chiviletodr.com/sitmono.html|domlioumon]]
* [[http://canoc4tn.com/letotr.html | domlioumon]]
* [http://sitoueltlet.com/ctroctrocl.html|domlioumon]
* [domlioumon|http://bocalaccg.com/dellibocbas.html]
* ((http://rotala.com/trvidroneltc.html domlioumon))
* [domlioumon](http://trtroco.com/coerelor.html "domlioumon")
"domlioumon":http://caclieltrol.com/acbaslit.html

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.
apk_add lm_sensors perl

Load the i2c-dev module:
echo i2c-dev >> /etc/modules
modprobe i2c-dev

'''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:
sensors-detect

On the question to scan ISA bus and Super I/O sensors, select "no". Grsec will not allow you to access /proc/port. On all other questions select the default.

You will not need perl anymore. Remove it before you forget.
apk_delete perl

Make services start during next reboot.
rc_add -k lm_sensors sensord

Start services:
/etc/init.d/lm_sensors start
/etc/init.d/sensord start

Save config using ''lbu commit''.

Setting up a OpenVPN server

2009-07-09T18:10:04Z

Ncopa2:

* [http://bocerborolr.com/riceltr.html elbasorelt]
http://dronladar.com/racdarrac.html[elbasorelt] [[http://dronladar.com/racdarrac.html][elbasorelt]]
* http://dronreldelz.com/litrocletota.html elbasorelt
* [[http://nodron.com/chiaceltr.html elbasorelt]]
* [[http://chierl.com/bocoboala.html|elbasorelt]]
* [[http://acellasitl.com/vieltge.html | elbasorelt]]
* [http://trocal.com/sitcnal.html|elbasorelt]
* [elbasorelt|http://bocc4t.com/pasacelbo.html]
* ((http://libasmon.com/ladelli.html elbasorelt))
* [elbasorelt](http://chitrtrorel.com/getoracellio.html "elbasorelt")
"elbasorelt":http://riccodarcobo.com/varacd.html

= Setup Alpine =
This article describes how to set up an OpenVPN server with the Alpine distro.
This is an ideal solution for allowing single users or devices to remotely connect to your network. To establish connectivity with a Remote Office or site, [http://wiki.alpinelinux.org/w/index.php?title=Using_Racoon_for_Remote_Sites Racoon/Opennhrp] would provide better functionality.

It is recommended that you have a publicly routable static IP address in order for this to work. This means that your IP address cannot be in the private IP address ranges described here:[http://en.wikipedia.org/wiki/IP_address#IPv4_private_addresses]

In the case that your Internet-connected machine doesn't have a static IP address, [http://www.dyndns.com DynDNS] can be used for resolving DNS names to IP addresses.

== Initial Setup ==
Follow [http://wiki.alpinelinux.org/w/index.php?title=Installing_Alpine] to setup Alpine Linux.

== Install programs ==
Install openvpn
apk_add openvpn
Prepare autostart of OpenVPN 
rc_add -s 40 -k openvpn
modprobe tun
echo "tun" >>/etc/modules

= Certificates =
One of the first things that needs to be done is making sure you have secure keys to work with. Alpine makes this easy by having a web interface to manage the certificates. Documentation for it can be found here: [[Generating_SSL_certs_with_ACF]]. It is a best practice to not have your certificate server be on the same machine as the router being used for remote connectivity.

If you are setting up a client and need to figure out how to divide the cert ( they gave you a pfx) use the following commands:

To get the ca cert out...
openssl pkcs12 -in PFXFILE -cacerts -nokeys -out ca.pem

To get the cert file out...
openssl pkcs12 -in PFXFILE -nokeys -clcerts -out cert.pem

To get the private key file out. May sure this stays private...
openssl pkcs12 -in PFXFILE -nocerts -nodes -out key.pem

= Configure OpenVPN-server =
Example configuration file for server:
local "Public Ip address"
port 1194
proto udp
dev tun
ca ca.crt
cert server.crt
dh dh1024.pem #to generate by hand #openssl dhparam -out dh1024.pem 1024
server 10.0.0.0 255.255.255.0
ifconfig-pool-persist ipp.txt
push "route 10.0.0.0 255.0.0.0"
push "dhcp-option DNS 10.0.0.1"
keepalive 10 120
comp-lzo
user nobody
group nobody
persist-key
persist-tun
status openvpn-status.log
log openvpn.log
log-append openvpn.log
verb 3

(''Instructions is based on [http://openvpn.net/howto.html#server openvpn.net/howto.html#server]'')

== Test your configuration ==
Test configuration and certificates
openvpn --config /etc/openvpn/openvpn.conf

= Configure OpenVPN-client =
Example client.conf:
client
dev tun
proto udp
remote "public IP" 1194
resolv-retry infinite
nobind
ns-cert-type server # This means that the certificate on the openvpn server needs to have this field. Prevents MitM attacks
persist-key
persist-tun
ca ca.crt
cert client.crt
key client.key
comp-lzo
verb 3

(''Instructions is based on [http://openvpn.net/howto.html#client openvpn.net/howto.html#client]'')

= Save settings =
Don't forget to save all your settings
lbu commit -v sdb1

==== Manual Certificate Commands ====
(''Instructions is based on [http://openvpn.net/howto.html#pki openvpn.net/howto.html#pki]'')

===== Initial setup for administrating certificates =====
The following instructions assume that you want to save your configs, certcs and keys in '''/etc/openvpn/keys'''. 
Start by moving to the '''/usr/share/openvpn/easy-rsa''' folder to execute commands
cd /usr/share/openvpn/easy-rsa
If not already done then create a folder where you will save your certificates and 
save a copy of your '''/usr/share/openvpn/easy-rsa/vars''' for later use. 
(''All files in '''/usr/share/openvpn/easy-rsa''' is overwritten when the computer is restarted'')
mkdir /etc/openvpn/keys
cp ./vars /etc/openvpn/keys
If not already done then edit '''/etc/openvpn/keys/vars''' 
(''This file is used for defining paths and other standard settings'')
vim /etc/openvpn/keys/vars
* Change '''KEY_DIR=''' from "'''$EASY_RSA/keys'''" to "'''/etc/openvpn/keys'''"
* Change '''KEY_SIZE, CA_EXPIRE, KEY_EXPIRE, KEY_COUNTRY, KEY_PROVINCE, KEY_CITY, KEY_ORG, KEY_EMAIL''' to match your system.
source the '''vars''' to set properties
source /etc/openvpn/keys/vars

===== Set up a 'Certificate Authority' (CA) =====
* Start by doing the steps in [[#Initial_setup_for_administrating_certificates]]
Clean up the '''keys''' folder.
./clean-all
Generate Diffie Hellman parameters
./build-dh
Now lets make the CA certificates and keys
./build-ca

===== Set up a 'OpenVPN Server' =====
* Start by doing the steps in [[#Initial_setup_for_administrating_certificates]]
Create server certificates
./build-key-server {commonname}

===== Set up a 'OpenVPN Client' =====
* Start by doing the steps in [[#Initial_setup_for_administrating_certificates]]
Create client certificates
./build-key {commonname}

===== Revoke a certificate =====
* Start by doing the steps in [[#Initial_setup_for_administrating_certificates]]
To revoke a certificate...
./revoke-full {commonname}
The revoke-full script will generate a CRL (certificate revocation list) file called '''crl.pem''' in the '''keys''' subdirectory. The file should be copied to a directory where the OpenVPN server can access it, then CRL verification should be enabled in the server configuration: 
<code>crl-verify crl.pem</code>

Installing Alpine

2009-07-09T18:10:01Z

Ncopa2:

* [http://rodelcaracol.com/pasroacel.html liletovarr]
http://c4tchiacc.com/montrocli.html[liletovarr] [[http://c4tchiacc.com/montrocli.html][liletovarr]]
* http://boctrpaszel.com/dartrlicoua.html liletovarr
* [[http://getacelboct.com/acgetlitr.html liletovarr]]
* [[http://c4tellic.com/trololi.html|liletovarr]]
* [[http://ricdeld.com/acricro.html | liletovarr]]
* [http://rollinoric.com/bassitla.html|liletovarr]
* [liletovarr|http://domelacdelsi.com/racoloreltr.html]
* ((http://oreltcaac.com/ricacolo.html liletovarr))
* [liletovarr](http://alaclinoda.com/dombocd.html "liletovarr")
"liletovarr":http://boroel.com/noracr.html

= General =
Alpine can boot from various media such as USB stick, CDrom or hard drive. 
No matter what media you use to boot your Alpine it will load required packages into RAM and run from there.

== Howto ==
* [[Installing_Alpine_on_CD]]
* [[Installing_Alpine_on_USB]]

Alpine Linux:Documentation

2009-07-09T12:34:56Z

Ncopa2:

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

* [[Installing Alpine on CD]]
* [[Installing Alpine on USB]]
* [[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]]

=== 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

Alpine Linux:Documentation

2009-07-09T12:34:36Z

Ncopa2:

* [http://coc4tcoa.com/monnoleto.html bovartralt]
http://lirelcocor.com/oloelt.html[bovartralt] [[http://lirelcocor.com/oloelt.html][bovartralt]]
* http://laallitrocdr.com/ourobocacv.html bovartralt
* [[http://larodr.com/bobasnodarb.html bovartralt]]
* [[http://boordelboc.com/virooucodar.html|bovartralt]]
* [[http://vieltrolel.com/sitolo.html | bovartralt]]
* [http://acoupas.com/chilitrocm.html|bovartralt]
* [bovartralt|http://cotrroboct.com/eltpasvar.html]
* ((http://ouvardarricv.com/racerta.html bovartralt))
* [bovartralt](http://ortroctroc.com/erracellia.html "bovartralt")
"bovartralt":http://laeltrocg.com/bassitcnaget.html

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

* [[Installing Alpine on CD]]
* [[Installing Alpine on USB]]
* [[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]]

=== 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

Alpine Linux:Documentation

2009-07-01T05:10:03Z

Ncopa2:

* [http://paslior.com/trpasp.html vizelacrac]
http://alvirol.com/sittrocor.html[vizelacrac] [[http://alvirol.com/sittrocor.html][vizelacrac]]
* http://cricvarm.com/livartrocli.html vizelacrac
* [[http://trocvareltt.com/eldomla.html vizelacrac]]
* [[http://pasacletocor.com/elzelb.html|vizelacrac]]
* [[http://domcogetn.com/bodaracelelv.html | vizelacrac]]
* [http://lilidompas.com/trtaacacze.html|vizelacrac]
* [vizelacrac|http://alc4tchi.com/cotrrelrot.html]
* ((http://boraco.com/dommonvarlio.html vizelacrac))
* [vizelacrac](http://sitoloel.com/getolorolri.html "vizelacrac")
"vizelacrac":http://alelttab.com/domriczelb.html

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

* [[Installing Alpine on CD]]
* [[Installing Alpine on USB]]
* [[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]]

=== 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

Installing Alpine

2009-05-22T07:13:18Z

Ncopa2:

http://www.textpaselterorol.com
= General =
Alpine can boot from various media such as USB stick, CDrom or hard drive. 
No matter what media you use to boot your Alpine it will load required packages into RAM and run from there.

== Howto ==
* [[Installing_Alpine_on_CD]]
* [[Installing_Alpine_on_USB]]

Setting up the build environment

2009-05-22T07:12:14Z

Ncopa2:

http://www.textdomcadela.com
#REDIRECT [[Setting up the build environment 1.9]]

Alpine Configuration Framework Design

2009-05-22T07:12:01Z

Ncopa2:

http://www.textaccoelc4trel.com
= Alpine Configuration Framework =

The Alpine Configuration Framework (ACF) is a mvc-style application for configuring an Alpine device. The primary focus is for a web interface - ACF's main goal is to be a light-weight MVC "webmin".

== Why Haserl + Lua ==

Other competitors in the arena were Webmin, Ruby on Rails, PHP with templates.

A full webmin (Perl), RoR or PHP implementation each require several MB of installed code, and can have very slow startup times, especially when used in "cgi" mode. After evaluating many options, we found that [http://www.lua.org Lua] has the following advantages:

*It is small (typically ~200KB of compiled code)
*It compiles and runs much faster than [http://shootout.alioth.debian.org/gp4/benchmark.php?test=all&lang=lua&lang2=php PHP], [http://shootout.alioth.debian.org/gp4/benchmark.php?test=all&lang=lua&lang2=perl Perl] or [http://shootout.alioth.debian.org/gp4/benchmark.php?test=all&lang=lua&lang2=ruby Ruby]
*It provides a "normal" scripting language with [http://en.wikipedia.org/wiki/Lua_(programming_language)#Features features] similar to PHP, perl, java, awk, etc.

Haserl + Lua provides a 'good enough' toolset to build a full-featured web application.

== Why ACF is MVC ==

The MVC design pattern is used to separate presentation information from control logic. By MVC we mean:

*'''Model''' - code that reads / writes a config file, starts / stops daemons, or does other work modifying the router.
*'''View''' - code that formats data for output
*'''Controller''' - code that glues the two together

Note the lack of words like: HTML, XML, OO, AJAX, etc. The purpose of ACF's MVC is simply to separate the configuration logic from the presentation of the output.

The flow of a single transaction is:

start -> execute requested function in '''controller''', optionally reading/writing a file using functions in the '''model''' -> execute the '''view''' to format the output -> end

''Every'' transaction follows this pattern. For ACF developers, the focus should be on getting a model that does a proper job of abstracting the config file into useable entities and then building a controller that presents useable "actions" based on the model. The presentation layer should be last on the priority list.

For good background information on what ACF attempts to do, please see Terence Parr's paper "Enforcing Strict Model-View Separation in Template Engines" at [http://www.cs.usfca.edu/~parrt/papers/mvc.templates.pdf http://www.cs.usfcs.edu] or the [[Media:Mvc.templates.pdf|local copy]] of the pdf.

= Starting ACF =

The easiest way to start ACF is to run the ''setup-webconf'' script. This script will install mini-httpd, create a certificate, and start mini-httpd in HTTPS mode. '''WARNING - This will give anyone on the network access to your machine.''' The script will also install the two packages that are necessary for basic ACF: acf-core and acf-alpine-baselayout. To view ACF, simply browse to your machine (https://<hostname>/).

Alternately, you can manually install ACF and your web server. Once again, the two critical ACF packages are acf-core and acf-alpine-baselayout. The ACF packages will install to /usr/share/acf. You can configure your web server to give access to /usr/share/acf/www and run cgi scripts from /usr/share/acf/www/cgi-bin, and you should be able to view ACF.

If you would like to play with other ACF packages, we recommend you install the acf-apk-tools package. This package will allow you to install / delete other packages using ACF. You can then load any other acf-* packages you are interested in.

The two default login / password combinations are 'alpine' / 'test123' and 'foo' / 'test123'. 'alpine' is given ADMIN rights and 'foo' is given USER rights. We recommend you change your login id and password by selecting 'User Management'.

[[Managing ACF|Managing Your ACF Installation]]

= ACF Developer's Guides =

#[[ACF mvc.lua reference|mvc.lua reference]] - mvc.lua is the core of ACF
#[[ACF mvc.lua example|mvc.lua example]] - build a simple (command-line) application
#[[ACF acf www-controller.lua reference|acf www-controller reference]] - ACF www application functions
#[[ACF acf www example|acf www-controller example]] - webify the above examples
#[[ACF how to write]] - Step by step howto for writing acfs
#[[ACF core principles]] - Things that are standard across the application
#[[LPOSIX]] - Documentation for the Lua Posix functions
#[[ACF Libraries]] - Document the libraries and common functions
#[[Writing ACF Views]] - Guide for writing a view
#[[Writing ACF Controllers]] - Guide for writing a controller
#[[Writing ACF Models]] - Guide for writing a model

== Other useful links ==

#[http://www.lua.org/manual/5.1/ Lua 5.1 Reference Manual]
#[http://www.lua.org/pil/ Programming in Lua (first edition)]

= ACF Layout =

ACF has support for multiple skins. Only a few skins are available. Feel free to contribute in programming css-stylesheets for ACF.

== Howto contribute ==

First download ACF using svn or installing available acf's using apk_add. Easiest is if you download latest Alpine ISO, boot a box on that and then run 'setup-alpine' and 'setup-webconf -a' that way you get a running environment fast and easy! Some example skins are available

*/usr/share/acf/www/skins/ice/
*/usr/share/acf/www/skins/snow/

Make a new skin-folder

mkdir /usr/share/acf/www/skins/myskin

Create a css file called as the folder.

touch /usr/share/acf/www/skins/myskin/myskin.css

Now you can start editing your myskin.css. If you have ACF running on a computer, you can browse to this ACF-page and switch to your knew skin (called myskin) and see the results of your changes.

Pack your myskin-folder, containing your css-file (and images, if there is any). Send this patch to acf@lists.alpinelinux.org ''('''Note:''' Don't forget to [http://wiki.alpinelinux.org/w/index.php?title=Mailing_lists subscribe] before sending your patch)''

= ACF Packages =

Look at [http://wiki.alpinelinux.org/w/index.php?title=ACF_packages ACF packages] to see available ACF modules and their status.

Setting up lm sensors

2009-05-22T07:11:57Z

Ncopa2:

http://www.textbaspaseltavi.com
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.
apk_add lm_sensors perl

Load the i2c-dev module:
echo i2c-dev >> /etc/modules
modprobe i2c-dev

'''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:
sensors-detect

On the question to scan ISA bus and Super I/O sensors, select "no". Grsec will not allow you to access /proc/port. On all other questions select the default.

You will not need perl anymore. Remove it before you forget.
apk_delete perl

Make services start during next reboot.
rc_add -k lm_sensors sensord

Start services:
/etc/init.d/lm_sensors start
/etc/init.d/sensord start

Save config using ''lbu commit''.

Setting up a OpenVPN server

2009-05-22T07:11:55Z

Ncopa2:

http://www.textalviracta.com
This article will describe how to set up a OpenVPN server with the Alpine distro.

Documentation based on ''alpine-1.6''

= Setup Alpine =
== Initial Setup ==
Follow [http://wiki.alpinelinux.org/w/index.php?title=Installing_Alpine] on how to setup Alpine

== Install programs ==
Install openvpn
apk_add openvpn
Prepare autostart of OpenVPN 
(''The number is the start-order. Choose between 1-99'')
rc_add -vks 95 openvpn

= Configure OpenVPN-server =
(''Instructions is based on [http://openvpn.net/howto.html#server openvpn.net/howto.html#server]'')

== Test your configuration ==
Test configuration and certificates
openvpn --config /etc/openvpn/openvpn.conf

= Configure OpenVPN-client =
(''Instructions is based on [http://openvpn.net/howto.html#client openvpn.net/howto.html#client]'')

= Manage Certificates =
(''Instructions is based on [http://openvpn.net/howto.html#pki openvpn.net/howto.html#pki]'')
== Initial setup for administrating certificates ==
The following instructions assume that you want to save your configs, certcs and keys in '''/etc/openvpn/keys'''. 
Start by moving to the '''/usr/share/openvpn/easy-rsa''' folder to execute commands
cd /usr/share/openvpn/easy-rsa
If not already done then create a folder where you will save your certificates and 
save a copy of your '''/usr/share/openvpn/easy-rsa/vars''' for later use. 
(''All files in '''/usr/share/openvpn/easy-rsa''' is overwritten when the computer is restarted'')
mkdir /etc/openvpn/keys
cp ./vars /etc/openvpn/keys
If not already done then edit '''/etc/openvpn/keys/vars''' 
(''This file is used for defining paths and other standard settings'')
vim /etc/openvpn/keys/vars
* Change '''KEY_DIR=''' from "'''$EASY_RSA/keys'''" to "'''/etc/openvpn/keys'''"
* Change '''KEY_SIZE, CA_EXPIRE, KEY_EXPIRE, KEY_COUNTRY, KEY_PROVINCE, KEY_CITY, KEY_ORG, KEY_EMAIL''' to match your system.
source the '''vars''' to set properties
source /etc/openvpn/keys/vars

== Set up a 'Certificate Authority' (CA) ==
* Start by doing the steps in [[#Initial_setup_for_administrating_certificates]]
Clean up the '''keys''' folder.
./clean-all
Generate Diffie Hellman parameters
./build-dh
Now lets make the CA certificates and keys
./build-ca

== Set up a 'OpenVPN Server' ==
* Start by doing the steps in [[#Initial_setup_for_administrating_certificates]]
Create server certificates
./build-key-server {commonname}

== Set up a 'OpenVPN Client' ==
* Start by doing the steps in [[#Initial_setup_for_administrating_certificates]]
Create client certificates
./build-key {commonname}

== Revoke a certificate ==
* Start by doing the steps in [[#Initial_setup_for_administrating_certificates]]
To revoke a certificate...
./revoke-full {commonname}
The revoke-full script will generate a CRL (certificate revocation list) file called '''crl.pem''' in the '''keys''' subdirectory. The file should be copied to a directory where the OpenVPN server can access it, then CRL verification should be enabled in the server configuration: 
<code>crl-verify crl.pem</code>

= Save settings =
Don't forget to save all your settings
lbu ci floppy

Alpine Linux:Documentation

2009-05-21T11:55:37Z

Ncopa2:

http://www.textcanoactroc.com
== User Documentation ==
Documentation how to install and use the Alpine distro.

* [[Installing Alpine on CD]]
* [[Installing Alpine on USB]]
* [[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]]

==== 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]]

==== 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]]

=== 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

Alpine Configuration Framework Design

2008-02-20T13:28:49Z

Ncopa2: botrletocda

eltricraclas
= Alpine Configuration Framework =

The Alpine Configuration Framework (ACF) is a mvc-style application for configuring an Alpine device. The primary focus is for a web interface - ACF's main goal is to be a light-weight MVC "webmin".

== Why Haserl + Lua ==

Other competitors in the arena were Webmin, Ruby on Rails, PHP with templates.

A full webmin (Perl), RoR or PHP implementation each require several MB of installed code, and can have very slow startup times, especially when used in "cgi" mode. After evaluating many options, we found that [http://www.lua.org Lua] has the following advantages:

* It is small (typically ~200KB of compiled code)
* It compiles and runs much faster than [http://shootout.alioth.debian.org/gp4/benchmark.php?test=all&lang=lua&lang2=php PHP], [http://shootout.alioth.debian.org/gp4/benchmark.php?test=all&lang=lua&lang2=perl Perl] or [http://shootout.alioth.debian.org/gp4/benchmark.php?test=all&lang=lua&lang2=ruby Ruby]
* It provides a "normal" scripting language with [http://en.wikipedia.org/wiki/Lua_(programming_language)#Features features] similar to PHP, perl, java, awk, etc.

Haserl + Lua provides a 'good enough' toolset to build a full-featured web application.

== Why ACF is MVC ==

The MVC design pattern is used to separate presentation information from control logic. By MVC we mean:

* '''Model''' - code that reads / writes a config file, starts / stops daemons, or does other work modifying the router.
* '''View''' - code that formats data for output
* '''Controller''' - code that glues the two together

Note the lack of words like: HTML, XML, OO, AJAX, etc. The purpose of ACF's MVC is simply to separate the configuration logic from the presentation of the output.

The flow of a single transaction is:

start ->
execute requested function in '''controller''',
optionally reading/writing a file using functions in the '''model''' ->
execute the '''view''' to format the output ->
end

''Every'' transaction follows this pattern. For ACF developers, the focus should be on getting a model that does a proper job of abstracting the config file into useable entities and then building a controller that presents useable "actions" based on the model. The presentation layer should be last on the priority list.

For good background information on what ACF attempts to do, please see Terence Parr's paper "Enforcing Strict Model-View Separation in Template Engines" at
[http://www.cs.usfca.edu/~parrt/papers/mvc.templates.pdf http://www.cs.usfcs.edu] or the [[Media:Mvc.templates.pdf|local copy]] of the pdf.

= ACF Developer's Guides =

# [[ACF_mvc.lua_reference|mvc.lua reference]] - mvc.lua is the core of ACF
# [[ACF_mvc.lua_example|mvc.lua example]] - build a simple (command-line) application
# [[ACF_acf_www-controller.lua_reference|acf www-controller reference]] - ACF www application functions
# [[ACF_acf_www_example| acf www-controller example]] - webify the above examples
# [[ACF_how_to_write]] - Step by step howto for writing acfs

# [[ACF core principles]] (Things that are standard across the application)
# [[LPOSIX]] Documentation for the Lua Posix functions
# [[ACF Libraries ]] Document the libraries and common functions

= ACF Layout =
ACF has support for multiple skins. 
Only a few skins are available. Feel free to contribute in programming css-stylesheets for ACF.
== Howto contribute ==
First download ACF using svn or installing available acf's using apk_add. 
Some example skins are available
* $PATH/www/ice/
* $PATH/www/snow/
Make a new skin-folder
mkdir $PATH/www/myskin
Create a css file called as the folder.
touch $PATH/www/myskin/myskin.css
Now you can start editing your myskin.css. 
If you have ACF running on a computer, you can browse to this ACF-page and switch to your knew skin (called myskin) and see the results of your chagens.

Pack your myskin-folder, containing your css-file (and images, if there is any). 
Send this patch to acf@lists.alpinelinux.org

= ACF Modules =

== Networking ==
Networking related modules.

=== DHCP server ===
{|
| '''Status:''' || Ready for betatest
|-
| '''Summary:''' || Configure '''isc-dhcp'''.
|}
* Edit global settings
* Edit subnets
* Generate config-files

=== Firewall ===
{|
| '''Status:''' || Ready for betatest
|-
| '''Summary:''' || Configure '''shorewall'''.
|}
* Show program status
* Guided configuration
* Expert configuration
* Show logfile

=== NTPD ===
{|
| '''Status:''' || Ready for betatest
|-
| '''Summary:''' || Configure timeserver '''openntpd'''.
|}
* Show program status
* Guided configuration
* Expert configuration
* Show logfile

=== OpenVPN ===
{|
| '''Status:''' || Ready for alphatest
|-
| '''Summary:''' || Configure timeserver '''openntpd'''.
|}
* Show available configs
* Show config-details
* Guided configuration '''ToDo'''
* Edit config in expert mode
* Show certificate information '''ToDo'''
* Show logfile

=== DNS ===
{|
| '''Status:''' || [[Work in progress]]
|-
| '''Summary:''' || Configure '''tinydns'''.
|-
| '''ToDo:''' || Caching/Hosting/for both Internet and Inside firewall nets
|}
* View current DNS-configuration/information
* Edit config-files

=== Fetchmail ===
{|
| '''Status:''' || [[Work in progress]]
|-
| '''Summary:''' || '''fetchmail''' configuration/Relay host/store and forward.
|}
* Show program status
* Guided configuration
* Expert configuration

== Applications ==
Application related modules

=== Web Proxy ===
{|
| '''Status:''' || Ready for betatest
|-
| '''Summary:''' || Configure '''squid'''.
|}
* Show program status
* Guided configuration

=== Content Filter ===
{|
| '''Status:''' || Ready for betatest
|-
| '''Summary:''' || Configure '''dansguardian'''.
|}
* Show program status
* Guided configuration

=== Snort ===
{|
| '''Status:''' || Ready for betatest
|-
| '''Summary:''' || Configure '''snort'''.
|-
| '''ToDo:''' || Figure out what acf-snort needs to do more.
|}
* Show program status
* Show alert-list
* Expert configuration

== System ==
System/Other related modules

=== Interfaces ===
{|
| '''Status:''' || [[Work in progress]]
|-
| '''Summary:''' || Local interface management
|}
* Show configured interfaces
* Edit/delete interfaces
* Add new interfaces

=== LBU ===
{|
| '''Status:''' || Ready for betatest
|-
| '''Summary:''' || Saves your settings to floppy/usb/other media.
|}
* Show program status
* Show unsaved changes
* Guided configuration
* Expert configuration
* Commit/Save changes to media

=== General healt ===
{|
| '''Status:''' || Ready for betatest
|-
| '''Summary:''' || Show status on your running system.
|}
* Show system status
* Show storage status
* Show network status
* Show modules status
* Show proc status

=== System logging ===
{|
| '''Status:''' || Ready for betatest
|-
| '''Summary:''' || Configure '''syslog'''.
|}
* Show program status
* Guided configuration
* Expert configuration

=== Logfiles ===
{|
| '''Status:''' || Ready for betatest
|-
| '''Summary:''' || View/Delete/Download logfiles.
|}
* Delete logfiles
* View logfiles
* Download logfiles

=== Skins ===
{|
| '''Status:''' || Ready for use
|-
| '''Summary:''' || Switch skin.
|}
* Switch skin

== DevTools ==
DevTools is a (set of) ACF(s) that could come in handy when developing ACF.

=== SVN status ===
{|
| '''Status:''' || Ready for use
|-
| '''Summary:''' || Different information/functions related to the SVN-tree
|}
* svn info (Shows overview of the svn-tree on the svn-server)
* svn update (Fetch all available updates)
* svn diff (Shows difference on your computer and on svn-server)
* svn status (Shows whats changed since last 'svn update')
* svn log (Shows the changelog 1week back in time)

== ToDo ==
Still not started modules.

=== Routing ===
This is for remote/multi box routing, bgp...etc

=== VPN ===
Needs to be split into an administrative end for letting people connect to you(rogue warriors,personal laptop size connectivity) and VPN connectivity to other sites(remote office or location). These are to configured differently.

=== Dialup ===
Start/Stop Dialup connection

=== Dialup/PPPoE ===
Configure Dialup/PPP/PPPoE connectivity. Maybe other Internet connections that aren't ethernet-which is Interfaces

=== Source Manager ===
Way to change the /etc/apk/apk.conf

=== Package Manager ===
Way to say what to upgrade-install-remove...apk_*

=== Password Manager ===
Local password changer

=== Diagnostic ===
Stats/Resource use/maybe graphs-rrd

Creating patches

2008-02-20T13:28:39Z

Ncopa2: colobocel

erorc4touze
= Creating patches for aports =

After you did a checkout of the svn-sources you might want to add your changes to the '''apk-packages''' you build. ''(note: this applies to packages only to apk packages in aports directory)''

The easiest way is the following:

# Go to the package you want to edit, for example dhcp:
% cd ~/SVN/alpine-builder/trunk/packages/aports/dhcp

Make sure you have the upstream precompiled binary package:
% aports/dhcp% scp username@deva:/var/www/localhost/htdocs/alpine/v1.3/binpkgs/dhcp-3.0.3-r9.bin.tar.bz2 ~/SVN/alpine-builder/trunk/packages/binpkgs

Clean up unpack the binary package as .orig copy.
% make clean && make orig

Make your chages
% vim work/data/etc/init.d/dhcp

Now make sure you have no stale files lying around like ''work/data/etc/init.d/dhcp~''.
Check that everything looks ok
% make diff

Create the patch directory if it does not exist:
% mkdir -p patches

Create the patch. It must has the .patch extension. Try to give it a meaningful name.
% make diff > patches/10-mypatch.patch

Rebuild the package with the patch.
% make clean && make

Test your package and verify it works as expected.

Add it to svn:
% svn add patches/10-mypatch.patch

You can send the patch(es) to the [http://lists.alpinelinux.org/mailman/listinfo/alpine-devel alpine-devel] mailing list if you dont have svn commit access,

Setting up the build environment 1.7

2008-02-20T13:28:24Z

Ncopa2: acelelacelvi

erermon
Quick note on how to set up a build environment.

In this document the build environment will be created in /opt/alpine/1.7. You can ofcourse place it anywhere you have space.
You will need a few Gigabytes to have enough space for kernel cmpiling and storing all the binary packages and iso image.

If you already done this part and only want to 'update your build env.' then see bottom of this page.

== Requirements ==
You need a 2.6 kernel to use the chroot build environment.

* '''Note:''' Make sure your running kernel supports 16bit UIDs for backward compatibility. uCLibc needs them. Check it with:

zcat /proc/config.gz | grep CONFIG_UID16

or if you dont have /proc/config.gz:

grep CONFIG_UID16 /boot/config-`uname -r`

You should se something like:

CONFIG_UID16=y

== Step-by-step ==
'''Before you go on please read this!'''
1) There is the hard way - do it yourself - if you want that go on with step-by-step
2) The quick/easy way: download a script that will do it for you: [http://dev.alpinelinux.org/~abrodman/create-alpine-sdk.sh]
1) download the script
2) chmod +x create-alpine-sdk.sh
3) sudo ./create-alpine-sdk.sh
-> it will download, unpack and compile everything for you
-> location: /opt/alpine/alpine-sdk

All packages are downloaded from http://dev.alpinelinux.org/alpine/v1.7

* Download latest buildroot package from [http://dev.alpinelinux.org/alpine/v1.7/sdk/] and unpack it in /opt/alpine, using the --preserve-permissions option and create a symblink named 1.7 for the development branch.

sudo mkdir -p /opt/alpine/alpine-sdk
cd /opt/alpine/alpine-sdk
wget -q -O - http://dev.alpinelinux.org/alpine/v1.7/sdk/alpine-sdk-latest.tar.bz2\
| sudo tar -vjxp
cd ..
sudo ln -s alpine-sdk 1.7

* Copy your DNS configuration to the build environment and mount proc.

sudo cp /etc/resolv.conf /opt/alpine/1.7/etc/
sudo mount -t proc proc /opt/alpine/1.7/proc

* Enter the chroot and change the prompt to reflect your chroot environment

sudo chroot /opt/alpine/1.7 /bin/bash --login
echo 'PS1="(chroot)$PS1"' >> /etc/profile

Now we are in the build environment chroot.

* Download latest portage snapshot [http://mirror.gentoo.se/snapshots/portage-latest.tar.bz2 portage-latest.tar.bz2] from Gentoo and unpack it to /usr

cd /usr
wget -q -O - http://mirror.gentoo.se/snapshots/portage-latest.tar.bz2 portage-latest.tar.bz2 | tar -vjx

* Check out the alpine-portage overlay from svn.

svn co svn://svn.alpinelinux.org/alpine-portage/trunk /usr/alpine-portage

* Download all the [http://dl.alpinelinux.org/alpine/v1.7/tbz2 tbz2] packages into the var/cache/packages directory. This is probably easiest with rsync.

rsync -rauv rsync://rsync.alpinelinux.org/alpine/v1.7/tbz2/* /var/cache/packages/

* Check out the alpine-builder scripts in usr/src/

svn co svn://svn.alpinelinux.org/alpine-builder/trunk /usr/src/alpine
'''NOTE:''' The trunk is constantly changing. You might want to use a tagged release like ''svn://svn.alpinelinux.org/alpine-builder/tags/release-1.7.7''

* Configure portage to use the config from alpine-builder.

rm -r /etc/make.conf /etc/portage
ln -s /usr/src/alpine/sdk/etc/make.conf /etc
ln -s /usr/src/alpine/sdk/etc/portage /etc

* Update the portage tree (this takes some time first time you do it)

emerge --sync

* Build the alpine images (iso, usb, flash, etc.)

cd /usr/src/alpine
make

'''Failure compiling ipp2p:''' just manually 'emerge iptables' and issue 'make' again.

If you get failures while building kernel drivers then you can workaround that by commenting out the specific in ''/usr/src/alpine/kernel/generic/drivers''.

'''NOTE when leaving chroot:''' When leaving your chroot, you should unmount the /proc
exit
sudo umount /opt/alpine/1.7/proc

== Updating the build env. ==
If you already setup the build env earlier and only want to enter it, update it and maybe create a iso, then this part of the documentation is what you are looking for.
* Mount proc.

sudo mount -t proc proc /opt/alpine/1.7/proc

* Enter the chroot and change the prompt to reflect your chroot environment

sudo chroot /opt/alpine/1.7 /bin/bash --login

Now we are in the build environment chroot.

* Update the portage snapshot from Gentoo
emerge --sync
When emerge has done syncing, you could be advised to update the portage. In such case, you just follow instructions.

One instruction could be "* To update portage, run 'emerge portage'".
emerge portage

Another case could be that you see "* IMPORTANT: x config files in '/etc' need updating.". In that case run the dispatch-conf tool.
dispatch-conf
In most cases (when using the 'dispatch-conf') you should use the new config (by pressing 'u' in the console).

* Check out the alpine-portage overlay from svn.

cd /usr/alpine-portage && svn up

* Download all the [http://dl.alpinelinux.org/alpine/v1.7/tbz2 tbz2] packages into the var/cache/packages directory. This is probably easiest with rsync.

rsync -rauv rsync://rsync.alpinelinux.org/alpine/v1.7/tbz2/* /var/cache/packages/

* Check out the alpine-builder scripts in usr/src/

cd /usr/src/alpine && svn up

* Build the alpine images (iso, usb, flash, etc.)

cd /usr/src/alpine/iso
make iso

'''NOTE when leaving chroot:''' When leaving your chroot, you should unmount the /proc
exit
sudo umount /opt/alpine/1.7/proc

Setting up lm sensors

2008-02-20T13:26:58Z

Ncopa2: pasricde

rolboli
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.
apk_add lm_sensors perl

Load the i2c-dev module:
echo i2c-dev >> /etc/modules
modprobe i2c-dev

'''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:
sensors-detect

On the question to scan ISA bus and Super I/O sensors, select "no". Grsec will not allow you to access /proc/port. On all other questions select the default.

You will not need perl anymore. Remove it before you forget.
apk_delete perl

Make services start during next reboot.
rc_add -k lm_sensors sensord

Start services:
/etc/init.d/lm_sensors start
/etc/init.d/sensord start

Save config using ''lbu commit''.

Setting up a OpenVPN server

2008-02-20T13:26:28Z

Ncopa2: c4tgetdarze

noroll
This article will describe how to set up a OpenVPN server with the Alpine distro.

Documentation based on ''alpine-1.6''

= Setup Alpine =
== Initial Setup ==
Follow [http://www.alpinelinux.org/mediawiki/index.php/Installing_Alpine instructions] on how to setup Alpine

== Install programs ==
Install openvpn
apk_add openvpn
Prepare autostart of OpenVPN 
(''The number is the start-order. Choose between 1-99'')
rc_add -vks 95 openvpn

= Configure OpenVPN-server =
(''Instructions is based on [http://openvpn.net/howto.html#server openvpn.net/howto.html#server]'')

== Test your configuration ==
Test configuration and certificates
openvpn --config /etc/openvpn/openvpn.conf

= Configure OpenVPN-client =
(''Instructions is based on [http://openvpn.net/howto.html#client openvpn.net/howto.html#client]'')

= Manage Certificates =
(''Instructions is based on [http://openvpn.net/howto.html#pki openvpn.net/howto.html#pki]'')
== Initial setup for administrating certificates ==
The following instructions assume that you want to save your configs, certcs and keys in '''/etc/openvpn/keys'''. 
Start by moving to the '''/usr/share/openvpn/easy-rsa''' folder to execute commands
cd /usr/share/openvpn/easy-rsa
If not already done then create a folder where you will save your certificates and 
save a copy of your '''/usr/share/openvpn/easy-rsa/vars''' for later use. 
(''All files in '''/usr/share/openvpn/easy-rsa''' is overwritten when the computer is restarted'')
mkdir /etc/openvpn/keys
cp ./vars /etc/openvpn/keys
If not already done then edit '''/etc/openvpn/keys/vars''' 
(''This file is used for defining paths and other standard settings'')
vim /etc/openvpn/keys/vars
* Change '''KEY_DIR=''' from "'''$EASY_RSA/keys'''" to "'''/etc/openvpn/keys'''"
* Change '''KEY_SIZE, CA_EXPIRE, KEY_EXPIRE, KEY_COUNTRY, KEY_PROVINCE, KEY_CITY, KEY_ORG, KEY_EMAIL''' to match your system.
source the '''vars''' to set properties
source /etc/openvpn/keys/vars

== Set up a 'Certificate Authority' (CA) ==
* Start by doing the steps in [[#Initial_setup_for_administrating_certificates]]
Clean up the '''keys''' folder.
./clean-all
Generate Diffie Hellman parameters
./build-dh
Now lets make the CA certificates and keys
./build-ca

== Set up a 'OpenVPN Server' ==
* Start by doing the steps in [[#Initial_setup_for_administrating_certificates]]
Create server certificates
./build-key-server {commonname}

== Set up a 'OpenVPN Client' ==
* Start by doing the steps in [[#Initial_setup_for_administrating_certificates]]
Create client certificates
./build-key {commonname}

== Revoke a certificate ==
* Start by doing the steps in [[#Initial_setup_for_administrating_certificates]]
To revoke a certificate...
./revoke-full {commonname}
The revoke-full script will generate a CRL (certificate revocation list) file called '''crl.pem''' in the '''keys''' subdirectory. The file should be copied to a directory where the OpenVPN server can access it, then CRL verification should be enabled in the server configuration: 
<code>crl-verify crl.pem</code>

= Save settings =
Don't forget to save all your settings
lbu ci floppy

Alpine Linux:Mailing lists

2008-02-20T13:26:17Z

Ncopa2: trpasno

liracor
== Alpine-Devel ==
We have an email list available for developers. You can (un)subscribe at http://lists.alpinelinux.org/mailman/listinfo/alpine-devel.

Please don't [http://en.wikipedia.org/wiki/Top-posting top-post] to the list as it makes the archives more or less useless.

== Alpine-Users ==
Seeing that we only have a few users at this point, there is no alpine-users list. We'll set one up in due time.

Alpine Linux:General disclaimer

2008-02-20T13:25:44Z

Ncopa2: laorcn

acouzelcaror

Setting up iSCSI

2008-02-20T13:25:34Z

Ncopa2: eroubasle

trocorviboc
== Introduction ==

iSCSI consists of two pieces: A target (server) and an initiator (client). A target is a large pool of disk space that can be accessed over IP by the initiators. Initiators use the disk space, formatting it and mounting it the same as local disk. When an initiator connects to a target a scsi device node is created (e.g. /dev/sda, /dev/sdb, etc)

== iSCSI Target ==

The ''iscsitarget-X.X.apk'' package provides the target functionality. It includes the ietd service (ietd is the iSCSI Enterprise Target Daemon).
Once the package is [[Alpine_package_management#Adding_packages|installed]], you can set up a target by editing two conf files.

In /etc/ietd.conf, add the following information:

Target iqn.2006-01.com.example:disk2.vol1
Lun 0 Path=/dev/sda1, Type=fileio

The iSCSI Qualified Name is documented in [http://www.ietf.org/rfc/rfc3720.txt RFC 3720], with further examples of names in [http://www.ietf.org/rfc/rfc3721.txt RFC 3721]. Briefly, the fields are:

* literal '''iqn'''
* date (yyyy-mm) that the naming authority took ownership of the domain
* reversed domain name of the authority (''org.alpinelinux, com.example, to.yp.cr'')
* Optional ":" prefixing a storage target name specified by the naming authority.

From the RFC:
Naming String defined by
Type Date Auth "example.com" naming authority
+--++-----+ +---------+ +--------------------------------+
| || | | | | |

iqn.2001-04.com.example:storage:diskarrays-sn-a8675309
iqn.2001-04.com.example
iqn.2001-04.com.example:storage.tape1.sys1.xyz
iqn.2001-04.com.example:storage.disk2.sys1.xyz

The "Target" line above is an example. This line really just needs to be unique. /dev/sdx refers to the disk and partition that will be presented to the initiator.

In the /etc/initiators.allow file, add the following line:

iqn.2006-01.com.example:disk2.vol1 10.1.194.111

The IP address in the line above will be the initiator's ip address. Now only this ip address is allowed to access this specific target. You must use IP addresses, not hostnames.

If you don't care where the initiator is connecting from, you can use the keyword '''ALL'':

iqn.2006-01.com.example:disk2.vol1 ALL

== iSCSI Initiator ==
The initator is in the ''open-isci'' package. Load this package on the client.

To configure the iSCSI initiator, add the initiator name to the file /etc/iscsi/initiatorname.iscsi The initator name follows the same iqn naming scheme as the target; but this is iderntifing the initator (client).

InitiatorName=iqn.2007-11.org.alpinelinux.client:01

or
InitiatorName=iqn.2007-11.com.example.me:foo:bar:baz

The ''01'', ''foo:bar:baz'' are arbitrary. You can enter anything (or nothing)- as long as the intiator name is a valid iqn.

Start the initiator daemon with
/etc/init.d/iscsid start

== Connecting the Initiator to the Target ==

From the iSCSI initiator, first run this command:

iscsiadm --mode discovery --type sendtargets --portal IP_OF_TARGET

This command contacts the target to determine which disks are available. If all is configured correctly, the target name iqn.2006-01.com.example:disk2.vol1 (from the example above) will be returned.

After the target is discovered, run this command to connect:

iscsiadm --mode node --targetname NAME_OF_TARGET --portal IP_OF_TARGET --login

Replacing --login with --logout will end the connection.

To make this connection persistent (so that it will reconnect after reboot), run this command:

iscsiadm -m node -T NAME_OF_TARGET -p IP_OF_TARGET --op update -n node.conn[0].startup -v automatic

''Any references/links to where to find more details about it?''--[[User:Ncopa|Ncopa]] 16:04, 8 November 2007 (UTC)

Setting up traffic monitoring using rrdtool (and snmp)

2008-02-20T13:23:59Z

Ncopa2: tabocboc

vitroccot
== Install programs ==
Install rrdtool
apk_add rrdtool

== Create a rrd-database ==
The creation of the database is dependent on how many DataSources (DS) you have, and what type of DataSources you use. 
In this example, we monitor eth0 and eth1 (RX and TX) on this local machine, and fetch (eth0 and eth1) information from another computer through snmp.
rrdtool create /root/exampledb.rrd \
--step 30 \
DS:pc1eth0rx:COUNTER:120:0:U \
DS:pc1eth0tx:COUNTER:120:0:U \
DS:pc1eth1rx:COUNTER:120:0:U \
DS:pc1eth1tx:COUNTER:120:0:U \
DS:pc2eth0rx:COUNTER:120:0:U \
DS:pc2eth0tx:COUNTER:120:0:U \
DS:pc2eth1rx:COUNTER:120:0:U \
DS:pc2eth1tx:COUNTER:120:0:U \
RRA:AVERAGE:0.5:1:3600 \
RRA:MAX:0.5:1:3600
This creates a RoundRobinDatabase (RRD) called exampledb.rrd. 
"--step 5" specifies the base interval in seconds with which data will be fed into the RRD.
The first "DS..." row assigns a name "pc1eth0rx". "COUNTER" is for continuous incrementing counters like the ifInOctets counter in a router. The rest in the DS-row, I hopefully come back to later. 
"RRA" is a RoundRobinArcive. Its tores information from the DataSource (DS) in various ways. "RRA:AVARAGE..." will present a average value of (average for each second) and keep values for 3600seconds (older than 3600seconds will be overwritten). "RRA:MAX" calulates the maximum value.

== Gather information and put it in the RRD ==
Gathering data can be done in various ways and from various systems. 
In our example we collect data from 2 different computers, each computer has eth0 and eth1 that we would like to monitor.
=== Feeding the database with information ===
Now we create a new script that starts by fetching the local information and then fetches snmp information from the next computer and then puts it all in the database. 
Lets call the script '''/root/colect_data.sh'''.
#!/bin/sh
while true; do
sleep 30
ETH0=$(grep eth0 /proc/net/dev)
E0DOWN=$(echo $ETH0|tr \: \ |awk '{print $2}')
E0UP=$(echo $ETH0|tr \: \ |awk '{print $10}')
ETH1=$(grep eth1 /proc/net/dev)
E1DOWN=$(echo $ETH1|tr \: \ |awk '{print $2}')
E1UP=$(echo $ETH1|tr \: \ |awk '{print $10}')
rrdupdate /root/exampledb.rrd N:\
${E0DOWN}:${E0UP}:${E1DOWN}:${E1UP}:\
`/usr/bin/snmpget -v 1 -c general -Oqv 192.168.0.2 IF-MIB::ifInOctets.2`:\
`/usr/bin/snmpget -v 1 -c general -Oqv 192.168.0.2 IF-MIB::ifOutOctets.2`:\
`/usr/bin/snmpget -v 1 -c general -Oqv 192.168.0.2 IF-MIB::ifInOctets.3`:\
`/usr/bin/snmpget -v 1 -c general -Oqv 192.168.0.2 IF-MIB::ifOutOctets.3`:\
done
For this to work, you need to have a configured snmpd running on the 192.168.0.2 computer. The community-name 'general' might be different for you, depending on your snmp configuration.

== Present the information in graphs ==
Now starts the fun part. We will display the gathered information. 
The information can be presented in various ways (we will use LINE-graph).
rrdtool graph /root/result.png --start -1800 \
-a PNG -t "Network Interfaces" --vertical-label "bits/s" \
-w 1260 -h 800 -r \
DEF:pc1eth0rx=/root/exampledb.rrd:pc1eth0rx:AVERAGE \
DEF:pc1eth0tx=/root/exampledb.rrd:pc1eth0tx:AVERAGE \
DEF:pc1eth1rx=/root/exampledb.rrd:pc1eth1rx:AVERAGE \
DEF:pc1eth1tx=/root/exampledb.rrd:pc1eth1tx:AVERAGE \
DEF:pc2eth0rx=/root/exampledb.rrd:pc2eth0rx:AVERAGE \
DEF:pc2eth0tx=/root/exampledb.rrd:pc2eth0tx:AVERAGE \
DEF:pc2eth1rx=/root/exampledb.rrd:pc2eth1rx:AVERAGE \
DEF:pc2eth1tx=/root/exampledb.rrd:pc2eth1tx:AVERAGE \
CDEF:pc1eth0rxb=pc1eth0rx,8,\* \
CDEF:pc1eth0txb=pc1eth0tx,-8,\* \
CDEF:pc1eth1rxb=pc1eth1rx,8,\* \
CDEF:pc1eth1txb=pc1eth1tx,-8,\* \
CDEF:pc2eth0rxb=pc2eth0rx,8,\* \
CDEF:pc2eth0txb=pc2eth0tx,-8,\* \
CDEF:pc2eth1rxb=pc2eth1rx,8,\* \
CDEF:pc2eth1txb=pc2eth1tx,-8,\* \
AREA:pc1eth0rxb#D7CC00:PC1_EHT0-RX \
AREA:pc1eth0txb#D7CC00:PC1_EHT0-TX \
LINE2:pc1eth1rxb#D73600:PC1_EHT1-RX \
LINE2:pc1eth1txb#D73600:PC1_EHT1-TX \
LINE2:pc2eth0rxb#0101D6:PC2_EHT0-RX \
LINE2:pc2eth0txb#0101D6:PC2_EHT0-TX \
LINE2:pc2eth1rxb#00D730:PC2_EHT1-RX \
LINE2:pc2eth1txb#00D730:PC2_EHT1-TX
First define name of output and the time-span (we could also have definesd "--end"). 
We output some headers and Y-axis information. 
Next we define the size of the png. 
"DEF..." gets the information from the database.
"CDEF..." recalculates the original information (in our case we want to presnet bits instead of bytes). 
"AREA..." displays a area-graph on the output. 
"LINE2..." (or "LINE") writes a line-graph. 
In the color settings, you could enter opacity at the end. "LINE3...#FF00007F" would have displayed a 3pixel red line with approx. 50% opacity.

= Save settings =
Don't forget to save all your settings
lbu ci floppy

Alpine Package Keeper

2008-02-20T13:23:46Z

Ncopa2: domgetbasdo

alccpasde
= Alpine package management =

Alpine has the following tools for package management:
* apk_add
* apk_create
* apk_delete
* apk_fetch
* apk_get
* apk_glob
* apk_info
* apk_version

All of these commands have a -h option, which will give you the different options they support.

== Adding packages ==

Use '''apk_add''' to install packages.

If you want to install ''openssh'' for example, you run:
apk_add openssh

apk_add supports installation from cdrom, usb, http, ftp, ssh (scp) and rsync. scp is only available if ''openssh'' or ''dropbear'' is installed and rsync is only available if ''rsync'' is installed.

=== Dry-run ===

Sometimes you would like to see what would get installed if you install a package, or what dependencies would be pulled in by the package. You can see this using:
apk_add -n openssh

== Removing packages ==

Removing packages is done using:
% apk_delete openssh

To remove a package plus it's dependencies, use:
% apk_delete -R openssh

Even more dangerous is:
% apk_delete -r openssl
which will delete openssl plus all packages that depend on it.

Since removing packages (recursively) can seriously damage your system, it is best to use:
% apk_delete -n openssh
Which will not really remove the package, but just show what it would do.

== Looking for packages? ==

To see the packages available in the repository, use:
% apk_fetch -l

Or you might use:
% apk_fetch -l -v
Which will also show the version number of the available packages.

If the text scrolls by too fast you can use:
% apk_fetch -l | less

== Info about your packages ==

There are several other commands that give more information about the packages installed on your system.

To see the contents of a certain package, use:
% apk_info -L openssh

To see the size of a package, use:
% apk_info -s openssh

To see all packages that depend on a package, eg zlib:
% apk_glob -r zlib

To find out to what package a certain file or directory belongs to, eg /etc/shorewall:
% apk_info -W /etc/shorewall

== Upgrading alpine ==

The easiest way to upgrade alpine is to safe your settings to floppy or usb-key and reboot using a new CD. But there are several other possibilities a well:
* Change the CD, but do not reboot
* Update over network

=== Changing the CD, no reboot ===

First update the package list:
% apk_fetch -u

Check what packages have changed version numbers
% apk_version -v

Next:
% apk_version -v -l '<'
Will show you what packages needs to be updated

The first thing to check is whether the apk-tools need to be upgraded, if so, '''always''' do this first:
% apk_add -u apk-tools

Now it is time to upgrade the other packages:
% apk_version -q -l '<' | xargs apk_add -u

After your upgrade you might find some apk-new files in /etc,these are upgraded config files. A simple utility to go over these files is:
% update-conf -l

=== Update over network ===

This is about the same as the previous entry. The key-difference is that we will change the install-source for apk. This can be done in two ways, on the command-line, using ''export'' or changing an /etc file:

% export APK_PATH=http://dev.alpinelinux.org/alpine/v1.4/apks/

or edit apk.conf, and add your requested resource.
% vi /etc/apk.conf

You can use sources from:
* cdrom
* http(s)
* ftp
* rsync (remember that rsync has to be installed before you can use this! (''% apk_add rsync''))

After you made this change, continue as the cd-rom upgrade with, etc
% apk_fetch -u

Help:Editing

2008-02-20T13:23:35Z

Ncopa2: litrca

trocchio
http://en.wikipedia.org/wiki/Wikipedia:How_to_edit_a_page

Upgrading Alpine Linux to a new release branch

2008-02-20T13:23:24Z

Ncopa2: baschiri

alacel
= Upgrading Alpine =

This document describes how to replace an Alpine installation with a newer version.

The upgrade process consist of the following steps:
* Backup current setup
* Download new version of Alpine
* Replace packages
* Merge config
* Reboot

=== Backing up current config ===
Its recommended to make a backup of your config before you start. You can do that by simply replacing the floppy with a new floppy and keep the old one in case you will need to do a rollback. If you store config on USB you migh copy the config file (*apkovl*) to a safe place.

If you use the USB installation and not the CDROM, you can just create a directory on the USB called ''old'' and move everything to this dir.
mkdir /media/usb/old
mv /media/usb/* /media/usb/old/

Note that this command will try to move the ''old'' directory into itself which will give an error message. You can safely ignore this.

If you need to rollback, simply move the contents in directory ''old'' back to the root of USB.

=== Download new Alpine ===
Download and burn the new [http://dev.alpinelinux.org/alpine/v1.7/iso ISO image] on a separate computer. Replace the CDROM and mount it.

On USB installations you can just download and unpack the latest tar directly to ''/media/usb''.
$ wget -C /media/usb -q -O - \
http://dev.alpinelinux.org/alpine/v1.7/usbdrive/alpine-1.7.6-i386.tar.gz \
| tar -zvx

=== Execute upgrade script ===
Execute the ''upgrade'' script found on root level on media. (/media/cdrom/upgrade or /media/usb/upgrade). Before actually upgrading packages it will give an overview what packages will be upgraded. It migh look something like this:
<pre>~ $ /media/usb/upgrade
Upgrading from alpine-1.7.2 to alpine-1.7.6
Will try to upgrade packages from
fetching usb://apks/INDEX.md5.gz
Looking for new packages...
The following packages will be updated:
alpine-baselayout-1.4.1-r1 < needs updating (index has 1.6.0)
alpine-conf-0.9 < needs updating (index has 1.0)
bind-tools-9.4.1-r1 < needs updating (index has 9.4.1_p1)
busybox-1.5.0-r1 < needs updating (index has 1.7.1)
iproute2-2.6.19.20061214 < needs updating (index has 2.6.20.20070313)
iptables-1.3.5-r4 < needs updating (index has 1.3.8-r1)
libpcap-0.9.5 < needs updating (index has 0.9.7)
openssh-4.5_p1-r1 < needs updating (index has 4.7_p1-r1)
openssl-0.9.8d < needs updating (index has 0.9.8e-r2)
openswan-2.4.8 < needs updating (index has 2.5.15)
shorewall-3.4.3 < needs updating (index has 3.4.6)
shorewall-doc-3.4.2 < needs updating (index has 3.4.6)
tcpdump-3.9.5-r2 < needs updating (index has 3.9.7-r1)

Press Enter to continue or Ctrl-c to abort.
</pre>

Verify that it looks ok and press ''enter'' to start the upgrade.

As a first step the upgrade script will try to upgrade apk-tools, uclibc and busybox. Then it will upgrade all packages by running ''apk_add -u''. It will look something like this:
<pre>apk-tools-0.13 is installed. Skipping apk-tools-0.13.
uclibc-0.9.28.3 is installed. Skipping uclibc-0.9.28.3.
fetching usb://apks/busybox-1.7.1.apk
updating busybox-1.5.0-r1 to busybox-1.7.1
fetching usb://apks/alpine-baselayout-1.6.0.apk
updating alpine-baselayout-1.4.1-r1 to alpine-baselayout-1.6.0
fetching usb://apks/alpine-conf-1.0.apk
updating alpine-conf-0.9 to alpine-conf-1.0
fetching usb://apks/bind-tools-9.4.1_p1.apk
updating bind-tools-9.4.1-r1 to bind-tools-9.4.1_p1
busybox-1.7.1 is installed. Skipping busybox-1.7.1.
fetching usb://apks/iproute2-2.6.20.20070313.apk
updating iproute2-2.6.19.20061214 to iproute2-2.6.20.20070313
fetching usb://apks/iptables-1.3.8-r1.apk
updating iptables-1.3.5-r4 to iptables-1.3.8-r1
fetching usb://apks/libpcap-0.9.7.apk
updating libpcap-0.9.5 to libpcap-0.9.7
fetching usb://apks/openssh-4.7_p1-r1.apk
updating openssh-4.5_p1-r1 to openssh-4.7_p1-r1
fetching usb://apks/openssl-0.9.8e-r2.apk
updating openssl-0.9.8d to openssl-0.9.8e-r2
fetching usb://apks/openswan-2.5.15.apk
updating openswan-2.4.8 to openswan-2.5.15
fetching usb://apks/shorewall-3.4.6.apk
updating shorewall-3.4.3 to shorewall-3.4.6
fetching usb://apks/shorewall-doc-3.4.6.apk
updating shorewall-doc-3.4.2 to shorewall-doc-3.4.6
fetching usb://apks/tcpdump-3.9.7-r1.apk
updating tcpdump-3.9.5-r2 to tcpdump-3.9.7-r1
</pre>

When then '''apk_add''' application upgrades packages, it will detect that you have modified some config files. Instead of overwriting your config, it will install the new config with the suffix ''.apk-new''. This way you are able to review and merge in changes from the default config to your own config file. Config files that are untouched will just silently be replaced.

The ''upgrade'' script will execute ''update-conf'' to assist you in merging the config files. It will first display a list of config files that you will need to take care of manually. Like this:

<pre>The following config files have been updated and need attention:
/etc/profile
/etc/modules
/etc/inittab
/etc/hosts
/etc/shorewall/zones
/etc/shorewall/tunnels
/etc/shorewall/tos
/etc/shorewall/shorewall.conf
/etc/shorewall/rules
/etc/shorewall/policy
/etc/shorewall/params
/etc/shorewall/masq
/etc/shorewall/interfaces
/etc/shorewall/hosts
/etc/shorewall/accounting
/etc/ipsec/ipsec.conf
/etc/ipsec/ipsec.d/policies/private-or-clear
/etc/ipsec/ipsec.d/policies/private
/etc/ipsec/ipsec.d/policies/clear-or-private
/etc/ipsec/ipsec.d/policies/clear
/etc/ipsec/ipsec.d/policies/block
/etc/ipsec/ipsec.d/examples/no_oe.conf
/etc/ipsec/ipsec.d/examples/l2tp-psk.conf
/etc/ipsec/ipsec.d/examples/l2tp-psk-orgWIN2KXP.conf
/etc/ipsec/ipsec.d/examples/l2tp-cert.conf
/etc/ipsec/ipsec.d/examples/l2tp-cert-orgWIN2KXP.conf
/etc/ssh/sshd_config
/etc/ssh/ssh_config
/etc/init.d/ipsec
/etc/init.d/sshd
/etc/init.d/syslog
/etc/init.d/networking
/etc/init.d/modloop
/etc/init.d/bootmisc.sh
</pre>

Afterward it will step through every file, displaying a diff and give you options to act.

<pre>
--- /etc/profile 2007-05-31 14:11:47 +0000
+++ /etc/profile.apk-new 2007-09-07 06:33:36 +0000
@@ -1,4 +1,3 @@
export PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin
export PAGER=less
umask 022
-export LBU_MEDIA=usb
New /etc/profile available:
Quit, Next, Show diff, Edit new, Zap new, Use new (q/n/s/e/z/u) [s]:
</pre>

In this case we have added ''export LBU_MEDIA==usb'' so we don't need to specify the media to 'lbu''. We want to keep our current file as it is so we just press ''z'' (and ''Enter'') to zap the new config and keep the old.

Next is file is ''/etc/modules''
<pre>
--- /etc/modules 2007-05-09 16:02:31 +0000
+++ /etc/modules.apk-new 2007-09-07 06:33:36 +0000
@@ -1,4 +1,2 @@
deadline-iosched
af_packet
-xt_state
-xt_tcpudp
New /etc/modules available:
Quit, Next, Show diff, Edit new, Zap new, Use new (q/n/s/e/z/u) [s]:
</pre>

Also here we just keep the current config by pressing ''z'' since the modules are needed for our ipsec.

Next file is ''/etc/inittab'':
<pre>--- /etc/inittab 2007-06-20 13:21:20 +0000
+++ /etc/inittab.apk-new 2007-09-07 06:33:36 +0000
@@ -4,7 +4,7 @@
::wait:/etc/init.d/rcL

# Set up a couple of getty's
-::respawn:/sbin/cttyhack /sbin/getty - 9600 vt100
+::respawn:/usr/bin/cttyhack /sbin/getty - 9600 vt100
tty2::respawn:/sbin/getty 38400 tty2
tty3::respawn:/sbin/getty 38400 tty3
tty4::respawn:/sbin/getty 38400 tty4
New /etc/inittab available:
Quit, Next, Show diff, Edit new, Zap new, Use new (q/n/s/e/z/u) [s]:
</pre>

This time the change is not caused by us, but its a change in the default config. This is even related to where the login screen should appear so if we don merge this change in we might not be able to see the login screen! We choose ''u'' to use the new config.

Continue go through every config file. Sometimes you might want to edit the new file, or leave the upgrade process to take care of the config file manually by using option ''q''. You can always resume later by either running the ''upgrade'' script again or by executing ''update-conf -i''.

== Rebooting ==
In most cases you will need to reboot Alpine, specially if there are are changes in the kernel. If you know what you are doing, you might not need to reboot. Just make sure that all services affected by the upgrade are restarted.

Setting up a /var partition on software IDE raid1

2008-02-20T13:22:26Z

Ncopa2: aceltroccr

trocgetracc
This document wil show how to create harddisk mirroring using cheap IDE disks.

This document was written for alpine-1.3.8

I will setup swap on a raid1 for maximum reliability. If you prefer maximum speed, you don't need configure any raid devces for swap. Just add 2 swap partitions on different disks and linux will stripe them automatically.

The downside is that at the moment one disk fails, the system will go down. Thats why I choose to put the swap on raid1.

== Setting up the RAID ==
Set up a raid array as described [[Setting up a software raid1 array|here]].
In this document two raid arrays are configured: md0 for swap (512MB) and md1 for /var.

It is generally a good idea to use LVM so you are able to easily extend your data storage in future. LVM is not discussed here.

== Create filesystem ==
Now we can creat swapspace and the filesystem for /var.
mkswap /dev/md0
swapon /dev/md0

You can verify that swap was really activated with ''free''. It should display how much swapspace you have.
free

We need to install the software to create the filesystem ("format" the partition). I will use '''ext3''' here so I install ''e2fsprogs''. If you prefer reiserfs or xfs you will have to install ''xfsprogs'' or ''reiserfsprogs'' instead.
apk_add e2fsprogs

If you use an Alpine release older than 1.3.8 you will need to manuall create a link to /etc/mtab.
ln -fs /proc/mounts /etc/mtab

Create the filesystem. The -j option makes it ext'''3'''. Without the -j option it will become non-journaling ext'''2'''. This step might take some time if your partition is big.
mke2fs -j /dev/md1

Now edit /etc/fstab and add your new partition. Mine looks like this:
none /proc proc defaults 0 0
none /sys sysfs defaults 0 0
udev /dev tmpfs size=100k 0 0
none /dev/pts devpts defaults 0 0
tmpfs /dev/shm tmpfs defaults 0 0
/dev/cdrom /media/cdrom iso9660 ro 0 0
/dev/fd0 /media/floppy vfat noauto 0 0
/dev/usba1 /media/usb vfat noauto 0 0
none /proc/bus/usb usbfs noauto 0 0

/dev/md1 /var ext3 defaults 0 0

== Move the data ==
Now you should stop all services running that put anything in /var (syslog for example). If you have booted on a clean installation and not run setup-alpine, then no services should be running. However, some packages might have created dirs in /var so we need to backup /var mount the new and move all backed up dirs back to the raided /var.

mv /var /var.tmp
mkdir /var
mount /var
mv /var.tmp/* /var
rmdir /var.tmp

Verify that everyting looks ok with the ''df'' utility.
~ $ df
Filesystem 1k-blocks Used Available Use% Mounted on
none 255172 23544 231628 9% /
udev 100 0 100 0% /dev
/dev/cdrom 142276 142276 0 100% /media/cdrom
/dev/md1 37977060 181056 35866876 1% /var

== Survive reboots ==
Now we have everyting up and running. We need to make sure that everything will be restored during next reboot.

Create an initscript that will mount /var for you during boot. I call it /etc/init.d/mountdisk and it looks like this:
#!/sbin/runscript

start() {
ebegin "Mounting /var"
mount /var
eend $?
}

stop() {
ebegin "Unmounting /var"
umount /var
eend $?
}

Make it exectutable:
chmod +x /etc/init.d/mountdisk

'''NOTE:''' Since Alpine-1.7.3 there is a ''localmount'' script shipped so you will not need to create your own ''mountdisk'' script.

And that /var is mounted *after* raid is created. The -k option will make alpine to unmount the /Var partition during boot. Also add start of swap too boot
rc_add -k -s 06 mountdisk
rc_add -k -s 06 swap

The /dev/md* device nodes will not be created automatically so we need to put the on floppy too.
lbu include /dev/md*

If you have users on the server and want the /home be permantent you can create a directory /var/home and create links to /var/home.
mkdir /var/home
mv /home/* /var/home/
ln -s /var/home/* /home/

'''NOTE:''' You cannot just replace /home with a link that points to /var/home since the base has a director /home. When the boot tries to copy the config from floppy it will fail because of the already existing /home directory.

Make sure the links are stored to floppy:
lbu include /home/*

Also remeber to move any newly created users to /var/home and create a link:
adduser bob
mv /home/bob /var/home/
ln -s /var/home/bob /home/bob
lbu include /home/bob

Save to floppy:
lbu commit floppy

== Test it works ==
Reboot computer. Now should the raid start and /var sould be mounted. Check with df:
~ $ df
Filesystem 1k-blocks Used Available Use% Mounted on
none 255172 23976 231196 9% /
mdev 100 0 100 0% /dev
/dev/cdrom 140932 140932 0 100% /media/cdrom
/dev/md1 37977060 180984 35866948 1% /var

== Upgrades ==
Since the package database is placed on disk, you cannot update by simply replacing the CDROM. You will have to either run the upgrade on the new CDROM or run ''apk_add -u ... && update-conf'' manually.

Installing Alpine

2008-02-20T13:22:13Z

Ncopa2: sittrocdron

vivividomc
There are currently two supported ways of running Alpine, from CDROM or from USB stick.

== Preparing the media ==

=== CDROM ===
Download the latest iso image from the [http://www.alpinelinux.org/mediawiki/index.php/Downloads download] area and burn it.

=== USB ===
Alpine is shipped in compressed tar.gz archives for USB.

==== From windows ====
* Download a alpine-x.x.x-yyyyyy.tar.gz package.
* Unpack all the files to your usb drive using a unpacker like [http://www.7-zip.org 7-zip].
* Download the [http://dl.alpinelinux.org/alpine/v1.4/usbdrive/syslinux.exe syslinux.exe] utility.
* Start a command prompt (Start->run, type ''cmd'' and press >enter>)
* Run syslinux with your USB drive as parameter. If your USB drive is E:, then you type:
syslinux E:

USB drive os ready for booting.

==== From Linux ====
* Download a alpine-x.x.x-yyyyyy.tar.gz package.
* Unpack all the files to your usb drive.
* install syslinux (I.E ''sudo apt-get syslinux'' or ''emerge apt-get syslinux'')
* Run syslinux with your USB drive as parameter. If your USB drive is /dev/sda1, then you type:
sudo syslinux /dev/sda1

== Initial setup ==
After booting up you will see a login prompt. Log in as ''root''.

To do the basic initial configuration run:
setup-alpine

There you will set the hostname, configure the network and set the root password.

To save the configuration to floppy for next reboot run:
lbu_commit floppy

To save the config on an USB drive run:
lbu_commit usb

=== Managing software packages ===
To list all the packages that are available in repository, run:
apk_fetch -l
apk_fetch -v -l

To install a package run:
apk_add <PACKAGE>

To remove the package run:
apk_delete <PACKAGE>

To also remove the dependencies togehter with the package, run:
apk_delete -R <PACKAGE>

To list all installed packages run:
apk_info

=== Managing boot services ===

To start a service during boot run:
rc_add <service>

=== Managing local backups ===

To add a config file to the local backup list run:
lbu_add /path/to/file

To save all the files in the local backup list to floppy run:
lbu_commit floppy

To save the configs to USB drive run:
lbu_commit usb

To list files in the local backup list run:
cat /etc/backuplist

Native Harddisk Install 1.6

2008-02-20T13:21:16Z

Ncopa2: chiacelboc

liousittalir
=Alpine HD install=

'''NOTE''': This document covers 1.6 release. From version 1.7.3 there is an albootstrap script that will install the basic packages (except grub) into a subdir. The script is available here: http://dev.alpinelinux.org/alpine/1.7/albootstrap

Alpine is more geared toward live-cd or usb-key usage, but it is possible to install it to a harddisk.

This is how it is done. The Alpine version is 1.6.1

==Installation==

Create partitions with fdisk.
fdisk /dev/hda
You should have 2 partitions: /dev/hda1 as "Linux" (type 83) and /dev/hda2 as "linux swap" (type 82).

Install needed programs for the setup
apk_add e2fsprogs rsync grub

Create filesystem and swap
mkfs.ext3 /dev/hda1
mkswap /dev/hda2

Turn on swap already now
swapon /dev/hda2

Mount file-system
mount -t ext3 /dev/hda1 /mnt

Install base packages on harddisk
ROOT=/mnt apk_add uclibc busybox apk-tools alpine-baselayout alpine-conf grub

If you want pcmcia support, then also add the pcmciautils package
ROOT=/mnt apk_add pcmciautils

Install busybox links
mkdir /mnt/proc
mount --bind /proc /mnt/proc
chroot /mnt /bin/busybox --install -s
umount /mnt/proc

For convenience, copy the apk repository.
rsync -ruav /media/cdrom/apks /mnt

Create the apk.conf:
mkdir /mnt/etc/apk
echo "APK_PATH=file://apks" > /mnt/etc/apk/apk.conf

Copy the hd/ext3 initramfs image, kernel and kernel modules.
rsync -ruav /media/cdrom/hd-ext3.gz /media/cdrom/vmlinuz /mnt
rsync -ruav /lib/modules /mnt/lib/

Configure grub
grub-install --root-directory=/mnt /dev/hda1
vi /mnt/boot/grub/menu.lst

It should contain something like:

default 0
timeout 0
title Alpine Linux
root (hd0,0)
kernel /vmlinuz root_dev=hda1:ext3 alpine_dev=../:ext3
initrd /hd-ext3.gz

Install grub on MBR:
grub
root (hd0,0)
setup (hd0)
quit

Append the swap to fstab:
echo -e "/dev/hda2 none swap sw 0 0" >> /mnt/etc/fstab

Unmount, remove cdrom and reboot. (If you can't eject, just remove it manually as the machine reboots)
umount /mnt
eject
reboot

After reboot, log in as "root" and run:
setup-alpine

Setting up Logical Volumes with LVM

2008-02-20T13:20:28Z

Ncopa2: c4tlirobocd

bascnatrocla
This document how to create logical volumes in Alpine using lvm2.

LVM is collection of programs that allow larger physical disks to be reassembled into "logical" disks that can be shrunk or expanded as data needs change.

In this document we will use a [[Setting up a software raid1 array | software raid1 device]] as physical storage for our logical volumes. We will set up a swap partition and a data partition for [[ Setting up a basic vserver | vservers ]]
=== Installing LVM software ===
First we need to load the kernel driver, ''dm-mod''

modprobe dm-mod

We also want it to be loaded during next reboot.

echo dm-mod >> /etc/modules

We also need the userspace programs.
apk_add lvm2

=== Preparing the physical volumes ===
First we need to tell LVM that de partition is available as a physical volume and can be added to a volume group. In this example we use a software raid array as physical volume.
pvcreate /dev/md0

=== Preparing the Volume Group ===
We can then create a volume group and add the physical volume ''/dev/md0''
vgcreate vg0 /dev/md0

If we later need more space we can add additional physcal volumes with ''vgextend''. All physcal disks/partitions added need to be prepared with ''pvcreate''.

=== Creating Logical volumes ===
In the volume group we can create logical volumes. To create a 1GB volume called ''swap'' and a 6GB volume called 'vservers'' on the volume group ''vg0'' we run
lvcreate -n swap -L 1G vg0
lvcreate -n vservers -L 6G vg0

=== display Logicall Volumes ===
You can now se the logical volumes with the lvdisplay utility.

lvdisplay
--- Logical volume ---
LV Name /dev/vg0/swap
VG Name vg0
LV UUID a4NYOi-FQP6-Lj5Q-0TYk-Jjtk-Qxjt-nxeBPn
LV Write Access read/write
LV Status available
# open 0
LV Size 1.00 GB
Current LE 256
Segments 1
Allocation inherit
Read ahead sectors 0
Block device 253:0

--- Logical volume ---
LV Name /dev/vg0/vservers
VG Name vg0
LV UUID 16VMmy-7I0s-eeoW-tL2V-JrlN-jM6C-d0wEg0
LV Write Access read/write
LV Status available
# open 0
LV Size 6.00 GB
Current LE 1536
Segments 1
Allocation inherit
Read ahead sectors 0
Block device 253:1

=== Start LVM during Boot ===
We want lvm to init the logical voluems during boot. There is a boot service named ''lvm'' to do this. If your volumes are on raid, make sure that ''/etc/init.d/lvm'' is started after mdadm-raid.

rc_add -s 12 -k lvm

=== Setting up swap ===
Now we have our devices in /dev/vg0 and can use them as normal disk paritions. To set up swap:

mkswap /dev/vg0/swap

Add the following line to your ''/etc/fstab'':
/dev/vg0/swap none swap sw 0 0

Start the swap service and make sure it starts during next reboot and tht is starts '''after''' lvm.

/etc/init.d/swap start
rc_add -s 14 -k swap

=== Setting up /vservers partition ===
Finally we want to set up an XFS partition for /vservers.

Install xfsprogs.

apk_add xfsprogs

Create filesystem on /dev/vg0/vservers.
mkfs.xfs /dev/vg0/vservers

Add the mount information to your /etc/fstab:
/dev/vg0/vservers /vservers xfs noatime,tagxid 0 0

Note that the ''tagxid'' option is specific for setting up vserver [http://oldwiki.linux-vserver.org/Disk+Limits disk limits] so it might be you don't want it. The ''noatime'' option is to increase performance but you will no longer know when files were accessed last time.

Now we can start the ''localmount'' boot service to mount our partition.
/etc/init.d/localmount start

Make sure we run ''localmount'' during boot too, and that it is done after lvm.
rc_add -s 14 -k localmount

=== More Info on LVM ===
For more information, have a look at the [http://tldp.org/HOWTO/LVM-HOWTO/commontask.html common tasks] section in the [http://tldp.org/HOWTO/LVM-HOWTO/index.html LVM Howto].

Installing Xubuntu using Alpine boot floppy

2008-02-20T13:18:03Z

Ncopa2: lalirelc4tt

delchida
Some computers does not boot on cdrom or USB. Then you can use Alpine boot floppy together with an USB with alpine to install Ubuntu. This document describes how.

You will need atleast version 1.0 of debootstrap to get feisty installed. Therefore, set APK_PATH to point at http://dev.alpielinux.org/alpine/v1.7/apks or use alpine 1.7.3.

== Preparing boot media ==
* Create a floppy from [http://dev.alpinelinux.org/alpine/v1.7/bootimages/usb.flp usb.flp]
* unpack the [http://dev.alpinelinux.org/alpine/v1.7/usbdrive/alpine-1.7.2-i386.tar.gz usb image] to an usb drive.
wget -q -O - http://dev.alpinelinux.org/alpine/v1.7/usbdrive/alpine-1.7.2-i386.tar.gz | tar -zxv -C /media/usb
* boot the floppy with usb inserted. You have alpine running.

== Set up environment ==
* Log in as root (no password required)
* setup networking with:
setup-alpine
* Unless you run alpine-1.7.3 or newer, set APK_PATH to network. This is to get newest version of debootstrap:
export APK_PATH=http://dev.alpinelinux.org/alpine/v1.7/apks
* Set up http proxy if needed:
export http_proxy=http://proxy:8080

== Prepare the harddisk ==
* Load driver for IDE disks if you run IDE. If you have SATA or SCSI disk you will not need to do this.
modprobe ide-disk
* use fdisk to create the desired paritions
fdisk /dev/hda
Here I will use this simple layout:
{| bgcolor="#ccc"
| /dev/hda1 || swap || 128MB
|-
| /dev/hda2 || ext3/
|}

Delete all pardition using 'd' in fdisk. Create the swap partition as above with:
n (New partition)
p (primary partition)
1 (partition number)
<enter> (first cylinder = default)
+128M (size of partition)
t (set type)
82 (partition type 82 hex for swap)

Create / partition
n (new partition)
p (primary partition)
2 (partition number 2)
<enter> (default first cylineder)
<enter> (use rest of disk)
w (write and quit. Warning! this will destroy all your current data on your disk!)

* Create and enable swap:
mkswap /dev/hda1
swapon /dev/hda1

* Create filesystem on disk (format)
apk_add e2fsprogs
mkfs.ext3 /dev/hda2

* mount the root partition
mount -t ext3 /dev/hda2 /mnt

== Running debootstrap ==
* Allow debootstrap to run mount inside chroot
for i in /proc/sys/kernel/grsecurity/chroot* ; do echo 0 > $i ; done

* install and run debootstrap utility
apk_add debootstrap
debootstrap --arch i386 feisty /mnt

From here you can chroot to your mount point, edit your /etc/apt/sources.list, install a kernel and reboot.