the thing about being able to run two kernels simultaneously, then move workloads from one to the other was kind of interesting. i think that means you could update your kernel without rebooting, but i'm stupid, so who knows?
it does seem kind of cool. the reason i thought about kubernetes is pod health checks, automatic rollbacks, and resource management (i only want my kernel update to have access to 16 megs of ram). i do wonder how a parallel kernel update could be run without affecting the filesystem if the changes result in failure. do you bind a virtual filesystem to the required directories, then somehow copy everything over if the new kernel is healthy? idk much about nerdy linux stuff
HepaticTampon 12 hours ago
the thing about being able to run two kernels simultaneously, then move workloads from one to the other was kind of interesting. i think that means you could update your kernel without rebooting, but i'm stupid, so who knows?
SignedSlut 11 hours ago
it does seem kind of cool. the reason i thought about kubernetes is pod health checks, automatic rollbacks, and resource management (i only want my kernel update to have access to 16 megs of ram). i do wonder how a parallel kernel update could be run without affecting the filesystem if the changes result in failure. do you bind a virtual filesystem to the required directories, then somehow copy everything over if the new kernel is healthy? idk much about nerdy linux stuff