1
0
Fork 0
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.
raspberrypi-build/README.md

63 lines
1.7 KiB
Markdown
Raw Normal View History

2020-02-08 02:25:24 -05:00
raspberrypi-build
=================
2020-02-08 02:25:24 -05:00
[![Build Status](https://travis-ci.org/kotovalexarian/raspberrypi-build.svg)](https://travis-ci.org/kotovalexarian/raspberrypi-build)
2017-09-23 23:48:00 -04:00
2020-02-08 02:25:24 -05:00
Tool used to create custom Debian GNU/Linux images for Raspberry Pi.
Based on [pi-gen](https://github.com/rpi-distro/pi-gen) tool used to create
2017-07-02 11:12:22 -04:00
the official [raspberrypi.org](https://raspberrypi.org) Raspbian images.
2017-06-30 17:36:04 -04:00
2017-07-09 12:53:10 -04:00
Table of contents
-----------------
* [Dependencies](#dependencies)
2017-07-09 12:59:16 -04:00
* [Build](#build)
2017-07-09 12:53:10 -04:00
* [System configuration](#system-configuration)
2017-06-30 17:36:04 -04:00
Dependencies
------------
2016-04-11 02:25:30 -04:00
On Debian-based systems:
```bash
2017-09-25 03:21:47 -04:00
apt-get install bash quilt parted qemu-user-static debootstrap zerofree \
dosfstools libcap2-bin grep rsync binfmt-support
```
2017-07-06 18:03:27 -04:00
2017-07-09 12:59:16 -04:00
Build
-----
2017-09-25 12:08:16 -04:00
Run `sudo ./run ./build.sh && sudo ./run ./mkimg.sh` to build the image.
2017-09-24 13:44:17 -04:00
The following files will be created:
2017-07-09 12:59:16 -04:00
* `rootfs/` - the root file system (`/` and `/boot/` partitions)
2020-02-08 02:25:24 -05:00
* `deploy/raspberrypi.img` - the image to write to SD card
2017-07-09 12:59:16 -04:00
2017-10-30 10:26:19 -04:00
#### WARNING
> During the execution of `sudo ./run ./build.sh` host directories `/dev`,
2017-12-02 03:52:48 -05:00
> `/dev/pts`, `/proc` and `/sys` are binded into `rootfs/` to provide
2017-10-30 10:26:19 -04:00
> 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.
2017-10-30 10:25:15 -04:00
2017-07-09 12:59:16 -04:00
2017-07-06 19:38:56 -04:00
System configuration
--------------------
2020-02-08 02:25:24 -05:00
The following information can be helpful when you connect:
2017-07-09 12:35:09 -04:00
2017-07-07 12:29:43 -04:00
* Root password is disabled
2017-07-06 19:38:56 -04:00
* 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