1
0
Fork 0
Tool used to create custom Debian GNU/Linux images for Raspberry Pi
This repository has been archived on 2023-03-27. You can view files and clone it, but cannot push or open issues or pull requests.
Find a file
2018-03-23 12:29:38 +00:00
files Add file /etc/vim/vimrc.local 2018-03-23 12:29:38 +00:00
keys Use Raspberry Pi repo for kernel and bootloader 2017-09-23 17:07:33 +00:00
patches Add file /etc/hosts 2017-10-30 14:10:57 +00:00
test Finalize test script at fail 2017-09-25 18:47:11 +00:00
.gitignore Use temporary directory to mount image to 2017-09-25 16:27:01 +00:00
.travis.yml Add test "partuuid" 2017-09-25 18:38:09 +00:00
build.sh Add file /etc/vim/vimrc.local 2018-03-23 12:29:38 +00:00
LICENSE Add myself to license 2017-06-30 21:25:30 +00:00
mkimg.sh Improve substitution 2017-09-25 19:05:26 +00:00
README.md Fix typo 2017-12-02 08:52:48 +00:00
run Do not include date to image file name 2017-09-26 08:34:59 +00:00

barnacleos/build

Build Status

Tool used to create the BarnacleOS images. Based on pi-gen tool used to create the official raspberrypi.org Raspbian images.

Table of contents

Dependencies

On Debian-based systems:

apt-get install bash quilt parted qemu-user-static debootstrap zerofree \
dosfstools libcap2-bin grep rsync

Build

Run sudo ./run ./build.sh && sudo ./run ./mkimg.sh to build the image. The following files will be created:

  • rootfs/ - the root file system (/ and /boot/ partitions)
  • deploy/BarnacleOS.img - the image to write to SD card

WARNING

During the execution of sudo ./run ./build.sh host directories /dev, /dev/pts, /proc and /sys are binded into rootfs/ to provide environment for chroot. They are unmounted in the end of script. However, script may fail, so they will remain mounted. If you run sudo rm -rf rootfs/, you can corrupt your host operating system state and you will have to reboot. Please be careful.

System configuration

The following information can be helpful when you connect to BarnacleOS:

  • Root password is disabled
  • User user has access via SSH with password password
  • SSH host keys are generated at first startup, so fingerprint is different for each installation of the same image
  • User has passwordless sudo

Connect to Wi-Fi

wpa_passphrase "your-wi-fi-ssid" "your-wi-fi-passphrase" | sudo tee -a /etc/wpa_supplicant/wpa_supplicant.conf
sudo ifup wlan0