Disclaimer

It’s my personal blog

I’m working for Oracle. However this is my personal blog. I write it in my personal time. It runs on my personal infrastructure privately paid and not on Oracle infrastructure. It was this way since the beginning of this blog, so it didn’t run on Sun infrastructure as well.

I write everything here out of personal interest, to further my knowledge and my love to write things and explain things. Nothing here is the opinion of my employer. Nothing here is endorsed by my employer. Not even that I’m blogging.

The rules of this blogs are the same since the beginning of c0t0d0s0.org

Technology

This blog is currently created by Jekyll. It’s a fully static webpage. As i mentioned, there is no functionality to comment. There are no trackbacks. I’m only using the standard logging of Strato, as the static pages are hosted there. This doesn’t contain IP addresses. At least not visible to me. Currently i’m putting my blog entries into github, and the process generated the webpage and syncs them into the webspace. Works reasonably well.

It works for me

When I’m talking about ideas or solutions in this blog, consider it as a report about my own experiences. You are responsible to check everything I write by sufficient testing.

The dirty secret

Just because I got this question in the past: Despite being a blog mostly about Solaris, it is not running on SPARC or Solaris. At the moment it’s hosted on a webspace provider as the blog is now simply a collection of static pages.

The reason for this is simple: As it’s a personal spare time project it was easiest just to drop a plain vanilla Debian on a server back in 2004 and I kept it that way. Furthermore, as this is a personal blog I wanted to be sure that i don’t use any software licensed by a former or current employer. Something that I just could use based on my employment status. Of course it’s not the same Debian of 2004, currently it’s Debian 10.

EMails

If an eMail is sent from any domain pointing to this blog it’s always signed via DKIM. The domains have SPF records pointing to the single MX in use. If one of the checks fails you can safely discard it.