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.

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.

Also, if you like htop, youre going to love btop.

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.

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.

It’s usable-ish, but still kinda crashy and prone to occasionally imploding.

I wouldn’t really use it as my sole daily driver, but for certain people doing certain things, it’s probably fine.

(It needs another year, honestly.)

Maybe?

It depends on if the added functions are software-based, or if there’s some hardware funkery going on.

Given it’s a consumer product, I’d wager it’s just a drive in an enclosure that does all their mirroring/backups/encryption stuff in software, but their marketing material doesn’t seem to say one way or the other.

Google indicates older versions can be reformatted, so I’d bet that’s still true.

If I’m wrong it’s not my fault, etc.

Hey, if you can do it on a 4004…

(Yes yes, you’d have to write an x86 emulator and it’d be slow as heck but I mean, you could.)

deleted by creator

I’m shocked I didn’t get downvoted to shit myself.

It’s just that it was VERY clearly either sanctions or a NSL, since the Linux Foundation is in the US and the two things that result in a public entity like that making silent, un-explained changes are, well, sanctions and NSLs and you don’t say shit because your lawyer told you not to.

I don’t necessarily agree that tossing contributors off an open-source project is in the spirit of the OFAC list, but the problem almost certainly is that they’re employed by some giant tech company in Russia.

And, in Russia, like in the US, and Israel, and China, and anywhere else you care to mention, tech companies are almost always involved in military supply chains, since shit don’t work without computers at this point.

Which leads to a cycle of being unable to work with Weapons, Inc. and someone works for Weapons, Inc. so now that person can’t be worked with either and so your choices are… comply with the OFAC list, or take a stupid amount of legal risk up to and including angry people with guns showing up to talk to you.

We really don’t know the whole story and immediately jumping to “Imperialists bad!” is how certain chunks of Lemmy roll these days.

I think they’d be much happier if they all moved to North Korea and helped achieve the goal of Juche by becoming dirt farmers.

Which is exactly what anyone who wasn’t wanting to just snort some concentrated outrage knew was the case.

And you can argue as to if OFAC list should apply to things like this or not, but the problem is that the enforcement options for OFAC violations include ‘stomp you into the ground until you’re powder’, most people are just going to comply.

The same reason people who drive 20 miles a day have worries about range on an EV that’ll do 300, or why people espouse the freedom of Android but then use the default Google apps.

People like the option of choice, even if they’re not necessarily ever going to engage in making a different one.

If there are two options for a computer, one is “will run everything” and the other is “will only run Windows” a good portion of people are still going to pick the first, even though very few of them will ever do anything else, simply because people really really like having the option of choice.

At least a decade old, if not more than.

If you wanted to swap your vendor EFI image to something else, at this point it’s all going to be via a SPI programmer, and if you own one of the two boards that it supports, coreboot/openboot.

But, essentially, you can’t swap because there’s very little supported hardware, and thus are stuck with your vendor proprietary EFI.

What’s hilarious, I guess? is that the EFI setup is more or less it’s own OS that can then chainboot an OS which is how the mid90s workstations (Sun, SGI, HP, etc.) worked.

…I still have some OS/2 (or, rather, ArcaOS) systems running here.

Mostly for a very limited subset of things that never really migrated across to “modern” windows - I have a BBS running on there because 16 bit DOS apps on OS/2 was pretty much the best way to run them when it was 1994, and in 2024 it’s still the best way to deal with them.

competition in the x86 OS space back then

Oh yeah: there were a stuuuupid amount of OSes.

On the DOS side you had MS, IBM, and Digital Research.

You also had a bunch of commercial UNIXes: NextStep, Solaris, Xenix/SCO, etc. along with Linux and a variety of BSDs. There were also a ton of Sys4/5 implementations that were single-vendor specific so they could sell their hardware (which was x86 and not something more exotic) that have vanished to time because that business model only worked for a couple of years, if that.

There was of course two different Windows (NT, 9x), OS/2 which of course could also run (some) Windows apps, and a whole host of oddballs like QNX and BeOS and Plan9 or even CP/M86.

It was a lot less of a stodgy Linux-or-Windows monoculture, and I miss it.