

Thinkpads are not what they once were. I finally gave up on them, moved over to a Framework, and haven’t regretted it.
Thinkpads are not what they once were. I finally gave up on them, moved over to a Framework, and haven’t regretted it.
I see you have yet to meetmy old friend Debian, who was supporting i386 until 2 weeks ago, and includes a much broader library of softwate than Microsoft has ever maintained.
Daily driver here. Stable for servers, testing for workstations.
Debian Testing isn’t as stable as Stable, but has been far more reliable than anyone else’s desktop releases. I’m also not a fan of Fedora and others’ policy of ending support on the day of a new release.
If for some reason you decide to hold back on an upgrade of Testing, you’ve still got five years of patch support coming. And if I do want to live on the bleeding edge, there’s always Sid (also called Unstable). That’s where you’ll run into the kind of instability you can expect from a rolling release.
My favorite will probably always be Gentoo, but I don’t always have time for that hobby.
Mind sharing? It would be nice to know what those support interactions are like in case others here (including myself) ever have to deal with them.
I also have some laptop repair experience, and am probably not the only one here that does. Maybe we can suggest something that gets you up and running more quickly than another round trip to the repair center?
Likewise. Really hard to make a judgement without a lot more information.
Our experience has been good. We have both a 13 and a 16, and they’ve done well in less than ideal conditions. Both AMDs, had the 13 since 23 and the 16 since 24. Had to open up one to adjust a cable for a flicker problem, and there was a driver issue for a bit with the wifi but that was on the OS side.
Honestly I’ve been pretty impressed, but we haven’t had to RMA anything so I can’t speak to the support experience if something happens during the warranty period.
Guinea fowl even more so
Lack of ground contact also deters termites.
Not everyone that disagrees with a law is in a position to immediately change it.
Nah. Replacing the kernel is probably planned for the next point release - it’ll just be GNU/systemd
It doesn’t break apt, Canonical just broke their version of apt just to prefer snaps now.
FTFY
Only reason it wouldn’t work is Canonical killing the .deb package. That was an unforced error. So no, still not a good idea.
The way this works in the server world is “95th percentile” billing. They track your bandwidth usage over the course of the month (probably in 5 minute intervals), strike off the 5% highest peaks, and your bill for the month is based on the highest usage remaining.
That’s considerably more honest than charging you based solely on the highest usage you could theoretically use at any time point in a 24 hour period (which is how ISPs define the “max bandwidth”) and then charging you again or cutting off your service if you use more than a certain amount they won’t even put in writing.
The money in calligraphy is usually made on wedding invitations, diplomas, “fine fining” menus, and corporate award certificates
They are
Off topic, but as a pen lover - those are lovely! Especially enjoyed the second two from the left.
You don’t need to run an X server on the headless server. As long as the libraries are compiled in to the client software (the GUI app), it will work. No GUI would need to be installed on the headless server, and the libraries are present in any common Linux distro already (and support would be compiled into a GUI-only app unless it was Wayland-only).
I agree that a GUI-only installer is a bad thing, but the parent was saying they didn’t know how it could be done. “ssh -X” (or -Y) is how.
literally no one will ever have that problem, but lets humor your ridiculous made up bullshit
Wow, your username really fits.
Actually, it’s a description of some of the issues I’m dealing with right now. And yes, we’re DIYing it with RJ45 wired switching outlets on a separate vlan and subnet. And yes, we use a chest freezer.
And yes, there are more automatic and passive ways to do some of these things, like planting deciduous trees to shade your south wall in summer but not winter. Not everyone owns their home and land though.
There are problems they can actually solve, mostly heating and power related:
In summer, lower the blinds on south facing windows when the sun comes up to reduce solar heating, then raise them in the evening to increase air flow against the window panes. This reduces the need for air conditioning, resulting in a surprising amount of power saved.
On a home solar system, start the washing machine, dishwasher, and dryer that were loaded in the morning when the batteries reach 80% charge. Allow them to run off the inverter rather than taking the charge/discharge losses involved in battery storage, reducing the size of both battery bank and solar array needed.
Lower the freezer temperature when there is a power surplus, and raise it back to normal when not so that cooling energy is used when it’s cheapest/most available
If you don’t work from home, you can’t do the second two yourself. They require automation. Reducing baseload requirements and battery storage needs can make a transition to renewable power much cheaper and more efficient. With mass adoption, that extends to power grids and not just off-grid homes, and has significant effects on things like the amount of lithium that needs to be mined or the number of coal and LNG power plants that are needed for times that are off-peak for wind and solar generation.
Advice from a long time sysadmin: You’re probably asking the wrong question. ncdu is an efficient tool, so the right question is why it’s taking so long to complete, which is probably an underlying issue with your setup. There are three likely answers:
sudo find $(grep '^/' /etc/fstab | awk '{print $2}') -xdev -type f -exec dirname {} \; | sort | uniq -c | sort -nr | head
explanation
This command doesn’t give an exact file count, but it’s good enough for our purposes.
sudo find # run find as root
$( … ) # Run this in a subshell - it’s the list of mount points we want to search
grep ‘^/’ /etc/fstab # Get the list of non-special local filesystems that the system knows how to mount (ignores many edge-cases)
awk ‘{print $2}’ # We only want the second column - where those filesystems are mounted
-xdev # tell find not to cross filesystem boundaries
-type f # We want to count files
-exec dirname {}; # Ignore the file name, just list the directory once for each file in it
sort|uniq -c # Count how many times each directory is listed (how many files it has)
sort -nr # Order by count descending
head # Only list the top 10
If they are temp files or otherwise not needed, delete them. If they’re important, figure out how to break it into subdirectories based on first letter, hash, or whatever other method the software creating them supports.