https://wiki.alpinelinux.org/w/api.php?action=feedcontributions&feedformat=atom&user=ForthAlpine Linux - User contributions [en]2026-04-30T18:14:30ZUser contributionsMediaWiki 1.40.0https://wiki.alpinelinux.org/w/index.php?title=Xen_Dom0&diff=15516Xen Dom02018-11-29T19:04:52Z<p>Forth: </p>
<hr />
<div>This guide will show you how to perform a Xen Dom0 install on a HDD, so you can have your Dom0. The first step is to perform a normal HDD install of Alpine Linux, which can be accomplished following the guide [[Install to disk]]. Once the install is finished, and you have rebooted into your new system, it's time to install the Xen packages:<br />
<br />
<pre><br />
# apk add xen xen-hypervisor seabios ovmf<br />
</pre><br />
<br />
seabios and ovmf provide bios and uefi firmwares.<br />
<br />
This will install Xen Hypervisor, xl cli command and all the required packages. The next step is to modify your extlinux.cfg and add an entry to boot Xen:<br />
<br />
Normal boot:<br />
<br />
<pre><br />
LABEL xen<br />
KERNEL /boot/mboot.c32<br />
APPEND /boot/xen.gz --- /boot/grsec root=UUID=<YOUR-DISK-UUID> modules=ext4 --- /boot/grsec.gz<br />
</pre><br />
<br />
Serial console boot:<br />
<pre><br />
LABEL xen<br />
KERNEL /boot/mboot.c32<br />
APPEND /boot/xen.gz com1=115200,8n1 console=com1 --- /boot/grsec root=UUID=<YOUR-DISK-UUID> modules=ext4 --- /boot/grsec.gz<br />
</pre><br />
<br />
{{Note|<nowiki>remember to change <YOUR-DISK-UUID> with the UUID of your boot disk (you can copy it from the normal Alpine Linux boot entry)</nowiki>}}<br />
<br />
com1=115200,8n1 console=com1 redirect xen and dom0 to a physical serial port, handy if you want to use a serial null modem cable instead of a keyboard+monitor combo or if your server has an kvm over ip.<br />
<br />
It's also a good idea to check [http://wiki.xen.org/wiki/Xen_Hypervisor_Boot_Options Xen Boot options] and set dom0_mem, dom0_vcpus_pin and dom0_max_vcpus at least.<br />
<br />
The next step is to load the necessary kernel modules for Xen, we will add them to /etc/modules, so they will be loaded automatically on boot:<br />
<br />
<pre><br />
# echo "xen_netback" >> /etc/modules<br />
# echo "xen_blkback" >> /etc/modules<br />
# echo "tun" >> /etc/modules<br />
</pre><br />
<br />
The last step is to configure startup services, we will need udev and xencommons at least to be started on boot:<br />
<br />
<pre><br />
rc-update add xenconsoled<br />
rc-update add xendomains<br />
rc-update add xenqemu<br />
rc-update add xenstored<br />
</pre><br />
<br />
Ok, now you have a fully functional Xen install, it's time to boot into it.<br />
<br />
<pre><br />
# reboot<br />
</pre><br />
<br />
Also remember to configure at least one network bridge following the [[Bridge]] guide.<br />
<br />
== See also ==<br />
* [[Xen Dom0 on USB or SD]]<br />
<br />
[[Category:Virtualization]]</div>Forthhttps://wiki.alpinelinux.org/w/index.php?title=Xen_Dom0&diff=15515Xen Dom02018-11-29T18:59:27Z<p>Forth: add seabios and ovmf packages</p>
<hr />
<div>This guide will show you how to perform a Xen Dom0 install on a HDD, so you can have your Dom0. The first step is to perform a normal HDD install of Alpine Linux, which can be accomplished following the guide [[Install to disk]]. Once the install is finished, and you have rebooted into your new system, it's time to install the Xen packages:<br />
<br />
<pre><br />
# apk add xen xen-hypervisor seabios ovmf<br />
</pre><br />
<br />
seabios and ovmf provide bios and uefi firmwares.<br />
<br />
This will install Xen Hypervisor and Tools (both xl and xend) and all the required packages. The next step is to modify your extlinux.cfg and add an entry to boot Xen:<br />
<br />
Normal boot:<br />
<br />
<pre><br />
LABEL xen<br />
KERNEL /boot/mboot.c32<br />
APPEND /boot/xen.gz --- /boot/grsec root=UUID=<YOUR-DISK-UUID> modules=ext4 --- /boot/grsec.gz<br />
</pre><br />
<br />
Serial console boot:<br />
<pre><br />
LABEL xen<br />
KERNEL /boot/mboot.c32<br />
APPEND /boot/xen.gz com1=115200,8n1 console=com1 --- /boot/grsec root=UUID=<YOUR-DISK-UUID> modules=ext4 --- /boot/grsec.gz<br />
</pre><br />
<br />
{{Note|<nowiki>remember to change <YOUR-DISK-UUID> with the UUID of your boot disk (you can copy it from the normal Alpine Linux boot entry)</nowiki>}}<br />
<br />
It's also a good idea to check [http://wiki.xen.org/wiki/Xen_Hypervisor_Boot_Options Xen Boot options] and set dom0_mem, dom0_vcpus_pin and dom0_max_vcpus at least.<br />
<br />
The next step is to load the necessary kernel modules for Xen, we will add them to /etc/modules, so they will be loaded automatically on boot:<br />
<br />
<pre><br />
# echo "xen_netback" >> /etc/modules<br />
# echo "xen_blkback" >> /etc/modules<br />
# echo "tun" >> /etc/modules<br />
</pre><br />
<br />
The last step is to configure startup services, we will need udev and xencommons at least to be started on boot:<br />
<br />
<pre><br />
rc-update add xenconsoled<br />
rc-update add xendomains<br />
rc-update add xenqemu<br />
rc-update add xenstored<br />
</pre><br />
<br />
Ok, now you have a fully functional Xen install, it's time to boot into it.<br />
<br />
<pre><br />
# reboot<br />
</pre><br />
<br />
Also remember to configure at least one network bridge following the [[Bridge]] guide.<br />
<br />
== See also ==<br />
* [[Xen Dom0 on USB or SD]]<br />
<br />
[[Category:Virtualization]]</div>Forthhttps://wiki.alpinelinux.org/w/index.php?title=Setting_up_a_software_RAID_array&diff=15339Setting up a software RAID array2018-07-11T12:00:10Z<p>Forth: /* Saving config */</p>
<hr />
<div>[[Category:Storage]]<br />
<br />
There are various forms of RAID: via a hardware RAID controller, via "fake RAID", and "software RAID" using <code>mdadm</code>, which is Linux-only. These instructions only discuss the last form of RAID. Also, it only discusses how to setup a RAID array for arbitrary storage. It is possible to have one's system root {{Path|/}}, or {{Path|/var}}, or swap, or even one's {{Path|/boot}}, on a RAID array. See [[Setting up disks manually]] for more details about doing any of that.<br />
<br />
== RAID Levels ==<br />
<br />
There are several "levels" of RAID to choose between:<br />
<br />
* RAID0 essentially just glues two devices together, making a larger virtual drive. Reads and writes are "striped" between the drives for speed improvements. (That is, your hardware may read from, or write different data to, multiple devices in parallel.) A "device" here is usually a partition of a hard drive.<br />
* RAID1 "mirrors" writes to two devices, for improved safety. Then if one of the devices fails, the data will still be available on the other.<br />
* RAID5 is similar to RAID1, but it uses three devices and provides the space of two of them. The data will be preserved as long as any two of the three devices continue to work.<br />
<br />
There are other RAID levels as well. [http://www.acnc.com/raidedu/0 Here is more explanation of their differences.]<br />
<br />
== Advice ==<br />
<br />
* Your {{Path|/boot}} partition should either not be on RAID, or else be on a RAID1 array, with no further layers of encryption or LVM. (Alpine's default bootloader extlinux can't handle either. Grub2 can handle {{Path|/boot}} being on LVM.) The usual practice is to create a small (32--100 MB) partition for {{Path|/boot}}. That can be a mirrored (RAID1) volume, however this is just for post-init access. That way, when you write a new kernel or bootloader config file to {{Path|/boot}}, it gets written to multiple physical partitions. During the pre-init, bootloader phase, only one of those partitions will be used (and it will be mounted read-only).<br />
* You can put swap on a RAID0 volume, but there doesn't seem to be any good reason to do so. The Linux kernel already knows how to stripe several swap partitions. So you can just devote multiple ordinary (not-residing-on-RAID) partitions to swap, and get the same effect. The downside from doing either of these things is that when one of your disk fails, the system will go down. For better reliability, you can create a mirrored (RAID1) volume and put swap there. This will let your system keep running even when one of the disks fails.<br />
* All partitions in a RAID array should be the same size.<br />
* Don't ever mount just one of the devices in a RAID1 array, even though it "has the same data" as the other. If you mount it r/w, then---even if you don't explicitly write anything to the device---it may get out of sync with the unmounted device, for example because the journal on its filesystem has been updated. If you ever subsequently mount the other device, or the two of them together, your data will likely become corrupted. If you have to do this, make sure you mount your device r/o. Better yet, abandon the device you didn't mount. '''Zero out its RAID headers''', and tell <code>mdadm</code> that that device has failed. Then you can if you like treat it as a new disk, which you can add as a replacement to your (now degraded) original RAID array.<br />
* A mirrored RAID array (level 1 or 5) protects you against hardware failure. It doesn't protect against <code>rm -rf /</code>, software errors, exploits, earthquakes, fire. Don't rely on RAID as a backup strategy.<br />
* Running a mirrored RAID only provides one line of defense against drive failures. It doesn't license you to stop thinking about them. If a device in a RAID 1 starts failing and you aren't aware of it, your data will end up just as silently corrupted as it would be if you were running one drive. You have to watch your logs.<br />
<br />
This document was updated for Alpine 2.4.6.<br />
<br />
== Loading needed modules ==<br />
Start with loading the raid1 kernel module:<br />
<br />
{{Cmd|modprobe raid1}}<br />
<br />
Add it to {{Path|/etc/modules}} so it gets loaded during next reboot:<br />
<br />
{{Cmd|echo raid1 >> /etc/modules}}<br />
<br />
== Creating the partitions ==<br />
<br />
Please read up on [https://raid.wiki.kernel.org/index.php/Partition_Types partition types], and why you should consider using 0xda instead of 0xfd.<br />
<br />
I will use {{Path|/dev/sda}} and {{Path|/dev/sdb}} in this document but your devices may be different. To find what disks you have available, look in {{Path|/proc/partitions}}.<br />
<br />
Create the partitions using fdisk.<br />
<br />
{{Cmd|fdisk /dev/sda}}<br />
<br />
I will create one single partition of type Linux raid autodetect. Use '''n''' in fdisk to create the partition and '''t''' to set type. Logical volumes will be created later. My partition table looks like this ('p' to print partition table):<br />
<br />
Device Boot Start End Blocks Id System<br />
/dev/sda1 1 17753 8388261 fd Linux raid autodetect<br />
<br />
Use '''w''' to '''w'''rite and quit.<br />
Do the same with your second disk.<br />
<br />
{{Cmd|fdisk /dev/sdb}}<br />
<br />
Mine looks like this:<br />
Device Boot Start End Blocks Id System<br />
/dev/sdb1 1 17753 8388261 fd Linux raid autodetect<br />
<br />
Alternately, if your disks are the same size (as they should be, see [[#Advice|above]]) you can copy the partition table from one to the other like this:<br />
<br />
{{Cmd|1=apk add sfdisk<br />
sfdisk -d /dev/sda {{!}} sfdisk /dev/sdb}}<br />
<br />
== Setting up the RAID array ==<br />
Install mdadm to set up the arrays.<br />
<br />
{{Cmd|apk add mdadm}}<br />
<br />
Create the array.<br />
<br />
{{Cmd|1=mdadm --create --level=1 --raid-devices=2 /dev/md0 /dev/sda1 /dev/sdb1}}<br />
<br />
<br />
== Monitoring sync status ==<br />
You should now be able to see the array syncronize by looking at the contents of {{Path|/proc/mdstat}}.<br />
<br />
~ # cat /proc/mdstat <br />
Personalities : [raid1] <br />
md0 : active raid1 sdb1[1] sda1[0]<br />
8388160 blocks [2/2] [UU]<br />
[=========>...........] resync = 45.3% (3800064/8388160) finish=0.3min speed=200003K/sec<br />
<br />
unused devices: <none><br />
<br />
You don't need to wait til it is fully syncronized to continue.<br />
<br />
== Saving config ==<br />
Create the /etc/mdadm.conf file so mdadm knows how your raid setup is:<br />
<br />
{{Cmd|mdadm --detail --scan > /etc/mdadm.conf}}<br />
<br />
To make sure the raid devices start during the next reboot run:<br />
{{Cmd|rc-update add mdadm-raid}}<br />
<br />
To use the raid array in {{Path|/etc/fstab}} at boot, mdadm service must be started at boot level:<br />
{{Cmd|rc-update add mdadm boot}}<br />
{{Cmd|rc-update add mdadm-raid boot}}<br />
<br />
<br />
If you're not running Alpine from a hard disk install, use {{Cmd|lbu commit}} as usual to save your configuration changes to your removable media.<br />
<br />
The raid device {{Path|/dev/md0}} is now ready to be used with [[Setting up Logical Volumes with LVM|LVM]] or mkfs.<br />
<br />
== Adding a RAID after the installation ==<br />
To add a softRAID on an already installed Alpine, you have to start with these 3 steps : <br />
<br />
3. [[Setting_up_a_software_RAID_array#Loading_needed_modules|Loading needed modules]]<br />
<br />
4. [[Setting_up_a_software_RAID_array#Creating_the_partitions|Creating the partitions]]<br />
<br />
5. [[Setting_up_a_software_RAID_array#Setting_up_the_RAID_array|Setting up the RAID array]]<br />
<br />
Then you have to update your initfs with the command mkinitfs.<br />
<br />
1. Be sure {{Path|/etc/mkinitfs/mkinitfs.conf}} contain '''raid''' which should looks like this :<br />
<br />
<code>features="ata base ide scsi usb virtio ext4 lvm raid"</code><br />
<br />
2. Update the initfs by this command<br />
<br />
{{Cmd|mkinitfs -c /etc/mkinitfs/mkinitfs.conf -b /}}<br />
<br />
== More Info on RAID ==<br />
These resources may be helpful:<br />
<br />
* [https://wiki.archlinux.org/index.php/RAID Arch wiki page on RAID]<br />
* [https://wiki.archlinux.org/index.php/Software_RAID_and_LVM Arch wiki page on RAID and LVM]<br />
* [https://wiki.archlinux.org/index.php/Convert_a_single_drive_system_to_RAID Arch wiki page on Converting an existing system to RAID] [http://en.gentoo-wiki.com/wiki/Migrate_to_RAID Gentoo wiki page on the same]<br />
* http://en.gentoo-wiki.com/wiki/RAID/Software<br />
* http://en.gentoo-wiki.com/wiki/Software_RAID_Install<br />
* http://www.gentoo.org/doc/en/gentoo-x86-tipsntricks.xml#software-raid<br />
* http://www.gentoo.org/doc/en/gentoo-x86+raid+lvm2-quickinstall.xml<br />
<br />
* http://yannickloth.be/blog/2010/08/01/installing-archlinux-with-software-raid1-encrypted-filesystem-and-lvm2/<br />
* http://anonscm.debian.org/gitweb/?p=pkg-mdadm/mdadm.git;a=blob_plain;f=debian/FAQ;hb=HEAD Debian MDADM FAQ<br />
* http://tldp.org/FAQ/Linux-RAID-FAQ/x37.html Linux RAID FAQ<br />
* https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Storage_Administration_Guide/ch-raid.html<br />
* http://linux-101.org/howto/arch-linux-software-raid-installation-guide<br />
* https://raid.wiki.kernel.org/index.php/Linux_Raid</div>Forthhttps://wiki.alpinelinux.org/w/index.php?title=KVM&diff=14108KVM2017-10-30T19:48:49Z<p>Forth: </p>
<hr />
<div>[https://www.linux-kvm.org/page/Main_Page KVM] is an open source virtualization solution in a kernel module. KVM can virtualize x86, PowerPC, and S390 guests.<br />
<br />
<br />
= Installing KVM =<br />
It is possible to install just qemu and libvirt for local management <br />
{{Cmd|sudo apk add qemu-system-x86_64 libvirt}}<br />
but most users will probably want libvirt-deamon and/or virt-manager for a GUI.<br />
{{Cmd|sudo apk add libvirt-daemon dbus polkit}}<br />
If you want to use other disk image formats than raw, you need qemu-img<br />
{{Cmd|sudo apk add qemu-img}}<br />
<br />
Enable the KVM kernel module<br />
{{Cmd|sudo modprobe kvm-intel}}<br />
or<br />
{{Cmd|sudo modprobe kvm-amd}}<br />
by defaults kvm use bridge to nat vm, if you want network with the default configuration, you need to load the tun module<br />
{{Cmd|sudo modprobe tun}}<br />
<br />
Add your user to the follwing groups so you can mange the vms<br />
{{Cmd|sudo addgroup user kvm<br />
sudo addgroup user qemu<br />
sudo addgroup user libvirt}}<br />
<br />
Set libvirtd and dbus to start on startup<br />
{{Cmd|sudo rc-update add libvirtd<br />
sudo rc-update add dbus}}<br />
<br />
== Configure PolicyKit ==<br />
In order to use libvirtd to remotely control KVM over ssh PolicyKit needs a .pkla informing it that this is allowed.<br />
Write the following file to /etc/polkit-1/localauthority/50-local.d/50-libvirt-ssh-remote-access-policy.pkla<br />
{{Cmd|<nowiki>[Remote libvirt SSH access]<br />
Identity=unix-group:libvirt<br />
Action=org.libvirt.unix.manage<br />
ResultAny=yes<br />
ResultInactive=yes<br />
ResultActive=yes</nowiki><br />
}}<br />
<br />
[[Category:Virtualization]]</div>Forthhttps://wiki.alpinelinux.org/w/index.php?title=Xen_Dom0&diff=5685Xen Dom02011-09-02T12:22:18Z<p>Forth: </p>
<hr />
<div>So before anything else verify that you can '''reliably''' log into your Alpine box through [[Setting_up_a_ssh-server|SSH]], because with some video chipset (intel in my case) xen will blank your screen so you will have to use SSH.<br />
<br />
Then upgrade your setup to [[Upgrading_to_Edge|Edge/testing]] (as of the date of writing, Xen is only available in Edge). Install Xen:<br />
<br />
{{Cmd|apk add xen}}<br />
<br />
Modify your extlinux.cfg (credits: http://lists.alpinelinux.org/alpine-devel/1406.html)<br />
since video card is not working for now, we will use a serial console:<br />
<br />
<pre><br />
SERIAL 0 115200 <br />
DEFAULT menu.c32<br />
PROMPT 0<br />
MENU TITLE Alpine/Linux Boot Menu<br />
MENU HIDDEN<br />
MENU AUTOBOOT Alpine will be booted automatically in # seconds.<br />
TIMEOUT 50<br />
<br />
LABEL 0<br />
MENU LABEL XEN<br />
KERNEL mboot.c32<br />
APPEND /boot/xen-4.gz iommu=1 dom0_mem=1024M dom0_max_vcpus=2 dom0_vcpus_pin loglvl=all guest_loglvl=all com1=115200,8n1 console=com1 --- /boot/grsec root=UUID=f40e340b-ea49-445b-81c0-4d7104b56662 modules=ext4 console=hvc0 earlyprintk=xen nomodeset --- /boot/grsec.gz<br />
<br />
LABEL 1<br />
MENU LABEL Linux<br />
KERNEL grsec<br />
APPEND initrd=grsec.gz root=UUID=f40e340b-ea49-445b-81c0-4d7104b56662 modules=ext4<br />
<br />
</pre><br />
Of course adapt this accordingly to your setup (UUID, modules, etc).<br />
<br />
Let's start Xen services:<br />
{{Cmd|<br />
apk add xen<br />
apk add udev<br />
rc-service udev start ; rc-service udev-postmount start<br />
rc-service xencommons start<br />
}}<br />
xl should work. If you want "xm" command<br />
{{Cmd|rc-service xend start}}<br />
<br />
So let's install services at boot time :<br />
{{Cmd|<br />
rc-update add udev sysinit<br />
rc-update add udev-postmount default<br />
rc-update add xencommons<br />
rc-update add xend<br />
}}<br />
<br />
since we use a serial line, let'a add a serial console prompt, modify your /etc/inittab accordinly:<br />
<pre><br />
# Put a getty on the serial port<br />
#ttyS0::respawn:/sbin/getty -L ttyS0 115200 vt100<br />
hvc0::respawn:/sbin/getty -L hvc0 115200 vt100<br />
</pre><br />
hvc0 is Xen console output, where we have already redirected the kernel messages.<br />
To switch to Xen console, type three time "Ctrl+a"<br />
<br />
Now you can configure your guest, but before don't forget to load Xen kernel module:<br />
{{Cmd|modprobe xen-gntdev<br />
modprobe xen-gntalloc<br />
modprobe tun<br />
echo "xen-gntdev" >> /etc/modules<br />
echo "xen-gntalloc" >> /etc/modules<br />
echo "tun" >> /etc/modules<br />
}}<br />
Yes, tun is not a Xen module but is needed to create tap interface in Dom0.<br />
Before creating your VM don't forget to create xenbr0 bridge, otherwise Xen will change eth0 into peth0 and eth0 will become a bridge (!):<br />
{{Cmd|<br />
brctl addbr xenbr0<br />
ifconfig xenbr0 up<br />
}}<br />
So now if you want to plug your "real" network card in your bridge: (192.168.1.10 is eth0 ip)<br />
{{Cmd|<br />
ifconfig eth0 0.0.0.0<br />
brctl addif xenbr0 eth0<br />
ifconfig xenbr0 192.168.1.10<br />
}}<br />
<br />
<br />
on going debug:<br />
vi /etc/rc.conf<br />
rc_sys="xen0"<br />
why ?</div>Forthhttps://wiki.alpinelinux.org/w/index.php?title=Xen_Dom0&diff=5684Xen Dom02011-09-02T12:19:30Z<p>Forth: cosmetic</p>
<hr />
<div>So before anything else verify that you can '''reliably''' log into your Alpine box through [[Setting_up_a_ssh-server|SSH]], because with some video chipset (intel in my case) xen will blank your screen so you will have to use SSH.<br />
<br />
Then upgrade your setup to [[Upgrading_to_Edge|Edge/testing]] (as of the date of writing, Xen is only available in Edge). Install Xen:<br />
<br />
{{Cmd|apk add xen}}<br />
<br />
Modify your extlinux.cfg (credits: http://lists.alpinelinux.org/alpine-devel/1406.html)<br />
since video card is not working for now, we will use a serial console:<br />
<br />
<pre><br />
SERIAL 0 115200 <br />
DEFAULT menu.c32<br />
PROMPT 0<br />
MENU TITLE Alpine/Linux Boot Menu<br />
MENU HIDDEN<br />
MENU AUTOBOOT Alpine will be booted automatically in # seconds.<br />
TIMEOUT 50<br />
<br />
LABEL 0<br />
MENU LABEL XEN<br />
KERNEL mboot.c32<br />
APPEND /boot/xen-4.gz iommu=1 dom0_mem=1024M dom0_max_vcpus=2 dom0_vcpus_pin loglvl=all guest_loglvl=all com1=115200,8n1 console=com1 --- /boot/grsec root=UUID=f40e340b-ea49-445b-81c0-4d7104b56662 modules=ext4 console=hvc0 earlyprintk=xen nomodeset --- /boot/grsec.gz<br />
<br />
LABEL 1<br />
MENU LABEL Linux<br />
KERNEL grsec<br />
APPEND initrd=grsec.gz root=UUID=f40e340b-ea49-445b-81c0-4d7104b56662 modules=ext4<br />
<br />
</pre><br />
Of course adapt this accordingly to your setup (UUID, modules, etc).<br />
<br />
Let's start Xen services:<br />
{{Cmd|<br />
apk add xen<br />
apk add udev<br />
rc-service udev start ; rc-service udev-postmount start<br />
rc-service xencommons start<br />
}}<br />
xl should work. If you want "xm" command<br />
{{Cmd|rc-service xend start}}<br />
<br />
So let's install services at boot time :<br />
{{Cmd|<br />
rc-update add udev sysinit<br />
rc-update add udev-postmount default<br />
rc-update add xencommons<br />
rc-update add xend<br />
}}<br />
<br />
since we use a serial line, let'a add a serial console prompt, modify your /etc/inittab accordinly:<br />
{{Cmd|<br />
# Put a getty on the serial port<br />
#ttyS0::respawn:/sbin/getty -L ttyS0 115200 vt100<br />
hvc0::respawn:/sbin/getty -L hvc0 115200 vt100<br />
}}<br />
hvc0 is Xen console output, where we have already redirected the kernel messages.<br />
To switch to Xen console, type three time "Ctrl+a"<br />
<br />
Now you can configure your guest, but before don't forget to load Xen kernel module:<br />
{{Cmd|modprobe xen-gntdev<br />
modprobe xen-gntalloc<br />
modprobe tun<br />
echo "xen-gntdev" >> /etc/modules<br />
echo "xen-gntalloc" >> /etc/modules<br />
echo "tun" >> /etc/modules<br />
}}<br />
Yes, tun is not a Xen module but is needed to create tap interface in Dom0.<br />
Before creating your VM don't forget to create xenbr0 bridge, otherwise Xen will change eth0 into peth0 and eth0 will become a bridge (!):<br />
{{Cmd|<br />
brctl addbr xenbr0<br />
ifconfig xenbr0 up<br />
}}<br />
So now if you want to plug your "real" network card in your bridge: (192.168.1.10 is eth0 ip)<br />
{{Cmd|<br />
ifconfig eth0 0.0.0.0<br />
brctl addif xenbr0 eth0<br />
ifconfig xenbr0 192.168.1.10<br />
}}<br />
<br />
<br />
on going debug:<br />
vi /etc/rc.conf<br />
rc_sys="xen0"<br />
why ?</div>Forthhttps://wiki.alpinelinux.org/w/index.php?title=Xen_Dom0&diff=5683Xen Dom02011-09-02T11:50:35Z<p>Forth: clean up</p>
<hr />
<div>So before anything else verify that you can '''reliably''' log into your Alpine box through [[Setting_up_a_ssh-server|SSH]], because with some video chipset (intel in my case) xen will blank your screen so you will have to use SSH.<br />
<br />
Then upgrade your setup to [[Upgrading_to_Edge|Edge/testing]] (as of the date of writing, Xen is only available in Edge). Install Xen:<br />
<br />
{{Cmd|apk add xen}}<br />
<br />
Modify your extlinux.cfg (credits: http://lists.alpinelinux.org/alpine-devel/1406.html)<br />
since video card is not working for now, we will use a serial console:<br />
<br />
<pre><br />
SERIAL 0 115200 <br />
DEFAULT menu.c32<br />
PROMPT 0<br />
MENU TITLE Alpine/Linux Boot Menu<br />
MENU HIDDEN<br />
MENU AUTOBOOT Alpine will be booted automatically in # seconds.<br />
TIMEOUT 50<br />
<br />
LABEL 0<br />
MENU LABEL XEN<br />
KERNEL mboot.c32<br />
APPEND /boot/xen-4.gz iommu=1 dom0_mem=1024M dom0_max_vcpus=2 dom0_vcpus_pin loglvl=all guest_loglvl=all com1=115200,8n1 console=com1 --- /boot/grsec root=UUID=f40e340b-ea49-445b-81c0-4d7104b56662 modules=ext4 console=hvc0 earlyprintk=xen nomodeset --- /boot/grsec.gz<br />
<br />
LABEL 1<br />
MENU LABEL Linux<br />
KERNEL grsec<br />
APPEND initrd=grsec.gz root=UUID=f40e340b-ea49-445b-81c0-4d7104b56662 modules=ext4<br />
<br />
</pre><br />
Of course adapt this accordingly to your setup (UUID, modules, etc).<br />
<br />
Let's start Xen services:<br />
{{Cmd|<br />
apk add xen<br />
apk add udev<br />
rc-service udev start ; rc-service udev-postmount start<br />
rc-service xencommons start<br />
}}<br />
xl should work. If you want "xm" command<br />
{{Cmd|rc-service xend start}}<br />
<br />
So let's install services at boot time :<br />
{{Cmd|<br />
rc-update add udev sysinit<br />
rc-update add udev-postmount default<br />
rc-update add xencommons<br />
rc-update add xend<br />
}}<br />
<br />
since we use a serial line, let'a add a serial console prompt, modify your /etc/inittab accordinly:<br />
<br />
# Put a getty on the serial port<br />
#ttyS0::respawn:/sbin/getty -L ttyS0 115200 vt100<br />
hvc0::respawn:/sbin/getty -L hvc0 115200 vt100<br />
<br />
hvc0 is Xen console output, where we have already redirected the kernel messages.<br />
To switch to Xen console, type three time "Ctrl+a"<br />
<br />
Now you can configure your guest, but before don't forget to load Xen kernel module:<br />
{{Cmd|modprobe xen-gntdev<br />
modprobe xen-gntalloc<br />
modprobe tun<br />
echo "xen-gntdev" >> /etc/modules<br />
echo "xen-gntalloc" >> /etc/modules<br />
echo "tun" >> /etc/modules<br />
}}<br />
Yes, tun is not a Xen module but is needed to create tap interface in Dom0.<br />
Before creating your VM don't forget to create xenbr0 bridge, otherwise Xen will change eth0 into peth0 and eth0 will become a bridge (!):<br />
{{Cmd|<br />
brctl addbr xenbr0<br />
ifconfig xenbr0 up<br />
}}<br />
So now if you want to plug your "real" network card in your bridge: (192.168.1.10 is eth0 ip)<br />
{{Cmd|<br />
ifconfig eth0 0.0.0.0<br />
brctl addif xenbr0 eth0<br />
ifconfig xenbr0 192.168.1.10<br />
}}<br />
<br />
<br />
on going debug:<br />
vi /etc/rc.conf<br />
rc_sys="xen0"<br />
why ?</div>Forthhttps://wiki.alpinelinux.org/w/index.php?title=Xen_Dom0&diff=5682Xen Dom02011-09-02T05:46:04Z<p>Forth: network tips</p>
<hr />
<div>So before anything else verify that you can '''reliably''' log into your Alpine box through [[Setting_up_a_ssh-server|SSH]], because with some video chipset (intel in my case) xen will blank your screen so you will have to use SSH.<br />
<br />
Then upgrade your setup to [[Upgrading_to_Edge|Edge/testing]] (as of the date of writing, Xen is only available in Edge). Install Xen:<br />
<br />
{{Cmd|apk add xen}}<br />
<br />
Modify your extlinux.cfg (credits: http://lists.alpinelinux.org/alpine-devel/1406.html)<br />
since video card is not working for now, we will use a serial console:<br />
<br />
<pre><br />
SERIAL 0 115200 <br />
DEFAULT menu.c32<br />
PROMPT 0<br />
MENU TITLE Alpine/Linux Boot Menu<br />
MENU HIDDEN<br />
MENU AUTOBOOT Alpine will be booted automatically in # seconds.<br />
TIMEOUT 50<br />
LABEL 0<br />
MENU DEFAULT<br />
MENU LABEL Linux 2.6.38.8-vs2.3.0.37-rc17<br />
KERNEL vmlinuz-2.6.38.8-vs2.3.0.37-rc17<br />
APPEND initrd=initramfs-2.6.38.8-vs2.3.0.37-rc17 root=UUID=f40e340b-ea49-445b-81c0-4d7104b56662 modules=sd-mod,usb-storage,ext4 quiet<br />
<br />
LABEL 1<br />
MENU LABEL Linux 2.6.36.3-scst<br />
KERNEL vmlinuz-2.6.36.3-scst<br />
APPEND initrd=initramfs-2.6.36.3-scst root=UUID=f40e340b-ea49-445b-81c0-4d7104b56662 modules=sd-mod,usb-storage,ext4 quiet<br />
<br />
LABEL 2<br />
MENU LABEL Linux 2.6.38.8-grsec<br />
KERNEL vmlinuz-2.6.38.8-grsec<br />
APPEND initrd=initramfs-2.6.38.8-grsec root=UUID=f40e340b-ea49-445b-81c0-4d7104b56662 modules=sd-mod,usb-storage,ext4 quiet<br />
<br />
LABEL 3<br />
MENU LABEL XEN<br />
KERNEL mboot.c32<br />
APPEND /boot/xen-4.gz loglvl=all guest_loglvl=all com1=115200,8n1 console=com1 dom0_mem=256M --- /boot/vmlinuz-grsec root=UUID=f40e340b-ea49-445b-81c0-4d7104b56662 modules=sd-mod,usb-storage,ext4 console=hvc0 earlyprintk=xen nomodeset --- /boot/initramfs-grsec<br />
</pre><br />
Of course replace root=UUID= with '''your''' UUID in yours.<br />
<br />
xl info won't work<br />
<br />
Start xecommons:<br />
<pre><br />
alpine:/boot# /etc/init.d/xencommons start<br />
Starting xenstored...FATAL: Failed to open evtchn device: No such file or directory<br />
</pre><br />
well this will fail but xl info will work anyway<br />
<br />
Oh but wait, evtchn device is built in the kernel, so why is there no /dev/xen/evtch file ?<br />
let's start udev ! ;)<br />
{{Cmd|rc-service udev start}}<br />
<br />
That's all folks !<br />
<br />
on going debug:<br />
vi /etc/rc.conf<br />
rc_sys="xen0"<br />
why ?<br />
<br />
<br />
Commands recap:<br />
{{Cmd|<br />
apk add xen<br />
apk add udev<br />
rc-service udev start ; rc-service udev-postmount start<br />
rc-service xencommons start<br />
}}<br />
If you want "xm" command<br />
{{Cmd|rc-service xend start}}<br />
<br />
So let's install services at boot time :<br />
{{Cmd|<br />
rc-update add udev sysinit<br />
rc-update add udev-postmount default<br />
rc-update add xencommons<br />
rc-update add xend<br />
}}<br />
<br />
since we use a serial line, let'a add a serial console prompt, modify your /etc/inittab accordinly:<br />
<br />
# Put a getty on the serial port<br />
#ttyS0::respawn:/sbin/getty -L ttyS0 115200 vt100<br />
hvc0::respawn:/sbin/getty -L hvc0 115200 vt100<br />
<br />
hvc0 is Xen console output, where we have already redirected the kernel messages.<br />
To switch to Xen console, type three time "Ctrl+a"<br />
<br />
Now you can configure your guest, but before don't forget to load Xen kernel module:<br />
{{Cmd|modprobe xen-gntdev<br />
modprobe xen-gntalloc<br />
modprobe tun<br />
echo "xen-gntdev" >> /etc/modules<br />
echo "xen-gntalloc" >> /etc/modules<br />
echo "tun" >> /etc/modules<br />
}}<br />
Yes, tun is not a Xen module but is needed to create tap interface in Dom0.<br />
Before creating your VM don't forget to create xenbr0 bridge, otherwise Xen will change eth0 into peth0 and eth0 will become a bridge (!):<br />
{{Cmd|<br />
brctl addbr xenbr0<br />
ifconfig xenbr0 up<br />
}}<br />
So now if you want to plug your "real" network card in your bridge: (192.168.1.10 is eth0 ip)<br />
{{Cmd|<br />
ifconfig eth0 0.0.0.0<br />
brctl addif xenbr0 eth0<br />
ifconfig xenbr0 192.168.1.10<br />
}}</div>Forthhttps://wiki.alpinelinux.org/w/index.php?title=Install_to_disk&diff=5674Install to disk2011-08-30T19:24:04Z<p>Forth: setup-alpine configures apk repositories</p>
<hr />
<div>{{Note|This document covers 2.x.x release.}}<br />
For 1.8.x and older please see [[Native Harddisk Install 1.6]]<br />
<br />
== Installation ==<br />
Run ''setup-alpine'' to configure the keyboard, hostname and networking.<br />
<br />
{{Cmd|setup-alpine}}<br />
<br />
Create partitions with fdisk. <br />
<br />
{{Cmd|fdisk /dev/sda}}<br />
<br />
You should have 2 partitions: /dev/sda1 as "Linux" (type 83) and /dev/sda2 as "linux swap" (type 82). The /dev/sda1 must be bootable (command "a" within fdisk).<br />
<br />
Install needed programs for the setup <br />
<br />
{{Cmd|apk add e2fsprogs syslinux mkinitfs}}<br />
<br />
Create filesystem and swap <br />
<br />
{{Cmd|mkfs.ext4 /dev/sda1<br />
mkswap /dev/sda2}}<br />
<br />
Mount file-system <br />
<br />
{{Cmd|mount -t ext4 /dev/sda1 /mnt}}<br />
<br />
Clone the current running config created by setup-alpine (hostname, networking root password)<br />
<br />
{{Cmd|<nowiki>lbu package - | tar -C /mnt -zx</nowiki>}}<br />
<br />
Install base packages on harddisk<br />
<br />
{{Cmd|<nowiki>apk add --root=/mnt --initdb $(cat /etc/apk/world)</nowiki>}}<br />
<br />
Append the / and swap to fstab:<br />
{{Cmd|echo -e "/dev/sda1 / ext4 defaults 1 1" &gt;&gt; /mnt/etc/fstab<br />
echo -e "/dev/sda2 none swap sw 0 0" &gt;&gt; /mnt/etc/fstab}}<br />
<br />
Configure the boot loader, extlinux. We use the provided syslinux as base.<br />
<br />
{{Cmd|cp /media/cdrom/syslinux.cf /mnt/boot/extlinux.conf<br />
vi /mnt/boot/extlinux.conf}}<br />
<br />
It should contain something like: <br />
timeout 20<br />
prompt 1<br />
default grsec<br />
label grsec<br />
kernel /boot/grsec<br />
append initrd=/boot/grsec.gz root=/dev/sda1 modules=ext4 quiet<br />
<br />
Install the bootloader:<br />
{{Cmd|extlinux -i /mnt/boot}}<br />
<br />
Install syslinux bootloader at the beginning of the MBR so its bootable (note that its sda and not sda1)<br />
<br />
{{Cmd|<nowiki>dd if=/usr/share/syslinux/mbr.bin of=/dev/sda</nowiki>}}<br />
<br />
Unmount, remove cdrom, and reboot. (If you can't eject, just remove it manually as the machine reboots) <br />
<br />
{{Cmd|umount /mnt<br />
umount /.modloop<br />
eject <br />
reboot}}<br />
<br />
After reboot, you should be able to log in as root with the password you created in <tt>setup-alpine</tt>.</div>Forthhttps://wiki.alpinelinux.org/w/index.php?title=Install_to_disk&diff=5673Install to disk2011-08-30T19:22:56Z<p>Forth: /* Installation */</p>
<hr />
<div>{{Note|This document covers 2.x.x release.}}<br />
For 1.8.x and older please see [[Native Harddisk Install 1.6]]<br />
<br />
== Installation ==<br />
Run ''setup-alpine'' to configure the keyboard, hostname and networking.<br />
<br />
{{Cmd|setup-alpine}}<br />
<br />
Create partitions with fdisk. <br />
<br />
{{Cmd|fdisk /dev/sda}}<br />
<br />
You should have 2 partitions: /dev/sda1 as "Linux" (type 83) and /dev/sda2 as "linux swap" (type 82). The /dev/sda1 must be bootable (command "a" within fdisk).<br />
<br />
Install needed programs for the setup <br />
<br />
{{Cmd|apk add e2fsprogs syslinux mkinitfs}}<br />
<br />
Create filesystem and swap <br />
<br />
{{Cmd|mkfs.ext4 /dev/sda1<br />
mkswap /dev/sda2}}<br />
<br />
Mount file-system <br />
<br />
{{Cmd|mount -t ext4 /dev/sda1 /mnt}}<br />
<br />
Clone the current running config created by setup-alpine (hostname, networking root password)<br />
<br />
{{Cmd|<nowiki>lbu package - | tar -C /mnt -zx</nowiki>}}<br />
<br />
Install base packages on harddisk<br />
<br />
{{Cmd|<nowiki>apk add --root=/mnt --initdb $(cat /etc/apk/world)</nowiki>}}<br />
<br />
Create the repositories list. In this example we use the cdrom as repository:<br />
<br />
{{Cmd|mkdir -p /mnt/etc/apk<br />
echo "/media/cdrom/packages/core" >> /mnt/etc/apk/repositories<br />
echo "/media/cdrom/packages/extra" >> /mnt/etc/apk/repositories}}<br />
<br />
Append the / and swap to fstab:<br />
{{Cmd|echo -e "/dev/sda1 / ext4 defaults 1 1" &gt;&gt; /mnt/etc/fstab<br />
echo -e "/dev/sda2 none swap sw 0 0" &gt;&gt; /mnt/etc/fstab}}<br />
<br />
Configure the boot loader, extlinux. We use the provided syslinux as base.<br />
<br />
{{Cmd|cp /media/cdrom/syslinux.cf /mnt/boot/extlinux.conf<br />
vi /mnt/boot/extlinux.conf}}<br />
<br />
It should contain something like: <br />
timeout 20<br />
prompt 1<br />
default grsec<br />
label grsec<br />
kernel /boot/grsec<br />
append initrd=/boot/grsec.gz root=/dev/sda1 modules=ext4 quiet<br />
<br />
Install the bootloader:<br />
{{Cmd|extlinux -i /mnt/boot}}<br />
<br />
Install syslinux bootloader at the beginning of the MBR so its bootable (note that its sda and not sda1)<br />
<br />
{{Cmd|<nowiki>dd if=/usr/share/syslinux/mbr.bin of=/dev/sda</nowiki>}}<br />
<br />
Unmount, remove cdrom, and reboot. (If you can't eject, just remove it manually as the machine reboots) <br />
<br />
{{Cmd|umount /mnt<br />
umount /.modloop<br />
eject <br />
reboot}}<br />
<br />
After reboot, you should be able to log in as root with the password you created in <tt>setup-alpine</tt>.</div>Forthhttps://wiki.alpinelinux.org/w/index.php?title=Installation&diff=5672Installation2011-08-30T19:14:46Z<p>Forth: /* Installation Handbook */</p>
<hr />
<div>The following information will assist you with the installation of Alpine Linux.<br />
[[Image:hdd_mount.png|left|link=]]<br />
<br /><br />
<br />
= Installation Quick-Start in 3 Easy Steps =<br />
<div style="float:left; font-size:30px; font-weight:bold;"><br />
1st<br />
</div><br />
<div style="margin-left:65px; background-color:#EDF2F2; border-style:solid; border-color:#6F7C91; border-width:0px; border-left-width:5px; min-height:55px; padding:5px;"><br />
[http://alpinelinux.org/downloads Download] the latest stable-release ISO.<br />
</div><br />
<br />
<br />
<div style="float:left; font-size:30px; font-weight:bold;"><br />
2nd<br />
</div><br />
<div style="margin-left:65px; background-color:#E0E9E9; border-style:solid; border-color:#606A82; border-width:0px; border-left-width:5px; min-height:55px; padding:5px;"><br />
Burn the ISO onto a blank CD using your favorite CD burning software.<br />
</div><br />
<br />
<br />
<div style="float:left; font-size:30px; font-weight:bold;"><br />
3rd<br />
</div><br />
<div style="margin-left:65px; background-color:#9faecc; border-style:solid; border-color:#324065; border-width:0px; border-left-width:5px; min-height:55px; padding:5px;"><br />
Boot from the CD, login as root with no password, and voilà! Enjoy Alpine Linux!<br />
</div><br />
<br />
<br /><br />
{{Tip|One of the first commands you might want to use is `setup-alpine`}}<br />
{{Tip|For RAM-based installs, continue by reading about [[Alpine local backup|Alpine Local Backup]]. Otherwise, for HDD-based installs, etc., continue reading one of the documents below.}}<br />
<br /><br />
<br />
= Installation Handbook =<br />
<br />
* [[Installing Alpine on HDD overwriting everything ]] ''(Quick and dirty install on a new machine)''<br />
* [[Installing Alpine on HDD dualbooting]]<br />
* [[Install to disk]]<br />
* [[Installing Alpine on USB]]<br />
* [[Installing Alpine on Compact Flash]]<br />
* [[Installing Alpine on a virtual machine]]<br />
* [[Installing Alpine Linux in a chroot]]<br />
* [[Upgrading Alpine]]</div>Forthhttps://wiki.alpinelinux.org/w/index.php?title=Install_to_disk&diff=5671Install to disk2011-08-30T19:10:45Z<p>Forth: </p>
<hr />
<div>{{Note|This document covers 2.x.x release.}}<br />
For 1.8.x and older please see [[Native Harddisk Install 1.6]]<br />
<br />
== Installation ==<br />
Run ''setup-alpine'' to configure the keyboard, hostname and networking.<br />
<br />
{{Cmd|setup-alpine}}<br />
<br />
Create partitions with fdisk. <br />
<br />
{{Cmd|fdisk /dev/sda}}<br />
<br />
You should have 2 partitions: /dev/sda1 as "Linux" (type 83) and /dev/sda2 as "linux swap" (type 82). The /dev/sda1 must be bootable (command "a" within fdisk).<br />
<br />
Install needed programs for the setup <br />
<br />
{{Cmd|apk add e2fsprogs syslinux mkinitfs}}<br />
<br />
Create filesystem and swap <br />
<br />
{{Cmd|mkfs.ext4 /dev/sda1<br />
mkswap /dev/sda2}}<br />
<br />
Mount file-system <br />
<br />
{{Cmd|mount -t ext4 /dev/sda1 /mnt}}<br />
<br />
Clone the current running config created by setup-alpine (hostname, networking root password)<br />
<br />
{{Cmd|<nowiki>lbu package - | tar -C /mnt -zx</nowiki>}}<br />
<br />
Install base packages on harddisk<br />
<br />
{{Cmd|<nowiki>apk add --root=/mnt --initdb apk-tools alpine-baselayout alpine-conf linux-grsec busybox-initscripts acct</nowiki>}}<br />
<br />
Create the repositories list. In this example we use the cdrom as repository:<br />
<br />
{{Cmd|mkdir -p /mnt/etc/apk<br />
echo "/media/cdrom/packages/core" >> /mnt/etc/apk/repositories<br />
echo "/media/cdrom/packages/extra" >> /mnt/etc/apk/repositories}}<br />
<br />
Append the / and swap to fstab:<br />
{{Cmd|echo -e "/dev/sda1 / ext4 defaults 1 1" &gt;&gt; /mnt/etc/fstab<br />
echo -e "/dev/sda2 none swap sw 0 0" &gt;&gt; /mnt/etc/fstab}}<br />
<br />
Configure the boot loader, extlinux. We use the provided syslinux as base.<br />
<br />
{{Cmd|cp /media/cdrom/syslinux.cf /mnt/boot/extlinux.conf<br />
vi /mnt/boot/extlinux.conf}}<br />
<br />
It should contain something like: <br />
timeout 20<br />
prompt 1<br />
default grsec<br />
label grsec<br />
kernel /boot/grsec<br />
append initrd=/boot/grsec.gz root=/dev/sda1 modules=ext4 quiet<br />
<br />
Install the bootloader:<br />
{{Cmd|extlinux -i /mnt/boot}}<br />
<br />
Install syslinux bootloader at the beginning of the MBR so its bootable (note that its sda and not sda1)<br />
<br />
{{Cmd|<nowiki>dd if=/usr/share/syslinux/mbr.bin of=/dev/sda</nowiki>}}<br />
<br />
Unmount, remove cdrom, and reboot. (If you can't eject, just remove it manually as the machine reboots) <br />
<br />
{{Cmd|umount /mnt<br />
umount /.modloop<br />
eject <br />
reboot}}<br />
<br />
After reboot, you should be able to log in as root with the password you created in <tt>setup-alpine</tt>.</div>Forthhttps://wiki.alpinelinux.org/w/index.php?title=Install_to_disk&diff=5670Install to disk2011-08-30T12:25:17Z<p>Forth: update to ext4 and various misc from real life</p>
<hr />
<div>{{Note|This document covers 1.9.x release.}}<br />
For 1.8.x and older please see [[Native Harddisk Install 1.6]]<br />
<br />
== Installation ==<br />
Run ''setup-alpine'' to configure the keyboard, hostname and networking.<br />
<br />
{{Cmd|setup-alpine}}<br />
<br />
Create partitions with fdisk. <br />
<br />
{{Cmd|fdisk /dev/sda}}<br />
<br />
You should have 2 partitions: /dev/sda1 as "Linux" (type 83) and /dev/sda2 as "linux swap" (type 82). The /dev/sda1 should be bootable.<br />
<br />
Install needed programs for the setup <br />
<br />
{{Cmd|apk add e2fsprogs syslinux mkinitfs}}<br />
<br />
Create filesystem and swap <br />
<br />
{{Cmd|mkfs.ext4 /dev/sda1<br />
mkswap /dev/sda2}}<br />
<br />
Mount file-system <br />
<br />
{{Cmd|mount -t ext4 /dev/sda1 /mnt}}<br />
<br />
Clone the current running config created by setup-alpine (hostname, networking root password)<br />
<br />
{{Cmd|<nowiki>lbu package - | tar -C /mnt -zx</nowiki>}}<br />
<br />
Install base packages on harddisk<br />
<br />
{{Cmd|<nowiki>apk add --root=/mnt --initdb apk-tools alpine-baselayout alpine-conf linux-grsec busybox-initscripts acct</nowiki>}}<br />
<br />
Create the repositories list. In this example we use the cdrom as repository:<br />
<br />
{{Cmd|mkdir -p /mnt/etc/apk<br />
echo "/media/cdrom/packages/core" >> /mnt/etc/apk/repositories<br />
echo "/media/cdrom/packages/extra" >> /mnt/etc/apk/repositories}}<br />
<br />
Append the / and swap to fstab:<br />
{{Cmd|echo -e "/dev/sda1 / ext4 defaults 1 1" &gt;&gt; /mnt/etc/fstab<br />
echo -e "/dev/sda2 none swap sw 0 0" &gt;&gt; /mnt/etc/fstab}}<br />
<br />
Configure the boot loader, extlinux. We use sthe provided syslinux as base.<br />
<br />
{{Cmd|cp /media/cdrom/syslinux.cf /mnt/boot/extlinux.conf<br />
vi /mnt/boot/extlinux.conf}}<br />
<br />
It should contain something like: <br />
timeout 20<br />
prompt 1<br />
default grsec<br />
label grsec<br />
kernel /boot/grsec<br />
append initrd=/boot/grsec.gz root=/dev/sda1 modules=ext4 quiet<br />
<br />
Install the bootloader:<br />
{{Cmd|extlinux -i /mnt/boot}}<br />
<br />
Fix the MBR so its bootable (note that its sda and not sda1)<br />
<br />
{{Cmd|<nowiki>dd if=/usr/share/syslinux/mbr.bin of=/dev/sda</nowiki>}}<br />
<br />
Unmount, remove cdrom, and reboot. (If you can't eject, just remove it manually as the machine reboots) <br />
<br />
{{Cmd|umount /mnt<br />
umount /.modloop<br />
eject <br />
reboot}}<br />
<br />
After reboot, you should be able to log in as root with the password you created in <tt>setup-alpine</tt>.</div>Forthhttps://wiki.alpinelinux.org/w/index.php?title=Xen_Dom0&diff=5655Xen Dom02011-08-23T14:48:17Z<p>Forth: load xen-gntdev module</p>
<hr />
<div>So before anything else verify that you can '''reliably''' log into your Alpine box through [[Setting_up_a_ssh-server|SSH]], because with some video chipset (intel in my case) xen will blank your screen so you will have to use SSH.<br />
<br />
Then upgrade your setup to [[Upgrading_to_Edge|Edge/testing]] (as of the date of writing, Xen is only available in Edge). Install Xen:<br />
<br />
{{Cmd|apk add xen}}<br />
<br />
Modify your extlinux.cfg (credits: http://lists.alpinelinux.org/alpine-devel/1406.html)<br />
since video card is not working for now, we will use a serial console:<br />
<br />
<pre><br />
SERIAL 0 115200 <br />
DEFAULT menu.c32<br />
PROMPT 0<br />
MENU TITLE Alpine/Linux Boot Menu<br />
MENU HIDDEN<br />
MENU AUTOBOOT Alpine will be booted automatically in # seconds.<br />
TIMEOUT 50<br />
LABEL 0<br />
MENU DEFAULT<br />
MENU LABEL Linux 2.6.38.8-vs2.3.0.37-rc17<br />
KERNEL vmlinuz-2.6.38.8-vs2.3.0.37-rc17<br />
APPEND initrd=initramfs-2.6.38.8-vs2.3.0.37-rc17 root=UUID=f40e340b-ea49-445b-81c0-4d7104b56662 modules=sd-mod,usb-storage,ext4 quiet<br />
<br />
LABEL 1<br />
MENU LABEL Linux 2.6.36.3-scst<br />
KERNEL vmlinuz-2.6.36.3-scst<br />
APPEND initrd=initramfs-2.6.36.3-scst root=UUID=f40e340b-ea49-445b-81c0-4d7104b56662 modules=sd-mod,usb-storage,ext4 quiet<br />
<br />
LABEL 2<br />
MENU LABEL Linux 2.6.38.8-grsec<br />
KERNEL vmlinuz-2.6.38.8-grsec<br />
APPEND initrd=initramfs-2.6.38.8-grsec root=UUID=f40e340b-ea49-445b-81c0-4d7104b56662 modules=sd-mod,usb-storage,ext4 quiet<br />
<br />
LABEL 3<br />
MENU LABEL XEN<br />
KERNEL mboot.c32<br />
APPEND /boot/xen-4.gz loglvl=all guest_loglvl=all com1=115200,8n1 console=com1 dom0_mem=256M --- /boot/vmlinuz-grsec root=UUID=f40e340b-ea49-445b-81c0-4d7104b56662 modules=sd-mod,usb-storage,ext4 console=hvc0 earlyprintk=xen nomodeset --- /boot/initramfs-grsec<br />
</pre><br />
Of course replace root=UUID= with '''your''' UUID in yours.<br />
<br />
xl info won't work<br />
<br />
Start xecommons:<br />
<pre><br />
alpine:/boot# /etc/init.d/xencommons start<br />
Starting xenstored...FATAL: Failed to open evtchn device: No such file or directory<br />
</pre><br />
well this will fail but xl info will work anyway<br />
<br />
Oh but wait, evtchn device is built in the kernel, so why is there no /dev/xen/evtch file ?<br />
let's start udev ! ;)<br />
{{Cmd|rc-service udev start}}<br />
<br />
That's all folks !<br />
<br />
on going debug:<br />
vi /etc/rc.conf<br />
rc_sys="xen0"<br />
why ?<br />
<br />
<br />
Commands recap:<br />
{{Cmd|<br />
apk add xen<br />
apk add udev<br />
rc-service udev start ; rc-service udev-postmount start<br />
rc-service xencommons start<br />
}}<br />
If you want "xm" command<br />
{{Cmd|rc-service xend start}}<br />
<br />
So let's install services at boot time :<br />
{{Cmd|<br />
rc-update add udev sysinit<br />
rc-update add udev-postmount default<br />
rc-update add xencommons<br />
rc-update add xend<br />
}}<br />
<br />
since we use a serial line, let'a add a serial console prompt, modify your /etc/inittab accordinly:<br />
<br />
# Put a getty on the serial port<br />
#ttyS0::respawn:/sbin/getty -L ttyS0 115200 vt100<br />
hvc0::respawn:/sbin/getty -L hvc0 115200 vt100<br />
<br />
hvc0 is Xen console output, where we have already redirected the kernel messages.<br />
To switch to Xen console, type three time "Ctrl+a"<br />
<br />
Now you can configure your guest, but before don't forget to load xen-gntdev kernel module:<br />
modprobe xen-gntdev<br />
echo "xen-gntdev" >> /etc/modules</div>Forthhttps://wiki.alpinelinux.org/w/index.php?title=Xen_Dom0&diff=5654Xen Dom02011-08-22T17:05:02Z<p>Forth: serial tty</p>
<hr />
<div>So before anything else verify that you can '''reliably''' log into your Alpine box through [[Setting_up_a_ssh-server|SSH]], because with some video chipset (intel in my case) xen will blank your screen so you will have to use SSH.<br />
<br />
Then upgrade your setup to [[Upgrading_to_Edge|Edge/testing]] (as of the date of writing, Xen is only available in Edge). Install Xen:<br />
<br />
{{Cmd|apk add xen}}<br />
<br />
Modify your extlinux.cfg (credits: http://lists.alpinelinux.org/alpine-devel/1406.html)<br />
since video card is not working for now, we will use a serial console:<br />
<br />
<pre><br />
SERIAL 0 115200 <br />
DEFAULT menu.c32<br />
PROMPT 0<br />
MENU TITLE Alpine/Linux Boot Menu<br />
MENU HIDDEN<br />
MENU AUTOBOOT Alpine will be booted automatically in # seconds.<br />
TIMEOUT 50<br />
LABEL 0<br />
MENU DEFAULT<br />
MENU LABEL Linux 2.6.38.8-vs2.3.0.37-rc17<br />
KERNEL vmlinuz-2.6.38.8-vs2.3.0.37-rc17<br />
APPEND initrd=initramfs-2.6.38.8-vs2.3.0.37-rc17 root=UUID=f40e340b-ea49-445b-81c0-4d7104b56662 modules=sd-mod,usb-storage,ext4 quiet<br />
<br />
LABEL 1<br />
MENU LABEL Linux 2.6.36.3-scst<br />
KERNEL vmlinuz-2.6.36.3-scst<br />
APPEND initrd=initramfs-2.6.36.3-scst root=UUID=f40e340b-ea49-445b-81c0-4d7104b56662 modules=sd-mod,usb-storage,ext4 quiet<br />
<br />
LABEL 2<br />
MENU LABEL Linux 2.6.38.8-grsec<br />
KERNEL vmlinuz-2.6.38.8-grsec<br />
APPEND initrd=initramfs-2.6.38.8-grsec root=UUID=f40e340b-ea49-445b-81c0-4d7104b56662 modules=sd-mod,usb-storage,ext4 quiet<br />
<br />
LABEL 3<br />
MENU LABEL XEN<br />
KERNEL mboot.c32<br />
APPEND /boot/xen-4.gz loglvl=all guest_loglvl=all com1=115200,8n1 console=com1 dom0_mem=256M --- /boot/vmlinuz-grsec root=UUID=f40e340b-ea49-445b-81c0-4d7104b56662 modules=sd-mod,usb-storage,ext4 console=hvc0 earlyprintk=xen nomodeset --- /boot/initramfs-grsec<br />
</pre><br />
Of course replace root=UUID= with '''your''' UUID in yours.<br />
<br />
xl info won't work<br />
<br />
Start xecommons:<br />
<pre><br />
alpine:/boot# /etc/init.d/xencommons start<br />
Starting xenstored...FATAL: Failed to open evtchn device: No such file or directory<br />
</pre><br />
well this will fail but xl info will work anyway<br />
<br />
Oh but wait, evtchn device is built in the kernel, so why is there no /dev/xen/evtch file ?<br />
let's start udev ! ;)<br />
{{Cmd|rc-service udev start}}<br />
<br />
That's all folks !<br />
<br />
on going debug:<br />
vi /etc/rc.conf<br />
rc_sys="xen0"<br />
why ?<br />
<br />
<br />
Commands recap:<br />
{{Cmd|<br />
apk add xen<br />
apk add udev<br />
rc-service udev start ; rc-service udev-postmount start<br />
rc-service xencommons start<br />
}}<br />
If you want "xm" command<br />
{{Cmd|rc-service xend start}}<br />
<br />
So let's install services at boot time :<br />
{{Cmd|<br />
rc-update add udev sysinit<br />
rc-update add udev-postmount default<br />
rc-update add xencommons<br />
rc-update add xend<br />
}}<br />
<br />
since we use a serial line, let'a add a serial console prompt, modify your /etc/inittab accordinly:<br />
<br />
# Put a getty on the serial port<br />
#ttyS0::respawn:/sbin/getty -L ttyS0 115200 vt100<br />
hvc0::respawn:/sbin/getty -L hvc0 115200 vt100<br />
<br />
hvc0 is Xen console output, where we have already redirected the kernel messages.<br />
To switch to Xen console, type three time "Ctrl+a"</div>Forthhttps://wiki.alpinelinux.org/w/index.php?title=Xen_Dom0&diff=5653Xen Dom02011-08-22T15:41:50Z<p>Forth: </p>
<hr />
<div>So before anything else verify that you can '''reliably''' log into your Alpine box through [[Setting_up_a_ssh-server|SSH]], because with some video chipset (intel in my case) xen will blank your screen so you will have to use SSH.<br />
<br />
Then upgrade your setup to [[Upgrading_to_Edge|Edge/testing]] (as of the date of writing, Xen is only available in Edge). Install Xen:<br />
<br />
{{Cmd|apk add xen}}<br />
<br />
Modify your extlinux.cfg (credits: http://lists.alpinelinux.org/alpine-devel/1406.html)<br />
since video card is not working for now, we will use a serial console:<br />
<br />
<pre><br />
SERIAL 0 115200 <br />
DEFAULT menu.c32<br />
PROMPT 0<br />
MENU TITLE Alpine/Linux Boot Menu<br />
MENU HIDDEN<br />
MENU AUTOBOOT Alpine will be booted automatically in # seconds.<br />
TIMEOUT 50<br />
LABEL 0<br />
MENU DEFAULT<br />
MENU LABEL Linux 2.6.38.8-vs2.3.0.37-rc17<br />
KERNEL vmlinuz-2.6.38.8-vs2.3.0.37-rc17<br />
APPEND initrd=initramfs-2.6.38.8-vs2.3.0.37-rc17 root=UUID=f40e340b-ea49-445b-81c0-4d7104b56662 modules=sd-mod,usb-storage,ext4 quiet<br />
<br />
LABEL 1<br />
MENU LABEL Linux 2.6.36.3-scst<br />
KERNEL vmlinuz-2.6.36.3-scst<br />
APPEND initrd=initramfs-2.6.36.3-scst root=UUID=f40e340b-ea49-445b-81c0-4d7104b56662 modules=sd-mod,usb-storage,ext4 quiet<br />
<br />
LABEL 2<br />
MENU LABEL Linux 2.6.38.8-grsec<br />
KERNEL vmlinuz-2.6.38.8-grsec<br />
APPEND initrd=initramfs-2.6.38.8-grsec root=UUID=f40e340b-ea49-445b-81c0-4d7104b56662 modules=sd-mod,usb-storage,ext4 quiet<br />
<br />
LABEL 3<br />
MENU LABEL XEN<br />
KERNEL mboot.c32<br />
APPEND /boot/xen-4.gz loglvl=all guest_loglvl=all com1=115200,8n1 console=com1 dom0_mem=256M --- /boot/vmlinuz-grsec root=UUID=f40e340b-ea49-445b-81c0-4d7104b56662 modules=sd-mod,usb-storage,ext4 console=hvc0 earlyprintk=xen nomodeset --- /boot/initramfs-grsec<br />
</pre><br />
Of course replace root=UUID= with '''your''' UUID in yours.<br />
<br />
xl info won't work<br />
<br />
Start xecommons:<br />
<pre><br />
alpine:/boot# /etc/init.d/xencommons start<br />
Starting xenstored...FATAL: Failed to open evtchn device: No such file or directory<br />
</pre><br />
well this will fail but xl info will work anyway<br />
<br />
Oh but wait, evtchn device is built in the kernel, so why is there no /dev/xen/evtch file ?<br />
let's start udev ! ;)<br />
{{Cmd|rc-service udev start}}<br />
<br />
That's all folks !<br />
<br />
on going debug:<br />
vi /etc/rc.conf<br />
rc_sys="xen0"<br />
why ?<br />
<br />
<br />
Commands recap:<br />
{{Cmd|<br />
apk add xen<br />
apk add udev<br />
rc-service udev start ; rc-service udev-postmount start<br />
rc-service xencommons start<br />
}}<br />
If you want "xm" command<br />
{{Cmd|rc-service xend start}}<br />
<br />
So let's install services at boot time :<br />
{{Cmd|<br />
rc-update add udev sysinit<br />
rc-update add udev-postmount default<br />
rc-update add xencommons<br />
rc-update add xend<br />
}}</div>Forthhttps://wiki.alpinelinux.org/w/index.php?title=Xen_Dom0&diff=5652Xen Dom02011-08-22T15:40:55Z<p>Forth: xencommons working after Xen bumped to 4.1.1</p>
<hr />
<div>So before anything else verify that you can '''reliably''' log into your Alpine box through [[Setting_up_a_ssh-server|SSH]], because with some video chipset (intel in my case) xen will blank your screen so you will have to use SSH.<br />
<br />
Then upgrade your setup to [[Upgrading_to_Edge|Edge/testing]] (as of the date of writing, Xen is only available in Edge). Install Xen:<br />
<br />
{{Cmd|apk add xen}}<br />
<br />
Modify your extlinux.cfg (credits: http://lists.alpinelinux.org/alpine-devel/1406.html)<br />
since video card is not working for now, we will use a serial console:<br />
<br />
<pre><br />
SERIAL 0 115200 <br />
DEFAULT menu.c32<br />
PROMPT 0<br />
MENU TITLE Alpine/Linux Boot Menu<br />
MENU HIDDEN<br />
MENU AUTOBOOT Alpine will be booted automatically in # seconds.<br />
TIMEOUT 50<br />
LABEL 0<br />
MENU DEFAULT<br />
MENU LABEL Linux 2.6.38.8-vs2.3.0.37-rc17<br />
KERNEL vmlinuz-2.6.38.8-vs2.3.0.37-rc17<br />
APPEND initrd=initramfs-2.6.38.8-vs2.3.0.37-rc17 root=UUID=f40e340b-ea49-445b-81c0-4d7104b56662 modules=sd-mod,usb-storage,ext4 quiet<br />
<br />
LABEL 1<br />
MENU LABEL Linux 2.6.36.3-scst<br />
KERNEL vmlinuz-2.6.36.3-scst<br />
APPEND initrd=initramfs-2.6.36.3-scst root=UUID=f40e340b-ea49-445b-81c0-4d7104b56662 modules=sd-mod,usb-storage,ext4 quiet<br />
<br />
LABEL 2<br />
MENU LABEL Linux 2.6.38.8-grsec<br />
KERNEL vmlinuz-2.6.38.8-grsec<br />
APPEND initrd=initramfs-2.6.38.8-grsec root=UUID=f40e340b-ea49-445b-81c0-4d7104b56662 modules=sd-mod,usb-storage,ext4 quiet<br />
<br />
LABEL 3<br />
MENU LABEL XEN<br />
KERNEL mboot.c32<br />
APPEND /boot/xen-4.gz loglvl=all guest_loglvl=all com1=115200,8n1 console=com1 dom0_mem=256M --- /boot/vmlinuz-grsec root=UUID=f40e340b-ea49-445b-81c0-4d7104b56662 modules=sd-mod,usb-storage,ext4 console=hvc0 earlyprintk=xen nomodeset --- /boot/initramfs-grsec<br />
</pre><br />
Of course replace root=UUID= with '''your''' UUID in yours.<br />
<br />
xl info won't work<br />
<br />
Start xecommons:<br />
<pre><br />
alpine:/boot# /etc/init.d/xencommons start<br />
Starting xenstored...FATAL: Failed to open evtchn device: No such file or directory<br />
</pre><br />
well this will fail but xl info will work anyway<br />
<br />
Oh but wait, evtchn device is built in the kernel, so why is there no /dev/xen/evtch file ?<br />
let's start udev ! ;)<br />
{{Cmd|rc-service udev start}}<br />
<br />
That's all folks !<br />
<br />
on going debug:<br />
vi /etc/rc.conf<br />
rc_sys="xen0"<br />
why ?<br />
<br />
<br />
Commands recap:<br />
{{Cmd|<br />
apk add xen<br />
apk add udev<br />
rc-service udev start ; rc-service udev-postmount start<br />
}}<br />
If you want "xm" command<br />
{{Cmd|rc-service xend start}}<br />
<br />
So let's install services at boot time :<br />
{{Cmd|<br />
rc-update add udev sysinit<br />
rc-update add udev-postmount default<br />
rc-update add xencommons<br />
rc-update add xend<br />
}}</div>Forthhttps://wiki.alpinelinux.org/w/index.php?title=Xen_Dom0&diff=5651Xen Dom02011-08-22T15:19:47Z<p>Forth: update / serial console / more accurate infos / almost working</p>
<hr />
<div>So before anything else verify that you can '''reliably''' log into your Alpine box through [[Setting_up_a_ssh-server|SSH]], because with some video chipset (intel in my case) xen will blank your screen so you will have to use SSH.<br />
<br />
Then upgrade your setup to [[Upgrading_to_Edge|Edge/testing]] (as of the date of writing, Xen is only available in Edge). Install Xen:<br />
<br />
{{Cmd|apk add xen}}<br />
<br />
Modify your extlinux.cfg (credits: http://lists.alpinelinux.org/alpine-devel/1406.html)<br />
since video card is not working for now, we will use a serial console:<br />
<br />
<pre><br />
SERIAL 0 115200 <br />
DEFAULT menu.c32<br />
PROMPT 0<br />
MENU TITLE Alpine/Linux Boot Menu<br />
MENU HIDDEN<br />
MENU AUTOBOOT Alpine will be booted automatically in # seconds.<br />
TIMEOUT 50<br />
LABEL 0<br />
MENU DEFAULT<br />
MENU LABEL Linux 2.6.38.8-vs2.3.0.37-rc17<br />
KERNEL vmlinuz-2.6.38.8-vs2.3.0.37-rc17<br />
APPEND initrd=initramfs-2.6.38.8-vs2.3.0.37-rc17 root=UUID=f40e340b-ea49-445b-81c0-4d7104b56662 modules=sd-mod,usb-storage,ext4 quiet<br />
<br />
LABEL 1<br />
MENU LABEL Linux 2.6.36.3-scst<br />
KERNEL vmlinuz-2.6.36.3-scst<br />
APPEND initrd=initramfs-2.6.36.3-scst root=UUID=f40e340b-ea49-445b-81c0-4d7104b56662 modules=sd-mod,usb-storage,ext4 quiet<br />
<br />
LABEL 2<br />
MENU LABEL Linux 2.6.38.8-grsec<br />
KERNEL vmlinuz-2.6.38.8-grsec<br />
APPEND initrd=initramfs-2.6.38.8-grsec root=UUID=f40e340b-ea49-445b-81c0-4d7104b56662 modules=sd-mod,usb-storage,ext4 quiet<br />
<br />
LABEL 3<br />
MENU LABEL XEN<br />
KERNEL mboot.c32<br />
APPEND /boot/xen-4.gz loglvl=all guest_loglvl=all com1=115200,8n1 console=com1 dom0_mem=256M --- /boot/vmlinuz-grsec root=UUID=f40e340b-ea49-445b-81c0-4d7104b56662 modules=sd-mod,usb-storage,ext4 console=hvc0 earlyprintk=xen nomodeset --- /boot/initramfs-grsec<br />
</pre><br />
Of course replace root=UUID= with '''your''' UUID in yours.<br />
<br />
xl info won't work<br />
<br />
Start xecommons:<br />
<pre><br />
alpine:/boot# /etc/init.d/xencommons start<br />
Starting xenstored...FATAL: Failed to open evtchn device: No such file or directory<br />
</pre><br />
well this will fail but xl info will work anyway<br />
<br />
Oh but wait, evtchn device is built in the kernel, so why is there no /dev/xen/evtch file ?<br />
let's start udev ! ;)<br />
{{Cmd|rc-service udev start}}<br />
<br />
That's all folks !<br />
<br />
on going debug:<br />
vi /etc/rc.conf<br />
rc_sys="xen0"<br />
<br />
and xencommons not launching at boot</div>Forthhttps://wiki.alpinelinux.org/w/index.php?title=Xen_Dom0&diff=5649Xen Dom02011-08-21T15:18:23Z<p>Forth: </p>
<hr />
<div>So before anything else verify that you can '''reliably''' log into your Alpine box through [[Setting_up_a_ssh-server|SSH]], because with some video chipset (intel in my case) xen will blank your screen so you will have to use SSH.<br />
<br />
Then upgrade your setup to [[Upgrading_to_Edge|Edge/testing]] (as of the date of writing, Xen is only available in Edge). Install Xen:<br />
<br />
{{Cmd|apk add xen}}<br />
<br />
Modify your extlinux.cfg: http://lists.alpinelinux.org/alpine-devel/1406.html<br />
<br />
<pre><br />
timeout 20<br />
prompt 1<br />
default grsec<br />
label grsec<br />
kernel /boot/vmlinuz-grsec<br />
append initrd=/boot/initramfs-grsec root=UUID=f40e340b-ea49-445b-81c0-4d7104b56662 modules=sd-mod,usb-storage,ext4<br />
label xen<br />
kernel mboot.c32<br />
append /boot/xen-4.gz console=/dev/null dom0_mem=256M vga=mode-0x0311 --- /boot/vmlinuz-grsec root=UUID=f40e340b-ea49-445b-81c0-4d7104b56662 modules=sd-mod,usb-storage,ext4 vga=785 --- /boot/initramfs-grsec<br />
</pre><br />
Of course replace root=UUID= with '''your''' UUID in yours.<br />
Default menu.c32 can mangle with Xen, further investigation needed, so don't use for now.<br />
<br />
Use the script found here: http://lists.xensource.com/archives/html/xen-devel/2010-03/msg01605.html<br />
<pre><br />
#!/bin/sh<br />
<br />
test -d /proc/xen || exit 0<br />
test -f /proc/xen/capabilities || mount -t xenfs xen /proc/xen<br />
test -f /proc/xen/capabilities || exit 0<br />
grep -q "control_d" /proc/xen/capabilities || exit 0<br />
<br />
for module in xen-evtchn evtchn blkbk netbk; do<br />
modprobe ${module}>/dev/null 2>&1<br />
done<br />
</pre><br />
xl info won't work<br />
<br />
Start xecommons:<br />
xencommons use bash, so install it.<br />
<br />
{{Cmd|apk add bash}} (should try sh instead)<br />
<br />
alpine:/boot# /etc/init.d/xencommons start<br />
Starting xenstored...FATAL: Failed to open evtchn device: No such file or directory<br />
<br />
well this will fail but xl info will work anyway<br />
<br />
Oh but wait, evtchn device is built in the kernel, so why is there no /dev/xen/evtch file ?<br />
let's start udev ! ;)<br />
<br />
That's all folks !<br />
<br />
vi /etc/rc.conf<br />
rc_sys="xen0"</div>Forthhttps://wiki.alpinelinux.org/w/index.php?title=Creating_an_Alpine_package&diff=5639Creating an Alpine package2011-08-15T06:21:07Z<p>Forth: /* Installing and configuring the alpine-sdk - developpement with Git added in the reading workflow */</p>
<hr />
<div>== General ==<br />
<br />
This document assumes that you have a working [[Setting up the build environment|build environment]], or use a diskbased alpine installation. <br />
<br />
=== The APKBUILDs ===<br />
<br />
The ''[http://git.alpinelinux.org/cgit/abuild/ abuild]'' script reads the ''[http://git.alpinelinux.org/cgit/abuild/tree/sample.APKBUILD APKBUILD]'' and executes the steps needed to create a package. <br />
<br />
=== The aports tree ===<br />
<br />
The [http://git.alpinelinux.org/cgit/aports aports] tree is a [http://git.alpinelinux.org/cgit/aports/tree directory tree] with many APKBUILDs. Those files are used when building alpine from source. <br />
<br />
== Installing and configuring the alpine-sdk ==<br />
<br />
The alpine-sdk is a metapackage that pulls in the most essential packages used to build new packages.<BR><br />
Install those packages now: <br />
<br />
{{Cmd|apk add alpine-sdk}}<br />
<br />
This would be a good time to create a normal user account for you to work in. (You weren't going to develop as root now, were you!) To create the user:<br />
<br />
{{Cmd|adduser <yourusername>}}<br />
<br />
To make life easier later, it's a good idea to add this user to /etc/sudoers. Append the line<br />
<br />
<yourusername> ALL=(ALL) ALL<br />
<br />
using the command:<br />
<br />
{{Cmd|visudo}}<br />
<br />
Now logout of the root account, and login as <yourusername>. From here on everything can be done in a normal user account, and operations that require superuser privileges can be done with sudo.<br />
<br />
The aports tree is in git so before we clone the aports tree we should configure git.<br />
<br />
{{Cmd|git config --global user.name "Your Full Name"<br />
git config --global user.email "your@email.address"}}<br />
<br />
Read carefully [[Development using git]] to grasp basic Git operations and configure email patches sending.<br />
<br />
Now we can clone the aports tree. <br />
<br />
{{Cmd|git clone git://dev.alpinelinux.org/aports}}<br />
<br />
Before we start creating or modifying APKBUILD files we need to setup abuild to our system/user. Edit the file abuild.conf to your requirements. Most of the defaults can be left alone, unless you are developing for a custom platform, in which case the comments in the file should guide you. The one field to edit is PACKAGER, so that you can get credit (or blame) for packages you create.<br />
<br />
{{Cmd|sudo vi /etc/abuild.conf}}<br />
<br />
We also need to prepare the location that the build process caches files when they are downloaded. By default this is /var/cache/distfiles. To create this directory and ensure that it is writeable, enter the following commands:<br />
<br />
{{Cmd|sudo mkdir -p /var/cache/distfiles}}<br />
{{Cmd|sudo chmod a+w /var/cache/distfiles}}<br />
<br />
Or add yourself to the abuild group<br />
<br />
{{Cmd|sudo groupadd <yourusername> abuild}}<br />
<br />
The last step in preparation is to configure the security keys for abuild with the command:<br />
<br />
{{Cmd|abuild-keygen -a -i}}<br />
<br />
== Getting some help ==<br />
<br />
It might be wise to start by checking what the abuild program can/cannot do.<br />
<br />
{{Cmd|abuild -h}}<br />
<br />
== Creating an APKBUILD file ==<br />
<br />
=== Use a template APKBUILD ===<br />
<br />
To create the actual APKBUILD file <tt>newapkbuild</tt> can serve you a template to start with. It will create a directory with the given package name, place an example/template APKBUILD file to the given directory, and fill some variables if those are provided. Please check the [[Package_policies| package policies]] page about naming details.<br />
<br />
If you doubt to which repository your package belongs to you can safely use '''testing'''. Building package in your aports/testing directory is not mandatory but this way the package is already at the right place.<br />
<br />
{{Cmd|newapkbuild ''packagename''}}<br />
<br />
'''newapkbuild options'''<br />
<br />
* '''-a''' Create autotools (use ./configure ...)<br />
* '''-c''' Copy a sample init.d, conf.d and install script to new directory<br />
* '''-d''' Set package description (pkgdesc) to DESC<br />
* '''-f''' Force even if directory already exist<br />
* '''-h''' Show this help<br />
* '''-l''' Set package license to LICENSE<br />
* '''-p''' Create perl package (Assume Makefile.PL is there)<br />
* '''-u''' Set package URL<br />
* '''-s''' Use sourceforge source url<br />
<br />
{{Note|On older Alpine systems, abuild -c -n ''packagename'' was the way to create APKBUILD files. The 'packagename' was a parameter to the -n option so order of -c and -n matters. }}<br />
<br />
If you are create a daemon package which needs initd scripts you can add the -c making it: <br />
<br />
{{Cmd|newapkbuild -c ''packagename''}}<br />
<br />
This will copy the sample initd and confd files to the build directory.<BR><br />
A third file sample.install file will be copied as well (we will discuss this later on).<br />
<br />
=== Modify your APKBUILD ===<br />
Edit APKBUILD and fill in the needed info (especially pkgname, pkgver, pkgdesc, url, license, depends and source). <br />
<br />
If you are going to use any of the variables for directories like $pkgdir, always make sure they are double quoted like: <br />
<br />
"$pkgdir"/somedir<br />
<br />
This will prevent issues with spaces/special characters in the future. <br />
<br />
{{Note|If you like syntax highlighting we suggest you to install vim. We have setup vim to recognize the APKBUILD file as a bash scripts so its easier to read them.}}<br />
<br />
=== APKBUILD variables/functions ===<br />
<br />
==== source ====<br />
<br />
The source variable is not only used to list the remote source files to fetch, it is also used to list the local files that abuild will need in order to build the apk. Examples of such local files include: init.d files, conf.d files, install files (see [[Creating an Alpine package#install|install variable]]), patches, and all other necessary files.<br />
<br />
Here are few things to note:<br />
<br />
* When you are finished adding local and/or remote files to ''source'', you can execute the following command to add their checksums to the APKBUILD file:<br />
: {{cmd|abuild checksum}}<br />
: {{Note|When later updating the content of ''source'', or updating a file that is listed in ''source'', you must also update their checksums again with the same command.}}<br />
<br />
* When the remote file is hosted at SourceForge, it's best to specify the special mirrors link used by SourceForge:<br />
: <pre>http://downloads.sourceforge.net/$pkgname/$pkgname-$pkgver.tar.gz</pre><br />
: (or similar depending on the package).<br />
<br />
* When the remote filename is not specified in the URI (ie, does not end in '/software-1.0.tar.gz'), such as:<br />
: <pre>http://oss.example.org/?get=software&ver=1.0</pre><br />
: You must prepend 'saveas-' to the protocol and append '/software-1.0.tar.gz' (for instance) to the end of the URI, like so:<br />
: <pre>saveas-http://oss.example.org/?get=software&ver=1.0/software-1.0.tar.gz</pre><br />
: This causes the file to be saved as ''software-1.0.tar.gz'' where abuild can use it, instead of ''?get=software&ver=1.0'', where abuild cannot use it.<br />
<br />
* abuild currently supports the following protocols for remote file retrieval:<br />
** http<br />
** https<br />
** ftp<br />
<br />
: {{Note|If the you want to download from https, you need GNU wget installed on your system.}}<br />
<br />
* abuild currently supports the following archive types/archive file extensions:<br />
** .tar.gz / .tgz<br />
** .tar.bz2<br />
** .tar.lzma<br />
** .tar.xz<br />
** .zip<br />
<br />
==== depends &amp; makedepends ====<br />
<br />
Depends are the actual running dependencies that a package would need when it is running. Makedepends are only needed when you are building a package. If you set a package, in depends you do not need to add it to makedepends as well. The best way to find out what the depends and makedepends of a package are is to [http://en.wikipedia.org/wiki/Rtfm RTFM]. <br />
<br />
No kidding, lots of important information can be found it the package INSTALL and README file (or the likes). Another good way is the run ./configure --help from the source directory to see which options are needed for configure to finish without errors. If you do not yet have a src directory you can create one with the command: <br />
<br />
{{Cmd|abuild unpack}}<br />
<br />
Running configure will also show you how you can disable a specific option for this package. A good example is for instance "--disable-nls" which will disable native language support and thus does not depend on gettext(libiconv,glib..). <br />
<br />
Alpine likes to keep things small, so we try to disable as much as possible without losing too many features. The exact disable/enable options are decided the package builder but please try to follow Alpine's design concept as much as possible. <br />
<br />
An easy way of quickly finding out the build info for a package is to check Arch Linux (Alpine package management and build scripts are similar) or Gentoo linux ebuilds (previous versions of Alpine were based on Gentoo). <br />
<br />
* [http://www.gentoo-portage.com Search ebuilds] <br />
* [http://sources.gentoo.org/viewcvs.py/gentoo-x86/ Gentoo CVS] <br />
* [http://www.archlinux.org/packages/search/ Arch Linux packages] <br />
<br />
After the package is successfully compiled and created we should make sure it didn't link to any package that is not present in the $depends variable. We do this by using scanelf. If scanelf is not yet installed on your system you can do that by installing pax-utils. <br />
<br />
{{Cmd|scanelf -nR pkg}}<br />
<br />
An example output of libcurl would be: <br />
<br />
ET_DYN libssl.so.0.9.8,libcrypto.so.0.9.8,libz.so.1,libc.so.0,ld-uClibc.so.0 pkg/usr/lib/libcurl.so.4.1.1<br />
<br />
You can see the needed files and should be able to find out which file belongs to which package.<br />
<br />
==== license ====<br />
<br />
If a package has a special/custom license we need to provide it with the release. Because we want to save space and don't like to have licenses all over our system we have decided to include the license in the doc subpackage. Please follow the following guidelines to add a proper license. Locate the license file inside the source package. Add the doc subpackage to the $subpackages variable as follows: <br />
<br />
subpackages="$pkgname-doc"<br />
<br />
Add a similar line to the following to your package() function, depending on the license description file: <br />
<br />
install -Dm644 COPYING "$pkgdir"/usr/share/licenses/$pkgname/COPYING<br />
<br />
If you follow these steps then abuild will automatically add the license to the package-doc apk for you.<br />
<br />
==== arch ====<br />
<br />
The package architecture(s) to build for. This can be one of: ''x86, x86_64, all,'' or ''noarch'', where ''all'' means all architectures, and ''noarch'' means it's architecture-independent (ie, a pure-python package).<br />
{{Tip|To determine if your APKBUILD can use ''noarch'', build the package for your architecture and then run "scanelf -R pkg" from the directory that the APKBUILD resides in, in order to scan for ELF files in the ''./pkg'' directory. If you do NOT get output from this, then ''noarch'' can be used.}}<br />
<br />
==== url ====<br />
<br />
Website address for the program. This is usefully later on when either finding documentation or other information about the package.<br />
<br />
==== pkgdesc ====<br />
<br />
A brief, one line, description of what the package does. Useful for the package management system.<br />
<br />
Here is an example from apk_info for the OpenSSH client package<br />
<br />
pkgdesc="Port of OpenBSD's free SSH release - client"<br />
<br />
==== pkgver ====<br />
<br />
Provide the release number of the package you are building.<br />
<br />
==== pkgrel ====<br />
<br />
The $pkgrel versioning is made so if you change something to your APKBUILD file without changing the actual $pkgver you can higer pkgrel so apk tools will detect it as an update. For instance if you forget to add a dependency you can add it afterward and you can +1 pkgver so apk finds this update and add the missing dependency. <br />
<br />
==== pkgname ====<br />
<br />
The base name of the package you are creating. For Freeswitch 1.0.6, you would use "freeswitch"<br />
<br />
==== install ====<br />
<br />
There are 6 different kinds of install scripts. Each script is called with the $pkgname.''<action>'' where ''<action>'' is one of the following:<br />
<br />
===== $pkgname.pre-install =====<br />
This script is executed before package is installed. Typical use is when package needs a user/group to be created. For example:<br />
<pre><br />
#!/bin/sh<br />
adduser -H -s /bin/false -D clamav 2>/dev/null<br />
exit 0<br />
</pre><br />
Note the ''exit 0'' at the end. If the script exits with failure (if the user already exist), the package will not be installed and apk add will exit with failure.<br />
<br />
===== $pkgname.post-install =====<br />
This script is executed after package is installed. Can be used to generate font cache and similar.<br />
<br />
===== $pkgname.pre-upgrade =====<br />
Same as pre-install but is executed before upgrading an already installed package.<br />
<br />
===== $pkgname.post-upgrade =====<br />
Same as post-install but is executed after upgrading an already installed package. <br />
<br />
===== $pkgname.pre-deinstall =====<br />
This script is executed before uninstalling a package. If script exits with failure apk will not uninstall the package.<br />
<br />
===== $pkgname.post-deinstall =====<br />
This script is executed after a package have been uninstalled. Can be used to update font caches and restore busybox links. For example:<br />
<pre><br />
#!/bin/sh<br />
busybox --install -s<br />
</pre><br />
<br />
<br />
If the package have an pre-install and post-install script the APKBUILD should have the ''install'' variable defined and the scripts should also be added to the source variable:<br />
<pre><br />
...<br />
install="$pkgname.pre-install $pkgname.post-install"<br />
source="http://....<br />
$install"<br />
...<br />
</pre><br />
<br />
==== subpackages ====<br />
<br />
$subpackages are made to split up the normal "make install" into separate packages. The most common subpackages we use are doc and dev. Because we like to keep our target system small we move documentation and development files (only needed when building packages) into separate packages. To use the specific program a user only need to install the base apk without package-doc or package-dev, but if he wants to read the manual he will need to install package-doc. <br />
<br />
The easiest way to find out if you need to use -dev and -doc is to first build the package without these options set and wait until the build finishes. When its finished you should have a pkg directory which is the fake root directory. Inside this directory you will see the structure as how it would be installed in / on the target system. <br />
<br />
To see if you need the -dev package you can run the following cmd: <br />
<br />
{{Cmd|find pkg/usr/ -name '*.[acho]' -o -name '*.la'}}<br />
<br />
If this returns any files you need to include the -dev package. <br />
<br />
<br> To see if you need the -doc package you can run the following cmd: <br />
<br />
{{Cmd|find pkg/usr/share -name doc -o -name man -o -name info -o -name html -o -name sgml -o -name licenses}}<br />
<br />
If this returns any directories you need to include the -doc package. <br />
<br />
===== Custom subpackages =====<br />
<br />
Some applications will have except doc and dev files other non needed at run time files which we want to separate away from the base package. Some packages include large test suites which are only needed in specific circumstances or binaries which have depends which we prefer not to install. To handle those we create our own package/function. In the APKBUILD below the build() function we create another function: <br />
<br />
test() {<br />
mkdir -p "$subpkgdir"/usr<br />
mv "$pkgdir"/usr/package-test "$subpkgdir"/usr/<br />
}<br />
<br />
<br />
We also need to add the package info to $subpackages variable: <br />
<br />
subpackages="$pkgname-doc $pkgname-dev $pkgname-test"<br />
<br />
After we finish building the package you should see another apk called packagename-test.apk which includes the files which we moved to the $subpkgdir dir. <br />
<br />
The above mentioned variables can also be used in our custom function. If we want for instance to build the test() function with perl support we would add: <br />
<br />
depends="perl"<br />
makedepends="perl-dev"<br />
<br />
If we would install the base package it would not install perl, but if we install the package-test package it would.<br />
<br />
==== Patches ====<br />
<br />
Please make sure you always submit human readable patches. Way's to create them are: <br />
<br />
directory compare: <br />
<br />
{{Cmd|diff -urp original_directory new_directory &gt; filename.patch}}<br />
<br />
file compare: <br />
<br />
{{Cmd|diff -up original.file new.file &gt; filename.patch}}<br />
<br />
If you are going to use multiple patches for a single package, the preferred way to handle those is a loop and numbering the patches. <br />
<br />
for i in "$srcdir"/*.patch; do<br />
msg "Applying ${i}"<br />
patch -p0 -i $i || return 1<br />
done<br />
<br />
Because multiple patches can patch the same file, we could create offset for the next patch. To make sure we always patch in a specified way we should number the patches as followed: <br />
<br />
10-patch1.patch 20-patch2.patch 30-patch3.patch<br />
<br />
This way we are always sure patch 1 is first and if we want to add additional patches between them we can use 11,12,21,22... <br />
<br />
==== Configure options ====<br />
<br />
Alpine has some default configure options we set by default. We use /usr for prefix to make sure everything is installed with /usr in front of it. If you notice that anything is installed in the wrong directory please run {{Cmd|./configure --help}} and see if you can set the correct location. <br />
<br />
We are not covering the depend switches here we have discussed this already in the depend section.<br />
<br />
{{Tip|Common steps for building package contain ''./configure'', ''make'' and ''make install''. Everyone of them should be enclosed by ''&#124;&#124; return 1'' to check exit status. Otherwise even if previous step fails e.g. ''./configure'', next will be launched e.g. ''make''. This complicates tracing the point, where package brakes. The same applies to installing additional files.}}<br />
<br />
==== Make options ====<br />
<br />
If you notice weird problems when compiling or installing the package with make/make install you could try to disable [http://www.gnu.org/software/make/manual/make.html#Parallel parallel] building/installing. A normal make line would be: <br />
<br />
make || return 1<br />
<br />
To disable parallel we use: <br />
<br />
make -j1 || return 1<br />
<br />
We can use the same for make install. <br />
<br />
Because we do not want to install the package in our build environment but we want to install it in a fake root directory we need to tell 'make install' to use another destination directory instead of '/'. We do this by setting a variable when we execute make install as followed: <br />
<br />
make DESTDIR="$pkgdir" install<br />
<br />
Please note that some Makefiles do not support this variable and will always install software in '/'. To make sure you do not mess up your build system NEVER run your build system as root but always use a custom user and sudo when needed. If by accident the Makefile does not support DESTDIR variable it will fail to install in our build system system directories.<br />
<br />
==== _builddir ====<br />
If you used <tt>newapkbuild</tt> to create your APKBUILD file, you must specify the path to your unpacked sources. Inside the sections during the prepare/build/install process ''_builddir'' is used. Most of the time a combination of ''$srcdir'' and ''$pkgname-$pkgver'' will work. When not, check the /src directory or the source tarball for the right string. Especially when you are working with automatically generated tarballs (like from github and gitorious), this needs to be adjusted.<br />
<br />
_builddir="$srcdir"/$pkgname-$pkgver<br />
<br />
==== Additional files ====<br />
<br />
If you want/need to install additional files not mentioned above you can use the following cmd (this is an example of a conf file): <br />
<br />
install -Dm644 doc/$pkgname.conf "$pkgdir"/etc/$pkgname.conf<br />
<br />
== Build the package ==<br />
<br />
If you did not already create the checksums as mentioned above you can do so now: <br />
<br />
{{Cmd|cd $pkgname<br />
abuild checksum}}<br />
<br />
It's about time we build our package. Because a build system should never have all the package installed to prevent linking to packages we don't want it to link we use a abuild recursively with the '''-r''' switch. It will install all dependency's from your repository and builds it, afterwards it will uninstall all those depending packages again. You could also use the '''-R''' switch which would build your package including the dependency packages. <br />
<br />
{{Cmd|abuild -r}}<br />
<br />
== Commit your work ==<br />
<br />
After you successfully build your package you can submit your APKBUILD to alpine git repository. <br />
<br />
Update your git repo, before adding new files: <br />
<br />
{{Cmd|cd $aportsdir<br />
git pull}}<br />
<br />
This should pull all the changes made by others into you local git repo. When you think you are ready you can add your files to git: <br />
<br />
{{Cmd|cd $apkbuilddir<br />
git add APKBUILD (include any other files needed for the build; $pkgname.install...)<br />
git commit}}<br />
<br />
Now your changes are only available locally in your repository. Because you do not have push rights to the Alpine aports repository you need to create diff (patch) of the changes you made and send this patch to the [http://lists.alpinelinux.org/alpine-devel/ alpine-devel mailinglist].<br />
<br />
== Send a patch ==<br />
<br />
[[Creating_patches#Only_the_last_commit_with_.27git_send-email.27|git send-email]] will do that for you.<br />
<br />
== See Also ==<br />
* [[APKBUILD Reference]]<br />
* [[Development using git]]</div>Forthhttps://wiki.alpinelinux.org/w/index.php?title=Creating_patches&diff=5638Creating patches2011-08-15T06:17:09Z<p>Forth: /* Only the last commit with 'git send-email' */</p>
<hr />
<div>There are several possible ways to send patches. Below the most common are described. <br />
<br />
== Only the last commit with 'git send-email' ==<br />
<br />
To submit the last commit as a patch to alpine-devel mailing list:<br />
<br />
{{Cmd|git send-email --to alpine-devel@lists.alpinelinux.org HEAD^}}<br />
<br />
The first line in commit message will be ''subject'' and the long description (separated with empty line) will be the body in the email. The example below shows <br />
<br />
<pre><br />
Initial APKBUILD file of packagename <- Subject line<br />
<br />
Enter some details about your package <- Mail body<br />
here if you like. <br />
</pre><br />
<br />
{{Note|The git send-email command is provided by the '''git-perl''' package. }}<br />
<br />
Read [[Development using git]] to send patch with SMTP Auth.<br />
<br />
== Multiple commits with 'git send-email' ==<br />
<br />
If you have many commits you can create a directory with patches and send them with <tt>git send-email</tt>.<br />
<br />
{{Cmd|<nowiki>rm -Rf patches<br />
mkdir patches<br />
git format-patch -o patches origin<br />
git send-email --compose --no-chain-reply-to --to alpine-devel@lists.alpinelinux.or</nowiki>}}<br />
<br />
This will produce the patches for each local commit in the directory "patches" and send them.<br />
Use --no-chain-reply-to make sure it doesn't reply.<br />
<br />
<!-- what does the following mean? --><br />
Don't do:<br />
* [PATCH 0/m]<br />
** [PATCH 1/m]<br />
*** [PATCH 2/m]<br />
**** ...<br />
But do:<br />
* [PATCH 0/m]<br />
** [PATCH 1/m]<br />
** [PATCH 2/m]<br />
** ..<br />
<br />
== Multiple patches with 'email' ==<br />
<br />
{{Cmd|git format-patch -1}}<br />
<br />
Where -1 sets how many commits you want to go back (mostly this is 1). This should create a patch called 0001......patch. <br />
<br />
An easy way to send this patch to the list is with an program called 'email'. <br />
<br />
{{Cmd|apk add email}}<br />
<br />
to send to the mailing list you would do: <br />
<br />
{{Cmd|email -a 0001...patch alpine-devel@lists.alpinelinux.org}}<br />
<br />
And provide a subject and body after you execute the above cmd.</div>Forthhttps://wiki.alpinelinux.org/w/index.php?title=Creating_patches&diff=5637Creating patches2011-08-15T06:14:23Z<p>Forth: /* Only the last commit with 'git send-email' */</p>
<hr />
<div>There are several possible ways to send patches. Below the most common are described. <br />
<br />
== Only the last commit with 'git send-email' ==<br />
<br />
To submit the last commit as a patch to alpine-devel mailing list:<br />
<br />
{{Cmd|git send-email --to alpine-devel@lists.alpinelinux.org HEAD^}}<br />
<br />
The first line in commit message will be ''subject'' and the long description (separated with empty line) will be the body in the email. The example below shows <br />
<br />
<pre><br />
Initial APKBUILD file of packagename <- Subject line<br />
<br />
Enter some details about your package <- Mail body<br />
here if you like. <br />
</pre><br />
<br />
{{Note|The git send-email command is provided by the '''git-perl''' package. }}<br />
<br />
Read http://wiki.alpinelinux.org/wiki/Development_using_git<br />
to send patch with SMTP Auth.<br />
<br />
== Multiple commits with 'git send-email' ==<br />
<br />
If you have many commits you can create a directory with patches and send them with <tt>git send-email</tt>.<br />
<br />
{{Cmd|<nowiki>rm -Rf patches<br />
mkdir patches<br />
git format-patch -o patches origin<br />
git send-email --compose --no-chain-reply-to --to alpine-devel@lists.alpinelinux.or</nowiki>}}<br />
<br />
This will produce the patches for each local commit in the directory "patches" and send them.<br />
Use --no-chain-reply-to make sure it doesn't reply.<br />
<br />
<!-- what does the following mean? --><br />
Don't do:<br />
* [PATCH 0/m]<br />
** [PATCH 1/m]<br />
*** [PATCH 2/m]<br />
**** ...<br />
But do:<br />
* [PATCH 0/m]<br />
** [PATCH 1/m]<br />
** [PATCH 2/m]<br />
** ..<br />
<br />
== Multiple patches with 'email' ==<br />
<br />
{{Cmd|git format-patch -1}}<br />
<br />
Where -1 sets how many commits you want to go back (mostly this is 1). This should create a patch called 0001......patch. <br />
<br />
An easy way to send this patch to the list is with an program called 'email'. <br />
<br />
{{Cmd|apk add email}}<br />
<br />
to send to the mailing list you would do: <br />
<br />
{{Cmd|email -a 0001...patch alpine-devel@lists.alpinelinux.org}}<br />
<br />
And provide a subject and body after you execute the above cmd.</div>Forthhttps://wiki.alpinelinux.org/w/index.php?title=Creating_patches&diff=5634Creating patches2011-08-14T22:49:42Z<p>Forth: /* Only the last commit with 'git send-email' */</p>
<hr />
<div>There are several possible ways to send patches. Below the most common are described. <br />
<br />
== Only the last commit with 'git send-email' ==<br />
<br />
To submit the last commit as a patch to alpine-devel mailing list:<br />
<br />
{{Cmd|git send-email --to alpine-devel@lists.alpinelinux.org HEAD^}}<br />
<br />
The first line in commit message will be ''subject'' and the long description (separated with empty line) will be the body in the email. The example below shows <br />
<br />
<pre><br />
Initial APKBUILD file of packagename <- Subject line<br />
<br />
Enter some details about your package <- Mail body<br />
here if you like. <br />
</pre><br />
<br />
{{Note|The git send-email command is provided by the '''git-perl''' package. }}<br />
<br />
How to send your patches through smtp-auth : https://git.wiki.kernel.org/index.php/GitTips#Using_msmtp_to_send_your_patches<br />
<br />
== Multiple commits with 'git send-email' ==<br />
<br />
If you have many commits you can create a directory with patches and send them with <tt>git send-email</tt>.<br />
<br />
{{Cmd|<nowiki>rm -Rf patches<br />
mkdir patches<br />
git format-patch -o patches origin<br />
git send-email --compose --no-chain-reply-to --to alpine-devel@lists.alpinelinux.or</nowiki>}}<br />
<br />
This will produce the patches for each local commit in the directory "patches" and send them.<br />
Use --no-chain-reply-to make sure it doesn't reply.<br />
<br />
<!-- what does the following mean? --><br />
Don't do:<br />
* [PATCH 0/m]<br />
** [PATCH 1/m]<br />
*** [PATCH 2/m]<br />
**** ...<br />
But do:<br />
* [PATCH 0/m]<br />
** [PATCH 1/m]<br />
** [PATCH 2/m]<br />
** ..<br />
<br />
== Multiple patches with 'email' ==<br />
<br />
{{Cmd|git format-patch -1}}<br />
<br />
Where -1 sets how many commits you want to go back (mostly this is 1). This should create a patch called 0001......patch. <br />
<br />
An easy way to send this patch to the list is with an program called 'email'. <br />
<br />
{{Cmd|apk add email}}<br />
<br />
to send to the mailing list you would do: <br />
<br />
{{Cmd|email -a 0001...patch alpine-devel@lists.alpinelinux.org}}<br />
<br />
And provide a subject and body after you execute the above cmd.</div>Forthhttps://wiki.alpinelinux.org/w/index.php?title=Template:Copying_Alpine_to_Flash&diff=5633Template:Copying Alpine to Flash2011-08-14T22:19:36Z<p>Forth: /* Format {{{1|Flash Medium}}} */</p>
<hr />
<div>== Copy Alpine to a {{{1|Flash Medium}}} ==<br />
<br />
# Insert the removable {{{1|flash medium (CF or USB stick)}}} into the computer.<br />
# Determine the name your computer uses for your {{{1|flash medium}}}. The following step is one way to do this.<br />
#* After inserting the {{{1|flash medium}}}, run the command:<br />
#* {{Cmd|dmesg}}<br />
#* At the end of this command you should see the name of your {{{1|flash medium}}}, likely starting with "sd". (For example: "sda").<br />
#* The remainder of this document will assume that your {{{1|flash medium}}} is called /dev/sda<br />
<br />
{{Warning|Be very careful about this. You do not want to mistakenly wipe your hard drive if it's on /dev/sda}}<br />
<br />
=== Format {{{1|Flash Medium}}} ===<br />
{{Cmd|fdisk /dev/sda}}<br />
* '''p''' Print list of partitions<br />
* '''d''' Delete all partitions (this may take a few steps)<br />
* '''n''' Create a new partition<br />
* '''p''' A primary partition<br />
* '''1''' Partition number 1<br />
** Use defaults for first and last cylinder (just press [Enter] twice).<br />
* '''t''' Change partition type<br />
* '''c''' Type: Win95 FAT32 (LBA)<br />
* '''a''' <big>Make the partition bootable (set boot flag)</big><br />
* '''1''' Partition number 1<br />
* '''w''' Write your changes to the device<br />
<br />
=== Install Syslinux ===<br />
{{Note|If the following commands fail due to 'No such file or directory', you may have to remove and reinsert the CF card, or even reboot, to get /dev/sda1 to appear}}<br />
# Install syslinux and dosfstools. If you have booted from an Alpine CD-ROM, use these commands:<br />
#* {{Cmd|apk add syslinux dosfstools}}<br />
#* {{Cmd|{{{|dd if=/usr/share/syslinux/mbr.bin of=/dev/sda}}}}}<br />
# Format the {{{1|flash medium}}} with a VFAT filesystem:<br />
#* {{Cmd|mkdosfs -F32 /dev/sda1}}<br />
#* {{Cmd|syslinux /dev/sda1}}<br />
#* {{Cmd|mkdir -p /media/sda1}}<br />
#* {{Cmd|mount -t vfat /dev/sda1 /media/sda1}}<br />
# Mount the Alpine Linux CD-ROM, and copy the files to the {{{1|flash medium}}}<br />
#* {{Cmd|mount /media/cdrom}}<br />
#* {{Cmd|cd /media/cdrom}}<br />
#* {{Cmd|cp -a .alpine-release * /media/sda1/ }}<br />
<br />
== Troubleshooting ==<br />
When your USB device is formatted to other filesystem than fat32, you might have to specify the necessary filesystem modules in boot parameters.<br />
<br />
To do so, mount the device, and alter the syslinux.cfg file line from <br />
append initrd=/boot/grsec.gz alpine_dev=usbdisk:vfat modules=loop,cramfs,sd-mod,usb-storage quiet<br />
to<br />
append initrd=/boot/grsec.gz alpine_dev=usbdisk:vfat modules=loop,cramfs,sd-mod,usb-storage,ext3 quiet<br />
<br />
in case of using ext3 formatted partition. Similar procedure might apply to other filesystems (if they are supported by syslinux or other bootloader of your choice and alpine kernel).<br />
<br />
Also, specifying waitusb=X option might help with certain usb devices that take a bit longer to register. X stands for the amount of seconds kernel will wait before looking for the installation media.</div>Forthhttps://wiki.alpinelinux.org/w/index.php?title=Creating_patches&diff=5632Creating patches2011-08-14T22:13:58Z<p>Forth: /* Multiple commits with 'git send-email' */</p>
<hr />
<div>There are several possible ways to send patches. Below the most common are described. <br />
<br />
== Only the last commit with 'git send-email' ==<br />
<br />
To submit the last commit as a patch to alpine-devel mailing list:<br />
<br />
{{Cmd|git send-email --to alpine-devel@lists.alpinelinux.org HEAD^}}<br />
<br />
The first line in commit message will be ''subject'' and the long description (separated with empty line) will be the body in the email. The example below shows <br />
<br />
<pre><br />
Initial APKBUILD file of packagename <- Subject line<br />
<br />
Enter some details about your package <- Mail body<br />
here if you like. <br />
</pre><br />
<br />
{{Note|The git send-email command is provided by the '''git-perl''' package. }}<br />
<br />
if it fails, try to install postfix to have a sendmail binary (default shipped is busybox's).<br />
<br />
== Multiple commits with 'git send-email' ==<br />
<br />
If you have many commits you can create a directory with patches and send them with <tt>git send-email</tt>.<br />
<br />
{{Cmd|<nowiki>rm -Rf patches<br />
mkdir patches<br />
git format-patch -o patches origin<br />
git send-email --compose --no-chain-reply-to --to alpine-devel@lists.alpinelinux.or</nowiki>}}<br />
<br />
This will produce the patches for each local commit in the directory "patches" and send them.<br />
Use --no-chain-reply-to make sure it doesn't reply.<br />
<br />
<!-- what does the following mean? --><br />
Don't do:<br />
* [PATCH 0/m]<br />
** [PATCH 1/m]<br />
*** [PATCH 2/m]<br />
**** ...<br />
But do:<br />
* [PATCH 0/m]<br />
** [PATCH 1/m]<br />
** [PATCH 2/m]<br />
** ..<br />
<br />
== Multiple patches with 'email' ==<br />
<br />
{{Cmd|git format-patch -1}}<br />
<br />
Where -1 sets how many commits you want to go back (mostly this is 1). This should create a patch called 0001......patch. <br />
<br />
An easy way to send this patch to the list is with an program called 'email'. <br />
<br />
{{Cmd|apk add email}}<br />
<br />
to send to the mailing list you would do: <br />
<br />
{{Cmd|email -a 0001...patch alpine-devel@lists.alpinelinux.org}}<br />
<br />
And provide a subject and body after you execute the above cmd.</div>Forthhttps://wiki.alpinelinux.org/w/index.php?title=Creating_patches&diff=5631Creating patches2011-08-14T22:03:46Z<p>Forth: /* Only the last commit with 'git send-email' */ troublesome</p>
<hr />
<div>There are several possible ways to send patches. Below the most common are described. <br />
<br />
== Only the last commit with 'git send-email' ==<br />
<br />
To submit the last commit as a patch to alpine-devel mailing list:<br />
<br />
{{Cmd|git send-email --to alpine-devel@lists.alpinelinux.org HEAD^}}<br />
<br />
The first line in commit message will be ''subject'' and the long description (separated with empty line) will be the body in the email. The example below shows <br />
<br />
<pre><br />
Initial APKBUILD file of packagename <- Subject line<br />
<br />
Enter some details about your package <- Mail body<br />
here if you like. <br />
</pre><br />
<br />
{{Note|The git send-email command is provided by the '''git-perl''' package. }}<br />
<br />
if it fails, try to install postfix to have a sendmail binary (default shipped is busybox's).<br />
<br />
== Multiple commits with 'git send-email' ==<br />
<br />
If you have many commits you can create a directory with patches and send them with <tt>git send-email</tt>.<br />
<br />
{{Cmd|<nowiki>rm -Rf patches<br />
mkdir patches<br />
git format-patch -o patches origin<br />
git send-email --to alpine-devel@lists.alpinelinux.org patches</nowiki>}}<br />
<br />
If you have multiple patch consider using:<br />
{{Cmd|git send-email --compose --no-chain-reply-to --to alpine-devel@lists.alpinelinux.org patches}}<br />
This will produce the patches for each local commit in the directory "patches" and send them.<br />
Use --no-chain-reply-to make sure it doesn't reply.<br />
<br />
<!-- what does the following mean? --><br />
Don't do:<br />
* [PATCH 0/m]<br />
** [PATCH 1/m]<br />
*** [PATCH 2/m]<br />
**** ...<br />
But do:<br />
* [PATCH 0/m]<br />
** [PATCH 1/m]<br />
** [PATCH 2/m]<br />
** ..<br />
<br />
== Multiple patches with 'email' ==<br />
<br />
{{Cmd|git format-patch -1}}<br />
<br />
Where -1 sets how many commits you want to go back (mostly this is 1). This should create a patch called 0001......patch. <br />
<br />
An easy way to send this patch to the list is with an program called 'email'. <br />
<br />
{{Cmd|apk add email}}<br />
<br />
to send to the mailing list you would do: <br />
<br />
{{Cmd|email -a 0001...patch alpine-devel@lists.alpinelinux.org}}<br />
<br />
And provide a subject and body after you execute the above cmd.</div>Forthhttps://wiki.alpinelinux.org/w/index.php?title=Creating_an_Alpine_package&diff=5630Creating an Alpine package2011-08-14T20:03:46Z<p>Forth: </p>
<hr />
<div>== General ==<br />
<br />
This document assumes that you have a working [[Setting up the build environment|build environment]], or use a diskbased alpine installation. <br />
<br />
=== The APKBUILDs ===<br />
<br />
The ''[http://git.alpinelinux.org/cgit/abuild/ abuild]'' script reads the ''[http://git.alpinelinux.org/cgit/abuild/tree/sample.APKBUILD APKBUILD]'' and executes the steps needed to create a package. <br />
<br />
=== The aports tree ===<br />
<br />
The [http://git.alpinelinux.org/cgit/aports aports] tree is a [http://git.alpinelinux.org/cgit/aports/tree directory tree] with many APKBUILDs. Those files are used when building alpine from source. <br />
<br />
== Installing and configuring the alpine-sdk ==<br />
<br />
The alpine-sdk is a metapackage that pulls in the most essential packages used to build new packages.<BR><br />
Install those packages now: <br />
<br />
{{Cmd|apk add alpine-sdk}}<br />
<br />
This would be a good time to create a normal user account for you to work in. (You weren't going to develop as root now, were you!) To create the user:<br />
<br />
{{Cmd|adduser <yourusername>}}<br />
<br />
To make life easier later, it's a good idea to add this user to /etc/sudoers. Append the line<br />
<br />
<yourusername> ALL=(ALL) ALL<br />
<br />
using the command:<br />
<br />
{{Cmd|visudo}}<br />
<br />
Now logout of the root account, and login as <yourusername>. From here on everything can be done in a normal user account, and operations that require superuser privileges can be done with sudo.<br />
<br />
The aports tree is in git so before we clone the aports tree we should configure git.<br />
<br />
{{Cmd|git config --global user.name "Your Full Name"<br />
git config --global user.email "your@email.address"}}<br />
<br />
Now we can clone the aports tree. <br />
<br />
{{Cmd|git clone git://dev.alpinelinux.org/aports}}<br />
<br />
Before we start creating or modifying APKBUILD files we need to setup abuild to our system/user. Edit the file abuild.conf to your requirements. Most of the defaults can be left alone, unless you are developing for a custom platform, in which case the comments in the file should guide you. The one field to edit is PACKAGER, so that you can get credit (or blame) for packages you create.<br />
<br />
{{Cmd|sudo vi /etc/abuild.conf}}<br />
<br />
We also need to prepare the location that the build process caches files when they are downloaded. By default this is /var/cache/distfiles. To create this directory and ensure that it is writeable, enter the following commands:<br />
<br />
{{Cmd|sudo mkdir -p /var/cache/distfiles}}<br />
{{Cmd|sudo chmod a+w /var/cache/distfiles}}<br />
<br />
Or add yourself to the abuild group<br />
<br />
{{Cmd|sudo groupadd <yourusername> abuild}}<br />
<br />
The last step in preparation is to configure the security keys for abuild with the command:<br />
<br />
{{Cmd|abuild-keygen -a -i}}<br />
<br />
== Getting some help ==<br />
<br />
It might be wise to start by checking what the abuild program can/cannot do.<br />
<br />
{{Cmd|abuild -h}}<br />
<br />
== Creating an APKBUILD file ==<br />
<br />
=== Use a template APKBUILD ===<br />
<br />
To create the actual APKBUILD file <tt>newapkbuild</tt> can serve you a template to start with. It will create a directory with the given package name, place an example/template APKBUILD file to the given directory, and fill some variables if those are provided. Please check the [[Package_policies| package policies]] page about naming details.<br />
<br />
If you doubt to which repository your package belongs to you can safely use '''testing'''. Building package in your aports/testing directory is not mandatory but this way the package is already at the right place.<br />
<br />
{{Cmd|newapkbuild ''packagename''}}<br />
<br />
'''newapkbuild options'''<br />
<br />
* '''-a''' Create autotools (use ./configure ...)<br />
* '''-c''' Copy a sample init.d, conf.d and install script to new directory<br />
* '''-d''' Set package description (pkgdesc) to DESC<br />
* '''-f''' Force even if directory already exist<br />
* '''-h''' Show this help<br />
* '''-l''' Set package license to LICENSE<br />
* '''-p''' Create perl package (Assume Makefile.PL is there)<br />
* '''-u''' Set package URL<br />
* '''-s''' Use sourceforge source url<br />
<br />
{{Note|On older Alpine systems, abuild -c -n ''packagename'' was the way to create APKBUILD files. The 'packagename' was a parameter to the -n option so order of -c and -n matters. }}<br />
<br />
If you are create a daemon package which needs initd scripts you can add the -c making it: <br />
<br />
{{Cmd|newapkbuild -c ''packagename''}}<br />
<br />
This will copy the sample initd and confd files to the build directory.<BR><br />
A third file sample.install file will be copied as well (we will discuss this later on).<br />
<br />
=== Modify your APKBUILD ===<br />
Edit APKBUILD and fill in the needed info (especially pkgname, pkgver, pkgdesc, url, license, depends and source). <br />
<br />
If you are going to use any of the variables for directories like $pkgdir, always make sure they are double quoted like: <br />
<br />
"$pkgdir"/somedir<br />
<br />
This will prevent issues with spaces/special characters in the future. <br />
<br />
{{Note|If you like syntax highlighting we suggest you to install vim. We have setup vim to recognize the APKBUILD file as a bash scripts so its easier to read them.}}<br />
<br />
=== APKBUILD variables/functions ===<br />
<br />
==== source ====<br />
<br />
The source variable is not only used to list the remote source files to fetch, it is also used to list the local files that abuild will need in order to build the apk. Examples of such local files include: init.d files, conf.d files, install files (see [[Creating an Alpine package#install|install variable]]), patches, and all other necessary files.<br />
<br />
Here are few things to note:<br />
<br />
* When you are finished adding local and/or remote files to ''source'', you can execute the following command to add their checksums to the APKBUILD file:<br />
: {{cmd|abuild checksum}}<br />
: {{Note|When later updating the content of ''source'', or updating a file that is listed in ''source'', you must also update their checksums again with the same command.}}<br />
<br />
* When the remote file is hosted at SourceForge, it's best to specify the special mirrors link used by SourceForge:<br />
: <pre>http://downloads.sourceforge.net/$pkgname/$pkgname-$pkgver.tar.gz</pre><br />
: (or similar depending on the package).<br />
<br />
* When the remote filename is not specified in the URI (ie, does not end in '/software-1.0.tar.gz'), such as:<br />
: <pre>http://oss.example.org/?get=software&ver=1.0</pre><br />
: You must prepend 'saveas-' to the protocol and append '/software-1.0.tar.gz' (for instance) to the end of the URI, like so:<br />
: <pre>saveas-http://oss.example.org/?get=software&ver=1.0/software-1.0.tar.gz</pre><br />
: This causes the file to be saved as ''software-1.0.tar.gz'' where abuild can use it, instead of ''?get=software&ver=1.0'', where abuild cannot use it.<br />
<br />
* abuild currently supports the following protocols for remote file retrieval:<br />
** http<br />
** https<br />
** ftp<br />
<br />
: {{Note|If the you want to download from https, you need GNU wget installed on your system.}}<br />
<br />
* abuild currently supports the following archive types/archive file extensions:<br />
** .tar.gz / .tgz<br />
** .tar.bz2<br />
** .tar.lzma<br />
** .tar.xz<br />
** .zip<br />
<br />
==== depends &amp; makedepends ====<br />
<br />
Depends are the actual running dependencies that a package would need when it is running. Makedepends are only needed when you are building a package. If you set a package, in depends you do not need to add it to makedepends as well. The best way to find out what the depends and makedepends of a package are is to [http://en.wikipedia.org/wiki/Rtfm RTFM]. <br />
<br />
No kidding, lots of important information can be found it the package INSTALL and README file (or the likes). Another good way is the run ./configure --help from the source directory to see which options are needed for configure to finish without errors. If you do not yet have a src directory you can create one with the command: <br />
<br />
{{Cmd|abuild unpack}}<br />
<br />
Running configure will also show you how you can disable a specific option for this package. A good example is for instance "--disable-nls" which will disable native language support and thus does not depend on gettext(libiconv,glib..). <br />
<br />
Alpine likes to keep things small, so we try to disable as much as possible without losing too many features. The exact disable/enable options are decided the package builder but please try to follow Alpine's design concept as much as possible. <br />
<br />
An easy way of quickly finding out the build info for a package is to check Arch Linux (Alpine package management and build scripts are similar) or Gentoo linux ebuilds (previous versions of Alpine were based on Gentoo). <br />
<br />
* [http://www.gentoo-portage.com Search ebuilds] <br />
* [http://sources.gentoo.org/viewcvs.py/gentoo-x86/ Gentoo CVS] <br />
* [http://www.archlinux.org/packages/search/ Arch Linux packages] <br />
<br />
After the package is successfully compiled and created we should make sure it didn't link to any package that is not present in the $depends variable. We do this by using scanelf. If scanelf is not yet installed on your system you can do that by installing pax-utils. <br />
<br />
{{Cmd|scanelf -nR pkg}}<br />
<br />
An example output of libcurl would be: <br />
<br />
ET_DYN libssl.so.0.9.8,libcrypto.so.0.9.8,libz.so.1,libc.so.0,ld-uClibc.so.0 pkg/usr/lib/libcurl.so.4.1.1<br />
<br />
You can see the needed files and should be able to find out which file belongs to which package.<br />
<br />
==== license ====<br />
<br />
If a package has a special/custom license we need to provide it with the release. Because we want to save space and don't like to have licenses all over our system we have decided to include the license in the doc subpackage. Please follow the following guidelines to add a proper license. Locate the license file inside the source package. Add the doc subpackage to the $subpackages variable as follows: <br />
<br />
subpackages="$pkgname-doc"<br />
<br />
Add a similar line to the following to your package() function, depending on the license description file: <br />
<br />
install -Dm644 COPYING "$pkgdir"/usr/share/licenses/$pkgname/COPYING<br />
<br />
If you follow these steps then abuild will automatically add the license to the package-doc apk for you.<br />
<br />
==== arch ====<br />
<br />
The package architecture(s) to build for. This can be one of: ''x86, x86_64, all,'' or ''noarch'', where ''all'' means all architectures, and ''noarch'' means it's architecture-independent (ie, a pure-python package).<br />
{{Tip|To determine if your APKBUILD can use ''noarch'', build the package for your architecture and then run "scanelf -R pkg" from the directory that the APKBUILD resides in, in order to scan for ELF files in the ''./pkg'' directory. If you do NOT get output from this, then ''noarch'' can be used.}}<br />
<br />
==== url ====<br />
<br />
Website address for the program. This is usefully later on when either finding documentation or other information about the package.<br />
<br />
==== pkgdesc ====<br />
<br />
A brief, one line, description of what the package does. Useful for the package management system.<br />
<br />
Here is an example from apk_info for the OpenSSH client package<br />
<br />
pkgdesc="Port of OpenBSD's free SSH release - client"<br />
<br />
==== pkgver ====<br />
<br />
Provide the release number of the package you are building.<br />
<br />
==== pkgrel ====<br />
<br />
The $pkgrel versioning is made so if you change something to your APKBUILD file without changing the actual $pkgver you can higer pkgrel so apk tools will detect it as an update. For instance if you forget to add a dependency you can add it afterward and you can +1 pkgver so apk finds this update and add the missing dependency. <br />
<br />
==== pkgname ====<br />
<br />
The base name of the package you are creating. For Freeswitch 1.0.6, you would use "freeswitch"<br />
<br />
==== install ====<br />
<br />
There are 6 different kinds of install scripts. Each script is called with the $pkgname.''<action>'' where ''<action>'' is one of the following:<br />
<br />
===== $pkgname.pre-install =====<br />
This script is executed before package is installed. Typical use is when package needs a user/group to be created. For example:<br />
<pre><br />
#!/bin/sh<br />
adduser -H -s /bin/false -D clamav 2>/dev/null<br />
exit 0<br />
</pre><br />
Note the ''exit 0'' at the end. If the script exits with failure (if the user already exist), the package will not be installed and apk add will exit with failure.<br />
<br />
===== $pkgname.post-install =====<br />
This script is executed after package is installed. Can be used to generate font cache and similar.<br />
<br />
===== $pkgname.pre-upgrade =====<br />
Same as pre-install but is executed before upgrading an already installed package.<br />
<br />
===== $pkgname.post-upgrade =====<br />
Same as post-install but is executed after upgrading an already installed package. <br />
<br />
===== $pkgname.pre-deinstall =====<br />
This script is executed before uninstalling a package. If script exits with failure apk will not uninstall the package.<br />
<br />
===== $pkgname.post-deinstall =====<br />
This script is executed after a package have been uninstalled. Can be used to update font caches and restore busybox links. For example:<br />
<pre><br />
#!/bin/sh<br />
busybox --install -s<br />
</pre><br />
<br />
<br />
If the package have an pre-install and post-install script the APKBUILD should have the ''install'' variable defined and the scripts should also be added to the source variable:<br />
<pre><br />
...<br />
install="$pkgname.pre-install $pkgname.post-install"<br />
source="http://....<br />
$install"<br />
...<br />
</pre><br />
<br />
==== subpackages ====<br />
<br />
$subpackages are made to split up the normal "make install" into separate packages. The most common subpackages we use are doc and dev. Because we like to keep our target system small we move documentation and development files (only needed when building packages) into separate packages. To use the specific program a user only need to install the base apk without package-doc or package-dev, but if he wants to read the manual he will need to install package-doc. <br />
<br />
The easiest way to find out if you need to use -dev and -doc is to first build the package without these options set and wait until the build finishes. When its finished you should have a pkg directory which is the fake root directory. Inside this directory you will see the structure as how it would be installed in / on the target system. <br />
<br />
To see if you need the -dev package you can run the following cmd: <br />
<br />
{{Cmd|find pkg/usr/ -name '*.[acho]' -o -name '*.la'}}<br />
<br />
If this returns any files you need to include the -dev package. <br />
<br />
<br> To see if you need the -doc package you can run the following cmd: <br />
<br />
{{Cmd|find pkg/usr/share -name doc -o -name man -o -name info -o -name html -o -name sgml -o -name licenses}}<br />
<br />
If this returns any directories you need to include the -doc package. <br />
<br />
===== Custom subpackages =====<br />
<br />
Some applications will have except doc and dev files other non needed at run time files which we want to separate away from the base package. Some packages include large test suites which are only needed in specific circumstances or binaries which have depends which we prefer not to install. To handle those we create our own package/function. In the APKBUILD below the build() function we create another function: <br />
<br />
test() {<br />
mkdir -p "$subpkgdir"/usr<br />
mv "$pkgdir"/usr/package-test "$subpkgdir"/usr/<br />
}<br />
<br />
<br />
We also need to add the package info to $subpackages variable: <br />
<br />
subpackages="$pkgname-doc $pkgname-dev $pkgname-test"<br />
<br />
After we finish building the package you should see another apk called packagename-test.apk which includes the files which we moved to the $subpkgdir dir. <br />
<br />
The above mentioned variables can also be used in our custom function. If we want for instance to build the test() function with perl support we would add: <br />
<br />
depends="perl"<br />
makedepends="perl-dev"<br />
<br />
If we would install the base package it would not install perl, but if we install the package-test package it would.<br />
<br />
==== Patches ====<br />
<br />
Please make sure you always submit human readable patches. Way's to create them are: <br />
<br />
directory compare: <br />
<br />
{{Cmd|diff -urp original_directory new_directory &gt; filename.patch}}<br />
<br />
file compare: <br />
<br />
{{Cmd|diff -up original.file new.file &gt; filename.patch}}<br />
<br />
If you are going to use multiple patches for a single package, the preferred way to handle those is a loop and numbering the patches. <br />
<br />
for i in "$srcdir"/*.patch; do<br />
msg "Applying ${i}"<br />
patch -p0 -i $i || return 1<br />
done<br />
<br />
Because multiple patches can patch the same file, we could create offset for the next patch. To make sure we always patch in a specified way we should number the patches as followed: <br />
<br />
10-patch1.patch 20-patch2.patch 30-patch3.patch<br />
<br />
This way we are always sure patch 1 is first and if we want to add additional patches between them we can use 11,12,21,22... <br />
<br />
==== Configure options ====<br />
<br />
Alpine has some default configure options we set by default. We use /usr for prefix to make sure everything is installed with /usr in front of it. If you notice that anything is installed in the wrong directory please run {{Cmd|./configure --help}} and see if you can set the correct location. <br />
<br />
We are not covering the depend switches here we have discussed this already in the depend section.<br />
<br />
{{Tip|Common steps for building package contain ''./configure'', ''make'' and ''make install''. Everyone of them should be enclosed by ''&#124;&#124; return 1'' to check exit status. Otherwise even if previous step fails e.g. ''./configure'', next will be launched e.g. ''make''. This complicates tracing the point, where package brakes. The same applies to installing additional files.}}<br />
<br />
==== Make options ====<br />
<br />
If you notice weird problems when compiling or installing the package with make/make install you could try to disable [http://www.gnu.org/software/make/manual/make.html#Parallel parallel] building/installing. A normal make line would be: <br />
<br />
make || return 1<br />
<br />
To disable parallel we use: <br />
<br />
make -j1 || return 1<br />
<br />
We can use the same for make install. <br />
<br />
Because we do not want to install the package in our build environment but we want to install it in a fake root directory we need to tell 'make install' to use another destination directory instead of '/'. We do this by setting a variable when we execute make install as followed: <br />
<br />
make DESTDIR="$pkgdir" install<br />
<br />
Please note that some Makefiles do not support this variable and will always install software in '/'. To make sure you do not mess up your build system NEVER run your build system as root but always use a custom user and sudo when needed. If by accident the Makefile does not support DESTDIR variable it will fail to install in our build system system directories.<br />
<br />
==== _builddir ====<br />
If you used <tt>newapkbuild</tt> to create your APKBUILD file, you must specify the path to your unpacked sources. Inside the sections during the prepare/build/install process ''_builddir'' is used. Most of the time a combination of ''$srcdir'' and ''$pkgname-$pkgver'' will work. When not, check the /src directory or the source tarball for the right string. Especially when you are working with automatically generated tarballs (like from github and gitorious), this needs to be adjusted.<br />
<br />
_builddir="$srcdir"/$pkgname-$pkgver<br />
<br />
==== Additional files ====<br />
<br />
If you want/need to install additional files not mentioned above you can use the following cmd (this is an example of a conf file): <br />
<br />
install -Dm644 doc/$pkgname.conf "$pkgdir"/etc/$pkgname.conf<br />
<br />
== Build the package ==<br />
<br />
If you did not already create the checksums as mentioned above you can do so now: <br />
<br />
{{Cmd|cd $pkgname<br />
abuild checksum}}<br />
<br />
It's about time we build our package. Because a build system should never have all the package installed to prevent linking to packages we don't want it to link we use a abuild recursively with the '''-r''' switch. It will install all dependency's from your repository and builds it, afterwards it will uninstall all those depending packages again. You could also use the '''-R''' switch which would build your package including the dependency packages. <br />
<br />
{{Cmd|abuild -r}}<br />
<br />
== Commit your work ==<br />
<br />
After you successfully build your package you can submit your APKBUILD to alpine git repository. <br />
<br />
Update your git repo, before adding new files: <br />
<br />
{{Cmd|cd $aportsdir<br />
git pull}}<br />
<br />
This should pull all the changes made by others into you local git repo. When you think you are ready you can add your files to git: <br />
<br />
{{Cmd|cd $apkbuilddir<br />
git add APKBUILD (include any other files needed for the build; $pkgname.install...)<br />
git commit}}<br />
<br />
Now your changes are only available locally in your repository. Because you do not have push rights to the Alpine aports repository you need to create diff (patch) of the changes you made and send this patch to the [http://lists.alpinelinux.org/alpine-devel/ alpine-devel mailinglist].<br />
<br />
== Send a patch ==<br />
<br />
[[Creating_patches#Only_the_last_commit_with_.27git_send-email.27|git send-email]] will do that for you.<br />
<br />
== See Also ==<br />
* [[APKBUILD Reference]]<br />
* [[Development using git]]</div>Forthhttps://wiki.alpinelinux.org/w/index.php?title=Creating_an_Alpine_package&diff=5629Creating an Alpine package2011-08-14T19:58:47Z<p>Forth: /* Installing and configuring the alpine-sdk */ add your user to abuild group</p>
<hr />
<div>== General ==<br />
<br />
This document assumes that you have a working [[Setting up the build environment|build environment]], or use a diskbased alpine installation. <br />
<br />
=== The APKBUILDs ===<br />
<br />
The ''[http://git.alpinelinux.org/cgit/abuild/ abuild]'' script reads the ''[http://git.alpinelinux.org/cgit/abuild/tree/sample.APKBUILD APKBUILD]'' and executes the steps needed to create a package. <br />
<br />
=== The aports tree ===<br />
<br />
The [http://git.alpinelinux.org/cgit/aports aports] tree is a [http://git.alpinelinux.org/cgit/aports/tree directory tree] with many APKBUILDs. Those files are used when building alpine from source. <br />
<br />
== Installing and configuring the alpine-sdk ==<br />
<br />
The alpine-sdk is a metapackage that pulls in the most essential packages used to build new packages.<BR><br />
Install those packages now: <br />
<br />
{{Cmd|apk add alpine-sdk}}<br />
<br />
This would be a good time to create a normal user account for you to work in. (You weren't going to develop as root now, were you!) To create the user:<br />
<br />
{{Cmd|adduser <yourusername>}}<br />
<br />
To make life easier later, it's a good idea to add this user to /etc/sudoers. Append the line<br />
<br />
<yourusername> ALL=(ALL) ALL<br />
<br />
using the command:<br />
<br />
{{Cmd|visudo}}<br />
<br />
add yourself to the abuild group (otherwise you won't be able to download packages into /var/cache/distfiles/ )<br />
<br />
{{Cmd|sudo groupadd <yourusername> abuild}}<br />
<br />
Now logout of the root account, and login as <yourusername>. From here on everything can be done in a normal user account, and operations that require superuser privileges can be done with sudo.<br />
<br />
The aports tree is in git so before we clone the aports tree we should configure git.<br />
<br />
{{Cmd|git config --global user.name "Your Full Name"<br />
git config --global user.email "your@email.address"}}<br />
<br />
Now we can clone the aports tree. <br />
<br />
{{Cmd|git clone git://dev.alpinelinux.org/aports}}<br />
<br />
Before we start creating or modifying APKBUILD files we need to setup abuild to our system/user. Edit the file abuild.conf to your requirements. Most of the defaults can be left alone, unless you are developing for a custom platform, in which case the comments in the file should guide you. The one field to edit is PACKAGER, so that you can get credit (or blame) for packages you create.<br />
<br />
{{Cmd|sudo vi /etc/abuild.conf}}<br />
<br />
We also need to prepare the location that the build process caches files when they are downloaded. By default this is /var/cache/distfiles. To create this directory and ensure that it is writeable, enter the following commands:<br />
<br />
{{Cmd|sudo mkdir -p /var/cache/distfiles}}<br />
{{Cmd|sudo chmod a+w /var/cache/distfiles}}<br />
<br />
The last step in preparation is to configure the security keys for abuild with the command:<br />
<br />
{{Cmd|abuild-keygen -a -i}}<br />
<br />
== Getting some help ==<br />
<br />
It might be wise to start by checking what the abuild program can/cannot do.<br />
<br />
{{Cmd|abuild -h}}<br />
<br />
== Creating an APKBUILD file ==<br />
<br />
=== Use a template APKBUILD ===<br />
<br />
To create the actual APKBUILD file <tt>newapkbuild</tt> can serve you a template to start with. It will create a directory with the given package name, place an example/template APKBUILD file to the given directory, and fill some variables if those are provided. Please check the [[Package_policies| package policies]] page about naming details.<br />
<br />
If you doubt to which repository your package belongs to you can safely use '''testing'''. Building package in your aports/testing directory is not mandatory but this way the package is already at the right place.<br />
<br />
{{Cmd|newapkbuild ''packagename''}}<br />
<br />
'''newapkbuild options'''<br />
<br />
* '''-a''' Create autotools (use ./configure ...)<br />
* '''-c''' Copy a sample init.d, conf.d and install script to new directory<br />
* '''-d''' Set package description (pkgdesc) to DESC<br />
* '''-f''' Force even if directory already exist<br />
* '''-h''' Show this help<br />
* '''-l''' Set package license to LICENSE<br />
* '''-p''' Create perl package (Assume Makefile.PL is there)<br />
* '''-u''' Set package URL<br />
* '''-s''' Use sourceforge source url<br />
<br />
{{Note|On older Alpine systems, abuild -c -n ''packagename'' was the way to create APKBUILD files. The 'packagename' was a parameter to the -n option so order of -c and -n matters. }}<br />
<br />
If you are create a daemon package which needs initd scripts you can add the -c making it: <br />
<br />
{{Cmd|newapkbuild -c ''packagename''}}<br />
<br />
This will copy the sample initd and confd files to the build directory.<BR><br />
A third file sample.install file will be copied as well (we will discuss this later on).<br />
<br />
=== Modify your APKBUILD ===<br />
Edit APKBUILD and fill in the needed info (especially pkgname, pkgver, pkgdesc, url, license, depends and source). <br />
<br />
If you are going to use any of the variables for directories like $pkgdir, always make sure they are double quoted like: <br />
<br />
"$pkgdir"/somedir<br />
<br />
This will prevent issues with spaces/special characters in the future. <br />
<br />
{{Note|If you like syntax highlighting we suggest you to install vim. We have setup vim to recognize the APKBUILD file as a bash scripts so its easier to read them.}}<br />
<br />
=== APKBUILD variables/functions ===<br />
<br />
==== source ====<br />
<br />
The source variable is not only used to list the remote source files to fetch, it is also used to list the local files that abuild will need in order to build the apk. Examples of such local files include: init.d files, conf.d files, install files (see [[Creating an Alpine package#install|install variable]]), patches, and all other necessary files.<br />
<br />
Here are few things to note:<br />
<br />
* When you are finished adding local and/or remote files to ''source'', you can execute the following command to add their checksums to the APKBUILD file:<br />
: {{cmd|abuild checksum}}<br />
: {{Note|When later updating the content of ''source'', or updating a file that is listed in ''source'', you must also update their checksums again with the same command.}}<br />
<br />
* When the remote file is hosted at SourceForge, it's best to specify the special mirrors link used by SourceForge:<br />
: <pre>http://downloads.sourceforge.net/$pkgname/$pkgname-$pkgver.tar.gz</pre><br />
: (or similar depending on the package).<br />
<br />
* When the remote filename is not specified in the URI (ie, does not end in '/software-1.0.tar.gz'), such as:<br />
: <pre>http://oss.example.org/?get=software&ver=1.0</pre><br />
: You must prepend 'saveas-' to the protocol and append '/software-1.0.tar.gz' (for instance) to the end of the URI, like so:<br />
: <pre>saveas-http://oss.example.org/?get=software&ver=1.0/software-1.0.tar.gz</pre><br />
: This causes the file to be saved as ''software-1.0.tar.gz'' where abuild can use it, instead of ''?get=software&ver=1.0'', where abuild cannot use it.<br />
<br />
* abuild currently supports the following protocols for remote file retrieval:<br />
** http<br />
** https<br />
** ftp<br />
<br />
: {{Note|If the you want to download from https, you need GNU wget installed on your system.}}<br />
<br />
* abuild currently supports the following archive types/archive file extensions:<br />
** .tar.gz / .tgz<br />
** .tar.bz2<br />
** .tar.lzma<br />
** .tar.xz<br />
** .zip<br />
<br />
==== depends &amp; makedepends ====<br />
<br />
Depends are the actual running dependencies that a package would need when it is running. Makedepends are only needed when you are building a package. If you set a package, in depends you do not need to add it to makedepends as well. The best way to find out what the depends and makedepends of a package are is to [http://en.wikipedia.org/wiki/Rtfm RTFM]. <br />
<br />
No kidding, lots of important information can be found it the package INSTALL and README file (or the likes). Another good way is the run ./configure --help from the source directory to see which options are needed for configure to finish without errors. If you do not yet have a src directory you can create one with the command: <br />
<br />
{{Cmd|abuild unpack}}<br />
<br />
Running configure will also show you how you can disable a specific option for this package. A good example is for instance "--disable-nls" which will disable native language support and thus does not depend on gettext(libiconv,glib..). <br />
<br />
Alpine likes to keep things small, so we try to disable as much as possible without losing too many features. The exact disable/enable options are decided the package builder but please try to follow Alpine's design concept as much as possible. <br />
<br />
An easy way of quickly finding out the build info for a package is to check Arch Linux (Alpine package management and build scripts are similar) or Gentoo linux ebuilds (previous versions of Alpine were based on Gentoo). <br />
<br />
* [http://www.gentoo-portage.com Search ebuilds] <br />
* [http://sources.gentoo.org/viewcvs.py/gentoo-x86/ Gentoo CVS] <br />
* [http://www.archlinux.org/packages/search/ Arch Linux packages] <br />
<br />
After the package is successfully compiled and created we should make sure it didn't link to any package that is not present in the $depends variable. We do this by using scanelf. If scanelf is not yet installed on your system you can do that by installing pax-utils. <br />
<br />
{{Cmd|scanelf -nR pkg}}<br />
<br />
An example output of libcurl would be: <br />
<br />
ET_DYN libssl.so.0.9.8,libcrypto.so.0.9.8,libz.so.1,libc.so.0,ld-uClibc.so.0 pkg/usr/lib/libcurl.so.4.1.1<br />
<br />
You can see the needed files and should be able to find out which file belongs to which package.<br />
<br />
==== license ====<br />
<br />
If a package has a special/custom license we need to provide it with the release. Because we want to save space and don't like to have licenses all over our system we have decided to include the license in the doc subpackage. Please follow the following guidelines to add a proper license. Locate the license file inside the source package. Add the doc subpackage to the $subpackages variable as follows: <br />
<br />
subpackages="$pkgname-doc"<br />
<br />
Add a similar line to the following to your package() function, depending on the license description file: <br />
<br />
install -Dm644 COPYING "$pkgdir"/usr/share/licenses/$pkgname/COPYING<br />
<br />
If you follow these steps then abuild will automatically add the license to the package-doc apk for you.<br />
<br />
==== arch ====<br />
<br />
The package architecture(s) to build for. This can be one of: ''x86, x86_64, all,'' or ''noarch'', where ''all'' means all architectures, and ''noarch'' means it's architecture-independent (ie, a pure-python package).<br />
{{Tip|To determine if your APKBUILD can use ''noarch'', build the package for your architecture and then run "scanelf -R pkg" from the directory that the APKBUILD resides in, in order to scan for ELF files in the ''./pkg'' directory. If you do NOT get output from this, then ''noarch'' can be used.}}<br />
<br />
==== url ====<br />
<br />
Website address for the program. This is usefully later on when either finding documentation or other information about the package.<br />
<br />
==== pkgdesc ====<br />
<br />
A brief, one line, description of what the package does. Useful for the package management system.<br />
<br />
Here is an example from apk_info for the OpenSSH client package<br />
<br />
pkgdesc="Port of OpenBSD's free SSH release - client"<br />
<br />
==== pkgver ====<br />
<br />
Provide the release number of the package you are building.<br />
<br />
==== pkgrel ====<br />
<br />
The $pkgrel versioning is made so if you change something to your APKBUILD file without changing the actual $pkgver you can higer pkgrel so apk tools will detect it as an update. For instance if you forget to add a dependency you can add it afterward and you can +1 pkgver so apk finds this update and add the missing dependency. <br />
<br />
==== pkgname ====<br />
<br />
The base name of the package you are creating. For Freeswitch 1.0.6, you would use "freeswitch"<br />
<br />
==== install ====<br />
<br />
There are 6 different kinds of install scripts. Each script is called with the $pkgname.''<action>'' where ''<action>'' is one of the following:<br />
<br />
===== $pkgname.pre-install =====<br />
This script is executed before package is installed. Typical use is when package needs a user/group to be created. For example:<br />
<pre><br />
#!/bin/sh<br />
adduser -H -s /bin/false -D clamav 2>/dev/null<br />
exit 0<br />
</pre><br />
Note the ''exit 0'' at the end. If the script exits with failure (if the user already exist), the package will not be installed and apk add will exit with failure.<br />
<br />
===== $pkgname.post-install =====<br />
This script is executed after package is installed. Can be used to generate font cache and similar.<br />
<br />
===== $pkgname.pre-upgrade =====<br />
Same as pre-install but is executed before upgrading an already installed package.<br />
<br />
===== $pkgname.post-upgrade =====<br />
Same as post-install but is executed after upgrading an already installed package. <br />
<br />
===== $pkgname.pre-deinstall =====<br />
This script is executed before uninstalling a package. If script exits with failure apk will not uninstall the package.<br />
<br />
===== $pkgname.post-deinstall =====<br />
This script is executed after a package have been uninstalled. Can be used to update font caches and restore busybox links. For example:<br />
<pre><br />
#!/bin/sh<br />
busybox --install -s<br />
</pre><br />
<br />
<br />
If the package have an pre-install and post-install script the APKBUILD should have the ''install'' variable defined and the scripts should also be added to the source variable:<br />
<pre><br />
...<br />
install="$pkgname.pre-install $pkgname.post-install"<br />
source="http://....<br />
$install"<br />
...<br />
</pre><br />
<br />
==== subpackages ====<br />
<br />
$subpackages are made to split up the normal "make install" into separate packages. The most common subpackages we use are doc and dev. Because we like to keep our target system small we move documentation and development files (only needed when building packages) into separate packages. To use the specific program a user only need to install the base apk without package-doc or package-dev, but if he wants to read the manual he will need to install package-doc. <br />
<br />
The easiest way to find out if you need to use -dev and -doc is to first build the package without these options set and wait until the build finishes. When its finished you should have a pkg directory which is the fake root directory. Inside this directory you will see the structure as how it would be installed in / on the target system. <br />
<br />
To see if you need the -dev package you can run the following cmd: <br />
<br />
{{Cmd|find pkg/usr/ -name '*.[acho]' -o -name '*.la'}}<br />
<br />
If this returns any files you need to include the -dev package. <br />
<br />
<br> To see if you need the -doc package you can run the following cmd: <br />
<br />
{{Cmd|find pkg/usr/share -name doc -o -name man -o -name info -o -name html -o -name sgml -o -name licenses}}<br />
<br />
If this returns any directories you need to include the -doc package. <br />
<br />
===== Custom subpackages =====<br />
<br />
Some applications will have except doc and dev files other non needed at run time files which we want to separate away from the base package. Some packages include large test suites which are only needed in specific circumstances or binaries which have depends which we prefer not to install. To handle those we create our own package/function. In the APKBUILD below the build() function we create another function: <br />
<br />
test() {<br />
mkdir -p "$subpkgdir"/usr<br />
mv "$pkgdir"/usr/package-test "$subpkgdir"/usr/<br />
}<br />
<br />
<br />
We also need to add the package info to $subpackages variable: <br />
<br />
subpackages="$pkgname-doc $pkgname-dev $pkgname-test"<br />
<br />
After we finish building the package you should see another apk called packagename-test.apk which includes the files which we moved to the $subpkgdir dir. <br />
<br />
The above mentioned variables can also be used in our custom function. If we want for instance to build the test() function with perl support we would add: <br />
<br />
depends="perl"<br />
makedepends="perl-dev"<br />
<br />
If we would install the base package it would not install perl, but if we install the package-test package it would.<br />
<br />
==== Patches ====<br />
<br />
Please make sure you always submit human readable patches. Way's to create them are: <br />
<br />
directory compare: <br />
<br />
{{Cmd|diff -urp original_directory new_directory &gt; filename.patch}}<br />
<br />
file compare: <br />
<br />
{{Cmd|diff -up original.file new.file &gt; filename.patch}}<br />
<br />
If you are going to use multiple patches for a single package, the preferred way to handle those is a loop and numbering the patches. <br />
<br />
for i in "$srcdir"/*.patch; do<br />
msg "Applying ${i}"<br />
patch -p0 -i $i || return 1<br />
done<br />
<br />
Because multiple patches can patch the same file, we could create offset for the next patch. To make sure we always patch in a specified way we should number the patches as followed: <br />
<br />
10-patch1.patch 20-patch2.patch 30-patch3.patch<br />
<br />
This way we are always sure patch 1 is first and if we want to add additional patches between them we can use 11,12,21,22... <br />
<br />
==== Configure options ====<br />
<br />
Alpine has some default configure options we set by default. We use /usr for prefix to make sure everything is installed with /usr in front of it. If you notice that anything is installed in the wrong directory please run {{Cmd|./configure --help}} and see if you can set the correct location. <br />
<br />
We are not covering the depend switches here we have discussed this already in the depend section.<br />
<br />
{{Tip|Common steps for building package contain ''./configure'', ''make'' and ''make install''. Everyone of them should be enclosed by ''&#124;&#124; return 1'' to check exit status. Otherwise even if previous step fails e.g. ''./configure'', next will be launched e.g. ''make''. This complicates tracing the point, where package brakes. The same applies to installing additional files.}}<br />
<br />
==== Make options ====<br />
<br />
If you notice weird problems when compiling or installing the package with make/make install you could try to disable [http://www.gnu.org/software/make/manual/make.html#Parallel parallel] building/installing. A normal make line would be: <br />
<br />
make || return 1<br />
<br />
To disable parallel we use: <br />
<br />
make -j1 || return 1<br />
<br />
We can use the same for make install. <br />
<br />
Because we do not want to install the package in our build environment but we want to install it in a fake root directory we need to tell 'make install' to use another destination directory instead of '/'. We do this by setting a variable when we execute make install as followed: <br />
<br />
make DESTDIR="$pkgdir" install<br />
<br />
Please note that some Makefiles do not support this variable and will always install software in '/'. To make sure you do not mess up your build system NEVER run your build system as root but always use a custom user and sudo when needed. If by accident the Makefile does not support DESTDIR variable it will fail to install in our build system system directories.<br />
<br />
==== _builddir ====<br />
If you used <tt>newapkbuild</tt> to create your APKBUILD file, you must specify the path to your unpacked sources. Inside the sections during the prepare/build/install process ''_builddir'' is used. Most of the time a combination of ''$srcdir'' and ''$pkgname-$pkgver'' will work. When not, check the /src directory or the source tarball for the right string. Especially when you are working with automatically generated tarballs (like from github and gitorious), this needs to be adjusted.<br />
<br />
_builddir="$srcdir"/$pkgname-$pkgver<br />
<br />
==== Additional files ====<br />
<br />
If you want/need to install additional files not mentioned above you can use the following cmd (this is an example of a conf file): <br />
<br />
install -Dm644 doc/$pkgname.conf "$pkgdir"/etc/$pkgname.conf<br />
<br />
== Build the package ==<br />
<br />
If you did not already create the checksums as mentioned above you can do so now: <br />
<br />
{{Cmd|cd $pkgname<br />
abuild checksum}}<br />
<br />
It's about time we build our package. Because a build system should never have all the package installed to prevent linking to packages we don't want it to link we use a abuild recursively with the '''-r''' switch. It will install all dependency's from your repository and builds it, afterwards it will uninstall all those depending packages again. You could also use the '''-R''' switch which would build your package including the dependency packages. <br />
<br />
{{Cmd|abuild -r}}<br />
<br />
== Commit your work ==<br />
<br />
After you successfully build your package you can submit your APKBUILD to alpine git repository. <br />
<br />
Update your git repo, before adding new files: <br />
<br />
{{Cmd|cd $aportsdir<br />
git pull}}<br />
<br />
This should pull all the changes made by others into you local git repo. When you think you are ready you can add your files to git: <br />
<br />
{{Cmd|cd $apkbuilddir<br />
git add APKBUILD (include any other files needed for the build; $pkgname.install...)<br />
git commit}}<br />
<br />
Now your changes are only available locally in your repository. Because you do not have push rights to the Alpine aports repository you need to create diff (patch) of the changes you made and send this patch to the [http://lists.alpinelinux.org/alpine-devel/ alpine-devel mailinglist].<br />
<br />
== Send a patch ==<br />
<br />
[[Creating_patches#Only_the_last_commit_with_.27git_send-email.27|git send-email]] will do that for you.<br />
<br />
== See Also ==<br />
* [[APKBUILD Reference]]<br />
* [[Development using git]]</div>Forthhttps://wiki.alpinelinux.org/w/index.php?title=Xen_Dom0&diff=5628Xen Dom02011-08-14T18:20:28Z<p>Forth: fully working now</p>
<hr />
<div>So before anything else verify that you car '''reliably''' log into your Alpine box through ssh, because with some video chipset (intel in my case) xen will blank your screen so you will have to use ssh.<br />
<br />
Then upgrade you setup to Edge / testing (as of the date of writing, Xen is only avaible in Edge).<br />
Install Xen:<br />
apk add xen<br />
<br />
Modify your extlinux.cfg: http://lists.alpinelinux.org/alpine-devel/1406.html<br />
<br />
timeout 20<br />
prompt 1<br />
default grsec<br />
label grsec<br />
kernel /boot/vmlinuz-grsec<br />
append initrd=/boot/initramfs-grsec root=UUID=f40e340b-ea49-445b-81c0-4d7104b56662 modules=sd-mod,usb-storage,ext4<br />
label xen<br />
kernel mboot.c32<br />
append /boot/xen-4.gz console=/dev/null dom0_mem=256M vga=mode-0x0311 --- /boot/vmlinuz-grsec root=UUID=f40e340b-ea49-445b-81c0-4d7104b56662 modules=sd-mod,usb-storage,ext4 vga=785 --- /boot/initramfs-grsec<br />
<br />
Of course replace root=UUID= with '''your''' UUID in yours.<br />
Default menu.c32 can mangle with Xen, further investigation needed, so don't use for now.<br />
<br />
Use the script found here: http://lists.xensource.com/archives/html/xen-devel/2010-03/msg01605.html<br />
<br />
#!/bin/sh<br />
<br />
test -d /proc/xen || exit 0<br />
test -f /proc/xen/capabilities || mount -t xenfs xen /proc/xen<br />
test -f /proc/xen/capabilities || exit 0<br />
grep -q "control_d" /proc/xen/capabilities || exit 0<br />
<br />
for module in xen-evtchn evtchn blkbk netbk; do<br />
modprobe ${module}>/dev/null 2>&1<br />
done<br />
<br />
xl info won't work<br />
<br />
Start xecommons:<br />
xencommons use bash, so install it: apk add bash (should try sh instead)<br />
alpine:/boot# /etc/init.d/xencommons start<br />
Starting xenstored...FATAL: Failed to open evtchn device: No such file or directory<br />
<br />
well this will fail but xl info will work anyway<br />
<br />
Oh but wait, evtchn device is built in the kernel, so why is there no /dev/xen/evtch file ?<br />
let's start udev ! ;)<br />
<br />
That's all folks !</div>Forthhttps://wiki.alpinelinux.org/w/index.php?title=Xen_Dom0&diff=5627Xen Dom02011-08-14T17:47:58Z<p>Forth: </p>
<hr />
<div>So before anything else verify that you car '''reliably''' log into your Alpine box through ssh, because with some video chipset (intel in my case) xen will blank your screen so you will have to use ssh.<br />
<br />
Then upgrade you setup to Edge / testing (as of the date of writing, Xen is only avaible in Edge).<br />
Install Xen:<br />
apk add xen<br />
<br />
Modify your extlinux.cfg: http://lists.alpinelinux.org/alpine-devel/1406.html<br />
<br />
timeout 20<br />
prompt 1<br />
default grsec<br />
label grsec<br />
kernel /boot/vmlinuz-grsec<br />
append initrd=/boot/initramfs-grsec root=UUID=f40e340b-ea49-445b-81c0-4d7104b56662 modules=sd-mod,usb-storage,ext4<br />
label xen<br />
kernel mboot.c32<br />
append /boot/xen-4.gz console=/dev/null dom0_mem=256M vga=mode-0x0311 --- /boot/vmlinuz-grsec root=UUID=f40e340b-ea49-445b-81c0-4d7104b56662 modules=sd-mod,usb-storage,ext4 vga=785 --- /boot/initramfs-grsec<br />
<br />
Of course replace root=UUID= with '''your''' UUID in yours.<br />
Default menu.c32 can mangle with Xen, further investigation needed, so don't use for now.<br />
<br />
Use the script found here: http://lists.xensource.com/archives/html/xen-devel/2010-03/msg01605.html<br />
<br />
#!/bin/sh<br />
<br />
test -d /proc/xen || exit 0<br />
test -f /proc/xen/capabilities || mount -t xenfs xen /proc/xen<br />
test -f /proc/xen/capabilities || exit 0<br />
grep -q "control_d" /proc/xen/capabilities || exit 0<br />
<br />
for module in xen-evtchn evtchn blkbk netbk; do<br />
modprobe ${module}>/dev/null 2>&1<br />
done<br />
<br />
xl info won't work<br />
<br />
Start xecommons:<br />
xencommons use bash, so install it: apk add bash (should try sh instead)<br />
alpine:/boot# /etc/init.d/xencommons start<br />
Starting xenstored...FATAL: Failed to open evtchn device: No such file or directory<br />
<br />
well this will fail but xl info will work anyway<br />
<br />
That's all folks !</div>Forthhttps://wiki.alpinelinux.org/w/index.php?title=Xen_Dom0&diff=5625Xen Dom02011-08-14T17:32:24Z<p>Forth: first draft</p>
<hr />
<div>So before anything else verify that you car '''reliably''' log into your Alpine box through ssh, because with some video chipset (intel in my case) xen will blank your screen so you will have to use ssh.<br />
<br />
Then upgrade you setup to Edge / testing (as of the date of writing, Xen is only avaible in Edge).<br />
Install Xen:<br />
apk add xen<br />
<br />
Modify your extlinux.cfg: http://lists.alpinelinux.org/alpine-devel/1406.html<br />
<br />
timeout 20<br />
prompt 1<br />
default grsec<br />
label grsec<br />
kernel /boot/vmlinuz-grsec<br />
append initrd=/boot/initramfs-grsec root=UUID=f40e340b-ea49-445b-81c0-4d7104b56662 modules=sd-mod,usb-storage,ext4<br />
label xen<br />
kernel mboot.c32<br />
append /boot/xen-4.gz console=/dev/null dom0_mem=256M vga=mode-0x0311 --- /boot/vmlinuz-grsec root=UUID=f40e340b-ea49-445b-81c0-4d7104b56662 modules=sd-mod,usb-storage,ext4 vga=785 --- /boot/initramfs-grsec<br />
<br />
Of course replace root=UUID= with '''your''' UUID in yours.<br />
Default menu.c32 can mangle with Xen, further investigation needed, so don't use for now.<br />
<br />
Use the script found here: http://lists.xensource.com/archives/html/xen-devel/2010-03/msg01605.html<br />
<br />
#!/bin/sh<br />
<br />
test -d /proc/xen || exit 0<br />
test -f /proc/xen/capabilities || mount -t xenfs xen /proc/xen<br />
test -f /proc/xen/capabilities || exit 0<br />
grep -q "control_d" /proc/xen/capabilities || exit 0<br />
<br />
for module in xen-evtchn evtchn blkbk netbk; do<br />
modprobe ${module}>/dev/null 2>&1<br />
done<br />
<br />
xl info won't work<br />
<br />
Start xecommons:<br />
<br />
alpine:/boot# /etc/init.d/xencommons start<br />
Starting xenstored...FATAL: Failed to open evtchn device: No such file or directory<br />
<br />
well this will fail but xl info will work anyway<br />
<br />
That's all folks !</div>Forthhttps://wiki.alpinelinux.org/w/index.php?title=Tutorials_and_Howtos&diff=5624Tutorials and Howtos2011-08-14T17:21:48Z<p>Forth: /* Drafts */</p>
<hr />
<div>[[Image:package_edutainment.svg|left|link=]]<br />
{{TOC right}}'''Welcome to Tutorials and Howtos, a place of basic and advanced configuration tasks for your Alpine Linux.'''<br />
The tutorials are hands-on and the reader is expected to try and achieve the goals described in each step, possibly with the help of a good examples. The output in one step is the starting point for the following step.<br/><br />
Howtos are smaller articles explaining how to perform a particular task with Alpine Linux. We encourage people to send in both complete articles as well as requesting topics to be covered. If you think you have the skills and knowledge to write an Alpine Linux related article please do so on this Wiki. If you want to request a topic, please add your request in this page [[Talk:Tutorials_and_Howtos|Discussion]]. <br />
<br />
== Installation ==<br />
<br />
* [[Setting up a basic vserver]]<br />
* [[Setting up Logical Volumes with LVM]]<br />
* [[Replacing non-Alpine Linux with Alpine remotely]]<br />
* [[XFCE Setup]]<br />
* [[Gnome Setup]]<br />
* [[Enable Serial Console on Boot]]<br />
* [[Alpine Linux package management#Local_Cache | How to enable APK caching]]<br />
* [[Installing Alpine on a virtual machine| Installation of Alpine Linux in a virtual machine]]<br />
* [[Setting up Alpine in a chroot]]<br />
* [[Upgrading to Edge]]<br />
* [[Setting up a software raid1 array]]<br />
* [[Manually editing a existing apkovl]]<br />
<br />
== Networking ==<br />
* [[Configure Networking]]<br />
* [[Howto Configure a Network Bridge]]<br />
* [[Howto Configure static routes]]<br />
* [[Using serial modem]]<br />
* [[Using HSDPA modem]]<br />
* [[Using Alpine on Windows domain with IPSEC isolation]]<br />
* [[Setting up Satellite Internet Connection]]<br />
* [[Connecting to a wireless accesspoint]]<br />
* [[Fault Tolerant Routing with Alpine Linux]]<br />
<br />
== iSCSI ==<br />
* [[iSCSI Target and Initiator Configuration]]<br />
* [[iSCSI Raid and Clustered File Systems]]<br />
* [[High performance SCST iSCSI Target on Linux software Raid]]<br />
<br />
== Network Services ==<br />
* [[Setting Up Lighttpd With FastCGI]]<br />
* [[Setting up a OpenVPN-server with Alpine]]<br />
* [[Setting up Zaptel/Asterisk on Alpine]]<br />
* [[Setting up Transmission (bittorrent) with Clutch WebUI]]<br />
* [[Hosting services on Alpine]] ''(This applies to hosting mail, webservices and other services)''<br />
** [[Setting up postfix with virtual domains]]<br />
** [[Protecting your email server with Alpine]]<br />
** [[Hosting Web/Email services on Alpine]]<br />
* [[Setting up a ssh-server]]<br />
* [[Multiple Instances of Services]]<br />
* [[ISP Mail Server HowTo]] ''(Postfix+PostfixAdmin+DoveCot+Roundcube+ClamAV+Spamd - A full-serivce ISP mail server)''<br />
** [[ISP Mail Server Upgrade 2.x]]<br />
** [[ISP Mail Server 2.x HowTo]] ''(Beta, please test)''<br />
* [[Freepbx on Alpine Linux]]<br />
* [[Apache authentication: NTLM Single Signon]]<br />
* [[Generating SSL certs with ACF]]<br />
* [[Changing passwords for ACF]]<br />
* [[Freeradius Active Directory Integration]]<br />
* [[High Availability High Performance Web Cache]] ''uCarp + HAProxy for High Availability Services such as Squid web proxy''<br />
<br />
== Web Applications ==<br />
* [[2600hz]] ''FreeSWITCH, Asterisk GUI web acces tool.''<br />
* [[Awstats]] ''Free log file analyzer.''<br />
* [[Drupal]] ''Content Management System (CMS) written in PHP.''<br />
* [[EyeOS]] ''Cloud Computing Desktop.''<br />
* [[FreePBX_V3]] ''FreeSWITCH, Asterisk GUI web acces tool.''<br />
* [[Glpi]] ''Information Resource-Manager.''<br />
* [[MediaWiki]] ''Free web-based wiki software application''<br />
* [[Pastebin]] ''Pastebin software application''<br />
* [[Phpizabi]] ''Social Networking Platform.''<br />
* [[PhpPgAdmin]] ''Web-based administration tool for PostgreSQL.''<br />
* [[Phpmyadmin]] ''Web-based administration tool for MYSQL.''<br />
* [[Redmine]] ''Project management system ''<br />
* [[Request-Tracker]] ''Ticket system''<br />
* [[Roundcube]] ''Webmail system''<br />
* [[Statusnet]] ''Microblogging Platform.''<br />
* [[Sqstat]] ''Script to look active squid users connections.''<br />
* [[Webmin]] ''A web-based interface for Linux system.''<br />
* [[WordPress]] ''Web software to create website or blog. ''<br />
<br />
== Monitoring ==<br />
* [[Traffic monitoring]] ''(For Alpine Linux firewalls)''<br />
* [[Setting up traffic monitoring using rrdtool (and snmp)]]<br />
* [[Setting up Smokeping]] ''(Smokeping network latency monitoring)''<br />
* [[Setting up Cacti]]<br />
* [[Setting up NRPE daemon]] ''(Performs remote Nagios checks)''<br />
* [[Setting up Zabbix]]<br />
* [[Setting Up Fprobe And Ntop]] ''NetFlow collection and analysis''<br />
<br />
== Misc ==<br />
* [[Setting up lm_sensors]]<br />
* [[Formatting HD/Floppy/Other]]<br />
* [[Screen on console]]<br />
* [[Using espeak on Alpine Linux]]<br />
* [[IPTV How To]]<br />
* [[Pllua]]<br />
* [[Error message on boot: Address space collision: host bridge window conflicts with Adaptor ROM]]<br />
<br />
== Drafts ==<br />
Those are not finished yet.<br />
* [[Install Alpine on coLinux]]<br />
* [[Using Racoon for Remote Sites]]<br />
* [[Setting up Transparent Squid Proxy]] ''(Covers Squid proxy and URL Filtering system)''<br />
** [[Obtaining user information via SNMP]] ''(Using the Squark Squid authentication helper)''<br />
* [[Setting up Streaming an Asterisk Channel]]<br />
* [[Setting up A Network Monitoring and Inventory System]] ''((Nagios + OpenAudit and related components)''<br />
* [[Intrusion Detection using Snort]] ''Installing and configuring Snort and related applications on Alpine 2.0.x''<br />
* [[IP Accounting]] ''Installing and configuring pmacct for IP Accounting, Netflow/sFlow collector''<br />
* [[Howto Setup a Wireless Access Point]] ''Setting up Secure Wireless AP w/ WPA encryption with bridge to wired network''<br />
* [[Xen Dom0]] ''Setting up Alpine as a dom0 for Xen hypervisor''<br />
<br />
== Obsolete Docs ==<br />
Those are candidates for rewriting/removal.<br />
* [[Bootstrapping Alpine on Soekris net4xxx]]<br />
* [[Bootstrapping Alpine on PC Engines ALIX.3]]<br />
* [[Setting up a /var partition on software IDE raid1]]<br />
* [[Native Harddisk Install]]<br />
* [[Installing XUbuntu using Alpine boot floppy]]<br />
* [[Setting up trac wiki]]</div>Forth