Alpine Linux - User contributions [en]

Classic install or sys mode on Raspberry Pi

2017-12-01T11:59:41Z

Walderich: Corrected link to mount-point of first partition

Howto for classic installation or "sys mode"

This method works with a desktop PC under Ubuntu and other linuxes

== PREPARATION ==

Download archive of Alpinelinux for Rasperry Pi :

http://dl-cdn.alpinelinux.org/alpine/v3.6/releases/armhf/alpine-rpi-3.6.2-armhf.tar.gz

On a class 10 sd-card with size of 8Go or more, create 2 partitions :
* First in fat16 with size of 128Mo. Check boot and lba flags
* Second in ext4 with the remaining place

Eject and insert your SD-card to recognize all the partitions

Now go inside the first partition (fat16).

Untar the archive with tar:
tar zxvf ~/Download/alpine-rpi-3.6.2-armhf.tar.gz

Because a bug, it's recommended to add in the partition a file named '''usercfg.txt''' with the unique line :

enable_uart=1

Eject properly the sd card, insert it in the Raspberry Pi, plug a usb keyboard, an HDMI and a network cables, and power on.
As a prompt is displaying, connect as root without password.

== INSTALLATION ==

So, execute the following commands :
* setup-alpine (''set the mapping keyboard, the timezone, how to connect to the network (dhcp is the best method), say "no" at "save config" and cache'')
* apk update
* apk add chrony (''Raspberry Pi has no battery for his hardware clock. So, synchronize with a ntp server'')
* service chronyd restart
* apk add e2fsprogs
* mount /dev/mmcblk0p2 /mnt (''The second partition in ext4 format where Alpinuxlinux is installing in sys mode'')
* setup-disk -m sys /mnt
* mount -o remount,rw /dev/mmcblk0p1 (''An update in the first partition is required for the next reboot'')
* rm -f /media/mmcblk0p1/boot/* (''clean up the boot folder in the first partition to drop unused files'')
* cd /mnt (''We are in the second partition'')
* rm boot/boot (''Drop the unused symbolink link'')
* mv boot/* /media/mmcblk0p1/boot/ (''Move the image and init ram for AlpineLinux at the right place'')
* rm -Rf boot
* mkdir media/mmcblk0p1 (''It's the mount point for the first partition on the next reboot'')
* ln -s media/mmcblk0p1/boot boot (''Don't worry about the error'')
* echo "/dev/mmcblk0p1 /media/mmcblk0p1 vfat defaults 0 0" >> etc/fstab (''Update /etc/fstab'')
* sed -i '/cdrom/d' etc/fstab (''Of course, you don't have any cdrom or floppy on the Raspberry Pi'')
* sed -i '/floppy/d' etc/fstab
* sed -i '/edge/s/^#//' etc/apk/repositories (''Enable the repository for the community if you want vim, mc, php, apache, nginx, ...'')
* cd /media/mmcblk0p1
* sed -i 's/^/root=\/dev\/mmcblk0p2 /' cmdline.txt (''Tell for the next boot that the root filesystem is on the second partition'')
* reboot

That works on Raspberry Pi 3B and 1B. But if you have the 1B version, let's be very, very patient (several tens of minutes)

If a hard disk is connected via usb, you can replace above /dev/mmcblk0p2 by /dev/sda1, for example.

If you don't like sed and regular expressions, you can use nano editor after executing the following command :

apk add nano

== POST-INSTALLATION ==

The Raspberry Pi (RPI) has no battery to keep the time updated. So, we need to enable the right service to synchronize with a ntp server:

* rc-update del hwclock boot
* rc-update add swclock boot
* service hwclock stop
* service swclock start

Update and upgrade the system :

* apk update
* apk upgrade

If you want a cool editor (''vim''), a files manager (''mc''), which tasks are running (''htop''), which services are starting on the boot process, add the right packages :

* apk add vim mc htop
* htop
* rc-update

The RPI 3B has wifi on board for networking. So, start service for the encrypted key on wpa2 protocol :

* apk add wpa_supplicant
* rc-update add wpa_supplicant boot
* service wpa_supplicant start
* setup-interface (''replace IP address by dhcp for all the interfaces if necessary, select the SSID network for wifi and add password'')
* ip addr (''to know the IP address for all interfaces'')

If you want to connect on your remote RPI via ssh, an additional user (''foo'') and sudo package are required because it's forbidden to conect as root :

* apk add sudo
* adduser foo
* adduser foo wheel
* visudo (''uncomment line #82 with "wheel ALL=(ALL) ALL". If vim is installed, save the changes by typing "Esc :x"'')

Classic install or sys mode on Raspberry Pi

2017-11-30T23:01:58Z

Walderich: Corrected path to partition when creating symbolic link to boot

Howto for classic installation or "sys mode"

This method works with a desktop PC under Ubuntu and other linuxes

== PREPARATION ==

Download archive of Alpinelinux for Rasperry Pi :

http://dl-cdn.alpinelinux.org/alpine/v3.6/releases/armhf/alpine-rpi-3.6.2-armhf.tar.gz

On a class 10 sd-card with size of 8Go or more, create 2 partitions :
* First in fat16 with size of 128Mo. Check boot and lba flags
* Second in ext4 with the remaining place

Eject and insert your SD-card to recognize all the partitions

Now go inside the first partition (fat16).

Untar the archive with tar:
tar zxvf ~/Download/alpine-rpi-3.6.2-armhf.tar.gz

Because a bug, it's recommended to add in the partition a file named '''usercfg.txt''' with the unique line :

enable_uart=1

Eject properly the sd card, insert it in the Raspberry Pi, plug a usb keyboard, an HDMI and a network cables, and power on.
As a prompt is displaying, connect as root without password.

== INSTALLATION ==

So, execute the following commands :
* setup-alpine (''set the mapping keyboard, the timezone, how to connect to the network (dhcp is the best method), say "no" at "save config" and cache'')
* apk update
* apk add chrony (''Raspberry Pi has no battery for his hardware clock. So, synchronize with a ntp server'')
* service chronyd restart
* apk add e2fsprogs
* mount /dev/mmcblk0p2 /mnt (''The second partition in ext4 format where Alpinuxlinux is installing in sys mode'')
* setup-disk -m sys /mnt
* mount -o remount,rw /dev/mmcblk0p1 (''An update in the first partition is required for the next reboot'')
* rm -f /media/mmcblk0p1/boot/* (''clean up the boot folder in the first partition to drop unused files'')
* cd /mnt (''We are in the second partition'')
* rm boot/boot (''Drop the unused symbolink link'')
* mv boot/* /media/mmcblk0p1/boot/ (''Move the image and init ram for AlpineLinux at the right place'')
* rm -Rf boot
* mkdir media/mmcblk1p1 (''It's the mount point for the first partition on the next reboot'')
* ln -s media/mmcblk1p1/boot boot (''Don't worry about the error'')
* echo "/dev/mmcblk0p1 /media/mmcblk0p1 vfat defaults 0 0" >> etc/fstab (''Update /etc/fstab'')
* sed -i '/cdrom/d' etc/fstab (''Of course, you don't have any cdrom or floppy on the Raspberry Pi'')
* sed -i '/floppy/d' etc/fstab
* sed -i '/edge/s/^#//' etc/apk/repositories (''Enable the repository for the community if you want vim, mc, php, apache, nginx, ...'')
* cd /media/mmcblk0p1
* sed -i 's/^/root=\/dev\/mmcblk0p2 /' cmdline.txt (''Tell for the next boot that the root filesystem is on the second partition'')
* reboot

That works on Raspberry Pi 3B and 1B. But if you have the 1B version, let's be very, very patient (several tens of minutes)

If a hard disk is connected via usb, you can replace above /dev/mmcblk0p2 by /dev/sda1, for example.

If you don't like sed and regular expressions, you can use nano editor after executing the following command :

apk add nano

== POST-INSTALLATION ==

The Raspberry Pi (RPI) has no battery to keep the time updated. So, we need to enable the right service to synchronize with a ntp server:

* rc-update del hwclock boot
* rc-update add swclock boot
* service hwclock stop
* service swclock start

Update and upgrade the system :

* apk update
* apk upgrade

If you want a cool editor (''vim''), a files manager (''mc''), which tasks are running (''htop''), which services are starting on the boot process, add the right packages :

* apk add vim mc htop
* htop
* rc-update

The RPI 3B has wifi on board for networking. So, start service for the encrypted key on wpa2 protocol :

* apk add wpa_supplicant
* rc-update add wpa_supplicant boot
* service wpa_supplicant start
* setup-interface (''replace IP address by dhcp for all the interfaces if necessary, select the SSID network for wifi and add password'')
* ip addr (''to know the IP address for all interfaces'')

If you want to connect on your remote RPI via ssh, an additional user (''foo'') and sudo package are required because it's forbidden to conect as root :

* apk add sudo
* adduser foo
* adduser foo wheel
* visudo (''uncomment line #82 with "wheel ALL=(ALL) ALL". If vim is installed, save the changes by typing "Esc :x"'')

Setting up a samba-ad-dc

2016-08-12T17:53:49Z

Walderich: Spelling correction

NOTES:
In all examples below, replace EXAMPLE with your NetBIOS domain name in caps, example.com with your DNS domain name, HOSTNAME with your system's host name in caps, and hostname with your system's host name.

Refer to the [https://wiki.samba.org/index.php/Active_Directory_Naming_FAQ Active Directory naming FAQ] before choosing your domain name.

= Installation =
Install packages:
{{Cmd|apk add samba-dc krb5 }}

= Edit hosts file =
You need to modify your {{Path|/etc/hosts}} file to look similar to this.

127.0.0.1 localhost.localdomain localhost
10.1.1.10 hostname.example.com hostname

= Create smb.conf =
Alpine doesn't provide an example configuration file in the package so you'll need to create one at {{Path|/etc/samba/smb.conf}}.

[global]
server role = domain controller
workgroup = EXAMPLE
realm = example.com
netbios name = HOSTNAME
passdb backend = samba4
idmap_ldb:use rfc2307 = yes

[netlogon]
path = /var/lib/samba/sysvol/example.com/scripts
read only = No

[sysvol]
path = /var/lib/samba/sysvol
read only = No

= Provision your Samba domain =
Answer the questions with your domain information:
{{Cmd|samba-tool domain provision --use-rfc2307 --interactive}}
Use the SAMBA_INTERNAL DNS option.
When asked for a forwarder IP, choose your internet DNS server. You can use your ISP or other public services (like Google) here.

= Configure resolv.conf =
Modify your {{Path|/etc/resolv.conf}} to include your new domain as a search domain and point to itself as the first nameserver.

search example.com
nameserver 10.1.1.10

= Configure Kerberos =
You need to replace krb5.conf with a link to the one generated by samba.
{{Cmd|ln -sf /var/lib/samba/private/krb5.conf /etc/krb5.conf}}

= Install new init script =
As of 3/31/2016 and Alpine 3.3.3, the included samba init script doesn't support starting it as a domain controller. Modify your {{Path|/etc/init.d/samba}} script like the one below.

#!/sbin/openrc-run

extra_started_commands="reload"

DAEMON=${SVCNAME#samba.}
SERVER_ROLE=`samba-tool testparm --parameter-name="server role" 2>/dev/null | tail -1`
if [ "$SERVER_ROLE" = "active directory domain controller" ]; then
daemon_list="samba"
elif [ "$DAEMON" != "samba" ]; then
daemon_list=$DAEMON
fi

depend() {
need net
after firewall
}

start_samba() {
mkdir -p /var/run/samba
start-stop-daemon --start --quiet --exec /usr/sbin/samba --
}

stop_samba() {
start-stop-daemon --stop --quiet --pidfile /var/run/samba/samba.pid
}

start_smbd() {
start-stop-daemon --start --quiet --exec /usr/sbin/smbd -- \
${smbd_options:-"-D"}
}

stop_smbd() {
start-stop-daemon --stop --quiet --pidfile /var/run/samba/smbd.pid
}

start_nmbd() {
start-stop-daemon --start --quiet --exec /usr/sbin/nmbd -- \
${nmbd_options:-"-D"}
}

stop_nmbd() {
start-stop-daemon --stop --quiet --pidfile /var/run/samba/nmbd.pid
}

start_winbindd() {
start-stop-daemon --start --quiet --exec /usr/sbin/winbindd -- \
$winbindd_options
}

stop_winbindd() {
start-stop-daemon --stop --quiet --pidfile /var/run/samba/winbindd.pid
}

start() {
for i in $daemon_list; do
ebegin "Starting $i"
start_$i
eend $?
done
}

stop() {
for i in $daemon_list; do
ebegin "Stopping $i"
stop_$i
eend $?
done
}

reload() {
for i in $daemon_list; do
ebegin "Reloading $i"
killall -HUP $i
eend $?
done
}

= Configure the Samba service =
Run these two commands to start the service on boot and to start the service right now.
{{Cmd|rc-update add samba}}
{{Cmd|rc-service samba start}}