lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 6 Apr 2009 21:27:15 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	"Trenton D. Adams" <trenton.d.adams@...il.com>
cc:	Chris Mason <chris.mason@...cle.com>, Theodore Tso <tytso@....edu>,
	Hua Zhong <hzhong@...il.com>,
	Jens Axboe <jens.axboe@...cle.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/8][RFC] IO latency/throughput fixes



On Mon, 6 Apr 2009, Trenton D. Adams wrote:
>
> Okay, so a config option is a benefit in what way, for these
> particular circumstances?  If someone wants to change the behaviour of
> the kernel, for this particular case, they can just use tune2fs, no?

Basically, I have a very simple policy in my kernel life:

 - I don't touch distribution settings. I update the kernel, and NOTHING 
   else.

(Ok, I lie. I do my own git version too, but I'm really unhappy when I 
feel like I need to maintain anything else)

And I have that policy because quite frankly, if I start tuning distro 
settings, I'll

 (a) forget about them and not do it on my next machine and 
 (b) do some magic that _I_ may know how to do but nobody else does, so 
     now what I'm doing is no longer relevant for anybody else
 (c) I'm no longer helping anybody else.

So I have a few bits and pieces that I develop (mainly the kernel but also 
git etc), and I don't make site-specific changes to them even if I could. 

In other words: if I make a change that helps me, I want to make sure
that I make that option available to everybody else, because quite
frankly that's a big portion of the whole point of open source.

The whole "scratch your itch" isn't just about scratching _your_ itch, 
it's about getting it (almost by mistake) fixed for a lot of other people 
too.

			Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ