Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263999AbUDFUhv (ORCPT ); Tue, 6 Apr 2004 16:37:51 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S264000AbUDFUhv (ORCPT ); Tue, 6 Apr 2004 16:37:51 -0400 Received: from kinesis.swishmail.com ([209.10.110.86]:64274 "EHLO kinesis.swishmail.com") by vger.kernel.org with ESMTP id S263999AbUDFUht (ORCPT ); Tue, 6 Apr 2004 16:37:49 -0400 Message-ID: <40731A02.5030502@techsource.com> Date: Tue, 06 Apr 2004 16:58:42 -0400 From: Timothy Miller MIME-Version: 1.0 To: Horst von Brand CC: Sergiy Lozovsky , Linux Kernel Mailing List Subject: Re: kernel stack challenge References: <200404062016.i36KGV6d004291@eeyore.valparaiso.cl> In-Reply-To: <200404062016.i36KGV6d004291@eeyore.valparaiso.cl> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 817 Lines: 22 Horst von Brand wrote: > OK, so you need the policy to be interpreted in-kernel (dunno why a > largeish high-level general purpose language is needed for that, when a > tiny interpreter for a specialized language will do very well, and has been > shown to work fine), and written in a "high level language" so that your > garden variety sysadmin _can_ write her own policy, but it really doesn't > matter because she'll never have to do so... > > Completely lost me. I was getting hung up on that one too, but I didn't know how to say it. You did a nice job. :) - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/