@jesse_b There's less typing if you run the whole script under sudo ;)

Honestly, it seems hard to argue against elevating only the parts that need it, minimal exposure and all that. Plus sudoing the whole script exposes the shell too, not just all the programs the shell calls. On the other hand interactive use where your shell is underprivileged for the task and you need to sudo everything is a pain. Not because of the typing but because tab completion of filenames doesn't work

@jesse_b just simplicity and ease of use. There is no risk here, the script is one command, so it seems more straightforward to run the script with sudo.

@terdon I would agree in this case, especially since sudo resets the environment, which is the issue in the question I think you're referring to.

It's far safer in the long run to run the script with sudo than to try to configure sudo to not clear the environment when running Python.

For me, it's also the principle of least surprise. I don't like my scripts to prompt me for passwords. It should fail when lacking permissions, with an informative error, so I know to explicitly run it as root.

@terdon True, I always assume users are just showing simplified examples to recreate the problem though

I don't like my sudo prompting me for passwords lol

Uhh I'm building rootfs, and it's taking so long time.

I initially read that as "I'm building roofs"

And after that, I gotta build the kernel as well. Dang it.

The host (NixOS) running VirtualBox having Ubuntu building its own Linux to be run in QEMU... This is an insanity.