manuel
/
void-mklive
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

README: clarify arm images slightly

This commit is contained in:
classabbyamp 2024-02-15 14:42:26 -05:00
parent a7698238e2
commit c4785dd957
No known key found for this signature in database
GPG Key ID: 6BE0755918A4C7F5
2 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
README.md generated
View File

@ -46,9 +46,9 @@ First create a ROOTFS for the desired architecture, then use
#### Generating ARM images
Platform-specific filesystem images contain a basic filesystem layout (`/` and
`/boot` partitions), ready to be copied to the target drive with `dd`. despite
the naming, they are not traditional "live" images like those available on x86
platforms, and do not need installation like live ISOs.
`/boot` partitions), ready to be copied to the target drive with `dd`. These are
not "live" images like those available on x86 platforms, and do not need
installation like live ISOs.
To generate these images, first create a PLATFORMFS for the desired platform,
then use [*mkimage.sh*](#mkimagesh) to generate the image.

6
README.md.in
View File

@ -44,9 +44,9 @@ First create a ROOTFS for the desired architecture, then use
#### Generating ARM images
Platform-specific filesystem images contain a basic filesystem layout (`/` and
`/boot` partitions), ready to be copied to the target drive with `dd`. despite
the naming, they are not traditional "live" images like those available on x86
platforms, and do not need installation like live ISOs.
`/boot` partitions), ready to be copied to the target drive with `dd`. These are
not "live" images like those available on x86 platforms, and do not need
installation like live ISOs.
To generate these images, first create a PLATFORMFS for the desired platform,
then use [*mkimage.sh*](#mkimagesh) to generate the image.