Please create an account to participate in the Slashdot moderation system


Forgot your password?

Comment: Re:Well, this just screwed the legal pooch... (Score 1) 225

by Paul Jakma (#49432503) Attached to: How Ubiquiti Networks Is Creatively Violating the GPL

The GPLv2 is not perfectly happy with DRM. It is very much possible to read the GPLv2 as requiring *all* material needed to install an executable, which would include keys:

“For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable.”

The GPLv2 was very much intended to allow end-users to be able to *install* modified works. The incident which motivated RMS to start this whole free software thing and come up with the GPL was a printer whose software he wanted to fix but couldn't. The freedom to modify software on hardware you own is what the GPL was intended to provide.

The GPLv2 is *not* "happy" with DRM. At best, this is an untested grey area simply because the GPLv2 predates the notion of DRM and so could not use the language we use today. However, it clearly intended to cover installation. The GPLv3 unambiguously fixes this wording issue. That does not mean the GPLv2 allows it though.


Amazon Requires Non-Compete Agreements.. For Warehouse Workers 331

Posted by Soulskill
from the you-may-not-lift-and-carry-objects-for-anyone-else dept.
Rick Zeman writes: Amazon, perhaps historically only second to Newegg in the IT nerdling's online shopping heart, has not only subjected their warehouse employees to appalling working conditions, but they're also making them sign a non-compete agreement for the privilege. Here's an excerpt from the agreement: "During employment and for 18 months after the Separation Date, Employee will not, directly or indirectly, whether on Employee's own behalf or on behalf of any other entity (for example, as an employee, agent, partner, or consultant), engage in or support the development, manufacture, marketing, or sale of any product or service that competes or is intended to compete with any product or service sold, offered, or otherwise provided by Amazon (or intended to be sold, offered, or otherwise provided by Amazon in the future)."

Comment: Re:There's a limit to what can be done (Score 1) 385

by Paul Jakma (#49356613) Attached to: Modern Cockpits: Harder To Invade But Easier To Lock Up

How many suicidal hijackings have there been? 3 - and the passengers had already realised on the day and changed their behaviour as #3 was in progress. The best defence against these hijacks was already in place by September 12th - the passengers.

How many suicidal pilot crashes have there been of jet airliners? At least 4.This one, Egypt Air 990, Mozambique Airlines TM470, Silk Air Flight 185, since 1999.

There's just no good defence against a suicidal pilot. Bear in mind that Egypt Air 990 went from level flight at FLA330 to the ocean in 43s, even thought the captain was back in the cockpit within 12s (no locked door then) and behind the controls no later than 27s.

Also bear in mind cockpits have at least one crash axe (for crashes and getting at electrical fires behind panels).

IMO the best thing to do would be to get rid of the locked doors. Whatever chance the other pilot has, it would surely be increased if other crew and/or passengers could easily and quickly get in to assist with any man-handling needed.

Comment: Re:Ummmm ... duh? (Score 3, Informative) 385

by Paul Jakma (#49356389) Attached to: Modern Cockpits: Harder To Invade But Easier To Lock Up

Gender is irrelevant. Egypt Air 990 crashed *without* locked cockpit doors. The captain was back in the cockpit within 12s of the co-pilot initiating a descent. He was making control inputs within 27s. However, he didn't start to suspect the cause of the problem might be the co-pilot until between 30s to 33s. The aircraft hit the sea at about 43s.

Every second may be vitally precious in these situations. Locked cockpit doors, even with over-rides, will waste potentially extremely-critical time.

Comment: Re:I'm dying of curiousity (Score 1) 188

by Paul Jakma (#49216975) Attached to: Software Freedom Conservancy Funds GPL Suit Against VMWare

Except they didn't re-implement the sub-system framework and data-structure APIs themselves. The lawsuit alleges that they took some code from Linux (e.g. radix tree, timer API stuff). Even if VMWare /had/ reimplemented those APIs from scratch, then there is still the issue that they /also/ have appropriated the code GPL-only drivers (as alleged by the lawsuit at least) for ESXi.

Also, will you provide that list of drivers? If you won't, I have to wonder if you're favourably predisposed to VMWare in some way.

Comment: Re:I'm dying of curiousity (Score 1) 188

by Paul Jakma (#49194837) Attached to: Software Freedom Conservancy Funds GPL Suit Against VMWare

BTW, a vendor that wrote a Linux driver could give a different, non-GPL licence to that driver code, of course. However, that still leaves the issue that Linux drivers are written within a framework of core Linux code (driver sub-system specific frameworks and further more generic services and data-structures). The driver vendor can not give a non-GPL licence for that core code they didn't write.

VMWare are alleged to have copied such core code too. Further, they are alleged to also have used GPL driver code (e.g. Hellwig's SCSI). So VMWare, according to the allegations, have borrowed GPL code on /both/ sides of the "line" between drivers and their supporting code. Without fulfilling the conditions required by the GPL for legal, licensed use of GPL code...

The world is no nursery. - Sigmund Freud