Which disk(s) would you like to use? (or '?' for help or 'none') Įnter where to store configs ('floppy', 'sdU1', 'usb' or 'none') :Įnter apk cache directory (or '?' or 'none') :Īfter the installer finished you can see how many created/modified files are detected and will be added to the backup: our bootable media files is basically untouched) and we are going to use sdU1 to hold our system customization. Now run setup-alpine and proceed until a question about local disk selection - in diskless mode we won't use any disk (ie. Lrwxrwxrwx 1 root root 17 Oct 19 13:16 /etc/apk/cache -> /media/sdU1/cache dev/sdU1 on /media/sdU1 type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=utf8,shortname=mixed,errors=remount-ro)Ĭreate local directory on USB media to hold local APK cache (see APK Local Cache for details). (Or correspondingly for other filesystems, if they are supported by syslinux and the Alpine Linux kernel.)Īfter one has booted the previously created Alpine Linux bootable USB medium, one has to prepare USB stick to hold local customizations and run setup-alpine to finish the installation.įirst let's find out where is our just booted USB media mounted, the location could vary.
In the case of an ext4 formatted partition. Then locate the "append" line, and change the alpine_dev= setting to match the used filesystem and add the filesystem's kernel module to the modules= list.Īppend alpine_dev=usbdisk:vfat modules=loop,cramfs,sd-mod,usb-storage quietĪppend alpine_dev=usbdisk: ext4 modules=loop,cramfs,sd-mod,usb-storage ,ext4 quiet Mount the boot device and edit the syslinux.cfg file. See: Alpine_Linux_package_management#Upgrading_.22diskless.22_and_.22data.22_disk_mode_installs Sys mode booting When the boot device is formatted with a filesystem other than those supported by default, the necessary initfs features need to be added to the modloop using update-kernel. Non-FAT32 Filesystems Diskless and data mode booting For other options, you can run cat /proc/partitions to see the available disks (i.e.For boot from USB, the device name should be 'usbdisk' (as shown above).You should replace the device name in this line:Īppend initrd=/boot/grsec.gz alpine_dev= usbdisk:vfat modules=loop,cramfs,sd-mod,usb-storage quiet
Then it is likely that the device name in syslinux.cfg is wrong. Initramfs emergency recovery shell launched. If you cannot boot from the boot device and you see something like: This should be done if you wish to have a fresh install.
The following procedure is for the Alpine Linux distribution itself, if you are using other Linux distro or other operating system you should know the best how to install syslinux and where mbr.bin file is located on your filesystem.
Warning: We assume here sdU is your USB stick which would hold bootable Alpine Linux files.
It describes how to manually create a custom (writable) USB boot device.Ĭopy ISO content to USB stick as individual files This process applies to Alpine Linux 1.9.0 or later. It consists an Installation of a diskless or data mode system with configs and package cache on the target device, and using the setup-bootable script to make the device bootable. This is now the preferable method to create a directly customizable bootable device. A device like an USB drive (flash, external HD, card reader, etc.) or a CF "CompactFlash", or SDcard.iso file containing the desired Alpine release ( Download). 3.1 Copy ISO content to USB stick as individual files.