Talk:Classic install or sys mode on Raspberry Pi: Difference between revisions

From Alpine Linux
No edit summary
m (Unsigned comment attribution.)
Line 10: Line 10:


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.
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.
<small><span class="autosigned">—&nbsp;Preceding [[Help:Signature|unsigned]] comment added by [[User:|User:]] ([[User talk:|{{int:talkpagelinktext}}]] • [[Special:Contributions/|{{int:contribslink}}]]) Ecloud</span></small>‎

Revision as of 13:22, 29 July 2023

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. Not sure yet if the result is quite what's needed.

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 [[User:|User:]] ([[User talk:|talk]] • contribs) Ecloud