Dmitrii Sharshakov
Dmitrii Sharshakov
> Right, I wasn't trying to imply that these flags would help your situation, just that these flags exist for a somewhat related purpose to specify primary package information. Got...
> Oh yes +1 for this. Currently our workaround is to remove or modify the fields which are non-deterministic. e.g. here via a Github Action: > > ``` > -...
Thanks for clarification, mixed-arch seems really cool! > The way I have done this is building a RISC-V binary to embed inside the Arm binary, and forcing the RISC-V entry...
Understood that, thanks. Should I close this or keep as a docs improvement proposal?
Another question (not really practical yet a cool thing). Can I reset and re-select the architecture for cpu1 multiple times without full reset? Like archsel = 0, reset, run Arm...
> Yes, I had a demo where all four cores were rendering 1/4 each of a DVI output by rebooting at 120 Hz. > > I think the current level...
> > Basically the only prohibited management from cpu0 to cpu1 is resetting while running a critical section or holding spinlocks? > > Not just spinlocks, any reset of a...
For the time being until I find some time to write a doc page, it should be just `selinux=0` to the cmdline
Alongside publishing SBOMs we should consider running Grype or another scanner in a CI job. Perhaps a cron job ran against all supported versions to track CVEs in those
I tested with a Fedora VM in which I deployed a Ceph single-node cluster using standard cephadm tooling. The VM as well as its storage disk (both qcow2) reside in...