Add .sh extension for dl360gen9-silent (Plus Ilo queries)

[draknyte1]

It's a small change, but one that justifies me making a PR otherwise.

@kendallgoto I was going to try raise an issue for you about any further notes/progress you'd made with SSH shell sessions.
There's a lot of toolbox documentation to read, so had hoped maybe you had some thoughts still. I have a rack of G8/G9 hardware and am giving up on phsical fan mods, so I've peered my head in here again after a year or two.
(Stubbing the fans is viable if anyone ever wants to know the pinouts)

Other queries I have, excuse my high level developer ignorance...
Could we just modify the curves directly in the firmware? (Rebake a curve that's 20% what's now defined?)
When patching 2.78+, what's the main blocker from adding the fan code from 2.77? (Copy paste from blob A -> B, adust offsets to match?)

[kendallgoto]

Could we just modify the curves directly in the firmware? (Rebake a curve that's 20% what's now defined?)

Yes, this was one of the approaches I was considering for patching 2.78+, but I haven't personally had time to look deeper into it.

When patching 2.78+, what's the main blocker from adding the fan code from 2.77? (Copy paste from blob A -> B, adust offsets to match?)

This process is reasonably accurate - however, it is a substantial undertaking compared to the original one to bring the command to v2.77, and not one that I have the tooling or time to develop the tooling to accomplish. Plus, without very flexible tooling, it's usually (in my experience) a pain to maintain these kinds of patches thru new upstream FW versions, etc.

Further - it is worth considering what the end goal is. The fan command was easy to expose and provided really powerful tooling. However, at the end of the day, most people just want to adjust the curves (or turn off some "features") in order to reduce their system's noise. Porting the entire fan command is not the only solution to this. Having a tool to build custom FW to-order with adjusted curves, sensor offsets, PCI detection, etc., would be another pathway. Creating a new system to adjust these properties in realtime via the web GUI, etc., is another.

Thanks for the contribution & feel free to dive into the work to contribute on the fixed curves - I'm setting up equipment to patch iLO3/4/5, but my free time to contribute is limited right now.

[kendallgoto]

I opened issues on the repo as well again, not sure why that was turned off. Sorry for the trouble.