Comments for cormander's blog http://cormander.com Thu, 26 Jan 2012 07:33:51 +0000 hourly 1 http://wordpress.org/?v=3.3.1 Comment on nagios snmp memory and swap plugin by You can find my stuff on GitHub | cormander's blog http://cormander.com/2011/11/nagios-snmp-memory-and-swap-plugin/#comment-268 You can find my stuff on GitHub | cormander's blog Thu, 26 Jan 2012 07:33:51 +0000 http://cormander.com/?p=118#comment-268 [...] stuff there. For example, I recently updated my rogue-beret-tools repository with my various snmp nagios plugins (which, by the way, you can also find on my account at Nagios Exchange). I’ve started [...] [...] stuff there. For example, I recently updated my rogue-beret-tools repository with my various snmp nagios plugins (which, by the way, you can also find on my account at Nagios Exchange). I’ve started [...]

]]> Comment on Monitor time drift with nagios and snmp by You can find my stuff on GitHub | cormander's blog http://cormander.com/2011/12/monitor-time-drift-with-nagios-and-snmp/#comment-252 You can find my stuff on GitHub | cormander's blog Thu, 19 Jan 2012 22:27:31 +0000 http://cormander.com/?p=149#comment-252 [...] more stuff there. For example, I recently updated my rogue-beret-tools repository with my various snmp nagios plugins (which, by the way, you can also find on my account at Nagios Exchange). I’ve [...] [...] more stuff there. For example, I recently updated my rogue-beret-tools repository with my various snmp nagios plugins (which, by the way, you can also find on my account at Nagios Exchange). I’ve [...]

]]> Comment on nagios snmp check all disks plugin by You can find my stuff on GitHub | cormander's blog http://cormander.com/2012/01/nagios-snmp-check-all-disks-plugin/#comment-251 You can find my stuff on GitHub | cormander's blog Thu, 19 Jan 2012 22:16:03 +0000 http://cormander.com/?p=175#comment-251 [...] cormander's blog Skip to content HomeAbout Me ← nagios snmp check all disks plugin [...] [...] cormander's blog Skip to content HomeAbout Me ← nagios snmp check all disks plugin [...]

]]> Comment on What some (many?) people don’t understand about the GPL by How to hook into (hijack) linux kernel functions via LKM | cormander's blog http://cormander.com/2011/08/what-some-many-people-dont-understand-about-the-gpl/#comment-181 How to hook into (hijack) linux kernel functions via LKM | cormander's blog Sat, 24 Dec 2011 06:27:45 +0000 http://cormander.com/?p=99#comment-181 [...] a similar method to do its runtime patching of the linux kernel, but I should also mention that Ksplice violates the GPL by not releasing their updated source code. Shame on Oracle! I’ll eventually settle the score [...] [...] a similar method to do its runtime patching of the linux kernel, but I should also mention that Ksplice violates the GPL by not releasing their updated source code. Shame on Oracle! I’ll eventually settle the score [...]

]]> Comment on What some (many?) people don’t understand about the GPL by How I license code | cormander's blog http://cormander.com/2011/08/what-some-many-people-dont-understand-about-the-gpl/#comment-156 How I license code | cormander's blog Wed, 14 Dec 2011 05:34:57 +0000 http://cormander.com/?p=99#comment-156 [...] a previous post about the GPL, I reference a [...] [...] a previous post about the GPL, I reference a [...]

]]> Comment on tpe-lkm “lock” sysctl feature by tpe-lkm “hardcoded_path” feature | cormander's blog http://cormander.com/2011/11/tpe-lkm-lock-sysctl-feature/#comment-130 tpe-lkm “hardcoded_path” feature | cormander's blog Thu, 01 Dec 2011 08:14:32 +0000 http://cormander.com/?p=139#comment-130 [...] cormander's blog Skip to content HomeAbout Me ← tpe-lkm “lock” sysctl feature [...] [...] cormander's blog Skip to content HomeAbout Me ← tpe-lkm “lock” sysctl feature [...]

]]> Comment on Where did all my free time go? by My first book review starts today | cormander's blog http://cormander.com/2011/06/where-did-all-my-free-time-go/#comment-127 My first book review starts today | cormander's blog Wed, 30 Nov 2011 01:19:14 +0000 http://cormander.com/?p=46#comment-127 [...] let’s not forget how much time I wasted on playing StarCraft II since it came out. So glad I finally kicked that [...] [...] let’s not forget how much time I wasted on playing StarCraft II since it came out. So glad I finally kicked that [...]

]]> Comment on Recursive function causes DoS in tpe-lkm by tpe-lkm DoS condition fixed | cormander's blog http://cormander.com/2011/11/recursive-function-causes-dos-in-tpe-lkm/#comment-122 tpe-lkm DoS condition fixed | cormander's blog Mon, 28 Nov 2011 06:38:04 +0000 http://cormander.com/?p=125#comment-122 [...] cormander's blog Skip to content HomeAbout Me ← Recursive function causes DoS in tpe-lkm [...] [...] cormander's blog Skip to content HomeAbout Me ← Recursive function causes DoS in tpe-lkm [...]

]]> Comment on A nagios snmp plugin that obeys snmp.conf by nagios snmp memory and swap plugin | cormander's blog http://cormander.com/2011/11/a-nagios-snmp-plugin-that-obeys-snmp-conf/#comment-112 nagios snmp memory and swap plugin | cormander's blog Sat, 19 Nov 2011 06:26:19 +0000 http://cormander.com/?p=112#comment-112 [...] cormander's blog Skip to content HomeAbout Me ← A nagios snmp plugin that obeys snmp.conf [...] [...] cormander's blog Skip to content HomeAbout Me ← A nagios snmp plugin that obeys snmp.conf [...]

]]> Comment on What some (many?) people don’t understand about the GPL by Tim Post http://cormander.com/2011/08/what-some-many-people-dont-understand-about-the-gpl/#comment-79 Tim Post Wed, 31 Aug 2011 03:20:33 +0000 http://cormander.com/?p=99#comment-79 This [ksplice] is truly one of the darker corners of licensing debate. The bulk of it comes down to being able to reproduce the build for a GPL module that it packages and inserts into your kernel. If you can reproduce it, there's no violation. If you can't, then yes -- there is some cause for eyebrow raising. If I can't study and modify that update en situ, then I don't have the rights that the GPL guaranteed. I question the entire motivation of making ksplice proprietary to begin with. One thing to note about the kernel is that simply using the kernel interface (via header inclusion to get the magic numbers / etc) is considered normal use of the kernel. So, just including those bits doesn't cause you to inherit the license of the kernel. More often than not, those bits are already available in glibc, which is licensed under the LGPL. This [ksplice] is truly one of the darker corners of licensing debate. The bulk of it comes down to being able to reproduce the build for a GPL module that it packages and inserts into your kernel. If you can reproduce it, there’s no violation. If you can’t, then yes — there is some cause for eyebrow raising. If I can’t study and modify that update en situ, then I don’t have the rights that the GPL guaranteed. I question the entire motivation of making ksplice proprietary to begin with.

One thing to note about the kernel is that simply using the kernel interface (via header inclusion to get the magic numbers / etc) is considered normal use of the kernel. So, just including those bits doesn’t cause you to inherit the license of the kernel. More often than not, those bits are already available in glibc, which is licensed under the LGPL.

]]>