| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
rootfs as well
|
| |
|
|
| |
more verbode when sdcard is done
|
| |
|
|
| |
(security risk)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
loop_rootfs using grub (WIP)
- Generic packages: nn-packages[-RELEASE] (using the optional '-RELEASE' variant)
- System packages: nn-packages-sys-(raspi|debian)[-RELEASE] (using the optional '-RELEASE' variant),
allow to distinguish not only for the RELEASE but the actual underlying distribution.
- On debian amd64, all required usb-storage etc modules are loaded for loop_rootfs/initrd
- loop_rootfs works on Raspi (Proprietary Bootloader) as well as on Debian (Grub Bootloader)
- loop_rootfs uses the first vfat block-device partition for /boot
- /boot will be mounted by loop_rootfs and handed over to new root-mount-point,
this avoids issues of using an undefined /boot partition (but the first)
- rotatelog_init_rootfs: Rotates /boot/init_rootfs.log if having more than 500 lines
- FIX export-image: Copy the rootfs.img to the exported full image,
which allows testing the image directly via qemu .. etc.
|
| |
|
|
| |
kernel
|
| |
|
|
|
|
| |
over all files
zip name: ${IMG_FILENAME}${IMG_SUFFIX}.sdcard.zip
|
| |
|
|
| |
'-' already
|
| |
|
|
| |
${DEPLOY_DIR2}/sdcard-${IMG_SUFFIX}
|
| |
|
|
| |
selection and cache, /usr/share/doc/ and most locale; See README.md
|
| |
|
|
|
| |
Also move the `/data/sdcard` copy of '/boot' to stage2 and custom stages,
only used in ROOTFS_RO.
|
| |
|
|
|
|
|
|
|
|
|
| |
dedicated DEPLOY_DIR subfolder for each stage...
We produce squashfs variants with compression:
- gzip
- lzo
- none
Use dedicated DEPLOY_DIR subfolder for each stage due to exploded sdcard folder: ${DEPLOY_DIR}/${IMG_FILENAME}-${STAGE}
|
| |
|
|
| |
bootable sdcard content)
|
| |
|
|
| |
contained
|
| |
|
|
| |
drop cache; dpkg: Remove doc, man, ..
|
| |
|
|
| |
(export-image, make_bootable); Add 'sdcard' folder in DEPLOY_DIR
|
| |
|
|
| |
EXPORT_DIRS (images) to toggle run_stage's behavior
|
| |
|
|
| |
(merged from `export-image/04-finalise/01-run.sh`
|
| |
|
|
|
|
|
|
| |
make_bootable_image); Use gzip if `DEPLOY_ZIP == 1`
Writing out the rootfs as a raw image,
we simply use the new `connect_raw_blkdev` on the finalized raw image
and dd the partition using the fs's block-size into a file.
|
| |
|
|
|
|
|
|
|
|
|
| |
(4GB), 4 rootfs2 (4GB); Keep full sized sdcard image.
qcow2_handling: make_bootable_image()
- Still resize rootfs, but keep the partition table intact for both 4GB rootfs.
This keeps the scard image fully sized, but allows to mount and use all partitions.
- Use `mount_rawimage` (qemu-nbd) for image mount instead of convoluted loop device
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously, fdisk was used by sending commands into its stdin, which is
not very robust (since it heavily relies on the interactive prompts
offered by fdisk as well as the default values it offers, which seem
prone to changing in future version).
It seems likely that in the past, fdisk was easier than parted since it
provides default values that make it easier to create adjacent
partitions, without precalculating all positions in the script. However
now that partitions are manually being aligned, all data must be
calculated anyway.
This commit changes the partition generation to use parted rather than
fdisk. For this, it rewrites various calculations and renames variables
to be easier to read as well. All values are now in number of bytes,
rather than mixing bytes and sectors.
This commit also makes makes sure that the boot partition and root
partition are always adjacent (previously the root partition was aligned
without also rounding the boot partition size, leaving some empty space
in between).
As a side effect of using parted, this also causes the "bootcode" part
of the MBR to be filled with some default x86 bootcode. This is totally
irrelevant for booting the Raspberry Pi, but it does prevent triggering
a bug in parted. When using parted to change the partition table (e.g.
when resizing the root partition on first boot by raspi-config's
init_resize.sh), the disk identifier would be changed due to this bug,
which would change the PARTUUID of all partitions. The init_resize.sh
script would work around this by updating the PARTUUID in e.g. fstab,
but that's fragile at best. This commit prevents the bug from
triggering and keeps the disk identifier the same.
See https://debbugs.gnu.org/35714 for details about this parted bug.
This commit fixes #284.
|
| | |
|
| |
|
|
| |
This reverts commit a016561600292047971b65d034f0e6eaeadd1122.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Remove ui and staging components
|
| |
|
|
|
|
|
|
|
| |
The `(..)/raspberrypi-kernel/changelog.Debian.gz` file is not guaranteed
to be present in the built `ROOTFS_DIR`, for example when building very
minimal images without package documentation. In these cases, the `firmware`
variable will be left empty and the subsequent calls to `curl` will return
large 404 HTML content from GitHub.
Instead, simply check if the changelog file exists before using it.
|
| | |
|
| |
|
|
| |
When copying files to boot, options that are not supported on fat32 can cause errors. For example owner, group and xattrs.
|
| |
|
|
| |
Fixes #251
|
| | |
|
| |
|
| |
Fix typo
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Fixes #156
|
| | |
|
| | |
|
| | |
|
| | |
|
