To: linux-kernel@vger.kernel.org
Path: not-for-mail
From: Bill Davidsen <davidsen@tmr.com>
Newsgroups: mail.linux-kernel
Subject: Re: propolice support for linux
Date: Thu, 13 Jan 2005 12:07:48 -0500
Organization: TMR Associates, Inc
Message-ID: <41E6AAE4.3010706@tmr.com>
References: <20050113140446.GA22381@infradead.org><20050113140446.GA22381@infradead.org> <20050113163733.GB14127@boetes.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: linux-kernel@vger.kernel.org
To: Han Boetes <han@mijncomputer.nl>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20040913
In-Reply-To: <20050113163733.GB14127@boetes.org>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1248
Lines: 25

Han Boetes wrote:
> Thanks for your comments! This wasn't my patch, just the closed
> thing to something working I could find. Here is my version.
> 
> Now all I wonder about is what the _NOVERS should become, since
> Arjen pointed it it `was dead,' since I don't really understand
> what he means with that.
> 
> Perhaps I should also add some additional comment about how little
> effect this extension resorts on kernel-level.
> 
> And I got two warnings about `int __guard = '\0\0\n\777';'
> 
> lib/propolice.c:15:15: warning: octal escape sequence out of range
> lib/propolice.c:15:15: warning: multi-character character constant

Unless you foresee a port of Linux to some 36 bit hardware (like 
MULTICS) with nine bit bytes, is there a reason not to us \377? I have 
used 36 (and 48) bit hardware, but I don't expect it to ever get a Linux 
port.

-- 
    -bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
  last possible moment - but no longer"  -me
-
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/