sutton050

Most of us are well aware of how much heat electronic equipment puts out, what can be less intuitive and harder to balance is the problem of heat from hard drives. Good organised machine operation, with clearly defined device usages, easy control of units across machines, sites or different customers is the key, therefore enter stage left a nice fat label to hold all the details of the unit. Except, this label acts as a heat blocker, reducing the surface area of the metallic or foil labelled drive as delivered, reducing the area across which the heat from the unit can dissipate, and even causing uneven heating, or heat wearing over time. The net result... For my project, a high mechanical drive mortality rate, which I simply could not explain, nor model or explain in the man lab. Only a trip to see how these machines were being employed sufficed to show the problem, label after label applied and reapplied, a drive on within a machine was untouchable it got so hot.  My solution, put...

Today I've come to a totally virgin installation upon a server, this was for a work group I've got to head up whom are looking at pushing MySQL with Python.  And things initially went wrong... I stipulated they had to use Python3 and thought everything else would be fine for them to install with Pip3, so... sudo apt-get update sudo apt-get upgrade sudo apt-get install python3 sudo apt-get install python3-pip sudo apt-get install mysql-server Everything looked fine, their user could install packages through Pip3 and they had Flask and a few other things and were flying.  I used the mysql client on the command like to test I could add a few items and also ran... sudo mysql_secure_installation To do the basic hardening of the database, so everything was fine... Right?....RIGHT?!?! No, not exactly....  "I can't get mysql.connector" .... Came the cry. And they were right, it reported a myriad of build issues and could not install.  I took a look... NIGHTMARE! It appear...