It looks to me like they were counting some windows variant as 'Other' for a time.
It looks to me like they were counting some windows variant as 'Other' for a time.
Holy shit… 1Tb drives too…
If only I had a use for them :/
Raid 0 on 3x500GB triples your failure rate (especially important on older drives, as I presume these are), and still won't get anywhere near an SSD in speed.
You could just mount the 3 drives separately and have storage that way, which means if one fails you've still got the data on the other two… it'd still suck but not as bad as losing everything.
If it was me I'd wait until I could afford the SSD… it'll be many times faster and newer.
Or actually do anything useful? No network, no filesystem… it's a hello world app isn't it…
If it's fun, it's not overkill!
You also have experience you can use in the workplace (even if it's mostly experience of what happens if you f**k things up).
So now you have to do that every time you install a flatpak.
Or just stick to a normal package manager, that does all that for you.
Used it once… it's as annoying as shit since you can't just run apps you have to type 'flatpack run org.mozilla.firefox' instead of just typing 'firefox' (and I had to google that because I just can't remember the sequence). Also for some reason it's slow… as you mentioned a 1 second delay before anything works. I can't see myself using it again.
The system is broken. Wipe it and start again. I could imagine a system with no configured root but root only is just a security nightmare and not worth using as a starting point.
I really hope that machine isn't exposed to the internet…
In theory a root application can drop capabilities when it starts up and remain root pid, but it's not that common… it's used for certain system apps that require root to increase security. It is not a replacement for unprivileged users.
I'm the same… I setup a VM but it was so much work just to setup a basic machine with ssh I gave up on it… I'm also no sure moving all the config out of /etc into a script is scaleable at all. I get that by copying the script from one machine to another you can duplicate configs… but we already have ansible for that.
What I've read looks good but it's going to need a track record of reliability before I'd trust it.
It's derived from the old shugart interfaces IIRC. But yes not IDE. I'm sure a converter is possible but USB makes more sense these days, or if you must an FDD controller card (assuming no motherboard support).
That's kind of used in apps everywhere… I can see why.
But not creating a symbolic link to 'firefox' when you install it, is a PITA. Apparently by design…
The only one I ever found in 2 years of pihole use was cdn.cookielaw.org… a good percentage of sites won't display with it blocked. Most other stuff is fine.
When I first installed pihole I went overboard with blocklists and broke nearly everything… don't do that :p
You know which site you're getting it from…check the SSL certificate and that's enough. If an official site got breached it'd be found out pretty quickly.
It's bad practice to stay in a root shell because it's easy to screw up and break something. That's why sudo exists… you only run something privileged if it absolutely has to.
If you want to experiment with UEFI you don't need systemd-boot either, just create an efi bootable kernel and direct boot it. reFind is still around I think too for graphical boot (although that's mainly used by macs… apple users like guis :p).
You can use a decimal number as well. It's rare to see that form of URL though.
2.1 is ancient.
A heck of a lot of old stuff has been deprecated in the intervening years… it's possible your drivers don't support emulating that old… although I'd found most can still do 1.x (because it was relatively simple, fixed pipeline).
TBH though if you're writing anything new I'd start with vulkan, as it's really the next gen and nowadays supported everywhere.
Use ddrescue… but if there are lots of errors what you get back might not be that useful. Once you have a full image mount it loopback (losetup -Pf) and get the files that way.
Don't try to mount the ssd directly as you can make things worse if the OS tries to write to it.
Just before shutdown you're at the terminal so something like this https://github.com/stolk/imcat on the image at the end of shutdown script might work.