Debian's /tmpest in a teapot
Debian's /tmpest in a teapot
Posted Jun 4, 2024 19:11 UTC (Tue) by bluca (subscriber, #118303)In reply to: Debian's /tmpest in a teapot by mb
Parent article: Debian's /tmpest in a teapot
No. The next Debian release, due next year, will change your machine's behaviour in many ways, as it will be documented in the (lengthy) release notes. If you like it - good. If you don't - too bad, either reconfigure appropriately or stay on the current version until it goes EOL, and then start paying somebody to give you support beyond that.
> There should be a *good* reason for these changes.
Only one reason is needed: I have decided as such. Don't like it? Don't worry, you can have your money back, give me an address and I'll post you a cheque for £0.
Posted Jun 4, 2024 19:13 UTC (Tue)
by bluca (subscriber, #118303)
[Link]
Posted Jun 4, 2024 19:26 UTC (Tue)
by mb (subscriber, #50428)
[Link] (1 responses)
Ok. That's the rule and I will also apply it to you.
Posted Jun 4, 2024 19:33 UTC (Tue)
by corbet (editor, #1)
[Link]
Posted Jun 6, 2024 1:49 UTC (Thu)
by jccleaver (guest, #127418)
[Link] (3 responses)
Yep, that's bluca's and systemd's philosophy in a nutshell, right there.
Posted Jun 6, 2024 9:13 UTC (Thu)
by bluca (subscriber, #118303)
[Link] (1 responses)
Posted Jun 6, 2024 12:16 UTC (Thu)
by Wol (subscriber, #4433)
[Link]
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,
Posted Jun 6, 2024 10:40 UTC (Thu)
by smurf (subscriber, #17840)
[Link]
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.
Debian's /tmpest in a teapot
Debian's /tmpest in a teapot
So ... once again we would appear to have reached a point where everybody has said their piece — several times — and any minds that might conceivably be changed will have been changed. This seems like a good place to stop this back-and-forth, please.
A place to stop
Debian's /tmpest in a teapot
Debian's /tmpest in a teapot
Debian's /tmpest in a teapot
Wol
Debian's /tmpest in a teapot