JP@daedalus@eigenmagic.net
It occurs to me that commands with a '--dry-run' option have the safety interlock backwards. The dangerous or destructive operation should default to a dry run unless you specifically crank the "yes I'm sure" lever.
JP@daedalus@eigenmagic.net
Steffo :steffo:@SteffoSpieler@fellies.social
@daedalus@eigenmagic.net Pull the lever, Kronk!!
crontab -r
Wrong lever!!
Glen T, heated, not stirred@glent@aus.social
@daedalus@eigenmagic.net BIND's "authoritative" command for configuring a DNS server is essentially a "Yes, really" check.
I think I'll disagree though. I've seen too many people cut-and-paste "rm -f" to think it would work. Even gmake's $(RM) is "rm -f".
The lack of garnish parameters was part of the joy of moving from MVS and VMS to Unix. I mean
//SYSPRINT DD SYSOUT=*
what value does that bring? Send printed output to the usual destination. Why does that need to be said? (This was a 'interlock' when written, 132x66 fanfold paper was not cheap).
Edit: related, commands which print status output, and output on success. Just don't. That's how IBM ended up with SYSPRINT needing to be specified for every batch job command. Unix saying "Let's solve that issue by not creating that issue was the correct answer".
Foone🏳️⚧️
@foone@digipres.club
@daedalus@eigenmagic.net I used to work somewhere which had a tool with a --my-resume-is-up-to-date flag for when you REALLY were sure you wanted to delete something
tw000@tw000@infosec.exchange
@daedalus@eigenmagic.net On some scripts I've written, I've included a default test=true parameter. You get all the output but no writes until you explicitly set test=false.
Scott Francis@darkuncle@infosec.exchange
@glent@aus.social @daedalus@eigenmagic.net silent on success; this is the way
JP@daedalus@eigenmagic.net
@foone@digipres.club Every day is a good day to test your backup recovery process.
Foone🏳️⚧️@foone@digipres.club
@daedalus@eigenmagic.net this wasn't even backup-fixable, it was an SSD-erase that had a risk of significant degrading the drives if overused. Like, using it in the wrong way could destroy a couple thousand dollars of hardware