There has been a few people with confusion as to whether the need for a partition table is there.
Specifically this line:
Take note of the device mount point. In our example above, it was mmcblk0
This can imply that the filesystem has to be placed on the disk, instead of on a partition; however, Unlaunch requires a partition table or it will complain. This should likely say in our example above, it was mmcblk0p1 since that would be a partition. (basically, this example is somewhat vague.) Then in the next line, mkdosfs /dev/(device mount point from above) would now be referencing mmcblk0p1 and not mmcblk0.
Though if an SD card somehow doesn't have a partition table to begin with, I don't know how I'd explain that via the guide (although if it's in this state they likely know how to make a partition table). I guess it can suggest looking at which TYPE each mount point is.
Was going to make a PR, but I can't think of a way to explain this, so made an issue instead.
lifehackerhansol
commented
3 years ago
There has been a few people with confusion as to whether the need for a partition table is there.
Specifically this line:
Take note of the device mount point. In our example above, it was mmcblk0This can imply that the filesystem has to be placed on the disk, instead of on a partition; however, Unlaunch requires a partition table or it will complain. This should likely say
in our example above, it was mmcblk0p1since that would be a partition. (basically, this example is somewhat vague.) Then in the next line,mkdosfs /dev/(device mount point from above)would now be referencingmmcblk0p1and notmmcblk0.Though if an SD card somehow doesn't have a partition table to begin with, I don't know how I'd explain that via the guide (although if it's in this state they likely know how to make a partition table). I guess it can suggest looking at which TYPE each mount point is.
Was going to make a PR, but I can't think of a way to explain this, so made an issue instead.