I think it had its uses in the past, specifically if it had the memory backup to prevent full array rebuilds and cached data loss on power failure.
Also at the height of raid controller use (I would say 90s and 2000s) there probably was some compute savings by shifting the work to a dedicated controller.
In modern day, completely agree.
I'm sure I've seen paid software that will detect and read data from several popular hardware controllers. Maybe there's something free that can do the same.
For the future, I'd say that with modern copy on write filesystems, so long as you don't mind the long rebuild on power failures, software raid is fine for most people.
I found this, which seems to be someone trying to do something similar with a drive array built with an Intel raid controller
Note, they are using drive images, you should be too.
The OP made clear it was a controller failure or entire system (I read hardware here) failure. Which does complicate things somewhat.
I would very much agree here. I've (admittedly mostly server side) been using linux for around 30 years now. But I'm still dual booting on my desktop. There's just a few things that will still only work in Linux, and also if I break things I can go to windows if I need to do something "right now"
Dual boot gives you the option of, if you have the time trying to make something work in linux. But, if you don't have the time, just boot to windows and do it.
How I do things, is I have drives that are shared between both OS (I use btrfs since there is a windows driver and, so far (around 3 years) I've had no corruption problems. But you can share ntfs too and a boot drive for both. But, it's not a requirement.
Also yes, it is quite easy to break a linux install. It's not really because Linux is bad. It's just because you have so much choice in which drivers to use, which desktop environment (and even the components that make it up) that it's easy to accidentally select some combination that doesn't work and you end up with only a console to fix things from.
I like that the OP is choosing Mint. I've not used Mint, but from all I've seen it looks a real good option for someone starting into Linux from no experience.
/mnt/shared/Development or E:\Development depending on which operating system is running.
Not in home mainly because I use the same directory in windows and Linux.
Yeah, but that's just because "nobody wants to work"
I recently made a new linux install (to replace my constantly breaking, likely due to my own doing Manjaro install). I went with Cinnamon initially, but in order to try out Wayland, I moved to KDE plasma.
I'm on NVidia, with two different resolution screens. Which causes occasional problems. But overall it's fine.
Yeah, I'm quite sure it's a deliberate activity to dissuade against private email servers. Keep everyone's email "in the club". Once you've got this much working you need a whole suite of tools to deal with the HUGE amount of spam you need to filter. It can be a hell of a lot.
kbin/mbin does have some mastadonesque facilities. So it straddles the line between threadiverse and I dunno what we call the mastadon side.
IRC was "kinda" federated. You needed to convince a server already in the network to accept your server. But in the early days requirements were quite low.
BBS was not really federated (except Fidonet I guess).
Usenet, I guess it kinda was. But only ISPs were really running NNTP servers. Only they and unis really had the resources to too.
You CAN do the full list of things to get accepted there. But you only need to fail a SINGLE test to get sent to junk mail jail.
To not be put to junk you need all of the following (oh and this can and will change one day and you'll go straight to junk)
Not sure if I missed any there. It's been a while since I set all this crap up.
Yeah, my only concern here was if it was opt-out. That'd be bad.
Now I completely understand the developer on this. This is useful info to have to help decide future changes/features and general direction, but balancing the right to privacy means this kind of data provision should ALWAYS be opt-in. Microsoft, you hearing me here?