I'd never use it on a production server due to the implications of data loss associated with such a command.
You could say this is the same as sysreq trigger b where everything is ignored and just reboot with ignorance.
I'd never use it on a production server due to the implications of data loss associated with such a command.
You could say this is the same as sysreq trigger b where everything is ignored and just reboot with ignorance.
Never had an issue.
Might look for a replacement should an issue arise.
Been driving Linux since sarge.
Never had an issue. Might look for a replacement should an issue arise. Been driving Linux since sarge.
You do you choom
Function is what I want.
Not sure I could get with the huge string of arguments, That needs to be shortened to follow the ls style of stacking letters behind minimal "-"
Does look good but I prefer function to form.
Interesting though
True but when people speak of rust being safe they actually mean the way it deals with memory and that it is harder to arbitrability view the mem space it uses unlike C and it's children.
Pretty soon being version 10/11+
People need to start being realistic.
It's gonna be a loong time before you fave game will run in native wayland.
Why does ls need a replacement?
What does this do that ls cannot?
Edit: cheers for the downvote for valid questions!! Guess the reddit mindset never leaves some.
Just stop