shadshack

joined 1 year ago
[–] shadshack@sh.itjust.works 4 points 2 months ago

Yeah I'm with you. Just say ACAB. No sense in obscuring it further than the acronym already does.

[–] shadshack@sh.itjust.works 6 points 4 months ago

This will be down voted, but I also tried a bunch of launchers and never found one I liked better than Nova. I ended up installing TrackerControl and Nova has its internet connection fully disabled. It doesn't need Internet for any features I use, so I felt like this was a good compromise, personally. I ended up starting to block trackers in all my apps now because of it, so I see it as a net win.

[–] shadshack@sh.itjust.works 14 points 5 months ago

Tracker Control on Android works well for system-wide tracker and ad blocking, and you can configure custom blocking rules per-app. Works without root by using a VPN profile (but no data leaves your device via the VPN, it just routes the traffic through this app).

[–] shadshack@sh.itjust.works 2 points 8 months ago

I think they don't take your phone, just scan it. I don't know how it works with this, but I have a trial for my state's digital ID app (the app works but isn't fully implemented as a complete replacement for physical IDs yet), and it has two modes I can put it in which generates a QR code on the screen with my data. One mode for police to scan at traffic stops which has my driver's license info, and one just called "age verification" which can be presented when buying alcohol which just verifies that I'm over 21. I like the privacy of the second mode, since there's no reason a liquor store needs to be able to see my home address.

[–] shadshack@sh.itjust.works 1 points 1 year ago (1 children)

How hard is replication across servers with just debian and qemu? I'm honestly not super great on linux knowledge. I'm a Windows sysadmin by trade, with maybe 10-20% linux. I run a few Ubuntu server VMs at home and some RHEL at work. So I'm looking for something as easy to set up and well-documented and supported as possible. Proxmox just seemed like the "industry standard" for selfhosting, but I was also looking at Unraid (which is supposedly better at storage and less good at virtualization) or even ESXI, but I didn't want to get into the VMWare payment bubble if I needed anything more than a simple host.

[–] shadshack@sh.itjust.works 2 points 1 year ago

Thanks, I wasn't sure about the data being taken care of first or last. First makes a lot more sense though. And prepping as many services into VMs ahead of time definitely sounds like it'll be the best way to reduce downtime, even if I then end up moving it into a different container again later on.

[–] shadshack@sh.itjust.works 2 points 1 year ago (2 children)

I hadn't seen that. Thanks for the link! That's definitely gonna be helpful.

 

I'm thinking about making some changes to my home server to make it a little more robust and let me do some cool new things with it (like actually trust it for backing up data to with NextCloud, replicating VMs or data across sites, etc). I'm just looking for any advice people might have for this process to migrate hypervisors.

What I currently have:

  • Windows 10 Pro OS with Hyper-V
  • Running some applications on the host OS (Plex/PRTG/Sonarr/Radarr)
  • Running a few VMs for things I set up after I realized "I should be doing these in VMs..."
  • 4 HDDs for data, each just mounted individually. 2 for TV, 1 for Movies, 1 for Backups

What I'd like to have:

  • Better OS for running the hypervisor (Proxmox is what I'm reading may be best, but I'm open to suggestions)
  • Nothing running on the host OS other than a hypervisor
  • All my services running virtualized, be that via Docker in a LXC or a guest OS.
  • My Drives all in a RAID 5. Planning to add more drives at some point as well.

My thoughts on the process are that the "easiest" way may be:

  1. Just throw a new OS drive in to install Proxmox on
  2. Export my VMs from Hyper-V and import them into Proxmox
  3. Set up the services I had running on the host OS previously in their own VMs/containers
  4. Make a new RAID either: a. with new disks or b. by combining data from my existing disks so I can get a free few disks to start the RAID with, then moving data into the RAID and clearing out more disks to then add to the RAID, rinse and repeat until done (that's a lot of data moving I'd like to avoid...)

I wasn't sure if it would be a smarter idea to do something more like this though (assuming this is all possible, I'm not even sure that it all is). If this is possible, it might reduce my downtime and make it so I can tackle this in bits at a time instead of having an outage the entire time and feeling like I need to rush to get it all done:

  1. New OS drive for Proxmox
  2. Use Proxmox to boot my Windows 10 drive (this I'm not sure about) so that everything continues as it's currently set up.
  3. Slowly migrate my services out of the Windows 10-hosted VMs and host-installed services
  4. I probably still have to deal with the RAID the way I mentioned above

Is there any other method I'm just totally not thinking of? Any tips/tricks for migrating those Hyper-V VMs? That part seems straightforward enough, but looking for any gotchas.

The reason I haven't done anything yet is because I only have so much time in the day, and I'm not trying to dedicate an entire weekend to this migration all at once. If I could split up the tasks it'd make it easier to do, obviously there are some parts that would be time-consuming.

Thanks in advance!

[–] shadshack@sh.itjust.works 3 points 1 year ago

So I'll just throw out my personal anecdote, as a Model 3 owner. Every single person who's ever gotten into my car for the first time cannot find the electronic button that opens the door, to the point that I got little vinyl decals with a door open symbol on them to indicate that button opens the door. Usually what happens for first-time passengers is one of two things:

  1. Someone can't find the button to open the door and immediately grabs the mechanical manual release and opens the door just fine (as long as they're in the passenger seat, as the rear seats do not have one. I agree that is dumb.)
  2. Someone finds the button and presses it, then the window rolls down slightly (about half an inch) and the door unlatches and partially opens. The person then thinks they just rolled down the window and doesn't just push the now-opened door, so the latch re-engages after a moment. I then tell them "push the button and then open the door" and then it's fine.

I agree that the way to open the door, even from the outside, is not intuitive when compared to what most people are accustomed to. Any time someone gets in for the first time I have to explain "press the big part with your thumb and then grab the handle". But it takes no more than half a second to figure out if you're the least bit observant. Hell, when I first got the car I drove my friend around for a few weeks before realizing the beeping when the passenger's door opened was because he used the manual mechanical door release instead of the button every time. He literally found the manual release more easily than the intended button for opening the door, and just thought that was the right way to open it until I told him otherwise.