Debian's /tmpest in a teapot

Posted Jun 6, 2024 1:49 UTC (Thu) by jccleaver (guest, #127418)
In reply to: Debian's /tmpest in a teapot by bluca
Parent article: Debian's /tmpest in a teapot

>If you like it - good. If you don't - too bad,

Yep, that's bluca's and systemd's philosophy in a nutshell, right there.

Debian's /tmpest in a teapot

Posted Jun 6, 2024 9:13 UTC (Thu) by bluca (subscriber, #118303) [Link] (1 responses)

Correct - thanks for noticing! We pick sensible defaults that can be relied on, and empower you to customize them easily if and when needed.

Debian's /tmpest in a teapot

Posted Jun 6, 2024 12:16 UTC (Thu) by Wol (subscriber, #4433) [Link]

And was it *you* who decided Debian's policy to change Debian's defaults?

If it's just Debian deciding to adopt systemd's defaults, that's not down to systemd.

bluca can be a pain in the arse - can't we all - but unless he's responsible for Debian policy I fail to see how this has anything to do with him.

(Or is this the transition where now-stable is SysVInit, and next-stable is systemd, but even there I fail to see how this is down to systemd at all ...)

Cheers,
Wol

Debian's /tmpest in a teapot

Posted Jun 6, 2024 10:40 UTC (Thu) by smurf (subscriber, #17840) [Link]

@corbet asked us, multiple times, to stop the adversial and/or unproductive comments.

It's a freakin' default. You don't like it, change it. Other systems have been using the same default settings for literally decades.

If your argument boils down to "it's a change and I don't like it", well, open your window, there's way worse changes than putting /tmp into RAM looming on the horizon. Doing something about these would be a more productive use of everybody's time.