Difference between revisions of "Replacing non-Alpine Linux with Alpine remotely"

From Alpine Linux
Jump to: navigation, search
Line 48: Line 48:
 
  fdisk /dev/hda
 
  fdisk /dev/hda
  
Create /boot/extlinux.conf with contents like (alpine_dev needs special care, generally hard-disks are sd* in alpine due to new kernel and libata; you also need to check the filesystem type):
+
Create /boot/extlinux.conf with contents like (alpine_dev needs special care, generally hard-disks are sd* in alpine due to new kernel and libata; you also need to check the filesystem type; kernel and initrd are relative to partition root):
 
  timeout 20
 
  timeout 20
 
  prompt 1
 
  prompt 1
 
  default grsec
 
  default grsec
 
  label grsec
 
  label grsec
   kernel /boot/grsec
+
   kernel /grsec
   append initrd=/boot/profile.gz alpine_dev=sda2:ext3 modloop=grsec.cmg modules=loop,cramfs,sd-mod,usb-storage,ext3 quiet
+
   append initrd=/profile.gz alpine_dev=sda2:ext3 modloop=grsec.cmg modules=loop,cramfs,sd-mod,usb-storage,ext3 quiet
  
 
Finally make the /boot partition bootable by extlinux.
 
Finally make the /boot partition bootable by extlinux.

Revision as of 11:16, 16 September 2009

Instructions to replace running Linux installation with Alpine Linux, remotely using ssh connection only.

Tested using alpine-1.9.0_rc2.

CAUTION: Practice with computer with physical access first. If something goes wrong, the remote box will very likely be left into unusable state.

WARNING: UNTESTED INSTRUCTION. WRITING IN PROGRESS.

Create apk overlay suitable for hard disk based tmpfs boot

The first step is to create Alpine configuration file with basic configuration of the host. We need the new box to start networking and ssh in the beginning so we can reconnect to it after reboot.

Create basic layout for the overlay:

mkdir overlay
cd overlay
mkdir -p etc/ssh etc/network etc/runlevels/default root/.ssh

If you want to keep the existing host identity (e.g. SSH key), you can copy them over:

cp -a /etc/{passwd,group,shadow,gshadow,hostname,resolv.conf,network/interfaces,ssh} etc/

You can copy the network/interfaces might not necessarily exists. Some distributions use different configuration file for network. If it does not exists, you need to create it. It should look something like:

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet static
      address ip.ad.dr.es
      netmask 255.255.255.0
      gateway gw.ad.dr.es

Finally, make the essential services start up automatically and create the overlay file:

ln -s /etc/init.d/networking etc/runlevels/default/networking
ln -s /etc/init.d/sshd etc/runlevels/default/sshd
tar czf ../host.apkovl.tar.gz *

Install Alpine cd-rom image on hard disk

We need to copy over two sets of information: the boot kernel (kernel, initramdisk and boot configuration) and operating system boot data (overlay, apk packages and kernel modules). These can reside on same partition if they fit. However, /boot is usually small, so you might want to put the apks on separate partition. This guide assumes they are on hda1 (/boot) sand hda2 (/).

We start with the easy task. Place the overlay file and the "apks" directory from cd-rom image to root of current installation:

cp host.apkovl.tar.gz /
cp -a /cdrom/apks /
cp -a /cdrom/boot/grsec.cmg /

Next we make the Alpine Linux kernel bootable (requires syslinux) and use fdisk to mark the /boot partition as bootable (if not done already):

cp -a /cdrom/boot/grsec{,.gz} /boot
dd if=/usr/share/syslinux/mbr.bin of=/dev/hda
fdisk /dev/hda

Create /boot/extlinux.conf with contents like (alpine_dev needs special care, generally hard-disks are sd* in alpine due to new kernel and libata; you also need to check the filesystem type; kernel and initrd are relative to partition root):

timeout 20
prompt 1
default grsec
label grsec
  kernel /grsec
  append initrd=/profile.gz alpine_dev=sda2:ext3 modloop=grsec.cmg modules=loop,cramfs,sd-mod,usb-storage,ext3 quiet

Finally make the /boot partition bootable by extlinux.

extlinux -i /boot

Install Alpine on hard-disk