Talk:Classic install or sys mode on Raspberry Pi

From Alpine Linux
Revision as of 13:35, 29 July 2023 by Ecloud (talk | contribs)

Another idea: 

# mount -o remount,rw /media/mmcblk0p1
# mount --bind /media/mmcblk0p1 /mnt/media/mmcblk0p1
# FORCE_BOOTFS=1 setup-disk -m sys /mnt

Then at least I don't see errors about being unable to write to /mnt/boot. But it ends up with redundant files in /media/mmcblk0p1 and /media/mmcblk0p1/boot. Which does it use to boot? The files in the root of the first partition, right? So actually maybe /media/mmcblk0p1 should be mounted to /mnt/boot... then it will just do some needless overwriting?

TBH I can't believe it's apparently been a couple of years of debate about how to work around the problems in the installation script, and it's still not fixed. I'm kindof new to alpine (except to the extent that it's the basis of postmarket OS) and having to work around installer problems does not make a good impression.

— Preceding unsigned comment added by Ecloud (talk • contribs) 09:17, 29 July 2023‎

Retrieved from "https://wiki.alpinelinux.org/w/index.php?title=Talk:Classic_install_or_sys_mode_on_Raspberry_Pi&oldid=23988"