sed harbors no demon beasts, in my experience.

On the other hand, by default using sed -i is where the demons come in.

No, sed, NOT in place. Not the first time. Show me what you want to do based on the instructions I gave you, and then we’ll talk about letting you play with the real data.

Thank you for the TL;dw. Sincerely appreciated.

Used it in a pinch once, and realized how incredibly awesome it is. Now, it’s my go-to.

Haven’t tried data and files on same stick, but…. Now I want to.

Only reason dd hasn’t bitten me is that in my head, if and of make perfect sense as input and output.

Doesn’t mean I won’t make that error tomorrow, ofc. But I tend not to alias except harmless stuff to avoid that very problem.

Seems to be something about the link rewrite, from where I sit - I can copy and paste the link and get exactly the expected page, but if I click it, it’s broken. Seems like a Lemmy issue, if anything, as the pasted link opens just fine.

I have this exact use case on a work machine, because the proxy flat refuses to prompt for the login, just goes straight to deny.

I own neither the proxy, nor the steaming heap of code that lives behind it, and I’m grateful for that every single day…

That’s the one I had in mind.

If the clock is off (bad CMOS battery, as others have noted); and there is a password “max age” setting that’s intended to be far, far, far in the future…

Well, your clock being off by a few hundred years might well trigger the (intended never) expiration setting.

Malware is a possibility, but I lean towards the date being the cause rather than an effect.

Yes - you’ll be well-served by the ThinkPad line in general. My first permanently dedicated Linux machine was a T430 and true to form things largely “just worked.”

That was enough years ago that I might well have needed to seed the network drivers on the usb key, and that was the worst of it.

They’re tanks, and the hw is generally easy and fairly intuitive to swap out the usual memory and HDD.

IIRC my first distro on that was Debian, had plenty of docs about the intersection of the distro and ThinkPad line.

Mint should be perfectly fine given that.

I will say that I try not to do fresh installs on unfamiliar hardware w/o some other available form of connectivity, my phone mostly is quite sufficient for the purpose. It’s just easier not to risk putting myself in a difficult position in the first place.

You’re in for some fun.

No harm enjoying a distro and being stable.

I’m a fan of Arch and derivatives but I need better odds of removed just working. Been running Mankato on desktop for some time to get both stable ish packages and also AUR as/where needed.

For servers, it’s Debian all the way for me. Ubuntu does some things I don’t personally love - no offense to the distro, it’s well constructed - and the recent ish changes in the RPM world didn’t sit well with me - strictly personal opinion.

Anything in a container generally runs on whatever the image was built with. It’s only a minimal pain to port simple dockerfiles, but when you get into multiple linked containers, that risks edge case bugs down the road.

Honestly, between the lot of it, I use a pretty representative sample - I think alpine on desktop would be kind of pointless to say the least, doesn’t mean I’m going to forego any container built on it.

Use case is a huge factor here, as is ability to grok multiple distros concurrently. I find that easy, but plenty of people don’t. For them, maybe rebuilding that image makes more sense.

Linux is all about doing what works for you and your use case.

FWIW, pacman doesn’t resonate nearly as well as pamac does with me. Probably because I haven’t had to dive deep into it. All about what works for an individual. If that’s stability on an Ubuntu derivative, great - Linux is Linux, in that context.

Seems a bit excessive of a judgement - under the best of conditions, my cursive is an absolute horror show. Always has been, and I’ve zero need for it with any frequency.

Suffice it to say, he’s not writing under the best of conditions. If you’d like to judge the content/intent, that’s your prerogative. But the quality of his penmanship is an utter irrelevancy.

While my primary masto is a single user instance, basically anywhere else I exist on the fedi is a subset of infosec dot *.

Those instances are all run by someone who a) is cool with spinning up a whole bunch of instances, b) is willing to risk the costs, and c) is excellent at delineating policy. There’s a “no removeding threads full stop” instance, and a “no threads by default, but user can flip switch” instance, for example.

That’s a method of operation that works from my pov but doesn’t suit everyone’s needs. Personally, I want nothing to do with threads but am more able to express my anti corp tendencies than I was in my twenties, and I’m more willing to accept that “it’s just bandwidth, find the instance that meets your needs.”

My needs involve no threads at all, but I can accomplish that with a very small amount of effort given. My circles.

I have been quite happy with my knock off no name over the ear Chinese/amazon special for months now.

When the battery life starts to suffer, I’ll spend the fifteen bucks again, but hasn’t been a problem at all.

Manjaro LXQT, on a Lenovo P70 that’s starting to show its age. They just work.

It’s basically the same headset hardware that I would’ve used in 2008 or so, tbh. Sound quality isn’t perfect but I am not an audiophile. They work equally well for music from my phone while driving since they’re one ear only.

Alpine. It’s powerful and fills a need in a specific use case. Just not my need, nor my use case, and that’s OK.

My docker usage is mostly testing and validation that when I run the code on the actual hardware, it will work as expected. I tend to want the container to match the target environment.

I can think of only one concrete example where the lead dev walked away - rightfully IIRC - and the community was able to pick it up, fork it, and actually maintain and continue to develop new features.

Sadly, that’s not often the case.

For my use cases at workstation level, Manjaro makes it really easy to work with whatever tooling I need - but I’m comfortable on CLI and aware of the risks/benefits.

Wouldn’t suggest it to a noob, ofc, but for me it’s a good middle ground where I can get things done, and also easily work with edge cases.

Not that I can’t build whatever I need to in the deb world, but I prefer to work with instead of against a distro’s packaging.

Login passwords are not something your pw manager can type.