No problem, just tab complete your way around the filesystem.
Infrastructure nerd, gamer, and Lemmy.ca maintainer
No problem, just tab complete your way around the filesystem.
That’s correct. You’re telling docker to bind to that specific network interface. The default is 0.0.0.0 which listens on all interfaces.
https://github.com/containrrr/watchtower is a bit cleaner than that
Bro, just docker-compose pull && docker-compose up -d
I’m appreciating how rapid the releases have been coming lately.
You could just swap the two disks and see if it follows the drive or the link.
If the drive, rma it. I don’t put a lot of faith in smart data.
Usually means a failing drive in my experience.
Look at workstation cards. Things like the T1000 for example.
Ntfs isn’t going to care or even be aware of the hypervisor FS, zfs or btrfs would both work fine.
Making sure you don’t have misaligned sectors, is pretty much the only major pitfall. Make sure you use paravirt storage and network drivers.
Edit: I just realized you’re asking for the opposite direction, but ultimately the same guidelines apply. It doesn’t matter what filesystems are on what, with the above caveats.
FYI setting my zigbee channel resolved all of my zigbee issues, all 3 networks run flawlessly in parallel for me: https://www.metageek.com/training/resources/zigbee-wifi-coexistence/
This, but I’d recommend zigbee over zwave. Zwave is kinda dead and not worth investing in, zigbee sensors and switches are much more available and cheaper. (I run both)
I do a similar setup to what you want, with inovelli switches. They’re nice but a bit pricy, there are cheaper options available.
Someone hasn’t learned to block themselves out a lunch hour.
Never attribute to malice that which is adequately explained by stupidity
Had a zfs array on an adaptec raid card. On reboot the partition table would get trashed and block the zfs pool from coming up, but running fdisk against the disk would recover it from the backup.
Had a script to run on reboot that just ran “fdisk -l” on every disk, then brought up the zfs pool. Worked great for years until I finally did a kernel upgrade that resolved it.
This is the only answer. Git history is forever.
I’d believe it. I’ve had hundreds of Linux servers that don’t have any desktop Gui at all deployed on them.
Linux desktop users make up an absolutely tiny fraction of Linux installs.
I haven’t actually setup vlans on mine yet so can’t help there.
All my sfps worked without messing with autoneg though.
Yes. I’ve always splurged on nice cards for my personal stuff. I think it’s more about the write behavior of Linux than anything else, since I’ve never had a card die in my camera.
I refuse to use a pi with SD at this point. Saving $50 isn’t worth my time to reinstall things.
Sar?