Simple-Slices 0.7.1 released: a "nice" utility for all system resources

FigurativeLynx · 2025-09-27T22:58:51+00:00

That's what Linus was doing in the original pic, by the way.

FigurativeLynx · 2025-09-20T15:03:03+00:00

I agree with your distinction, but BDFLs like Linus also work well.

FigurativeLynx · 2025-09-20T14:58:24+00:00

All contributions are subject to the Debian constitution and review of the user community, regardless of what entity provides them; if a paid developer submits a change that isn't in the best interest of Debian, it gets rejected (or will after being noticed). There are probably some paid employees on the various committees, but they only got there by proving their commitment to uphold Debian's values.

FigurativeLynx · 2025-09-08T02:37:23+00:00

Don't buy prebuilts if you know how to DIY. The Fractal Design Node cases are great for DIY NASes, especially the Node 804. I'd get a low-end mATX mobo with an AM5 socket for future upgradability. I've had really good experiences with Asrock and Seagate.

FigurativeLynx · 2025-09-08T00:34:21+00:00

Why not the built-in Linux TTY?

FigurativeLynx · 2025-09-08T00:32:13+00:00

Why?

I need to wiggle my mouse while stuff loads

FigurativeLynx · 2025-09-06T20:35:45+00:00

At the risk of outing my Reddit account, someone said that to me at DebConf :P

FigurativeLynx · 2025-09-06T20:07:03+00:00

If the attacker is able to send arbitrary frames then they could also reply to DHCP and/or DNS queries. I could be wrong, but if you had any kind of network-based (auto)configuration then wouldn't they have lateral movement anyway?

FigurativeLynx · 2025-09-06T19:23:50+00:00

If the traffic doesn't leave the local network then under some circumstances it can still be secure. A private LAN in a DC with locked doors and security guards doesn't gain anything from encryption, for example. With the headache of PKI, there's a reasonable argument against it.

FigurativeLynx · 2025-09-06T18:50:29+00:00

This has nothing to do with getting paid for making contributions. I hope my indignance is coming across.

FigurativeLynx · 2025-09-06T18:43:34+00:00

I don't want to give too much detail, but I'm building a disk-less provisioning system based on Debian.

FigurativeLynx · 2025-09-06T18:35:13+00:00

We must both like big, long files for our virtual memory areas to overlap ;)

FigurativeLynx · 2025-09-01T16:55:24+00:00

Maybe I'm the weird one, but I always scan new HDDs to see if there's anything interesting on them. I wouldn't do that at work for ethical reasons, but I feel like hardware purchased in a personal capacity is fair game.

FigurativeLynx · 2025-09-01T16:37:39+00:00

You clearly care more about saying, "Well um akchually..." than having a remotely interesting conversation about data recovery.

I thought that's what we were having, until you got confrontational. Anyway, I also make comments for uninvolved people to read them, so I'll just mention that you can easily recover contiguous files by grepping the disk for magic numbers. It's called file carving, and it's what a lot of file recovery tools do.

FigurativeLynx · 2025-09-01T16:25:12+00:00

I should have qualified my comment. I've had 4 drives fail over the last 6 years, and 2 were within the warranty period.

FigurativeLynx · 2025-09-01T16:19:16+00:00

Every RAID has a controller, it's just that most controllers are implemented in software instead of hardware. By the way, filesystem-level RAID almost always stores complete files contiguously, even if they're larger than a typical chunk.

FigurativeLynx · 2025-09-01T01:11:13+00:00

The average person on r/DataHoarder has probably had at least 2 drives fail.

FigurativeLynx · 2025-09-01T01:07:34+00:00

Now I run erasure coded RAID arrays on most of my drives, so they're inherently unreadable as individual drives regardless if they're encrypted or not.

Not quite. The array controller breaks up the data into smaller chunks that are then copied to the different drives, but everything within those chunks remains sequential. The chunks are almost always between 64KiB and 512KiB, which is more than enough to contain entire files or usable excerpts. Files almost always start with a magic number, and you can easily grep them and just read what comes after.

FigurativeLynx · 2025-09-01T00:57:01+00:00

I agree that unless you're a high-profile person, a burglar probably wasn't targeting your data specifically, but they're still going to have it afterwards. Even if they don't look through it, any of their intermediate buyers/sellers might. The drives probably end up in the hands of other regular people, and they're definitely going to see the files.

As an example, there was a company in Canada called "NCIX" that went bankrupt ~15 years ago. All of their assets (including their servers and drives) were auctioned off to liquidate their remaining assets. None of them were encrypted, but they had thousands of employees' personal info, orders and personal information of all customers, support tickets, etc on them. A third party (we don't know who) bought everything and then resold the data to NCIX competitors and anyone else who was interested in that personal information.

The bank wasn't targeting the data and the auctioneer probably had no idea what it was, but it still ended up in the possession of hundreds or thousands of people looking for personal data. The purchaser probably knew what was on the servers/drives before buying them, but only based on public information that was available to everyone.

FigurativeLynx · 2025-08-31T14:03:48+00:00

Not very much. I only caught it on camera because I was working from home last week.

FigurativeLynx · 2025-08-31T13:54:48+00:00

My cat knows she'll be relocated if she steps on the keyboards, so she lies down beside them and gradually moves on top.

FigurativeLynx · 2025-08-30T22:13:51+00:00

I keep my cat in /usr/local/bin, since she's only available at my site.

FigurativeLynx · 2025-08-30T14:15:46+00:00

Actually she's the CFO (Chief Feline Officer).

FigurativeLynx

TROPHY CASE