Webshell and Fixdisk

As an ex-trainer, if I wrote or said something that any of the target audience either didn't understand or misunderstood I'd backup and try again*, because blaming the audience for your failure is a great way to empty the auditorium.
I'm sure BH knew what he meant and prpr claims he got the message, but many others obviously didn't.
You aren't a perfect communicator BH (being polite here), so get off your high horse and accept that you are sometimes wrong and right at the same time.

(* In the intro for my sessions (with usually 10-20 participants) I always said "If you don't understand something - put your hand up immediately. If you didn't get it then you aren't the only one." And every time that happened I'd see a few other faces 'saying' "Me too". Like this thread.)
 
I know you're quite a stupid, trolling type of person, but it was: "Launch fixdisk automatically at boot if a flag is detected."
How do you think the flag gets set? By somebody setting it, that's how.
 
I know you're quite a stupid, trolling type of person, but it was: "Launch fixdisk automatically at boot if a flag is detected."
How do you think the flag gets set? By somebody setting it, that's how.
You've got no idea of how many fairly specialised steps you just took in this exchange.

Something which is wholly frowned upon by the likes of you when one of the "stupid ones" fails the "explain step by step" test.
 
In my programming days the system set flags. Operators made inputs and settings.
In my programming days the hardware could, and would, set flags. The programmer could force flags to be set. Operators controlled the system, allegedly. Users cocked things up.
In the context of this argument, if fixdisk currently only runs when you tell it to - then BH’s idea that IF you set a flag fixdisk runs automatically on next reboot makes sense to me. (Like getting Windows to do a disk check or defrag on next boot? You can carry on regardless in the meantime.) Whether it is a good idea is another matter.
 
Anyhow, there's an argument that making WebShell a mandatory package sets up an extra networking service that might cause debugging issues, even if I can't actually recall that having occurred.
 
Back
Top