This shows you the differences between two versions of the page.
|
ass:labs-2025:04:tasks:02 [2026/07/16 14:48] florin.stancu |
ass:labs-2025:04:tasks:02 [2026/07/16 15:08] (current) florin.stancu |
||
|---|---|---|---|
| Line 11: | Line 11: | ||
| Since we need to install the Debian binaries executable on a 64-bit ARM architecture, we will need to split the installation into two stages: first, the .deb (Debian install packages) are downloaded from a Debian mirror server and unpacked into the target rootfs directory. Afterwards, since Debian will need to run some scripts to setup its distro system, we must **emulate** the target architecture. Enter [[https://www.qemu.org/|qemu]] which will help us to just that! | Since we need to install the Debian binaries executable on a 64-bit ARM architecture, we will need to split the installation into two stages: first, the .deb (Debian install packages) are downloaded from a Debian mirror server and unpacked into the target rootfs directory. Afterwards, since Debian will need to run some scripts to setup its distro system, we must **emulate** the target architecture. Enter [[https://www.qemu.org/|qemu]] which will help us to just that! | ||
| - | Finally, we need to obtain the ''debian-rootfs.tar.gz'' archive with the contents of our newly-created Aarch64 Debian. Use ''tar'' to ''c''reate a g''z''ipped archive, and be sure to ''p''reserve permissions! | + | Finally, we need to obtain the ''debian-rootfs.tar.gz'' archive with the contents of our newly-created Aarch64 Debian. Use ''tar'' to ''c''reate a g''z''ipped archive, and be sure to ''p''reserve permissions: |
| - | The final results should be something like: | + | <code bash> |
| - | <code> | + | sudo tar czpf debian-rootfs.tar.gz -C debian-rootfs/ . |
| - | -rw-r--r-- 1 root root 213M 2026-07-26 14:23 debian-rootfs.tar.gz | + | |
| </code> | </code> | ||