@IceWolf that's even nicer. 20+ years in the shell and still learning.

@ed1conf @nixCraft I HAVE BEEN THERE AND DO NOT RECOMMEND.

/me tries to suppress twitching eye

@IceWolf Same. The hints from `dpkg-reconfigure debconf' are revealing of the mindset. It's good to know that "i am a control freak" is not the default, but that such users are willing to be accommodated.

One of my early learning experiences was running

for p in $(dpkg --get-selections | cut -f 1) ; do dpkg-reconfigure --priority=low $p ; done

...which took a while to get through.

@danderson Absolutely, during a midterm.

@gisgeek My initial question is, how many of those books are recently generated AI slop?

It's not an obvious language, so it would be easy to foist off slop on unwitting customers. "I don't get it" and "this is nonsense" are able to stand quite close together, semantically.

@EndorNim Back in the day, part of its appeal to me was that it encouraged you to think carefully on multiple axes about the names of variables and the forms of data you were munging.

@cleantext

http://mywiki.wooledge.org/BashGuide

greycat & lhunath aim for having the basics explained well, so you can actually use the shell.

There is nothing so good that Microsoft cannot ruin it:

https://www.jpt.sh/posts/quitting-github/

"This is fundamentally a labor issue. Developers of free & open source software still own their software, the fact that we choose not to charge for it does not diminish our ability to say what can & cannot be done with it. That is the truth that all licensing is premised upon. Microsoft and other genAI companies are committed to saying “not good enough, we’ll take it for free.”

@IGVazquez That looks just like what apt-listchanges puts out, but this isn't sounding familiar.

Perhaps there is an additional mechanism for apt dist-upgrade, but that is a guess, not knowledge.

@IGVazquez @debian
If it was that, then
apt-listchanges -a -f pager /var/cache/apt/archives/$package_version.deb
might help. No need to be root, either.

@pheonix I ran debian from woody to stretch; the only time I had to do installs were when I got a new machine or I borked the system on my learning curve. Weekly, sometimes daily, my first year or so. But def not yearly, after the first year.

@mcourcel I recall Korg released a no-cost software version of Kaossilator for android a few years back; this is feasible!

@jackjanssen 1) see if it's missing from the server because the file is missing, or if it's missing from the server because the packaging system is incorrect:
apt-cache policy $software

2) This can happen when you have a mix of releases, like stable, oldstable, testing. You can sometimes push the package resolver in certain directions with something like "apt-get install -t oldstable $software"

I do not know about the German translations of debian, but in English the man page for apt-get is MUCH more detailed than the man page for apt.

@bazkie
I think there's a difference between someone who doesn't *notice* that they are hurting you and someone that doesn't *care* that they are hurting you.

Someone who doesn't notice, will say "oh fuck, het spijt me" when you point it out. Someone who doesn't care is, for as long as they have not yet got what they want, indistinguishable from someone who enjoys causing suffering.
So yeah, guaranteed pain to interact with. Sounds like a good reason to react strongly to prevent.

@pierogiburo
you absolute hexagon.

@Phiznlil
The primary advantage is that Ubuntu is based on debian's testing release, which has countless *KNOWN UNACCEPTABLE BUGS* at any given time other than about a minute before declaration as stable on release day, and debian (stable) is based on fixing those bugs before release.

Though I have to admit, the ubuntu installer sure is slick.

@starlabssystems I'm running #devuan now, ever since debian switched to systemd for the laughable reason that everyone else was doing it rather than because it was an inherently good choice.

@wlonk I am not letting #gravy anywhere near my mission critical stuff until they switch to a memory safe language.

@mildsunrise Whoops off by one. Laugh if you want, point if you must.

/me wanders away embarrassed by my third reading comprehension failure today

@mildsunrise
That does not look to be the case:

https://www.openwall.com/lists/oss-security/2025/06/30/2
"Impact:
Sudoers files that include rules where the host field is not the current host or "ALL" are affected. This primarily affects sites that use a common sudoers file that is distributed to multiple machines. Sites that use LDAP-based sudoers (including SSSD) are similarly impacted."

I've not yet encountered a sudoers tutorial that doesn't specify "ALL" so I honestly doubt this is a problem for the average user, even for ubuntu.

Sure, it's an important bug. but "on any machine" seems an exaggeration.