I'm on a pretty old version of mbin (I have some modifications I made for federation issues back when it was kbin). I need to spend a weekend to pilot an upgrade and make sure I can run it safely live.
But even then it's better in some ways already and I never feel like I'm missing something from lemmy. But I think just calling the whole thing lemmy puts off people that are seeing things through a political lens.
Pretty sure that's only true about Lemmy. There are other threadiverse apps. The mistake is people calling the threadiverse lemmy.
These days with UEFI it's much less likely to break things. Worse case though you just boot from a LIVE USB boot, chroot in and rerun grub/your bootloader installer. Often even if windows puts its own bootloader first, you can choose your bootloader from the bios boot menu and just rerun the bootloader installer.
It used to be a lot worse.
I said elsewhere, I hope this is just some way to track changes over time per user.
But they need to take an anonymous hash of some non changing data or create an install id that is used for this and nothing else (e.g it identifies a unique user but not the person or hardware behind the user).
Too much identifying info is just pushed around like we shouldn't care, it's become a real problem.
The way I read it, the developer wanted opt-out but it's likely it will be opt-in. I'm find with opt-in and vehemently against opt-out for telemetry.
I would prefer the information was statistical only. Rather than hostname (making the assumption they only want hostname to be able to somehow separate the data to follow changes over time), a much better idea would be some kind of hash based on information unlikely to change, but enough information that it would be unlikely possible to brute-force the original data out of the hash. So all they know is, this data came from the same machine, but cannot ID the machine. Maybe some kind of unique but otherwise untrackable unique ID is created at install time and ONLY used for this purpose and no other.
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?
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.
This one threw me off. I'd muted discord by mistake. Weirdly voice still works. I spent ages checking and double checking settings to see why I wasn't getting notification sounds and the ptt sound. Dismissing any mute possibility because voice was working.
When I found it was this....