Family - Ties of Blood
Tonight I enjoyed the rare opportunity to watch a Bollywood movie in Berlin,
almost at the same time the movie is released in India. We usually only get a
hand full of Indian movies every year, to very small cinemas, and about one to
two years after they ran in India.
I personally enjoyed the film quite a lot, even though the critics in India
seem to be disappointed by it. But well, what do I care about those critics ;)
One advantage of watching Bollywood movies in Germany is that you don't need a
ticket reservation, since very few people are interested in those movies
anyway. Second, you can actually enjoy a film without some 20 to 30something
minutes of advertisements and anti-screener propaganda.
First GPLv3 draft
As almost every reader of this journal will know, the first GPLv3 draft has been published, and
everyone is invited to comment on it.
I obviously already left some comments, though I still want to write up a
somewhat larger article on my thoughts on it. This journal entry is not that article ;)
In general, I'm quite relieved. I had somewhat mixed expectations - but
almost everything looks quite fine, and there are hardly any issues. I obviously
like the DRM countermeasures.
From a gpl enforcement point of view, it is very good to see that the "complete
corresponding source code" has been specified in more detail. This should save
us from the hassle of ever again starting the discussion (nit-picking) on
whether "scripts to control compilation and installation" (GPLv2) really only
means scripts, or whether it also covers other methods controlling compilation and
What is a real problem, and I hope this can still be resolved, is the new "60
days" grace period that was introduced. With GPLv2, the right to distribute
the software was automatically revoked in the case non-conformant distribution
has happened. In the v3 draft, there is a grace period where the rights _may_
be terminated, and only 60 days after being notified by one of the copyright
The intention of it is to take care of "inadvertent violation". As harmless
and reasonable as this sounds, this change has the potential to render most of
the current enforcement success of gpl-violations.org impossible in the future.
From all the 60+ cases that we've enforced, I cannot tell you one case where
the defendant would not claim that the violation was inadvertent. So in
reality, inadvertent basically means "we didn't care". However, the whole
point of the gpl enforcement exercise is to raise awareness and make them care
before it is too late.
The 60 days grace period is not acceptable. On the one hand, we (in Germany)
basically loose the ability to apply for preliminary injunctions. PI's are
only granted in case of urgency, which translates (depending on the court) to
something like 30 days. So if I know for more than 30 days that somebody is
infringing on my copyright (and don't get the matter resolved with him in that
period of time), then I can't consider this matter as urgent.
The 60 days grace period is also not acceptable, because it would basically
reduce the motivation to comply with the license in the first place. So for
EvilCorp Inc. it is perfectly possible to design a product using GPL licensed
software, not comply with the license, ship the product, wait for a copyright
holder to send a notice, make sure that I ship all the remaining in-stock
products that do not contain a written offer, GPL text and/or source code in
the 60 remaining days, and then start behaving GPL compliant. If such behaviour has
no consequences at all, why would anyone behave different in the first place?
iptables-1.4 branch opened
Since we now have the x_tables kernel side code in the upcoming 2.6.16 series,
I'm working on getting iptables-1.4.x done to actually take advantage of
the new kernel's abilities.
The main reason why people are interested in this, is to get matches like
'state' and 'conntrack' working for IPv6. Even though 2.6.15 has nf_conntrack
and thus state tracking for IPv6, you cannot really use it from ip6tables yet.
The same goes for all native x_tables matches and targets. However, I think
we'll also release a new version of iptables-1.3.x just with 'state' and
'conntrack' support, since it gives a more stable foundation for production
users than a completely new 1.4.x branch with hundreds of kilobytes of patches.