From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <5d375e920704151000m13b90389w2188ec1b78059809@mail.gmail.com>
Date: Sun, 15 Apr 2007 19:00:52 +0200
From: Uriel <uriel99@gmail.com>
To: 9fans@cse.psu.edu
In-Reply-To: <5d375e920704150106m5865747flb6ae25392f8744ca@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <f93786a38200d44b7406b3181b4e2c20@cat-v.org>
	<5d375e920704150106m5865747flb6ae25392f8744ca@mail.gmail.com>
Subject: [9fans] Re: [sources] 20070413: /rc/bin/cpurc.local
Topicbox-Message-UUID: 48cf89f6-ead2-11e9-9d60-3106f5b1d025

On 4/15/07, Uriel <uriel99@gmail.com> wrote:
> Note that there is no way to check the state of the
> variable, so one has no clue if one is enabling or disabling
> 'coopsched', whatever it does this interface is clearly far from
> ideal.

Seems that I was overzealous (as usual) in this point, I read the code
but then forgot, dho correctly reminded me that there is a kprint
reporting the new state of coopsched when toggled, but this is still
an ugly, non standard and inconvenient interface.

uriel