After almost half a century, I'm still doing it...
-
so long as you're mobile, any phone can become a mobile phone. lol
-
I started to DBAN (wipe) my internal drive once instead of an attached drive. That was the last time I ran DBAN on a machine with any drives of value plugged in.
-
I was scared to move the cloud for this reason. I was used to running to the server room and the KVM if things went south. If that was frozen, usually unplugging the server physically from the switch would get it calm down.
Now Amazon supports a direct console interface like KVM and you can virtually unplug virtual servers from their virtual servers too.
-
Like 3 weeks ago on my (testing) server I accidentally DD'd a Linux ISO to the first drive in my storage array (I had some kind of jank manual "LVM" bullshit I set up with odd mountpoints to act as a NAS, do not recommend), no Timeshift, no Btrfs snapshot. It gave me the kick in the pants I needed to stop trying to use a macbook air with 6 external hard drives as a server though. Also gave me the kick in the pants I needed to stop using volatile naming conventions in my fstab.
-
Not SysAdmin but about a year into my first software engineer job I was working on the live DB in SQL without using BEGIN TRAN ROLLBACK TRAN.
Suffice to say I broke the whole system my making an UPDATE without a WHERE clause. Luckily we have regular backups but it was a lot of debugging with the boss before I realised it was me.
-
not RAID10 I hope...
-
Check out JetKVM
-
This.
Do it. This saved my life on more than one occasion.
You'll think “nah, it'll be fine” and then at 11pm when your brain's fried on vending machine coffee you'll be glad that you did it.. 3 times over...
-
Lol I've locked myself out of so many random cloud and remote instances like this that now I always make a sleep chain or a kill timer with tmux/screen.
Usually like:
./risky_dumb_script.sh ; sleep 30 ; ./undo.sh
Or
./risky_dumb.script.sh
Which starts with a 30 second sleep, and:
(tmux) sleep 300 ; kill PID
-
Until you block ICMP one day and then wonder why the server keeps rebooting...
(Been there. Done it)
-
Without repeating my other comment. This approach saved my life many times
-
Harsh (to yourself), but fair
-
It's VMs within VMs within VMs.
-
Use cockpit by Red Hat. It gives you a GUI to make networking changes*, and will check if the connection still works before making the change. If the connection doesn't work (like the ip addresses changed), it will undo the change and then warn you. You can then either force the change through or leave it be.
*via NetworkManager only.
-
Nice! I currently have a PiKVM but haven't been able to get it working with my NVR. Maybe this would work better.
-
I still prefer net-tools and use ifconfig eth0 up
That ip mess I'd rather do without, and those funky UU device/interface names I wish them out of my system -
That's probably because of netplan, right? You should be able to get the same results with just
netplan try. -
Netplan is an abstraction layer, so it can go over systemd-networkd, NetworkManager, or ip. I suppose it's better though, because it can be used with multiple backends.
-
Right, but the entirety of Cockpit is not necessarily required.
-
You don't need to install cockpit om the server being configured, you can use it as a gui to connect from other machines via the flatpak, over ssh.
