Mathieu Hezemans

Mathieu "Thieu" Hezemans (21 June 1915, in Eindhoven – 4 February 1985) was a Dutch racing driver and entrepreneur.[1]

Career

Mathieu Hezemans operated a vehicle trade in his hometown of Eindhoven and was one of the first Dutch importers of the Porsche brand. As a driver, he was active in the 1950s. Several times he raced at the 1000 km race on the Nordschleife of the Nürburgring race. In 1953 he was ranked overall fifteenth and in 1956 the 26th in the final ranking. In 1956 he drove together with Carel Godin de Beaufort at the 24 Hours of Le Mans, but fell out prematurely after a suspension failure.

Family

Mathieu Hezemans was the first racer from the Dutch Hezemans family. His son Antoine, known as Toine Hezemans, was a successful GT and sports car pilot in the 1970s becoming European Touring Car Champion in 1970 and 1973, winning the 1971 Targa Florio and, among other things winning twice the 1000 km at the Nürburgring race and once the 24-hour race of Daytona. His grandsons Mike and Loris Hezemans took the profession of a professional racer.

Sources

  • Christian Moity, Jean-Marc Teissèdre, Alain Bienvenu: 24 heures du Mans, 1923–1992. Éditions d’Art, Besançon 1992, ISBN 2-909413-06-3.
gollark: Oh, so you mean this `hdr` goes at the start and the `dofs` thing tells you where the bit appended to the end is?
gollark: Perhaps the headers should also store the location of the last header, in case of [DATA EXPUNGED].
gollark: There are some important considerations here: it should be able to deal with damaged/partial files, encryption would be nice to have (it would probably work to just run it through authenticated AES-whatever when writing), adding new files shouldn't require tons of seeking, and it might be necessary to store backups on FAT32 disks so maybe it needs to be able of using multiple files somehow.
gollark: Hmm, so, designoidal idea:- files have the following metadata: filename, last modified time, maybe permissions (I may not actually need this), size, checksum, flags (in case I need this later; probably just compression format?)- each version of a file in an archive has this metadata in front of it- when all the files in some set of data are archived, a header gets written to the end with all the file metadata plus positions- when backup is rerun, the system™ just checks the last modified time of everything and sees if its local copies are newer, and if so appends them to the end; when it is done a new header is added containing all the files- when a backup needs to be extracted, it just reads the end and decompresses stuff at the right offset
gollark: I don't know what you mean "dofs", data offsets?

References

This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.