Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)K
Posts
4
Comments
81
Joined
5 days ago

  • Another thing they may have in mind is ATX PSUs. The pinouts on those for the same physical plug vary not only by maker and model but sometimes even by year. So if you get an aftermarket ATX-to-SATA cable that fits just fine in the SATA plug on your ATX PSU, it may put 12v on the 5v and fry your drives or mobo when you plug it in even if it's from the same brand.

    Don't ask me why there is a voltmeter on my desk.

  • 💁🦋

  • Terrible headline. Should have just been "Rockchip has...".

    Am I showing my age if I say that Tomshardware used to be decent?

  • Personally I'm too paranoid about security and sus of Intel to be comfortable with vPro but you do you.

    That said, I'd go for 1, considering you already have that 6th gen on hand in case you need a spare.

    Otherwise 3 or 4 (whichever is available on secondary markets for a decent price) and hang on to that Pentium in case need arises. Doesn't sound like the extra power draw of an i7 is worth it for this build.

  • Up to 300 or so could be reasonable if the RAM and SSD are decent.

  • OK?

    I think 2013 gear and low-end hardware can still be useful in 2026. And that it can be win-win to give old gear a new home.

    But it wouldn't be honest selling stuff that can't physically handle what a reasonable user would expect from a PC to someone who is not capable to install an OS themselves and doesn't understand what the limitations are.

    Not too dissimilar to marketing CMR HDDs as "NAS drives", which I hope we all agree is a scam.

    And just so I don't get misread on that part, "HD" = 720p.

  • In that case I'd give it away for free. Or sell it without an OS to someone who knows what they're getting and leave them to figure it out.

  • OK, so let's cut it down and say we have 4 PCs for someone with a family and home server, with 4 DIMMs each.

    You are saying the first rule of PC building says that this house should have at least 16 unused DIMMs on the shelf. I'd say 2-4 is reasonable if they are all compatible.

    "Buy two extra of everything" is a good rule and scales for the individual. "Buy double of everything" is not.

  • Do you get a different result if you replace that :0 with your actual DISPLAY value?

    Also make sure you run that in a context that does have access to the x server (i guess keep your display manager running as you do this).

    Depending on your setup you should be running such commands as normal user instead of root.

  • In the offchance that shenanigans are afoot, some malware will fudge mtimes (but not always ctimes) to prevent detection.

    If you get files showing up as changed with -cmin but not modified with -mmin, that's a bright red one.

  • Can it play Youtube in HD without lagging?

    I guess that would be roughly my bar for what I'd feel OK with passing on to someone clueless.

  • I always heard the first rule as "stay grounded". Having 1TB of RAM on stock just in case sounds not grounded.

    A spare kit or two should be enough for most folks. With one or two spares of everything else so you can test suspicious parts separate from prod.

    A bit of redundancy and foresight is good but no need to be excessive about it.

  • I'm curious: What's motivating you to do that when the memmap param can do the same without patching?

  • While you can put your root filesystem on ZFS and many people do it, it is considered a little more advanced setup and it's more common to run ext4 on / and then zfs for mounted datasets on e.g. /var and /home.

    A catch with ZFS is that it does not have a compatible license with Linux, which prevents many distros from shipping compiled modules directly. So the most common way to ship it is by DKMS, which (automatically) compiles the ZFS module from source. This is done by installing the zfs-dkms package.

    The ZFS version obviously needs to be compatible with your kernel and sometimes it can take a while for ZFS to Linux. Arch does not coordinate releases so especially if you're not on the LTS kernel, you can run into situations where ZFS is no longer available after an upgrade. Furthermore, zfs-dkms is not in Arch repos but in AUR so you have to build even that from source for each upgrade of ZFS. Not recommended for beginners.

    That a partial or failed system upgrade can leave you in a place without ZFS modules is one reason why putting / on ZFS is not more common.

    In debian, you just apt-get install zfs-dkms.

    Alpine Linux maintainers decided to just ignore the license issue and ship a compiled zfs package including kernel modules.

  • Unless you took a backup I guess it's not relevant anymore but if it happens again you can narrow down files last changed around some timestamp like so: find /var -mmin +4 -mmin -5