Fixed time reporting incorrectly in hostat

[mjwaxios]

On my builds of hostat the date would show as 1888, this is due to the way the endianness happens for ints. Corrected by shifting each byte into a u_long

[larsbrinkhoff]

@bictorv, I'm checking all ITS submodules before doing an all around refresh. Is this pull request something that would be good to include?

[bictorv]

Thanks for the reminders, I just pushed an update to master (simplified the code a tiny bit, and removed the commented-out code). Please check that it works correctly on big-endians, since I only have little-endian machines.

The second commit (adding #! to .py files) should be a separate PR (one issue per PR, please), and should only be done for "programs", i.e. those who check if __name__ == "__main__".