Alpine Linux - User contributions [en]

Talk:Classic install or sys mode on Raspberry Pi

2023-07-29T15:24:30Z

Ecloud:

Another idea:

<pre>
# mount -o remount,rw /media/mmcblk0p1
# mount --bind /media/mmcblk0p1 /mnt/media/mmcblk0p1
# FORCE_BOOTFS=1 setup-disk -m sys /mnt
</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 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 [[Help:Signature|unsigned]] comment added by [[User:Ecloud|Ecloud]] ([[User talk:Ecloud|{{int:talkpagelinktext}}]] • [[Special:Contributions/Ecloud|{{int:contribslink}}]]) 09:17, 29 July 2023‎

Talk:Classic install or sys mode on Raspberry Pi

2023-07-29T13:36:24Z

Ecloud:

Another idea:

<pre>
# mount -o remount,rw /media/mmcblk0p1
# mount --bind /media/mmcblk0p1 /mnt/media/mmcblk0p1
# FORCE_BOOTFS=1 setup-disk -m sys /mnt
</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?

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.

— 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‎

Talk:Classic install or sys mode on Raspberry Pi

2023-07-29T13:35:41Z

Ecloud:

Another idea:

<pre>
# mount -o remount,rw /media/mmcblk0p1
# mount --bind /media/mmcblk0p1 /mnt/media/mmcblk0p1
# FORCE_BOOTFS=1 setup-disk -m sys /mnt
</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?

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 [[Help:Signature|unsigned]] comment added by [[User:Ecloud|Ecloud]] ([[User talk:Ecloud|{{int:talkpagelinktext}}]] • [[Special:Contributions/Ecloud|{{int:contribslink}}]]) 09:17, 29 July 2023‎

Talk:Classic install or sys mode on Raspberry Pi

2023-07-29T13:17:42Z

Ecloud:

Another idea:

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

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.

Talk:Classic install or sys mode on Raspberry Pi

2023-07-29T13:17:37Z

Ecloud:

Another idea:

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

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.

Talk:Classic install or sys mode on Raspberry Pi

2023-07-29T13:16:09Z

Ecloud: Created page with "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 t..."

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.