Catch up on stories from the past week (and beyond) at the Slashdot story archive


Forgot your password?
DEAL: For $25 - Add A Second Phone Number To Your Smartphone for life! Use promo code SLASHDOT25. Also, Slashdot's Facebook page has a chat bot now. Message it for stories and more. Check out the new SourceForge HTML5 Internet speed test! ×

Submission + - Handling large amounts of data with complex relationships? (

jd writes: "This is a problem I've mentioned in a couple of posts, but I really need the expert advice only Slashdot can offer. I have a lot of old photos (many hundreds) and old negatives (about 7,500 or so) covering 150 years and four different branches of the family.

The first challenge is to find a way to index every scan (date, geography, people) to be able to relate the images. Google+/Picasa doesn't even come close to what is needed — its capacity to relate information is very limited.

The second challenge is to identify major landmarks. Few of the pictures have any information and whilst I can identify some places I cannot identify everything. Not even close. Searching the web for similar images using the image as the "keyword" — that is an interesting challenge.

The third challenge is to store the images. Each of the scans is around 3.5 gigabytes in size using CCITT 4 compressed TIFF files. That gives me a storage requirement of 28 (SI) terabytes (27.3 real terabytes), which is more than I really want. Since I am producing a digital backup of the negatives, I don't want to lose resolution or detail where I can avoid it. Clearly, I can't avoid it completely — I can't afford a personal data silo — but keeping loss to a minimum is important.

What would people suggest as the best solution to these various technical problems? Besides getting a brain transplant and a new hobby."

Submission + - When and How to deal with GPL violations? ( 1

jd writes: "There are many pieces of software out there such as seL4 (kindly brought to my attention by another reader) where the vendor has indeed written something that they're entitled to Close Source but where their closed-source license includes the modifications to GPLed software such as the Linux kernel.

Then there's a second type of behaviour. Code Sourcery produced two versions of their VSIPL++ image processing library — one closed-source, one GPLed. It was extremely decent of them. When Mentor Graphics bought them, they continued developing the closed-course one and discontinued, then deleted, the GPL variant. It's unclear to me if that's kosher as the closed variant must contain code that had been GPLed at one point.

Here's the problem: Complaining too much will mean we get code now that maybe 4 or 5 people tops will actually care about. It will also make corporations leery of any other such work in future, where that work will be of greater value to a greater number of people.

So the question I want to ask is this: When is it a good time to complain? By what rule-of-thumb might you decide that one violation is worth cracking down on and another should be let go to help encourage work we're never going to do ourselves?"

Slashdot Top Deals

Work is the crab grass in the lawn of life. -- Schulz