From: Andrea Arcangeli <andrea@suse.de>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Larry McVoy <lm@bitmover.com>, linux-kernel@vger.kernel.org
Subject: Re: Fix for wrong OOM killer trigger?
Date: Sun, 21 Sep 2003 16:22:52 +0200 [thread overview]
Message-ID: <20030921142252.GB16399@velociraptor.random> (raw)
In-Reply-To: <m1smmqjug2.fsf@ebiederm.dsl.xmission.com>
On Sun, Sep 21, 2003 at 04:40:29AM -0600, Eric W. Biederman wrote:
> Careful with your accusations Larry, some of us can answer those questions,
> in ways that won't support your argument.
It didn't worth an answer IMHO, he's ignoring lots of efforts going on,
AFIK you're in the bios area like many others, especially for x86-64 it
sounds very promising. notably these days my PDA strictly runs open
source since I strictly need it for security reasons, for istance I
nuked Opera immediatly and replaced it with konqueror and the whole
openzaurus suite, I will do the same soon with the cellphone, and
everything he listed is all but critical, and we pay that as well to
have some sort of warranty most of the time, at least for the first few
years, nothing like the bkbits.net that can be shutdown anyday, Larry
made sure he can turn everything "free" of anytime AFIK. And we have
many providers for cellphones microwaves cars etc.. not just one. If
something breaks and can't be repaired I throw it away and buy another
one.
But it would be unacceptable to throw away the whole 2.5 changesets
instead. And without this bkcvs export in the open, they could be lost
anyday of the week. And I can't even try to extract those with b*tkeeper,
since it's illegal to do so from my part. yeah, if there wasn't bkcvs,
somebody had to sacrifice his freedom for us to extract this closed info
encoded in proprietary form (like a .doc). since many already sacrificed
their freedom of development in this area, maybe it wouldn't be too bad,
they're already screwed so it can't go worse for them, but bkcvs to me
sounds much safer than an hope that somebody oneday will do the
conversion after sacrificing its freedom and after sorting out the
linearization of the tree.
Andrea - If you prefer relying on open source software, check these links:
rsync.kernel.org::pub/scm/linux/kernel/bkcvs/linux-2.[45]/
http://www.cobite.com/cvsps/
svn://svn.kernel.org/linux-2.[46]/trunk
next prev parent reply other threads:[~2003-09-21 14:22 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-19 17:16 Roland Bless
2003-09-19 17:30 ` Marc-Christian Petersen
2003-09-19 19:25 ` Andrea Arcangeli
2003-09-19 19:35 ` Russell King
2003-09-19 20:01 ` Andrea Arcangeli
2003-09-19 20:52 ` Larry McVoy
2003-09-19 21:05 ` Formal complaint , " Mr. James W. Laferriere
2003-09-20 6:36 ` David S. Miller
2003-09-20 3:31 ` Andrea Arcangeli
2003-09-20 4:30 ` Larry McVoy
2003-09-20 12:22 ` Bernd Schmidt
2003-09-20 13:52 ` Willy Tarreau
2003-09-20 13:54 ` Larry McVoy
2003-09-20 19:56 ` Gateways (was Re: Fix for wrong OOM killer trigger?) Jamie Lokier
2003-09-20 20:14 ` Larry McVoy
2003-09-21 11:52 ` David S. Miller
2003-09-20 16:07 ` Fix for wrong OOM killer trigger? Valdis.Kletnieks
2003-09-20 14:23 ` Andrea Arcangeli
2003-09-20 15:13 ` Larry McVoy
2003-09-20 17:14 ` Flames (was: Fix for wrong OOM killer trigger?) Stephen Satchell
2003-09-20 17:46 ` Alan Cox
2003-09-21 10:40 ` Fix for wrong OOM killer trigger? Eric W. Biederman
2003-09-21 14:22 ` Andrea Arcangeli [this message]
2003-09-21 14:52 ` Larry McVoy
2003-09-21 15:53 ` Andrea Arcangeli
2003-09-23 12:46 ` Bas Mevissen
2003-09-20 11:09 ` Roland Bless
2003-09-20 14:34 ` Andrea Arcangeli
2003-09-22 10:11 ` Roland Bless
2003-09-22 13:02 ` Andrea Arcangeli
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030921142252.GB16399@velociraptor.random \
--to=andrea@suse.de \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@bitmover.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®