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

From Alpine Linux
No edit summary
No edit summary
 
Line 7: Line 7:
</pre>
</pre>


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?
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 so that turned out to be a bit of a mess to clean up after all. And trying to use mmcblk0p1 for apk cache is not so great either, that was another thing to fix.


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.  These instructions on this page are not step-by-step correct.
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 for a rpi installation, 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.  These instructions on this page are not step-by-step correct.


<small><span class="autosigned">—&nbsp;Preceding [[Help:Signature|unsigned]] comment added by [[User:Ecloud|Ecloud]] ([[User talk:Ecloud|{{int:talkpagelinktext}}]] • [[Special:Contributions/Ecloud|{{int:contribslink}}]]) 09:17, 29 July 2023</span></small>‎
<small><span class="autosigned">—&nbsp;Preceding [[Help:Signature|unsigned]] comment added by [[User:Ecloud|Ecloud]] ([[User talk:Ecloud|{{int:talkpagelinktext}}]] • [[Special:Contributions/Ecloud|{{int:contribslink}}]]) 09:17, 29 July 2023</span></small>‎

Latest revision as of 15:24, 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. But it ends up with redundant files in /media/mmcblk0p1 and /media/mmcblk0p1/boot so that turned out to be a bit of a mess to clean up after all. And trying to use mmcblk0p1 for apk cache is not so great either, that was another thing to fix.

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 for a rpi installation, 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. These instructions on this page are not step-by-step correct.

— Preceding unsigned comment added by Ecloud (talkcontribs) 09:17, 29 July 2023