Closed DogeLeader closed 7 months ago
You cannot use Gitpod or Github Codespaces to build Shimboot.
Alright, thanks.
You can try remounting the filesystem with the exec
and dev
flags.
Find the mount point by doing findmnt -T .
On my PC this prints out the following:
TARGET SOURCE FSTYPE OPTIONS
/ /dev/sdb2 ext4 rw,noatime
Now run sudo mount -o remount,exec,dev {TARGET}
, replacing {TARGET}
with the path listed as the target in the output of the previous command.
what does the mountpoint look like
where in the output is it?
It says "permission denied"
Can you send the output of the commands you're running?
@DogeLeader Try running these commands in your terminal, I tested it to work on Github Codespaces:
mountpoint="$(findmnt -T . | tail -n1 | cut -f1 -d' ')"
mount -o remount,dev,exec "$mountpoint"
This was also fixed in the latest commit, so do a git pull
and try again.
abc@418b89848064:~/shimboot$ findmnt -T . TARGET SOURCE FSTYPE OPTIONS /config /dev/loop3[/codespacemount/workspace/DesktopOnCodespaces/Save] ext4 rw,node
That looks to be right, you can try re-running the scripts now.
what should i copy?
Out of the output
You don't need to copy anything, I've already fixed the bug here. Just clone the repository again and retry the build.
oh alright ill try
sudo ./build_rootfs.sh data/rootfs bookworm
mount: /config: permission denied.
Did you delete and clone the repository again from scratch?
yep
Try running sudo DEBUG=1 ./build_rootfs.sh data/rootfs bookworm
, and copy-paste the entire output of that command.
what I do from here on?
I figured it out the command only works when it is this: sudo ./build_rootfs.sh /data/rootfs bookworm. You have to add a / before data. But after that I still did not have full access to /config.
I could not complete the process successfully. So I have one request, please add the: Jacuzzi board to the pre-built image uploads
Thanks for all the tech support!
I look forward to your response!
Jacuzzi is an ARM-based board, those are not supported yet. See issue #8
Are you going to add arm support in the future?
Because it would be very helpful.
Not going lie, my the school has our Chromebooks locked down tight: Our Chromebooks are arm based and they have digital write protection.
yes, again see issue #8 for arm support progress
this error happens when I use the command: sudo ./build_rootfs.sh data/rootfs bookworm:
mknod: /workspace/shimboot/rootfs/test-dev-null: Operation not permitted E: Cannot install into target '/workspace/shimboot/rootfs' mounted with noexec or nodev