Um, I should have "invested" in $TRUMP coin instead? :-)

That seems like a *you* problem, not the password's. :-)

... $45.47 would have lost him $1.98/month/line.

There's an important difference. Cancer will usually keep reproducing until it kills the host. Humanity has hope. If we kill off enough billionaires and their bum-lickers, we might actually learn to live within the limits of our environment. In every society evolved enough to give women control of their own fertility, birthrates plummet. That takes care of the actual numbers problem. That just leaves the greedy, the arrogant and the power hungry to deal with...and that's where things get bloody.

I wonder how they'll feel if a president gets Seal Team 6 to assassinate one of them, to install someone else ... Oops! too late. /cynical-conspiracy-theories

(Noting that Trump's lawyer asserted that a scenario like this would be legal and immune and SCOTUS didn't contradict it.)

Adding: Passwords also work in the dark.

The only time either of my Windows 10 or Linux (Ubuntu, now Mint) systems have ever crashed was due to a hardware issue and I can count on one hand the number of times that's happened across both systems over the last 10+ years. Whatever is going on with your systems isn't the norm.

I get unlimited talk/text for $10/month with 5G data at $5/GB using the Ting Mobile Flex plan.
I've never used more than ~ 100 MB data/month, so my bill is $17.24/month.
My service is over T-Mobile, but Ting supports Verizon too...

Anything with this guy is probably going to cost more than elsewhere -- there has to be something to skim off. Grifters gonna grift...

From TFA:

Yuk.

More sadly, waiting to see how they rule when a Democrat is in office ...

Their lawyer continued, "It's the least we could do."

Keeping the home directories in another tree has been a thing for a very long time. I was working with Xenix in the early 1990s with a second hard drive, and kept all the home directories on the external hard drive. When I needed to do an OS reinstall, it just a matter of mounting the external file system on the path. Same would apply if you're using NFS or any other network file system.

What distort? We're running Ubuntu LTS on workstations, and we keep the updates rolling, and have no significant issues. Generally when we want to do feature updates, we don't do in-place upgrades at all, we just build a new image and roll it out. We want complete control over new feature rollouts, including any major new upgrades of key software like LibreOffice.

And honestly, that's pretty much how we were managing Windows prior to beginning the migration. Updates in general are always a risky business, and I've seen upgrades in every OS I've worked with since Windows 3.1 go horribly awry. I've baked Windows systems, Linux systems, BSD systems, and even had to finally give up and reinstall my M1 Mac because the major release upgrade worked about 90%, but there was enough peculiar behavior that it just wasn't worth trying to track down.

In all cases in an enterprise environment, regardless of OS, you don't want feature updates, significant changes to functionality, or installs of major version of updates to software. When it comes to that, you're working in a lab environment, rolling out to a few users to test stability and interoperability, and then pushing them out to all the workstations. This isn't a Linux thing, this is just how an IT department stays sane and doesn't screw up the whole organization's workflow.

There are only a few circumstances I can imagine where LTS support over three or four years would even be desirable, and most of those are pretty niche use cases dealing with specialized equipment or legacy systems. In general, whether it's Linux, BSD, Windows or even MacOS, it's always better to do a full reinstall with the new OS. Heck, by the time Windows Server 2003 went mainstream, only madmen were doing in-place upgrades on domain controllers. The better solution was always to build a new DC and then decommission the old one.

All my worst upgrade disasters in any OS came from in-place upgrades just fucking everything up. At best, it left a lot of old cruft hanging around, at worst it rendered a system almost unusable, and it was usually a bit of both.

The way I'm rolling out Debian and Ubuntu at work these days is just working images. Sometimes there's some funky hardware that requires after I clone an image that needs some intervention, but generally it just works. New images are generated every six months, or when a new release has been tested, rinse and repeat. In the business world you don't give a crap about anything but quick up time, and I have a stack of spares in a closet that get refreshed regularly, and when something blows up, you grab one off the shelf and move on. New OS upgrade, new image.