NireBryce

reality is the battlefield

the first line goes in Cohost embeds

🐥 I am not embroiled in any legal battle
🐦 other than battles that are legal 🎮

I speak to the universe and it speaks back, in it's own way.

mastodon

email: contact at breadthcharge dot net

I live on the northeast coast of the US.

'non-functional programmer'. 'far left'.

conceptual midwife.

https://cohost.org/NireBryce/post/4929459-here-s-my-five-minut

If you can see the "show contact info" dropdown below, I follow you. If you want me to, ask and I'll think about it.


NireBryce
@NireBryce

but NixOS has a mechanism to supplant a host operating system, called nixos-infect or nixos-assimilate, and as a joke I replied to someone with

but like, the pieces are there. you could have nixos-infect(malware variant) where as part of the process you image the drive into a container.

and then just run the host OS on top of nixos potentially without the installing person being any wiser, since nixos also has like, pre-grub hooks IIRC.

i mean they'd be pretty wise because it'd take like three hours. but still.

anyway putting it out there in case someone else needs some bad ideas to chew on. but it'd take Some Work so don't like, white whale this for a shitpost



You must log in to comment.

in reply to @NireBryce's post:

you joke, but I considered something like this For Serious as a @styx-os feature

but, maybe a lot less invasively. we are having styx install to an existing OS, and it does already have the option to add itself to the existing bootloader. We could virtualize the host OS under styx, then - and allow seamless access to applications and the like across both systems

it could be. we'll be using nix and nixpkgs defs as a package build backend, capturing them to plug-and-play style styx application images. using tooling which we call charon. we're also likely employing kerberos on our backend, too