Alpine Linux - User contributions [en]

Alpine Linux:FAQ

2007-09-18T09:25:52Z

WikiSysop: /* How can i build my own package? */

=Fequently Asked Questions=

==General==

=== I have found a bug, where can I report it? ===
Before reporting any bugs, please search the [http://bugs.alpinelinux.org bug database] to make sure that the bug is not already reported.

Preferred way to send bug reportes is via the ''sendbug'' application shipped with alpine. Run ''setup-sendbug'' to configure your default sender email address and your outgoing SMTP server.

Once that is done, run
sendbug

If your alpine box is unable to send emails for some reason it is also possible to just to send an email to bugs [at] alpinelinux.org. Please make the bug report as specific as possible.

For general tips how to write a good bug reports, see [http://www.chiark.greenend.org.uk/~sgtatham/bugs.html this article].

'''NOTE:''' On alpine releases prior 1.7.5 you will need to use ''send-pr'' instead of 'sendbug''. Use ''setup-problem-reporting'' to configure your email adress and outgoing SMTP server.

'''TIP:''' If you have problems with the vi editor, try installing nano. Set the environment variable ''EDITOR'' to make send-pr use nano.
apk_add nano
echo "EDITOR=nano" >> /etc/profile
export EDITOR=nano
sendbug

=== How can I contribute? ===
You can contribute by using the software and give feedback.
You can contribute by helping with the documenting your experiences using this wiki.

Your contributions are highly appreciated.

==Audio==

=== How do I play my .ogg/.mp3 files? ===
First, the sound card should be recognized (you must have /dev/snd/***** files)

sox, mpg321, mpg123, oggplay, etc all use the oss sound driver, while Alpine uses ALSA drivers. So you need to load the snd-pcm-oss compatibility module. While you're at it, you might need aumix to turn up the sound volume

echo snd-pcm-oss >> /etc/modules
modprobe snd-pcm-oss
apk_add aumix sox
aumix (set volume settings)
play really_cool_song.mp3

== Configuration ==

=== How do I set local timezone? ===
Timezone if set in the file /etc/TZ. If this is not set time will displayed in UTC. Set how other uClibc based distros does this:
http://leaf.sourceforge.net/doc/buci-tz3.html
http://www.sonoracomm.com/index.php?option=com_content&task=view&id=107&Itemid=32

For a more complete list over timezones see http://astronomy.physics.tamu.edu/Java/Tools/Misc/Clock/zones.html

== Packages ==
=== Can you build an apk package for ...? ===
Yes, I probably can. Please check if your wanted package exist in gentoo portage by searching in http://packages.gentoo.org. Please post a package request on [http://lists.alpinelinux.org/mailman/listinfo/alpine-devel alpine-devel] mailing list and we will look at it.

If there is no Gentoo package, then the best would be to create and ebuild and submit it to http://bugs.gentoo.org. Once your package is in gentoo its very easy to create and maintain the package in Alpine. During special conditions, we might create and maintain this package in the Alpine portage overlay, but its best if it could be officially included in Gentoo.

Currently, packages that require gettext, iconv, java or mono will be rejected for technical reasons. Packages requiring xorg, ruby, python perl, php or will most likely also be rejected but not for technical reasons.

=== How can i build my own package? ===
If you need compile you will need a toolchain to do it for you. Use the [http://dl.alpinelinux.org/alpine/v1.7/buildroot/ alpine-buildroot] as base and set up a Gentoo hardened uclibc [http://www.bulah.com/embeddedgentoo.html chroot].

If you want to create a package that just containins scripts, then you can simply create a tar.gz package and give it a proper name. There is a utlity, [http://apk-tools.sourceforge.net/apk_create.html apk_create], to assist you in creating packages. The [http://apk-tools.sourceforge.net/apk_create.html man page] has details on internals.

Alpine Linux:FAQ

2007-09-18T09:24:47Z

WikiSysop: /* How do I set local timezone? */

=Fequently Asked Questions=

==General==

=== I have found a bug, where can I report it? ===
Before reporting any bugs, please search the [http://bugs.alpinelinux.org bug database] to make sure that the bug is not already reported.

Preferred way to send bug reportes is via the ''sendbug'' application shipped with alpine. Run ''setup-sendbug'' to configure your default sender email address and your outgoing SMTP server.

Once that is done, run
sendbug

If your alpine box is unable to send emails for some reason it is also possible to just to send an email to bugs [at] alpinelinux.org. Please make the bug report as specific as possible.

For general tips how to write a good bug reports, see [http://www.chiark.greenend.org.uk/~sgtatham/bugs.html this article].

'''NOTE:''' On alpine releases prior 1.7.5 you will need to use ''send-pr'' instead of 'sendbug''. Use ''setup-problem-reporting'' to configure your email adress and outgoing SMTP server.

'''TIP:''' If you have problems with the vi editor, try installing nano. Set the environment variable ''EDITOR'' to make send-pr use nano.
apk_add nano
echo "EDITOR=nano" >> /etc/profile
export EDITOR=nano
sendbug

=== How can I contribute? ===
You can contribute by using the software and give feedback.
You can contribute by helping with the documenting your experiences using this wiki.

Your contributions are highly appreciated.

==Audio==

=== How do I play my .ogg/.mp3 files? ===
First, the sound card should be recognized (you must have /dev/snd/***** files)

sox, mpg321, mpg123, oggplay, etc all use the oss sound driver, while Alpine uses ALSA drivers. So you need to load the snd-pcm-oss compatibility module. While you're at it, you might need aumix to turn up the sound volume

echo snd-pcm-oss >> /etc/modules
modprobe snd-pcm-oss
apk_add aumix sox
aumix (set volume settings)
play really_cool_song.mp3

== Configuration ==

=== How do I set local timezone? ===
Timezone if set in the file /etc/TZ. If this is not set time will displayed in UTC. Set how other uClibc based distros does this:
http://leaf.sourceforge.net/doc/buci-tz3.html
http://www.sonoracomm.com/index.php?option=com_content&task=view&id=107&Itemid=32

For a more complete list over timezones see http://astronomy.physics.tamu.edu/Java/Tools/Misc/Clock/zones.html

== Packages ==
=== Can you build an apk package for ...? ===
Yes, I probably can. Please check if your wanted package exist in gentoo portage by searching in http://packages.gentoo.org. Please post a package request on [http://lists.alpinelinux.org/mailman/listinfo/alpine-devel alpine-devel] mailing list and we will look at it.

If there is no Gentoo package, then the best would be to create and ebuild and submit it to http://bugs.gentoo.org. Once your package is in gentoo its very easy to create and maintain the package in Alpine. During special conditions, we might create and maintain this package in the Alpine portage overlay, but its best if it could be officially included in Gentoo.

Currently, packages that require gettext, iconv, java or mono will be rejected for technical reasons. Packages requiring xorg, ruby, python perl, php or will most likely also be rejected but not for technical reasons.

=== How can i build my own package? ===
If you need compile you will need a toolchain to do it for you. Use the [http://dl.alpinelinux.org/alpine/v1.5/buildroot/ alpine-buildroot] as base and set up a Gentoo hardened uclibc [http://www.bulah.com/embeddedgentoo.html chroot].

If you want to create a package that just containins scripts, then you can simply create a tar.gz package and give it a proper name. There is a utlity, [http://apk-tools.sourceforge.net/apk_create.html apk_create], to assist you in creating packages. The [http://apk-tools.sourceforge.net/apk_create.html man page] has details on internals.

Alpine Linux:FAQ

2007-09-18T09:14:51Z

WikiSysop: /* I have found a bug, where can I report it? */

=Fequently Asked Questions=

==General==

=== I have found a bug, where can I report it? ===
Before reporting any bugs, please search the [http://bugs.alpinelinux.org bug database] to make sure that the bug is not already reported.

Preferred way to send bug reportes is via the ''sendbug'' application shipped with alpine. Run ''setup-sendbug'' to configure your default sender email address and your outgoing SMTP server.

Once that is done, run
sendbug

If your alpine box is unable to send emails for some reason it is also possible to just to send an email to bugs [at] alpinelinux.org. Please make the bug report as specific as possible.

For general tips how to write a good bug reports, see [http://www.chiark.greenend.org.uk/~sgtatham/bugs.html this article].

'''NOTE:''' On alpine releases prior 1.7.5 you will need to use ''send-pr'' instead of 'sendbug''. Use ''setup-problem-reporting'' to configure your email adress and outgoing SMTP server.

'''TIP:''' If you have problems with the vi editor, try installing nano. Set the environment variable ''EDITOR'' to make send-pr use nano.
apk_add nano
echo "EDITOR=nano" >> /etc/profile
export EDITOR=nano
sendbug

=== How can I contribute? ===
You can contribute by using the software and give feedback.
You can contribute by helping with the documenting your experiences using this wiki.

Your contributions are highly appreciated.

==Audio==

=== How do I play my .ogg/.mp3 files? ===
First, the sound card should be recognized (you must have /dev/snd/***** files)

sox, mpg321, mpg123, oggplay, etc all use the oss sound driver, while Alpine uses ALSA drivers. So you need to load the snd-pcm-oss compatibility module. While you're at it, you might need aumix to turn up the sound volume

echo snd-pcm-oss >> /etc/modules
modprobe snd-pcm-oss
apk_add aumix sox
aumix (set volume settings)
play really_cool_song.mp3

== Configuration ==

=== How do I set local timezone? ===
Help needed to write this. Meanwhile:
http://leaf.sourceforge.net/doc/buci-tz3.html
http://www.sonoracomm.com/index.php?option=com_content&task=view&id=107&Itemid=32

== Packages ==
=== Can you build an apk package for ...? ===
Yes, I probably can. Please check if your wanted package exist in gentoo portage by searching in http://packages.gentoo.org. Please post a package request on [http://lists.alpinelinux.org/mailman/listinfo/alpine-devel alpine-devel] mailing list and we will look at it.

If there is no Gentoo package, then the best would be to create and ebuild and submit it to http://bugs.gentoo.org. Once your package is in gentoo its very easy to create and maintain the package in Alpine. During special conditions, we might create and maintain this package in the Alpine portage overlay, but its best if it could be officially included in Gentoo.

Currently, packages that require gettext, iconv, java or mono will be rejected for technical reasons. Packages requiring xorg, ruby, python perl, php or will most likely also be rejected but not for technical reasons.

=== How can i build my own package? ===
If you need compile you will need a toolchain to do it for you. Use the [http://dl.alpinelinux.org/alpine/v1.5/buildroot/ alpine-buildroot] as base and set up a Gentoo hardened uclibc [http://www.bulah.com/embeddedgentoo.html chroot].

If you want to create a package that just containins scripts, then you can simply create a tar.gz package and give it a proper name. There is a utlity, [http://apk-tools.sourceforge.net/apk_create.html apk_create], to assist you in creating packages. The [http://apk-tools.sourceforge.net/apk_create.html man page] has details on internals.

Downloads

2007-09-18T09:01:59Z

WikiSysop: removed links to usa mirror

== Stable Releases ==
Even numbered releases (eg, 1.6.x) are believed to be stable and ready for use in production environments. Minor number increments in stable releases (for example, from 1.6.2 to 1.6.3) will be bug fixes and security updates only.

=== Alpine 1.6 ===
{|
|[http://dev.alpinelinux.org/alpine/v1.6/ Master mirror] (low bandwidth)
|[http://dev.alpinelinux.org/alpine/v1.6/iso ISO]
|[http://dev.alpinelinux.org/alpine/v1.6/usbdrive USB]
|-
|[http://dl.alpinelinux.org/alpine/v1.6/ USA mirror]
|[http://dl.alpinelinux.org/alpine/v1.6/iso ISO]
|[http://dl.alpinelinux.org/alpine/v1.6/usbdrive USB]
|}

== Development Releases ==
Odd numbered releases (eg, 1.7.x) are development releases. They should be used for testing, learning, and development only. Minor number increments in development versions (eg, 1.7.0 to 1.7.1) may break things, be warned.

=== Alpine 1.7 ===
{|
|[http://dev.alpinelinux.org/alpine/v1.7/ Master mirror] (low bandwidth)
|[http://dev.alpinelinux.org/alpine/v1.7/iso ISO]
|[http://dev.alpinelinux.org/alpine/v1.7/usbdrive USB]
|-
|[http://dl.alpinelinux.org/alpine/v1.7/ USA mirror]
|[http://dl.alpinelinux.org/alpine/v1.7/iso ISO]
|[http://dl.alpinelinux.org/alpine/v1.7/usbdrive USB]
|}

== Old Releases ==
=== Alpine 1.5 ===
{|
|[http://dev.alpinelinux.org/alpine/v1.5/ Master mirror] (low bandwidth)
|[http://dev.alpinelinux.org/alpine/v1.5/iso ISO]
|[http://dev.alpinelinux.org/alpine/v1.5/usbdrive USB]
|}

=== Alpine 1.4 ===
{|
|[http://dev.alpinelinux.org/alpine/v1.4/ Master mirror] (low bandwidth)
|[http://dev.alpinelinux.org/alpine/v1.4/iso ISO]
|[http://dev.alpinelinux.org/alpine/v1.4/usbdrive USB]
|}

=== Alpine 1.3 ===
{|
|[http://dev.alpinelinux.org/alpine/v1.3/ Master mirror] (low bandwidth)
|[http://dev.alpinelinux.org/alpine/v1.3/iso ISO]
|[http://dev.alpinelinux.org/alpine/v1.3/usbdrive USB]
|}

== Sources ==

The sources of alpine are stored in subversion. To check out the tree use one of the following commands:

For annonymous access you can use:
svn co svn://svn.alpinelinux.org/alpine-builder/trunk

Which will checkout the alpine-builder directory in the current directory.

== Requirements ==

To be able to actually build packages you need apk-tools, either located [[http://dev.alpinelinux.org/distfiles/ here]] or a debian-package (ubuntu-package, but it is all just shell-script) [[http://dev.alpinelinux.org/~plovs/ here]].

Setting up traffic monitoring using rrdtool (and snmp)

2007-09-18T08:55:10Z

WikiSysop: removed the initial "set up alpine"

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

Installing Xubuntu using Alpine boot floppy

2007-09-18T08:53:18Z

WikiSysop: /* Prepare the harddisk */ fixed table layou

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.

Installing Xubuntu using Alpine boot floppy

2007-09-18T08:50:18Z

WikiSysop: /* Set up environment */ fixed typo in URL

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:
{
|/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.

Installing Xubuntu using Alpine boot floppy

2007-09-18T08:49:53Z

WikiSysop: imported from old wiki

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.alpielinux.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:
{
|/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.

Native Harddisk Install 1.6

2007-09-18T08:48:25Z

WikiSysop: imported from old wiki

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

2007-09-18T08:47:43Z

WikiSysop: imported from old wiki

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

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 Zaptel/Asterisk on Alpine

2007-09-18T08:46:30Z

WikiSysop: imported from old wiki

= installing Asterisk on Alpine =

Asterisk is an open-source voip server. It can be used both with sip-clients as with phones and/or phonesystems.

''Note:''
We used Alpine version 1.1.3-beta8

== Installation ==

Booted from CD

Log in as root, no password needed
$ setup-alpine

Set hostname, network settngs and root-password
$ apk_add openssh asterisk

Make ssh run at bootup:
$ rc_add sshd

Configure asterisk, we copied settings from our previous install, on
Debian Sarge. The only change we had to make to our previous asterisk
config was:
$ vi modules.conf

under [modules], make sure
load => “res_musiconhold.so”
is loaded before other modules

Make asterisk run at bootup:
$ rc_add asterisk

== Zaptel ==

We use an isdn card to connect to our phone-center. It uses the zaptel
driver. To load all the needed modules we had to make the following
changes:
$ vi /etc/modules

Add the following modules:
zaphfc
zaptel
af_packet

$vi /etc/modules.conf

Add:
options torisa base=0xd0000
alias char-major-196 torisa
alias wctdm wcfxs
alias wct2xxp wct4xxp

== Wrapping up ==

Commit to floppy
$ lbu co floppy

Reboot to make sure you made no mistakes, done.

I prefer to reboot staright after installation. If I made a mistake, I rather find out now then in a couple of monts, when I will for sure have forgotton how I set it all up.

== Permissions ==

To run asterisk as user asterisk, we had to add asterisk to the dialout group:
$ grep asterisk /etc/group

dialout:x:20:root,asterisk

To be able to support sip dial-in clients, we run asterisk as root:
$ vi /etc/conf.d/asterisk

And set:
ASTERISK_USER="root:root"

See also issues

== Issues ==

For sip clients to call in we had have to run Asterisk as root, this needs to be fixed. Asterisk on alpine runs as root out of the box.

== Memory-usage ==

$ free

<pre>
total used free shared buffers

Mem: 185824 51772 34052 0 184

Swap: 0 0 0

Total: 185824 51772 134052
</pre>

==Call logging==

To log phonecalls to a csv-file, edit : /etc/asterisk/modules.conf
$ vi /etc/asterisk/modules.conf

And add load => cdr_csv.so:
<pre>
;
; Asterisk configuration file
;
; Module Loader configuration file
;

[modules]
autoload=no

load => cdr_csv.so
etc
</pre>

Now your logs will be in ''/var/log/asterisk/cdr-csv/Master.csv''

For other forms of logging, see [[http://www.voip-info.org/wiki/view/Asterisk+billing here]]

This box is running the following services:
Ssh, asterisk, tinc and openvpn All this would fit in 64mb.

= resources =

A very nice series of articles called "VoIPowering Your Office with Asterisk: SOHO VoIP" can be found here:

* Intro, How to connect an Asterisk server to legacy phones and phone service, [[http://www.voipplanet.com/backgrounders/article.php/3619986 part 1]]
* Set up a connection to the outside world and set up internal extensions, [[http://www.voipplanet.com/backgrounders/article.php/3622036 part 2]]
* Configure outbound calling, [[http://www.voipplanet.com/backgrounders/article.php/3623521 Part 3]]
* Voicemail, [[http://www.voipplanet.com/backgrounders/article.php/3624946 Part 4]]
* Playing Asterisk .gsm files, [[http://www.voipplanet.com/backgrounders/article.php/3625916 Part 5]]
* Creating our own custom prompts and greetings, [[http://www.voipplanet.com/backgrounders/article.php/3626661 Part 6]]

Help:Contents

2007-09-18T07:33:41Z

WikiSysop: added link to mediawiki help

Please see http://www.mediawiki.org/wiki/Help:Formatting

Setting up a OpenVPN server

2007-09-17T14:21:50Z

WikiSysop: imported from old wiki

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

Setting up a /var partition on software IDE raid1

2007-09-17T14:20:42Z

WikiSysop: imported from old wiki

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.

Setting up a software RAID array

2007-09-17T11:59:43Z

WikiSysop: imported from old wiki

This document will show how to create hard disk mirroring using cheap IDE disks.

This document was written for alpine-1.3.8 or later. It is tested with alpine-1.7.3.

I will setup 2 raid devices, md0 for swap and md1 for data. I use swap on a raid1 for maximum reliability. If you prefer maximum speed, you don't need configure any raid devices 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.

== Loading needed modules ==
Start with loading the ide-disk and raid1 kernel modules. If you use SATA or SCSI disks you will not need the ide-disk module.

modprobe ide-disk
modprobe raid1

Add them to /etc/modules so they get loaded during next reboot.

echo ide-disk >> /etc/modules
echo raid1 >> /etc/modules

== Creating the partitions ==
I will use /dev/hde and /dev/hdg in this document but you will probably use /dev/hda and /dev/hdc. Note that the disks should not be connected on the same IDE bus (sharing the same IDE cable). To find what disks you have available, look in /proc/partitions or look at the /dev/disk* links that the mdev system has created.
~ $ ls -l /dev/disk*
lrwxrwxrwx 1 root root 3 Aug 24 12:49 /dev/disk -> hde
lrwxrwxrwx 1 root root 3 Aug 24 12:49 /dev/disk0 -> hde
lrwxrwxrwx 1 root root 3 Aug 24 12:49 /dev/disk1 -> hdg

Create the partitions using fdisk.

fdisk /dev/hde

I will use 512MB for swap and the rest for /var. My partition table looks like this:
Device Boot Start End Blocks Id System
/dev/hde1 1 992 499936+ fd Linux raid autodetect
/dev/hde2 993 77545 38582712 fd Linux raid autodetect

Remeber to set the type (with 't' in fdisk) to Linux raid autodetect. (fd)

Do the same with your second disk.

fdisk /dev/hdg

Mine looks like this:

Device Boot Start End Blocks Id System
/dev/hdg1 1 992 499936+ fd Linux raid autodetect
/dev/hdg2 993 77545 38582712 fd Linux raid autodetect

== Setting up the raid array
Install mdadm to set up the arrays.

apk_add mdadm

Make the /dev nodes before creating the arrays. [[User:Ncopa|Ncopa]]NOTE:[[User:Ncopa|Ncopa]] This is not necessary with alpine-1.7.3

mknod /dev/md0 b 9 0
mknod /dev/md1 b 9 1

Create the arrays.
mdadm --create -l 1 -n 2 /dev/md0 /dev/hde1 /dev/hdg1
mdadm --create -l 1 -n 2 /dev/md1 /dev/hde2 /dev/hdg2

== Monitorin sync status ==
You should now be able to see the array syncronize by looking at the contents of /proc/mdstat.
~ $ cat /proc/mdstat
Personalities : [raid1]
md1 : active raid1 hdg2[1] hde2[0]
38582592 blocks [2/2] [UU]
[==>..................] resync = 10.5% (4056192/38582592) finish=68.5min speed=8388K/sec

md0 : active raid1 hdg1[1] hde1[0]
499840 blocks [2/2] [UU]

unused devices: <none>

You don't need to wait til it is fully syncronized to continue.

== Saving config ==
Create the /etc/mdadm.conf file so mdadm knows how your raid setup is:
mdadm --detail --scan > /etc/mdadm.conf

To make sure the raid devices start during the next reboot run:
rc_add -s 10 -k mdadm-raid

The ~~-s 10~~ option is to make sure that the raid arrays are started early, before things like lvm and localmount.

Use lbu commit as usual to save configs to usb or floppy.

You should now be able to create swap on /dev/md0 and a filesystem on /dev/md1 using the ~~mkswap~~ and ~~mkfs.*~~ commands.

Comparison with other distros

2007-09-17T11:58:33Z

WikiSysop: imported page from old wiki

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

Alpine Package Keeper

2007-09-17T11:56:27Z

WikiSysop: imported page from old wiki

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

After you booted into Alpine you have a very minimal linux install, so you might want to start installing packages. Use the following command, to install ssh:
% apk_add openssh
As you can see dependencies are automatically pulled in.

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

Installing Alpine

2007-09-17T11:50:29Z

WikiSysop: /* From windows */ fixed link to 7-zip

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

Installing Alpine

2007-09-17T11:47:34Z

WikiSysop: imported page from old wiki

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 [7zip http://www.7-zip.org/]
* 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

Alpine Linux:Documentation

2007-09-17T11:46:45Z

WikiSysop: removed Getting started since the doc is missing

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

* [[Installing Alpine]]
* [[Alpine package management]]
* [[Comparison with Gentoo and Debian]]
* Submitting [[Problem Reports]]

=== Misc. HOWTOS ===
* [[Setting up a software raid1 array]]
* [[Setting up a /var partition on software IDE raid1]]
* [[Setting up a OpenVPN-server with Alpine]]
* [[Setting up Zaptel/Asterisk on Alpine]]
* [[Setting up lm_sensors]]
* [[Native Harddisk Install]]
* [[Installing XUbuntu using Alpine boot floppy]]
* [[Setting up traffic monitoring using rrdtool (and snmp)]]

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

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

* [[Setting up the build environment]]
* [[Creating patches]]
* [[Alpine Configuration Framework Design]] (Why ACF is the way it is)

== 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:Mailing lists

2007-09-17T11:45:15Z

WikiSysop: imported page from old wiki

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

MediaWiki:Sidebar

2007-09-17T11:44:01Z

WikiSysop: remove troubleshooting since it was never used

Alpine Linux:Documentation

2007-09-17T11:42:51Z

WikiSysop: imported page

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

* [[Getting Started]]
* [[Installing Alpine]]
* [[Alpine package management]]
* [[Comparison with Gentoo and Debian]]
* Submitting [[Problem Reports]]

=== Misc. HOWTOS ===
* [[Setting up a software raid1 array]]
* [[Setting up a /var partition on software IDE raid1]]
* [[Setting up a OpenVPN-server with Alpine]]
* [[Setting up Zaptel/Asterisk on Alpine]]
* [[Setting up lm_sensors]]
* [[Native Harddisk Install]]
* [[Installing XUbuntu using Alpine boot floppy]]
* [[Setting up traffic monitoring using rrdtool (and snmp)]]

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

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

* [[Setting up the build environment]]
* [[Creating patches]]
* [[Alpine Configuration Framework Design]] (Why ACF is the way it is)

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

2007-09-17T11:41:00Z

WikiSysop: imported from old wiki

=Fequently Asked Questions=

==General==

=== I have found a bug, where can I report it? ===
From alpine run:
setup-problem-reporting
That will help you set up outgoing mailserver and will configure your email address.
Then you can run ''send-pr'' to submit a bug.

'''TIP:''' If you have problems with the vi editor, try installing nano. Set the environment variable ''EDITOR'' to make send-pr use nano.
apk_add nano
echo "EDITOR=nano" >> /etc/profile
export EDITOR=nano
send-pr

Otherwise its just to send an email to bugs [at] alpinelinux.org. Please make the bug report as specific as possible.

For general tips how to write a good bug reports, see [http://www.chiark.greenend.org.uk/~sgtatham/bugs.html this article].

=== How can I contribute? ===
You can contribute by using the software and give feedback.
You can contribute by helping with the documenting your experiences using this wiki.

Your contributions are highly appreciated.

==Audio==

=== How do I play my .ogg/.mp3 files? ===
First, the sound card should be recognized (you must have /dev/snd/***** files)

sox, mpg321, mpg123, oggplay, etc all use the oss sound driver, while Alpine uses ALSA drivers. So you need to load the snd-pcm-oss compatibility module. While you're at it, you might need aumix to turn up the sound volume

echo snd-pcm-oss >> /etc/modules
modprobe snd-pcm-oss
apk_add aumix sox
aumix (set volume settings)
play really_cool_song.mp3

== Configuration ==

=== How do I set local timezone? ===
Help needed to write this. Meanwhile:
http://leaf.sourceforge.net/doc/buci-tz3.html
http://www.sonoracomm.com/index.php?option=com_content&task=view&id=107&Itemid=32

== Packages ==
=== Can you build an apk package for ...? ===
Yes, I probably can. Please check if your wanted package exist in gentoo portage by searching in http://packages.gentoo.org. Please post a package request on [http://lists.alpinelinux.org/mailman/listinfo/alpine-devel alpine-devel] mailing list and we will look at it.

If there is no Gentoo package, then the best would be to create and ebuild and submit it to http://bugs.gentoo.org. Once your package is in gentoo its very easy to create and maintain the package in Alpine. During special conditions, we might create and maintain this package in the Alpine portage overlay, but its best if it could be officially included in Gentoo.

Currently, packages that require gettext, iconv, java or mono will be rejected for technical reasons. Packages requiring xorg, ruby, python perl, php or will most likely also be rejected but not for technical reasons.

=== How can i build my own package? ===
If you need compile you will need a toolchain to do it for you. Use the [http://dl.alpinelinux.org/alpine/v1.5/buildroot/ alpine-buildroot] as base and set up a Gentoo hardened uclibc [http://www.bulah.com/embeddedgentoo.html chroot].

If you want to create a package that just containins scripts, then you can simply create a tar.gz package and give it a proper name. There is a utlity, [http://apk-tools.sourceforge.net/apk_create.html apk_create], to assist you in creating packages. The [http://apk-tools.sourceforge.net/apk_create.html man page] has details on internals.

Downloads

2007-09-17T11:40:06Z

WikiSysop: Protected "Downloads" [edit=sysop:move=sysop]

== Stable Releases ==
Even numbered releases (eg, 1.6.x) are believed to be stable and ready for use in production environments. Minor number increments in stable releases (for example, from 1.6.2 to 1.6.3) will be bug fixes and security updates only.

=== Alpine 1.6 ===
{|
|[http://dev.alpinelinux.org/alpine/v1.6/ Master mirror] (low bandwidth)
|[http://dev.alpinelinux.org/alpine/v1.6/iso ISO]
|[http://dev.alpinelinux.org/alpine/v1.6/usbdrive USB]
|-
|[http://dl.alpinelinux.org/alpine/v1.6/ USA mirror]
|[http://dl.alpinelinux.org/alpine/v1.6/iso ISO]
|[http://dl.alpinelinux.org/alpine/v1.6/usbdrive USB]
|}

== Development Releases ==
Odd numbered releases (eg, 1.7.x) are development releases. They should be used for testing, learning, and development only. Minor number increments in development versions (eg, 1.7.0 to 1.7.1) may break things, be warned.

=== Alpine 1.7 ===
{|
|[http://dev.alpinelinux.org/alpine/v1.7/ Master mirror] (low bandwidth)
|[http://dev.alpinelinux.org/alpine/v1.7/iso ISO]
|[http://dev.alpinelinux.org/alpine/v1.7/usbdrive USB]
|-
|[http://dl.alpinelinux.org/alpine/v1.7/ USA mirror]
|[http://dl.alpinelinux.org/alpine/v1.7/iso ISO]
|[http://dl.alpinelinux.org/alpine/v1.7/usbdrive USB]
|}

== Old Releases ==
=== Alpine 1.5 ===
{|
|[http://dev.alpinelinux.org/alpine/v1.5/ Master mirror] (low bandwidth)
|[http://dev.alpinelinux.org/alpine/v1.5/iso ISO]
|[http://dev.alpinelinux.org/alpine/v1.5/usbdrive USB]
|-
|[http://dl.alpinelinux.org/alpine/v1.5/ USA mirror]
|[http://dl.alpinelinux.org/alpine/v1.5/iso ISO]
|[http://dl.alpinelinux.org/alpine/v1.5/usbdrive USB]
|}

=== Alpine 1.4 ===
{|
|[http://dev.alpinelinux.org/alpine/v1.4/ Master mirror] (low bandwidth)
|[http://dev.alpinelinux.org/alpine/v1.4/iso ISO]
|[http://dev.alpinelinux.org/alpine/v1.4/usbdrive USB]
|-
|[http://dl.alpinelinux.org/alpine/v1.4/ USA mirror]
|[http://dl.alpinelinux.org/alpine/v1.4/iso ISO]
|[http://dl.alpinelinux.org/alpine/v1.4/usbdrive USB]
|}

=== Alpine 1.3 ===
{|
|[http://dev.alpinelinux.org/alpine/v1.3/ Master mirror] (low bandwidth)
|[http://dev.alpinelinux.org/alpine/v1.3/iso ISO]
|[http://dev.alpinelinux.org/alpine/v1.3/usbdrive USB]
|-
|[http://dl.alpinelinux.org/alpine/v1.3/ USA mirror]
|[http://dl.alpinelinux.org/alpine/v1.3/iso ISO]
|[http://dl.alpinelinux.org/alpine/v1.3/usbdrive USB]
|}

* [http://www.alpinelinux.org/downloads/alpine/v0.5/ Alpine 0.5]

== Sources ==

The sources of alpine are stored in subversion. To check out the tree use one of the following commands:

For annonymous access you can use:
svn co svn://svn.alpinelinux.org/alpine-builder/trunk

Which will checkout the alpine-builder directory in the current directory.

== Requirements ==

To be able to actually build packages you need apk-tools, either located [[http://dev.alpinelinux.org/distfiles/ here]] or a debian-package (ubuntu-package, but it is all just shell-script) [[http://dev.alpinelinux.org/~plovs/ here]].

Downloads

2007-09-17T11:38:29Z

WikiSysop: imported and merged "subversion" and "downloads" from old wiki

== Stable Releases ==
Even numbered releases (eg, 1.6.x) are believed to be stable and ready for use in production environments. Minor number increments in stable releases (for example, from 1.6.2 to 1.6.3) will be bug fixes and security updates only.

=== Alpine 1.6 ===
{|
|[http://dev.alpinelinux.org/alpine/v1.6/ Master mirror] (low bandwidth)
|[http://dev.alpinelinux.org/alpine/v1.6/iso ISO]
|[http://dev.alpinelinux.org/alpine/v1.6/usbdrive USB]
|-
|[http://dl.alpinelinux.org/alpine/v1.6/ USA mirror]
|[http://dl.alpinelinux.org/alpine/v1.6/iso ISO]
|[http://dl.alpinelinux.org/alpine/v1.6/usbdrive USB]
|}

== Development Releases ==
Odd numbered releases (eg, 1.7.x) are development releases. They should be used for testing, learning, and development only. Minor number increments in development versions (eg, 1.7.0 to 1.7.1) may break things, be warned.

=== Alpine 1.7 ===
{|
|[http://dev.alpinelinux.org/alpine/v1.7/ Master mirror] (low bandwidth)
|[http://dev.alpinelinux.org/alpine/v1.7/iso ISO]
|[http://dev.alpinelinux.org/alpine/v1.7/usbdrive USB]
|-
|[http://dl.alpinelinux.org/alpine/v1.7/ USA mirror]
|[http://dl.alpinelinux.org/alpine/v1.7/iso ISO]
|[http://dl.alpinelinux.org/alpine/v1.7/usbdrive USB]
|}

== Old Releases ==
=== Alpine 1.5 ===
{|
|[http://dev.alpinelinux.org/alpine/v1.5/ Master mirror] (low bandwidth)
|[http://dev.alpinelinux.org/alpine/v1.5/iso ISO]
|[http://dev.alpinelinux.org/alpine/v1.5/usbdrive USB]
|-
|[http://dl.alpinelinux.org/alpine/v1.5/ USA mirror]
|[http://dl.alpinelinux.org/alpine/v1.5/iso ISO]
|[http://dl.alpinelinux.org/alpine/v1.5/usbdrive USB]
|}

=== Alpine 1.4 ===
{|
|[http://dev.alpinelinux.org/alpine/v1.4/ Master mirror] (low bandwidth)
|[http://dev.alpinelinux.org/alpine/v1.4/iso ISO]
|[http://dev.alpinelinux.org/alpine/v1.4/usbdrive USB]
|-
|[http://dl.alpinelinux.org/alpine/v1.4/ USA mirror]
|[http://dl.alpinelinux.org/alpine/v1.4/iso ISO]
|[http://dl.alpinelinux.org/alpine/v1.4/usbdrive USB]
|}

=== Alpine 1.3 ===
{|
|[http://dev.alpinelinux.org/alpine/v1.3/ Master mirror] (low bandwidth)
|[http://dev.alpinelinux.org/alpine/v1.3/iso ISO]
|[http://dev.alpinelinux.org/alpine/v1.3/usbdrive USB]
|-
|[http://dl.alpinelinux.org/alpine/v1.3/ USA mirror]
|[http://dl.alpinelinux.org/alpine/v1.3/iso ISO]
|[http://dl.alpinelinux.org/alpine/v1.3/usbdrive USB]
|}

* [http://www.alpinelinux.org/downloads/alpine/v0.5/ Alpine 0.5]

== Sources ==

The sources of alpine are stored in subversion. To check out the tree use one of the following commands:

For annonymous access you can use:
svn co svn://svn.alpinelinux.org/alpine-builder/trunk

Which will checkout the alpine-builder directory in the current directory.

== Requirements ==

To be able to actually build packages you need apk-tools, either located [[http://dev.alpinelinux.org/distfiles/ here]] or a debian-package (ubuntu-package, but it is all just shell-script) [[http://dev.alpinelinux.org/~plovs/ here]].

MediaWiki:Sidebar

2007-09-17T11:35:24Z

WikiSysop: removed "subversion" and "trac"

Older News

2007-09-17T05:56:29Z

WikiSysop: Protected "News" [edit=sysop:move=sysop]

Alpine Linux:Todo

2007-09-15T14:51:27Z

WikiSysop: imported from old wiki

== Short Term ==
This is a list of things need to be done in close future:

=== Busybox ===
* diff: support for -n option (needed by rcs) NOTE: might not be needed! use rcs from openbsd instead.
* ssmtp applet (needed by send-pr/sendbug)
* mktemp: -p and -t option (needed by vserver)
* grep: support for -x option (needed by vserver)
* /bin/sh: support for -l option (needed by vserver) (fixed)
* add support for start-stop-daemon -R/--retry (needed by postgresql)

=== for 1.8 ===
* test vserver and decide if we will continue support it (done)
* vserver install docs (partly done)
* rename vmlinuz to bzImage and rename modules.cmg to modloop.cmg (done)
* create a dir struc for kernel and related files: (done)
kernels/generic/bzImage
kernels/generic/modloop.cmg
kernels/generic/initramfs/
kernels/generic/bootimages/
kernels/vs/bzImage
kernels/vs/modloop.cmg
kernels/vs/initramfs/
kernels/vs/bootimages/
...
* Create a mini kernel with just host bridge drivers (pci), net drivers and disk stuff. (done)
* Create a minimal iso image for install to disk from network.
* Create a package with keyboard layout files.
* setup-kbd script that selects keyboard and copies it to /etc/somewhere (so it gets committed to floppy)
* move packages/aports directory to aports/. There will never be more then apks for now. Create the filelist dynamically.
* run mdev in initramfs image and remove ash if possible.
* port openbsd's sendbug (in progress)
* port openbsd's rcs (suspended until uclibc issues are resolved)

=== Website/hosting ===
* Fix webinterface to GNAT's bugtracker.
* Create a HOWTO section where people can post articles on how they set up specific configurations.
* Change the stylesheets to give the website a more unique touch. (low priority)
* new wiki site using haserl

=== Build Environment ===
* Scripts to automatic download latest buildroot, packages and build scripts and build an iso. Run this script every night and send the status of the process somwhere.

=== apk-tools ===
* integrate/fix gzsign and sign packages
* release apk-tools-1.0
* apk-tools-2.0 (C version)

== Long Term ==
Items needed to be done in longer term:

* port openbsd spamd and integrate with ipsets/shorewall

=== Installer ===
* Some kind of modularized installer that permits users to create their own installers. Something that read "pre-seeds" or configure Alpine boxes from pre-generated textfiles. The software generating those setup config textfiles (pre-seeds) could be windows executables (wizards) that spits out a textfile to a floppy or a floppy image.

=== Web configuration ===
* Create a framework, using AJAX and the MVC (model-view-contoller) strategy. Something that could be re-used by other projects like [http://www.leaf-project.org LEAF].
* create webconf modules

=== Harddisk support ===
Those items are low priority, but would be nice to have.

* Support for full harddisk installation (run everything from harddisk)
* DONE: Support for hybrid harddisk installations (run OS from USB drive/cdrom and mount /var on disk(s))
* DONE: Support for raid (hardware and software)

=== Documentation ===
* Ship some documentation on the CD
* A list of commands that are unique for Alpine (like lbu_add, lbu_commit, etc... - this is what a "newbie" linux user asked for)

Alpine Linux:Ideas

2007-09-15T14:50:42Z

WikiSysop: imported from old wiki

'''This is the place to put feature requests and share ideas for Alpine.''' From these we'll update our [[Roadmap]], which in turn populates our [[To-do]] list. Discussions of ideas should probably take place on the Alpine-Devel [[Mailing_lists | mailing list]], but feel free to use the discussion function of the wiki too.

=== User documentation ===
It would be nice with specific howto's. Not only the basics (setting ut a NAT'ing gateway) but some really different, wierd stuff, like setting up encrypted partitions, storing configs on subversion, connect a webcamera to a cgi script, things that you cannot do on the standard SOHO routers.

=== Signing packages ===
Make a port of the freebsd pkg_sign, stripping out everything but the x509 part. Using this will allow us to ship a certificate with the distro and make it possible to verify that updates really comes from the same (or authorized) origin.

It is possible to sign single packages or the INDEX file, or any other file, as long as it is gzipped.

=== Booting from net ===
Provide ip address and remote hostname as kernel parameter and run directly from network. The only thing needed for this would probably be a special initramfs image.

=== Local backups of the configs ===
There are lot of ways to do this. We should support a few.
Things that is really interesting is stoing them on a subversion repository.

[http://www.gnu.org/software/rcs/rcs.html rcs] might be an alternative.

=== Webconfig framework ===
I have no idea how this should be done. But i think we should support and encourage ssl from the very beginning.

on 16 Aug 2006, Natanael posted to the mailing list:

Some ideas for the webconf.

1. Log changes.

Log changes and add a posibility to add user comments. Something like
blogging. You can add comments.

Log could look like:

<id> <when> <who> <what> <where> <comment>

For example:
admin changed ip of eth0 from 192.168.0.100 to 192.168.0.1 "Just testing"
admin added firewall rule <bla bla> "Disallow web traffic thats not proxied"
admin changd password for root
ncopa removed static ip from DHCP server "This device is no longer used"

2. User comments on the web pages.

ncopa <date>
The static routes are there as a workaroud for ....

admin <date>
Note that this is the second DHCP server so don't change the ip range withough checking rtr-02

Regarding item 1, busybox diff is built into alpine. The model could run a diff from the previous config file and the current config file; also noting ip addr / timestamp / username for the person making the change. This has the very interesting possiblity of rollbacks - playing a diff "backwards" (patch -R) could allow for undo/redo within the web framework.

Item 2 is just another text file for the controller to manage.

=== Running from read only media ===
One of the concepts are that the media from where the sytem loads should be readonly. We could have a check in the boot process if media is readonly. If it is not, refuse to start. This is specially good for USB sticks, where a USB stick that is possible to physically write protect would be required.

=== Installer templates ===
Have some "templates", or presseeds or something similar so you can easily install a lot of alpine boxes.

=== Autorun program/script on CD ===
Could be nice with an autorun program that will be executed when cd is inserted in a windows computer. It could have a menu with the following options:
* create boot floppy for CDROM
* create boot floppy for USB
* install Alpine on an USB drive

=== Package database ===
A database with all the packages and their status.

Possibility to rate/vote packages? Some easy way for users to give feedback on what packages they think we should focus on.

=== Version number on floppy ===
As Alpine progresses, the data stored no the floppy needs to be converted from version tho the other. It would be nice to be able to see what version of Alpine the data on the floppy belongs to. Then the conversion script will have to do less magic to upgrade the data.

=== SSL signed floppies ===
Make it possible to sign/encrypt the data on the floppies. the floppies contain the most valuable data of alpine. It would be nice if setup-alpine would ask if I want to create a new key, or import an existing key and then encrypt or sign the contents of the floppy with it. On a reboot the admin would have to give the password for the system to run. Since mission critical systems have an UPS, this should not really be a problem.

=== Packages we would like to add or investigate to be added, to alpine ===

To be used with Asterisk:
* [[http://freshmeat.net/projects/zgsmplay/ zgsmplay]], see also [[http://www.voipplanet.com/backgrounders/article.php/3625916 here]] - This package will give the possibility to listen to the gsm (sound-)files on the server.

Maybe later:
* Cherokee (in unstable Gentoo atm)

Comment: See [[FAQ]]

=== Installer for headless installs ===
Installer that would create a bootable iso/usbdrive + a working config. Could be written in wxWidgets so it could be run from either Windows or Linux.

MediaWiki:Sidebar

2007-09-15T14:50:16Z

WikiSysop: removed "Donations"

Older News

2007-09-15T14:48:49Z

WikiSysop: imported from old wiki

MediaWiki:Sidebar

2007-09-15T14:41:32Z

WikiSysop:

MediaWiki:Sidebar

2007-09-15T14:40:30Z

WikiSysop:

MediaWiki:Sidebar

2007-09-15T14:40:11Z

WikiSysop:

MediaWiki:Sidebar

2007-09-15T14:36:54Z

WikiSysop: switching back

MediaWiki:Sidebar

2007-09-15T14:29:40Z

WikiSysop: imported sidebar from old wiki