![](https://sh.itjust.works/pictrs/image/66c775fb-0c4f-4039-9461-4e19ec56efb8.webp)
![](https://programming.dev/pictrs/image/170721ad-9010-470f-a4a4-ead95f51f13b.png)
I got my first job with AIX in the early 2000’s after the previous admin did a reinstall of the OS vs an upgrade on prod, with unverified backups. It was a resume generating event.
They lost over 3 months of data and barely survived it.
I got my first job with AIX in the early 2000’s after the previous admin did a reinstall of the OS vs an upgrade on prod, with unverified backups. It was a resume generating event.
They lost over 3 months of data and barely survived it.
Especially if its a system that you have told management needs to be replaced but they aren’t interested in spending the money…
Not only that, but it’s no longer your problem when its in the cloud. You can blame the cloud for everything!
Lmao at RAM chips and CPU cola
The attack vectors I’m thinking of just come from the inherent complexity and centralization. I’m just considering the amount of damage that can be done with a compromised DA account for example vs a non directory environment.
It’s complicated. Done right it can be more secure, not done right it’s less secure.
I also only get brought in for problems for the last however many years, so I’m probaby a bit biased at this point haha.
I have had to tell companies they are going to have to rebuild thier AD from scratch because they didn’t know what thier DSRM password was (usually after a ransomware attack). These are the sort of hassles I think about vs non AD.
You could look at freeIPA or something similar to stay on Linux.
I’m an AD specialist, starting when it came out with server 2000, and can tell you it’s a waste of time for a home network unless you are doing this just because you want to learn it.
It will definitly not make your life any easier, and will increase attack vectors, especially if you don’t know how to secure and protect it.
You mean the late 1900’s
It’s decided by server. Most require it to cut down on spamming and trolls
When initializing a new array, it’s a (usually optional) process of zeroing out the newly added disks. Sometimes it’s required as part of calculating parity across the array (redundancy data).
Hopefully all the different clients will soon support good blocking. With connect for android I can block instances and keywords, but I most just continually block on a community basis what I don’t want to see from All. I’m sure there are hundreds in there. This keeps it quite relevant for me but I’m still in the flow of seeing new subs. I do subscribe to all the ones I really like.
So it’s a curation process, but a more active one vs trying to hunt subs down like I used to do with Reddit.
Probably the delusion that any windows admin can manage it if it has a graphical UI.
I’ve run into this several times
I’ve also done the same, it’s been great.
The usb OS drive for Unraid is to load the OS to RAM. Using the SSDs for an OS vs cache drives seems like a waste to me.
I’ve used a whole range of NAS platforms and devices over the years and nothing compares to Unraid for a solid all in one solution for a homelab.
It’s datacapped at 1TB before you get throttled, and the performance is always degrading, and you have to buy from an asshole.
I’d do it if I was desperate, but it’d essentially have to be the only option available.
Thanks for the post, super appreciate the posting of other communties. I think this is a great way to grow Lemmy and create discoverability for niche communities, I’ll keep that in mind myself on future opportunities.