All legit. At the end of the day, both the commands that go through systemd and the direct cat something >/proc/… or cat something >/sys/… are all doing the same thing - telling the kernel to do some procedure.
There’s some settings stuff in /proc and /sys that you don’t want to tweak without knowing the effects, as they could break things in hard to fix ways, but for stuff like beeping or changing sleep states, the worst you’ll do is lock up your computer and need to reboot. And even that is rare unless the hardware really doesn’t like a particular sleep state.
You can echo ‘mem’ > /sys/power/state as root to suspend. Or echo sleep into the file for hibernate.
Wait, holup. Is this legit or one of those “break your PC” joke things?
All legit. At the end of the day, both the commands that go through systemd and the direct cat something >/proc/… or cat something >/sys/… are all doing the same thing - telling the kernel to do some procedure.
There’s some settings stuff in /proc and /sys that you don’t want to tweak without knowing the effects, as they could break things in hard to fix ways, but for stuff like beeping or changing sleep states, the worst you’ll do is lock up your computer and need to reboot. And even that is rare unless the hardware really doesn’t like a particular sleep state.