ryan

> this is essentially what https://github.com/taiki-e/install-action does. We could recommend using that in the readme, for now? oh neat! yeah let's do that

thanks for the response! after running docker it didn't even occur to me that the runtime would need > 2GB of ram, is this too low to be worthwhile? (i...

@teq0 i've subsequently got `k3s` via `k3sup` running on a cluster of Pi 3s without any issue (though the leader is a Pi 4) on [raspbian aarch64](https://downloads.raspberrypi.org/raspios_lite_arm64/images/), not heavily loaded...

huh, yeah bus sharing with linux drivers / other applications is certainly an interesting problem, for now i think the recommendation is probably don't do this :-/ for unshared use...

> How do you drive CS manually if that flag is set? ahh, i have always just used a separate GPIO (or patched the device tree to disable CS1, never...

i think there's an underlying issue here expecting `TARGET` to be a viable tuple when this could also be a json file for a more specific target. it seems like...

> Ideally we'd use https://github.com/rust-lang/rust/issues/94039 for this ahh how nice that'll be! fyi there's similar logic in [heapless](https://github.com/japaric/heapless/blob/main/build.rs) that might serve as a point of reference for some missing options....

I have the same error `failed to create shield, hint: do other cpusets exist?` on debian buster with cset version `1.5.6`. `cset set` shows that i have an additional set...

It looks like there are some assumptions about existing cpusets, manually creating a set with `cset set -s user -c 0-7` then invoking shield with `cset shield --sysset=root --userset=user -k...

Manually creating and moving processes between sets still works, for example: - `sudo cset set -s system -c 0-1 -m 0` to create a system cpuset with cores 1-0 -...