Language Selection

English French German Italian Portuguese Spanish

Interview with Michael Meeks of

Filed under

On the Novell website, there is a page dedicated to the company's Distinguished Engineers. One of these is Michael Meeks, a Cambridge graduate who began his Linux career at GNOME desktop start-up Ximian, and now works as part of Novell's team. Daniel James met him just prior to the announcement of the Novell/Microsoft agreement, and opened the interview with his favourite opening question to any free software hacker...

DJ: What was your first computer?

MM: I was encouraged to program by my mother, because she was a Head of Maths, so I had a BBC Micro and was doing simple BASIC programming. Then came the era of type-in games, so you could learn programming syntax. As my typing was not very quick, I had time to consider the constructs. Eventually I was writing assembler, and this led to x86; but all this was with proprietary software, really. Just on top of Windows, or DOS - a little bit of the Novell technologies crept in there, but only briefly. I left school and went to work doing PASCAL programming, on VT420's, VMS on Alpha machines, cross-compiling to 68000 embedded systems, real-time, the lot. Lot's of good stuff there, and quite interesting in many ways.

During my gap year I became a Christian, and at that point I realised my computer was riddled with non-free software, most of it stolen. So we had a big fight about this, me and God, and the voice of conscience was quite clear that this was not what should go on. So eventually, I ditched it to run Linux instead, which at the time was not good news. The hardware support, and anything graphical or visual, was just hopeless.

DJ: So it was a sort of 'forty days in the wilderness'?

Full Story.

More in Tux Machines

Security Leftovers

  • Friday's security updates
  • Researchers poke hole in custom crypto built for Amazon Web Services
    Underscoring just how hard it is to design secure cryptographic software, academic researchers recently uncovered a potentially serious weakness in an early version of the code library protecting Amazon Web Services. Ironically, s2n, as Amazon's transport layer security implementation is called, was intended to be a simpler, more secure way to encrypt and authenticate Web sessions. Where the OpenSSL library requires more than 70,000 lines of code to execute the highly complex TLS standard, s2n—short for signal to noise—has just 6,000 lines. Amazon hailed the brevity as a key security feature when unveiling s2n in June. What's more, Amazon said the new code had already passed three external security evaluations and penetration tests.
  • Social engineering: hacker tricks that make recipients click
    Social engineering is one of the most powerful tools in the hacker's arsenal and it generally plays a part in most of the major security breaches we hear about today. However, there is a common misconception around the role social engineering plays in attacks.
  • Judge Gives Preliminary Approval to $8 Million Settlement Over Sony Hack
    Sony agreed to reimburse employees up to $10,000 apiece for identity-theft losses
  • Cyber Monday: it's the most wonderful time of year for cyber-attackers
    Malicious attacks on shoppers increased 40% on Cyber Monday in 2013 and 2014, according to, an anti-malware and spyware company, compared to the average number of attacks on days during the month prior. Other cybersecurity software providers have identified the December holiday shopping season as the most dangerous time of year to make online purchases. “The attackers know that there are more people online, so there will be more attacks,” said Christopher Budd, Trend Micro’s global threat communications manager. “Cyber Monday is not a one-day thing, it’s the beginning of a sustained focus on attacks that go after people in the holiday shopping season.”

Openwashing (Fake FOSS)

Android Leftovers

Slackware Live Edition – Beta 2

  • Slackware Live Edition – Beta 2
    Thanks for all the valuable feedback on the first public beta of my Slackware Live Edition. It allowed me to fix quite a few bugs in the Live scripts (thanks again!), add new functionality (requested by you or from my own TODO) and I took the opportunity to fix the packages in my Plasma 5 repository so that its Live Edition should actually work now.
  • Updated multilib packages for -current
  • (Hopefully) final recompilations for KDE 5_15.11
    There was still some work to do about my Plasma 5 package repository. The recent updates in slackware-current broke several packages that were still linking to older (and no longer present) libraries which were part of the icu4c and udev packages.