Forgot your password?

Comment: Re:Gee, that's worse than no encryption isn't it? (Score 1) 303

by buchner.johannes (#46691765) Attached to: OpenSSL Bug Allows Attackers To Read Memory In 64k Chunks

If only they had written OpenSSL in Java instead of C! I'm wondering how many friends I can get on Slashdot with that statement.

..., I think that we need to do three things:

  1) Pay money for security audits of critical security infrastructure like OpenSSL
  2) Write lots of unit and integration tests for these libraries
  3) Start writing alternatives in safer languages

Given how difficult it is to write safe C, I don't see any other options. ...

(from, someone else linked this below).

Comment: Re:Sounds like a RC plane not a drone (Score 2) 178

Never had anyone get hit by one. Now they're banned. Sad.

Over a period of eight years, lawn darts had sent 6,100 people to the emergency room. 81% of those cases involved children 15 or younger, and half of those were 10 or younger. The majority of injuries were to the head, face, eyes or ears, and many had led to permanent injury or disability.

And one was killed.

Just use plastic ones!

Comment: Wow ... just why? (Score 3, Interesting) 100

by buchner.johannes (#46662399) Attached to: Microsoft To Allow Code Contributions To F#

"let" statements -- really?
And the selling feature is list comprehension? Looks like they are trying to go into Haskells direction.
Testimonials say it's better than C# for data analysis?
Well, that train has left the station, with R, Python (and Julia) being available. This can not be won by languages, but with high-quality statistics / visualisation / machine learning libraries.

License is Apache v2 by the way.

Comment: Re:Projections (Score 4, Insightful) 987

by buchner.johannes (#46624815) Attached to: UN Report: Climate Changes Overwhelming

Nothing significant can happen unless everyone does.

Not true. If 20% do something, it will be significant.
Everyone blame everyone else, and don't do anything? No thank you. Try at least.

And here's the thing - most countries (especially poorer countries) don't give the tiniest bit of a fuck.

Not true. Countries are affected differently, and some poor countries are highly concerned.

If everyone in America did what I'm saying it would make an impact, but A) That will never happen and B) It would just delay the inevitable, because of china etc.

So scenario A It's true and we're all fucked and can't do anything about it. Thus we're arguing over..nothing.

Scenario B It's not true and we're arguing over..nothing.

It doesn't paint the greatest picture of humanity but I'm fairly certain it's an accurate one.

You are falsely blaming others. Even if not everyone contributes, change can be achieved, and it should be tried. Non-contributing countries could even be fined for not contributing to the common rescue attempt.

China has about the same emissions as the US. And guess why China has so much emissions? Because of the outsourced productions (electronics, clothing, toys). The US could easily implement requirements that their outsourced products have to adhere to emission limits!

Comment: Re:Beta testers (Score 5, Interesting) 91

by buchner.johannes (#46529617) Attached to: OpenSUSE 13.2 To Use Btrfs By Default

You can create a file system on a file on your disk (similar to a swap file).
Contrary to popular believe this is not slower than a partition, because if the file is mostly continuous, it can be mapped to disk directly by the kernel. Here I create a file system using a sparse file:
$ truncate +20G mylocal.fs
$ mkfs.btrfs mylocal.fs
$ mkdir -p mylocal; sudo mount mylocal.fs mylocal/

You can use such file systems, for example, to bundle directories with many files, which are deleted/created many times. This causes fragmentation in the file system. Contrary to another popular believe, yes, this is a problem on Linux file systems, and it slows down reads. None of the file system currently has a defragger implemented. Btrfs is actually developing one, but I think it is not in the release yet. The recommended solution is rewriting files (shake).

Sub file system containers can be easily resized, and with sparse files only use up the space filled with data. I use them for the linux kernel build directory (you shouldn't build in /usr/src), for portage (many files, changing frequently), and scientific data directories, to limit the fragmentation, and keep speed high. I use reiserfs for this -- find a managing script here:

Chemist who falls in acid is absorbed in work.