I personally call this process of setting up a new device, whether for me or for someone else, "shit shoveling". It is something of a ritual.
In the former case the thing that needs to be removed is the entirety of the OS (and if that proves to be impossible, the device is returned or discarded), and in the latter it's a scan of all apps and removal of all unnecessary apps, my grandma does not need Samsung Galaxy Games, thank you very much.
I have been doing this for decades. My files are in a sub-directory of $HOME. It also makes it very obvious when a piece of software does not treat your $HOME with respect.
On Windows this was always easier because, for some reason, most everyone respected %appdata% compared to XDG_CONFIG_HOME, but also because hidden files wasn’t just a naming convention but an actual separate metadata flag.
Always... Except for the decades before this became common. Never a bloated C: root directory. Microsoft even had games store stuff in My Documents\Games at one point. My Documents was a user dir that saw a lot of abuse over the years.
> Jeff once simultaneously reduced all binary sizes by 3% and raised the severity of a previously known low-priority Python bug to critical-priority in a single change that contained no Python code.
This sounds really plausible. A change to the C toolchain/library (for example, specialized/inlined memcpy) may affect binary sizes significantly, and may change the behavior of something the C standard leaves undefined (for example, memcpy with overlapping arguments).
I have such a Python bug right now because of something that fork()s in a way that can't posix_spawn(). One of those is a lot easier to make performant than the other.
I had the same reaction. Haven't they been selling DGX boxes for almost 10 years now? And they've been selling the rack-scale NVL72 beast for probably a few years.[1]
When nVIDIA sells DGX directly they usually still partner with SuperMicro, etc. for deployment and support. It sounds like they're going to be offering those services in-house now, competing with their resellers on that front.
Back when my job involved using Kubernetes and Helm, the solution I found was to use `| toJson` instead: it generates one line that happens to be valid YAML as well.
where podman-wrapper passes `--user=1000:1000 --userns=auto:uidmapping=1000:$SERVICE_UID:1,gidmapping=1000:$SERVICE_GID:1` (where the UID/GID are set based on the $USER environment variable). Each container runs as 1000:1000 inside the container, which is mapped to the correct user on the host.
In the former case the thing that needs to be removed is the entirety of the OS (and if that proves to be impossible, the device is returned or discarded), and in the latter it's a scan of all apps and removal of all unnecessary apps, my grandma does not need Samsung Galaxy Games, thank you very much.
reply