Difference between revisions of "Debian/Raspberry Pi"
(replaced "schroot -c stretch" with "sudo schroot -c test") |
|||
Line 9: | Line 9: | ||
* Set up an ''schroot'' environment by following the instructions: https://wiki.debian.org/Schroot, | * Set up an ''schroot'' environment by following the instructions: https://wiki.debian.org/Schroot, | ||
* Log into your ''schroot'' shell from the terminal, | * Log into your ''schroot'' shell from the terminal, | ||
− | schroot -c | + | sudo schroot -c test |
* Clone the repository | * Clone the repository | ||
git clone <nowiki>https://github.com/Rishabh42/rpi23-gen-image</nowiki> | git clone <nowiki>https://github.com/Rishabh42/rpi23-gen-image</nowiki> |
Revision as of 02:01, 25 June 2017
2017-06-22
Sucrose images for the Raspberry Pi 3 can be created by using this fork repository:
This was tested on Debian stretch platform which was set up in an schroot shell on Ubuntu.
The method is:
- Set up an schroot environment by following the instructions: https://wiki.debian.org/Schroot,
- Log into your schroot shell from the terminal,
sudo schroot -c test
- Clone the repository
git clone https://github.com/Rishabh42/rpi23-gen-image
- Install dependencies by going through the readme file in the repo and executing the commands described,
- Change your directory to the cloned repo and run this command to start the building process:
sh rpi23-gen-image.sh
This takes some time as the scripts start downloading and configuring packages to build an image.
- Once the process is complete in the terminal, navigate to this directory:
~/rpi23-gen-image/images/stretch
to find the image that was built.
Some changes have been made to the original repo: https://github.com/drtyhlpr/rpi23-gen-image which can be viewed in the commit history of the fork mentioned above.
2017-06-21
Sugar on RPI image
This image can be considered still in beta. This is not the final build.
Here is the link : Download
Repository : here
Fork used: here
If the image does not work on the first boot (or fails to login), please restart your RPI and try again. --HrishiP (talk) 10:49, 21 June 2017 (IST)