I don’t think that’s what’s happening. There’s no hard requirement for cat to read everything straight into memory. It can send data once it’s available, and the receiving process can read it as fast as it wants. There are cases where this might be more clear: Let’s say you have a big video file that you want to convert to something that only supports like y4m input and is not in ffmpeg. A common way is something like ffmpeg -i infile -f yuv4mpegpipe - | encoder --y4m outfile - I’m pretty sure ffmpeg won’t read the whole infile into memory, nor will it store the whole y4m representation in memory. Instead, it will decode infile as necessary and push into the pipe at the speed the encoder can handle.

But yeah, I remember something about tar using libraries for compression being more efficient that piping its output to a compressor. So it’s still the better route, but probably not as much better as you think.

Then those containers or virtual machines should add this or create the home as needed.

systemd has its own containers, so this is the implementation of that requirement; “virtual machines” might use this exact binary to create home, among other directories like srv and what not. Someone at one point probably said “we always need to create these when spinning up systems, maybe systems can provide a mechanism to do that for us?” and then it was implemented.

Having/home listed as a tmp file on regular systems is problematic by the nature of what tmpfiles claims it does.

systemd-tmpfiles claims the following:

systemd-tmpfiles creates, deletes, and cleans up files and directories, using the configuration file format and location specified in tmpfiles.d(5). Historically, it was designed to manage volatile and temporary files, as the name suggests, but it provides generic file management functionality and can be used to manage any kind of files.

I rather think having a purge command was the issue here, at the very least it should print a big fat warning at what it does, better even list all affected files and directories. There’s no reason a normal user needs this and with the name of the binary, it’s totally misleading, which is an issue in these situations.

E.g. for quick provisioning of containers or virtual machines, this is also to make sure the required directories always exist. In a normal distribution, /home already exists, so systemd-tmpfiles does nothing, but there are cases where you want to setup a standard directory structure and this is a declarative alternative to scripts with a lot of mkdir, chmod and chown.

The name systemd-tmpfiles is kind of historic at this point, but wasn’t changed due to backwards compatibility and all.

This would be somewhat interesting if it wasn’t for the fact that most of the countries in BRICS had massive human rights issues themselves or weren’t otherwise problematic:

Brazil: massive problems under Bolsonaro, luckily he’s no longer president

Russia: was against Ukraine, Mafia gas station state, oppression of homosexuals. Assassinated Nationals on foreign soil.

India: Hindu ethnostate with a caste system, also assassinated Nationals on foreign soil.

China: destabilizing source that uses economic influence to sabotage Western ones through state-sponsored espionage and other measures. Oppression of religious groups (Uighur, abduction of Gedhun Choekyi Nyima…), massive surveillance of its own population…

South Africa: actually probably the best of the bunch since apartheid ended though definitely not without issues

If they want so much, they can have their own financial system, but no other country can be forced to participate. It’s just nose again to detract from their own crimes. Which is a shame because they’re important topics that are being hijacked by these assholes. Especially the point of “unilateral protectionist measures” by a group that China is a member of is morning but ridiculous.

Alright, not that I wrote or implied that anywhere… In fact Java was probably the whole reason Oracle bought Sun to gain leverage over Android. Which fits very much into what I wrote - one company innovates, another one buys them to squeeze users (Google wasn’t a customer of Sun, they used their own implementation which wasn’t exactly Java but also not exactly anything else). Just that Sun by all means wasn’t a small company, I mean they controlled almost a full stack with their own processors (SPARC), workstations and servers (Blade was somewhat famous), an operating system with Solaris (and if you want to count it even JavaOS) and Java on top of those, and they contributed a lot of technology like NFS, ZFS (license discussions aside). On the other hand, when they bought someone, the product wasn’t just milked to death, but actually integrated into their stack and continued to be developed in the open.

Shame it turned out that way, I guess Sun was a bit overleveraged with how much they did vs. how much they made from it. And to think that Oracle paid less than a fifth than what Twitter sold for later for all of that technology to go to waste, just for a chance to sue Google… But we long as suits continue to license their stuff because they have cool advertisements at airports, this will keep going.

Oracle was never really innovative on a technical level , it’s first and foremost a company focused on selling licenses, and they’re really innovative in that regard but if you fall for that as a company, I have no pity, this is their whole schtick.

Big companies in general are often rather conservative in nature while innovation happens on smaller scale and later expands.

The big problem is rather that a lot of innovation has been absorbed by the big companies via buyouts, especially when money was cheap to borrow. Innovation bears risk, buying an established solution and milking existing users much less so.

I don’t think the users are without blame. A lot of people ignore the red flags when a solution is just convenient enough (we need the commercial support / this exactly covers our use case so we don’t have to hire someone to adapt it / …) and the vendor then cashes out when moving away from his solution would be really expensive.

I think there’s still a lot of innovation lately, but a lot people are just looking for the next big thing that does everything it feels like.

I found it especially funny that his initials are the same as Mike Tyson’s.

The guy is an absolute gaming legend. Just figuring out so much about a single game on your own and then optimizing it to such a degree with all the randomness involved. Truly obsessed

Nice info.

If you want know more about a completely different aspect of Punch-Out!, watch https://www.youtube.com/watch?v=TBR9ypSOTGQ

So in the non US game version, Soda Popinski is named Vodka Dunkenski.

I thought this was an issue with revisions, I still he was also called Vodka in the early US version.

I mean even Mike Tyson got renamed to Mr Dream later…

Isn’t he called “Don Flamenco”? Haha

What are you using right now?

The discussion is about koalas

You’re just envious

Did Gauss or Euler get an AEAD cipher mode named after them?

Also basically every Linux big name posted there. It was so great. I’m still sad it’s gone

Is docker even declarative?

Also you can build docker images from nix derivations

https://peanuts.fandom.com/wiki/Football_gag

I know you’re joking anyways, but I always cringe when I see that. There’s no need to invoke su there. If you want a root shell, use sudo -s or sudo -i depending on what kind of shell you want.

There’s a keepassxc-full package that comes with all the functionality. Anyhow, Debian does not have the concept of USE flags, these don’t make sense in a binary-based distribution.

NixOS: (1, 2) - You can define specific package versions but with the large repos I doubt there is much QA going on

It depends on the nixpkgs channel you use (I’m also using the term for flakes here, though technically these are then called inputs). The main channels, those being NixOS-stable whatever the current version is at the time and NixOS-unstable have a rather big set of packages that must be built successfully before users get updates, including the tests defined in the build system plus sometimes distribution-specific tests, though these are often rather simple, like start program and see if its port is open. Even more, when a library gets updated, all programs and other libraries depending on it get rebuilt as well, including all tests.

Now what if a package outside of that scope breaks? Most likely, your new configuration won’t build, so you’re stuck on an older but working configuration, or it does build, but something doesn’t work. But I’m the latter case, you can still choose to start the older working configuration.

Also the more complicated packages have very dedicated and capable maintainers from my experience, sure the smaller stuff is often updated mostly automatically with merge request created by bots and just the final merge approved by the maintainer, but the big infrastructure is usually tested quite well.

As a downside, this can sometimes lead to longer periods without updates when a lot of stuff has to get rebuilt and something doesn’t work (multiple days, but not weeks). You can then switch to another set in case the problematic packages don’t affect you, or just wait. However, saying there’s little QA is unfair, in fact from my experience there’s more QA in nixpkgs than in most distributions.

I don’t recommend NixOS to new users because it abstracts a lot of stuff away and makes use of mechanics that are helpful to understand first. But if you’re comfortable with Linux, NixOS is a great distribution that even on unstable works very well. Then again, it allows specific packages to depend on very specific versions of other packages, which is partially the reason you’d use a stable distribution.