Perhaps it was just a little too simple?

https://www.microsoft.com/en-us/evalcenter/evaluate-windows-11-iot-enterprise-ltsc

Keep in mind, though, that you’ll still have to do some activation and KMS hackery to make them usable, but you can at least use an installer that’s going to be clean.

From Microsoft. They actually provide ISO downloads for the 11 LTSC versions, so there’s not really any reason to go grab some random one off totally-legit-software-and-totatlly-not-malware.com or whatever.

Does !12345:p do what you want?

Edit: that also makes hitting the up arrow result in whatever command that was, so if you wanted to edit the line or whatever, you could !12345:p, up, then edit and execute.

Uh, are you sure your shell you’re using is bash and not zsh or something else?

Bash is indeed just !12345.

Why not save time and do it the other way?

Install the minimal/netinstall image, and then add what you need.

You’ll probably spend less time adding than trying to figure out what’s installed that you do or don’t need and trying to remove random packages without breaking anything.

Kudos for the unique delivery method, I guess?

(Also I do not like this sudden appearance of QR codes in daily life like for menus and shit for exactly this reason: just give me a URL if you must, or print something out and stop being cheap.)

two commands: dd and resize2fs, assuming you’re using ext4 and not something more exotic.

one makes a block-level copy of one device to another like so: dd if=/dev/source-drive of=/dev/destination-drive

the other is used to resize the filesystem from whatever size it was, to whatever size you tell it (or the whole disk; I’d have to go read a manpage since it’s been a bit)

the dd is completely safe, but the resize2fs command can break things, but you’d still have the data on the original drive, so you could always start over if it does - i’d unplug the source drive before you start doing any expansion stuff.

dd then resize the fs?

Edit: one caveat here I forgot: if your fstab is using UUIDs, you’re going to have to update that, since the new drive won’t be the same UUID because, well, it’s not the same drive.

sidequests that involve you slowly following an NPC

I haate those quests. ‘Quick! We must urgently go do something to save everyone!’ and then waddles off like an over-stuffed penguin.

Can we PLEASE at least make these stupid NPCs walk at player run speed, it’s been obnoxious for like 30 years now.

My comment was more FDM vs resin support removal, and that it’s not like resin is all sunshine and rainbows.

If anything, modern tree supports for FDM have fixed the giant-blob-of-plastic problem with supports you’d previously get on smaller models, where you’d end up with, uh, well, a giant blob of plastic stuck to an arm or a sword or whatever.

Still not fantastic, but until someone figures out antigravity, it’s what it is.

print with supports, but removing supports from such thin, fragile bits of a model is nigh impossible without doing damage

Removing resin supports is worse, if anything.

They leave little bumps where they’re cut off that you have to then try to VERY VERY gently sand off without bending or breaking said fiddly models.

Yeah DNS is, in general, just goofy and weird and a lot of the interactions I wouldn’t expect someone who’s done it for years to necessarily know.

And besides, the round-robin thing is my favorite weird DNS fact so any excuse to share it is great.

Yeah, I noticed that.

It’s on my to-do list for next week since I should have time to sort that out/file a bug if it’s something that’s not a configuration error.

Uh, don’t do that if you expect your mail to be delivered.

Multiple PTRs, depending on how the DNS service is set up, may be returned in round-robin fashion, and if you return a PTR that doesn’t match what your HELO claims you are, then congrats on your mail being likely tossed in the trash.

Pick the most accurate name (that is, match your HELO domain), and only set one PTR.

(Useless fact of the day: multiple A records behave the same way and you can use that as a poverty-spec version of a load balancer.)

sudo smartctl -a /dev/yourssd

You’re looking for the Media_Wearout_Indicator which is a percentage starting at 100% and going to 0%, with 0% being no more spare sectors available and thus “failed”. A very important note here, though, is that a 0% drive isn’t going to always result in data loss.

Unless you have the shittiest SSD I’ve ever heard of or seen, it’ll almost certainly just go read-only and all your data will be there, you just won’t be able to write more data to the drive.

Also you’ll probably be interested in the Total_LBAs_Written variable, which is (usually) going to be converted to gigabytes and will tell you how much data has been written to the drive.

As a FunFact™, you’re more likely to have the SSD controller die than the flash wear out at this point.

Even really cheap SSDs will do hundreds and hundreds of TB written these days, and on a normal consumer workload we’re talking years and years and years and years of expected lifespan.

Even the cheap SSDs in my home server have been fine: they’re pushing 5 years on this specific build, and about 200 TBW on the drives and they’re still claiming 90% life left.

At that rate, I’ll be dead well before those drives fail, lol.

My read was ‘we need to make more communities, AND we need more users’ and I’m not sure why more communities solves anything since I’ve shown Lemmy to several actual real touch-grass kind of friends and they’re all like ‘but why? there’s nothing there.’

Which is both very wrong, and completely understandable because if you go searching for a community about something, you’ll find a whole lot of no activity ones and that’s just a misleading and confusing presentation which they’re taking the wrong impression away from.

I don’t think there’s a group of users who are just sitting out there waiting for a community about Longaberger baskets to make the jump off reddit, but there are a LOT of people who would move if it looks like it’s not just another “reddit killer” with lots of empty zones of nothingness.

Hard disagree.

A million empty communities simply makes all of lemmy look like a barren wasteland nobody uses.

We, if anything, need to stop making a community for every single edgecase that someone might ever one day want to talk about, and focus on the basics, until there’s enough people interested in some random niche thing to justify adding the community.

That is to say, it should be organic community growth led by users making a more specific community from a larger community, and not server admins making, for example, 421,000 different sports team communities hoping users will somehow magically appear and use any of them.

Lemmy is still at the scale that a single /c/NFL could more than adequately handle the entire volume of people talking about NFL games, and we don’t really need a /c/ for each league, team, player, and coach or whatever.

Read up on the saga of /r/jailbait sometime if you want to be utterly confused how the FBI didn’t show up and arrest everyone involved with Reddit.