[3856] in arla-drinkers
Re: Arla 0.42-RC2
daemon@ATHENA.MIT.EDU (Tomas Olsson)
Tue Apr 4 10:32:41 2006
From arla-drinkers-bounces@stacken.kth.se Tue Apr 04 14:32:41 2006
Return-Path: <arla-drinkers-bounces@stacken.kth.se>
Delivered-To: arla-drinkers-mtg@bloom-picayune.mit.edu
Received: (qmail 25897 invoked from network); 4 Apr 2006 14:32:41 -0000
Received: from mx1.kth.se (130.237.32.140)
by charon.mit.edu with SMTP; 4 Apr 2006 14:32:41 -0000
Received: from localhost (localhost.localdomain [127.0.0.1])
by mx1.kth.se (Postfix) with ESMTP id 143D3140A50;
Tue, 4 Apr 2006 16:32:40 +0200 (CEST)
Received: from mx1.kth.se ([127.0.0.1])
by localhost (mx1.kth.se [127.0.0.1]) (amavisd-new, port 10024) with LMTP
id 20416-01-51; Tue, 4 Apr 2006 16:32:38 +0200 (CEST)
Received: from tapas.stacken.kth.se (tapas.stacken.kth.se [130.237.234.140])
by mx1.kth.se (Postfix) with ESMTP id 2498914098E;
Tue, 4 Apr 2006 16:32:38 +0200 (CEST)
Received: from tapas.stacken.kth.se (localhost [127.0.0.1])
by tapas.stacken.kth.se (Postfix) with ESMTP id DE28E534F3;
Tue, 4 Apr 2006 16:32:37 +0200 (CEST)
X-Original-To: arla-drinkers@tapas.stacken.kth.se
Delivered-To: arla-drinkers@tapas.stacken.kth.se
Received: from brev.stacken.kth.se (brev.stacken.kth.se [130.237.234.84])
by tapas.stacken.kth.se (Postfix) with ESMTP id 001CA534F3
for <arla-drinkers@tapas.stacken.kth.se>;
Tue, 4 Apr 2006 16:32:35 +0200 (CEST)
Received: from mx3.kth.se (mx3.kth.se [130.237.48.97])
by brev.stacken.kth.se (8.12.10/8.12.10) with ESMTP id k34EWZbB015575
for <arla-drinkers@stacken.kth.se>;
Tue, 4 Apr 2006 16:32:35 +0200 (MET DST)
Received: from localhost (localhost.localdomain [127.0.0.1])
by mx3.kth.se (Postfix) with ESMTP id 2F3D1140D15
for <arla-drinkers@stacken.kth.se>;
Tue, 4 Apr 2006 16:32:35 +0200 (CEST)
Received: from mx3.kth.se ([127.0.0.1])
by localhost (mx3.kth.se [127.0.0.1]) (amavisd-new,
port 10024) with LMTP
id 12843-01-52; Tue, 4 Apr 2006 16:32:33 +0200 (CEST)
Received: from kashyyyk.ite.kth.se (kashyyyk.ite.kth.se [130.237.31.35])
by mx3.kth.se (Postfix) with ESMTP id 9EA3D1406C9;
Tue, 4 Apr 2006 16:32:33 +0200 (CEST)
Received: by kashyyyk.ite.kth.se (Postfix, from userid 18404)
id 942E17C861C; Tue, 4 Apr 2006 16:32:33 +0200 (CEST)
From: Tomas Olsson <tol@stacken.kth.se>
To: Jeffrey Hutzelman <jhutz@cmu.edu>
Subject: Re: Arla 0.42-RC2
References: <lsrbqvpxoy3.fsf@kashyyyk.ite.kth.se>
<nnpsjy8zsz.fsf@sellafield.lysator.liu.se>
<lsry7ylu7l1.fsf@kashyyyk.ite.kth.se>
<1DD0597778163FD925163115@mariner.pc.cs.cmu.edu>
Date: 04 Apr 2006 16:32:33 +0200
In-Reply-To: <1DD0597778163FD925163115@mariner.pc.cs.cmu.edu>
Message-ID: <lsr8xqltnr2.fsf@kashyyyk.ite.kth.se>
Lines: 16
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
MIME-Version: 1.0
X-Virus-Scanned: by amavisd-new at kth.se
X-Spam-Status: No, hits=-4.9 tagged_above=-200.0 required=5.0 tests=BAYES_00
X-Spam-Level:
Cc: arla-drinkers@stacken.kth.se
X-BeenThere: arla-drinkers@stacken.kth.se
X-Mailman-Version: 2.1.6
Precedence: list
List-Id: Arla discussions <arla-drinkers.stacken.kth.se>
List-Unsubscribe: <https://lists.stacken.kth.se/mailman/listinfo/arla-drinkers>,
<mailto:arla-drinkers-request@stacken.kth.se?subject=unsubscribe>
List-Archive: <http://lists.stacken.kth.se/pipermail/arla-drinkers>
List-Post: <mailto:arla-drinkers@stacken.kth.se>
List-Help: <mailto:arla-drinkers-request@stacken.kth.se?subject=help>
List-Subscribe: <https://lists.stacken.kth.se/mailman/listinfo/arla-drinkers>,
<mailto:arla-drinkers-request@stacken.kth.se?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: arla-drinkers-bounces@stacken.kth.se
Errors-To: arla-drinkers-bounces@stacken.kth.se
X-Virus-Scanned: by amavisd-new at kth.se
Jeffrey Hutzelman <jhutz@cmu.edu> writes:
> Yup; you're going to have that problem with 2.6.16, because they went
> off and moved things into different sections. Worse, if the kernel is
> compiled with CONFIG_DEBUG_RODATA, then on some platforms the system
> call table will actually be stored in read-only pages, and attempts to
> update it will result in a panic.
>
How... oh well, as usual I guess. This is new for 2.6.16, right?
> We probably should do something about getting updated syscall table
> probing code back into Arla.
>
Or just throw the syscall code away. Do people really need it? Is it
possible to use the keyrings for reasonable pag storage nowadays?
/t
_______________________________________________
Arla-drinkers mailing list
Arla-drinkers@stacken.kth.se
https://lists.stacken.kth.se/mailman/listinfo/arla-drinkers
