aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
...
* Custom personal build config 02 + 03: Only produce stage2 (developer test)Sven Gothel2021-07-182-1/+3
| | | | | | | | | | | Goal reached: stage2 produced for raspi-arm64 + debian-amd64 merged into one 'dual-2GiB-01.img' using 'loop_rootfs' were bootable on - raspi4 - qemu amd64 - Intel NUK amd64 i6 w/ EFI (vfat) and other partitions The 2G test image was created using scripts/make_dualboot_image.sh
* loop_rootfs: find_blkpart -> find_partition: Search for first matching ↵Sven Gothel2021-07-182-64/+111
| | | | | | | | | | | | | | | partition: fstype + 'a magic file id' First fstype partition is not good enough, especially if having a vfat EFI partitions and perhaps other systems installed. Hence find_partition: - for all blk-partitions - for all matching desired fstype, mounted - if 'loop_rootfs.id' exists, done! To ensure logging won't interfere with returned echo'ed strings (stdout), "overloaded" the log facility with 'mylog_.." using stderr output.
* initramfs: Ensure package lzop is installed and in initrd to benefit from ↵Sven Gothel2021-07-183-1/+4
| | | | faster inflater
* multi-arch/boot: Handle GRUB boot-code images, showcase full feature via ↵Sven Gothel2021-07-184-0/+179
| | | | | | | | | | | | | | | | | | | | | | | | | 'make_dualboot_image' 'make_dualboot_image' creates a new raw image file: - creating one vfat partition covering whole size - formating partition with vfat - provision GRUB boot-code (expecting 'grub' folder on vfat partition) - copy custom files to vfat partition using image file handling via NBD (updated imagetool.sh). The custom files are sourced from two sdcard diskimages folder generated with our pi-gen branch: - raspi arm64 - debian amd64 Simply copied both content into one merge folder, passed as last argument 'provisioning-dir' to this script. +++ Grub file handling takes care of both boot-code image locations, 446 bytes in MBR and the MBR gap from [512 bytes - partition-start[
* Bump example config files .. (hostname matched project, version)Sven Gothel2021-07-186-12/+12
|
* Raspi cmdline: Be quietSven Gothel2021-07-183-3/+3
|
* GRUB custom.cfg: Be quietSven Gothel2021-07-181-1/+1
|
* stage2 (network): Drop resolvconf as it lead to use GOOG 8.8.8.8 NSSven Gothel2021-07-181-1/+2
| | | | /etc/resolv.conf will be defined via dhcpcd directly via dhcp
* stage2 (network): Use dhcpcd for Debian as well; Take dhcp host-name if ↵Sven Gothel2021-07-182-1/+4
| | | | provided!
* stage2: Make GRUB boot-code images relocatable (clone)Sven Gothel2021-07-181-3/+5
| | | | | | - don't use UUIDs but file-id - preload modules via core.img (within MBR-gap) - Don't use installation specific load.cfg, remove it.
* stage2: Disable systemd-remount-fs: Already mounted correctly and no live ↵Sven Gothel2021-07-181-0/+5
| | | | mapping /etc/fstab
* Use $BASH_SOURCE[0] instead of $0Sven Gothel2021-07-182-2/+2
|
* Enhance NBD/Image handling via imagetool.sh (use reusable stateless ↵Sven Gothel2021-07-184-113/+386
| | | | | | | | | | functions from new lib_nbd_img_handling) imagetool.sh - new connect* and disconnect - mount/umount stateless, multiple usage - lib_nbd_img_handling used as base implementation for qcow2_handling and imagetool.sh
* Remove obsolete tagging scripts to SKIP stages and image creationSven Gothel2021-07-182-54/+0
|
* multi-arch: Slim down grub.cfg on Debian amd64 targetSven Gothel2021-07-172-3/+9
|
* multi-arch: Fix stage0/00-configure-apt: Perform 'dpkg' within i/o piped ↵Sven Gothel2021-07-171-5/+7
| | | | on_chroot (otherwise no arm64 emulation)
* multi-arch: Support vanilla Debian for 'amd64' and 'i386' architecture incl. ↵Sven Gothel2021-07-1769-655/+1336
| | | | | | | | | | | | | | | | | | | | | | | 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.
* Add 'on_chroot.sh', demonstrate means to run tasks on target architecture ↵Sven Gothel2021-07-101-0/+46
| | | | | | | | using a simple rootfs image Tested compilation of direct_bt for aarch64, resulting in correct binaries in just ~5 minutes. Issues: Running the Java unit tests fails sadly, might need to investigate OpenJDK11 + qemu-aarch64.
* ./imagetool.sh: Allow unmount w/o NBD_DEV, i.e. single mounted rootfs imageSven Gothel2021-07-101-3/+4
|
* README.md: Fix grammarSven Gothel2021-07-091-1/+1
|
* stage2: Add iftopSven Gothel2021-07-092-2/+2
|
* qcow2_handling: Use fixed PART_NO (at least a variable)Sven Gothel2021-07-091-2/+3
|
* stage2's: /etc/init.d/resize2fs_once: Add maximizing rootfs partition size ↵Sven Gothel2021-07-091-4/+27
| | | | | | | | before resize2fs. The install image's partition has been downsized to match the shrunken rootfs for efficient storage and copy to sdcard. Hence 'resize2fs_once' must also resize the parition to the end of the sdcard, then resize2fs for maximum size.
* scripts/qcow2_handling: Reactivate partition resizing (Fix PART_START grep ↵Sven Gothel2021-07-091-7/+6
| | | | for 2nd parition)
* scripts/chroot-example.sh: Adding example how to use the qcow2 image chroot ↵Sven Gothel2021-07-091-0/+24
| | | | for custom tasks
* Add stage3a_dev: Image '-litexdev', developer system on top of stage3a; ↵Sven Gothel2021-07-097-33/+64
| | | | Cleaned README.md
* Drop recommended packages if using reduced footprint or not explicitly ↵Sven Gothel2021-07-093-4/+20
| | | | selected (default); Disable apt-cache for all configurations
* stage2: Add autofs, since nfs-common is default autofs is desired in a ↵Sven Gothel2021-07-092-0/+2
| | | | networking fs environment
* build example rw rootfs: Don't use REDUCED_FOOTPRINT for writable rootfs ↵Sven Gothel2021-07-091-1/+1
| | | | (expect default man and /usr/share)
* bullseye: build.sh: Fix case for IS_TESTINGSven Gothel2021-07-091-4/+5
|
* bullseye: scripts/0[12]-build*: Move to 'bullseye'Sven Gothel2021-07-092-4/+4
|
* skip/unskip: Add stage3[ab] SKIP_IMAGESSven Gothel2021-07-092-0/+4
|
* stage2: boot/config-rootfs*.txt: Use new sd_force_pio=on (disabled though)Sven Gothel2021-07-092-2/+2
|
* stage2: Fix /boot/config.txt (renamed from alternative naming)Sven Gothel2021-07-091-4/+4
|
* bullseye: build.sh: Set 'IS_TESTING' based on 'RELEASE' setting.Sven Gothel2021-07-091-0/+16
|
* bullseye: build.sh: Use RELEASE dependend nn-packages[-nr][-${RELEASE}] if ↵Sven Gothel2021-07-0912-11/+141
| | | | | | exists Testing with bullseye, we see some divergence, i.e. python3 for python[2] and certain packages are no more available.
* qcow2_handling mkfs.ext4: Reenable dropping 'huge_file' feature and ↵Sven Gothel2021-07-091-3/+3
| | | | 'has_journal' for writable image
* Fix he build scripts (generic), no APT_PROXY by default (personal anyways) ↵Sven Gothel2021-07-092-4/+4
| | | | .. etc
* Enable EXPORT_IMAGE for stage3a '-litex', useful for basic xorg no-desktop ↵Sven Gothel2021-07-093-0/+57
| | | | | | initial writable rootfs Adding/renaming build scripts accordingly
* None ROOTFS_RO: Only use 250 MiB vfat boot parition (as in arm64 branch)Sven Gothel2021-07-081-2/+13
|
* stage2: Reenable nfs-common and rsync (services disabled); Add iotop and ↵Sven Gothel2021-07-082-3/+5
| | | | powertop
* mkfs.ext4: Only set reserved-blocks-percentage to zero if ROOTFS_RO is setSven Gothel2021-07-081-1/+5
|
* initrd: loop_rootfs: test/reset_initrd.sh: Convenience script for target ↵Sven Gothel2021-07-061-0/+10
| | | | machine to rebuild initrd.img
* initrd: loop_rootfs: Resolve logging, use persistent /boot/init_rootfs.log ...Sven Gothel2021-07-061-0/+42
| | | | | | | | | | | | | | | | | | | | | Ensure loop_rootfs log output persists across boots and hence fallback, otherwise we can't validate the 'fallback reboot' stage. We also need to document its actions. This takes 'quiet' into account, i.e. - if 'quiet' or 'log_output' via 'debug' is set: just redirect to file - else use 'tee' to copy to console as well Further a potential 'debug' 'log_output', i.e. '/run/initramfs/initramfs.debug', is made persistent (appended) to '/boot/init_debug.log'. Since Busybox shell has no Process Substitution (Bash), we manually create a PIPE and spawn the tee or print process. Further `tee_date` and `add_date` is being used to print the UTC timestamp upfront.
* initrd loop_rootfs: perform fsck on rootfs-file w/o intend to modify '-n'Sven Gothel2021-07-061-1/+1
| | | | | | Since no console is available, fsck would fail anyways. Tested w/ ext4 rootfs file
* stage2: Readd wifi (wpasupplicant, wireless-tools, firmware)Sven Gothel2021-07-061-1/+1
|
* stage2: initrd loop_rootfs: Perform at least a 'unsquashfs -l` superficial ↵Sven Gothel2021-07-065-7/+41
| | | | | | integrity check if 'squashfs' Also have initrd loop_rootfs check_fsfile() be more verbose for documentation.
* export-image: Add squashfs w/ zstd-10, sadly zstd is disabled in Raspberry ↵Sven Gothel2021-07-061-3/+4
| | | | kernel
* install-deps: Add fatattrSven Gothel2021-07-061-1/+1
|
* export-image (ro): Create zip storage only archive of sdcard and SHA256SUMS ↵Sven Gothel2021-07-041-0/+7
| | | | | | over all files zip name: ${IMG_FILENAME}${IMG_SUFFIX}.sdcard.zip
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-03 21:35:46 +0000