kotovalexarian
/
raspberrypi-build
Archived
1
0
Fork 0
Code
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.
751 Commits 1 Branch 0 Tags 1.1 MiB
Shell 100%
Go to file
Alex Kotov 50aeb89ec1
Decrease reserved space 		2020-02-12 04:24:59 +05:00
files Configure network interfaces with DHCP 2020-02-08 22:05:16 +05:00
keys Get rid of I2P 2018-03-30 11:26:47 +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 Add configuration file 2018-03-24 01:37:29 +00:00
.travis.yml Add Debian package "binfmt-support" to requirements 2018-03-23 15:52:56 +00:00
LICENSE Change license because there is no original code 2018-03-24 01:02:35 +00:00
README.md Replace sysvinit with systemd 2020-02-09 14:40:54 +05:00
build.sh Install package "gettext" 2020-02-09 14:45:00 +05:00
mkimg.sh Decrease reserved space 2020-02-12 04:24:59 +05:00
run Rename BarnacleOS 2020-02-08 12:25:24 +05:00

README.md

raspberrypi-build

Build Status

Tool used to create custom Debian GNU/Linux images for Raspberry Pi. 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 binfmt-support

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/raspberrypi.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:

  • 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