hannibal5

Runnin ZFS in linux is not good idea. That's why I'm currently using OpenSolars and maybe switching to FreeBSD in the future for file and db servers.

The problem with btrfs time estimate is that it takes long time for filesystems to become reliable enough that you can put important data on them. ZFS has crossed that threshold, it takes years and years for btrfs.

I don't think manned mission to Mars should be priority for NASA either. "You absolutely have to have person there to decide what to do" argument is not convincing if you would spend the same amount of money for robotic missions to Mars and it's moons.

You are also right. Small projects don't need them because you have to time to to look trough the few changes fast.

Linux development would not go as smooth if it would not have rules (that are quite minimal btw.). If everyone would commit code with different indentation and these changes would constantly end in git, it would be chaos. Same for commit logs. It does not matter at all for those who are contribution only time from time, but if it's your everyday job to read trough them it's important.

I don't see any reason why you can't integrate static analysis into dynamic language development process like in CL. SBCL compiler already does huge amount of type analysis in compile time. Instead of type errors, it gives type warnings and hints for the purpose of making faster code.

What if you would extend this functionality outside compilation. What if you could declare functions that are entry points to the "program" and you would do block compilation equivalent and give type errors if programmer wants them. This would probably be before commit type thing and part of testing.

Here is the example sentence in standard hacker rudeness scale:

0. Please fix this.

1. Fix this now, you moron. <-- Linus

2. I guess, we don't use this until you find way to fix this. Maybe I help with FreeBSD project meanwhile.

3. I need you to fix this NOW.

4. I NEED TO YOU TO FIX THIS NOW!

5. I NEED YOU TO FIX THIS NOW, MORON!

Why should we not spit on people who don't care about commit logs. When Linus is insulting person, that stings a while. Shitty developer is insulting and harassing everyone day by day.

Being honest and aggressive is way to get people change their behavior or leave.

I'm not saying that Linus is right here. I'm just pointing out that rudeness can be the right way to deal with people who don't take a hint.

I think it's would be good idea in general. If you provide significant infrastructure services from distant countries, you must move servers close.

Science 30 August 2013: Vol. 341 no. 6149 pp. 976-980 DOI: 10.1126/science.1238041 Poverty Impedes Cognitive Function

You know what. It can be shown that climate skepticism is mostly Anglo Saxon phenomenon. It seems to be related to political and lobbying efforts.

Most of the world, South America, Europe(outside UK), Russia, India, China, ..., acknowledge the climate change and not because of politics.

Maybe you guys should change your Anglo Saxon "I'm not an expert but I have feelings and an opinion" attitude.

Currently world produces enough food for everyone. Then why do we have 700 - 800 million malnourished people, even more people facing food insecurity, why we are destroying farmland and why are we wasting the primary macronutrients: nitrogen (N), phosphorus (P), potassium (K).

Overpopulation is real because we as species are not distributing resources equally and we are not rational.

To achieve the goal of working less, you need to own capital. Technology changes the capital vs. work equation towards capital at the same time when there is increasing global supply of educated workforce. It's just supply and demand. Workers are simply competing towards bottom.

To get to position where you need to work less you would need to have:

1. Change taxation from work to capital.

2. Basic income.

He has worked previously in mostly corporate and private context, so 2048 is just fine. Now he works with people and data NSA wants their hands on and he wants the data to be secure also in the future. It's just reasonable to move to 4096 key sizes.

http://www.pgp.net/pgpnet/pgp-faq/pgp-faq-keys.html#key-size

>Dr Lenstra and Dr Verheul offer their recommendations for keylengths. In their calculation, a 2048 bit key should keep your secrets safe at least until 2020 against very highly funded and knowledgeable adversaries (i.e. you have the NSA working against you). Against lesser adversaries such as mere multinationals your secret should be safe against bruteforce cryptoanalysis much longer, even with 1024 bit keys.

See also: http://www.keylength.com

The data centers are located in two Finnish cities F-Secure does not reveal.

Capitalism is private ownership of the means of productions. There is nothing in capitalism that implies less inequality. If the balance between capital and work switches to favor capital more, there will be inequality.

"Only wimps use tape backup: _real_ men just upload their important stuff on ftp, and let the rest of the world mirror it ;)"

source: https://groups.google.com/forum/#!msg/linux.dev.kernel/2OEgU...

Whatever are the laws, policies and culture that we create now can have effect that is felt hundreds of years from now.

Now is the defining moment. This issue should be pushed more and more and not just with more articles.

1. Both are operating systems

2. Both are conceptually simple.

3. There is always nice command that does what you want but you somehow forget it. I can't believe that Common Lisp has just 900+ symbols but I routinely forget some of them when programming.

The guy behind /dev/random is Ted Ts'o who has worked as Kerberos V5 project leader is part of security area directorate in IETF and chair of IPSec working group.

As far as I see /dev/random uses the best practices and don't innovate unnecessarily. If somebody is willing to spend time actually vetting the implementation, that would be great.