DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=from:to:subject:in-reply-to:references:user-agent:date:message-id
         :mime-version:content-type;
        b=L6oISWnPbEm0sphEX6pAj6qKMcDaAp5s/YD33SJ31q4Q1w4t16H+Jae6LXXnX4YenS
         pGC50zdLv+rom02kRFd3R+LFMJUnqd70wc1YiUuAt1eTUcW7Awy4gBkT+Ia5cKM2ck9m
         eU8Wd+5DnJ049HxhN8565STVQ7bYSD8kgXgQg=
From: Ben Gamari <bgamari@gmail.com>
To: jason.vas.dias@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: per-chroot clock module ?
In-Reply-To: <201011271821.35039.jason.vas.dias@gmail.com>
References: <201011271821.35039.jason.vas.dias@gmail.com>
User-Agent: Notmuch/0.5-3-g22aadfc (http://notmuchmail.org) Emacs/23.1.1 (x86_64-pc-linux-gnu)
Date: Sat, 27 Nov 2010 13:57:19 -0500
Message-ID: <874ob2r3w0.fsf@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1135
Lines: 28

On Sat, 27 Nov 2010 18:21:34 +0000, Jason Vas Dias <jason.vas.dias@gmail.com> wrote:
> Greetings -
> 
> Sorry in advance if this is a stupid idea, but -
> 
> I'd really like to be able to set a distinct "clock" for a specific chroot environment, 
> such that the super-user could call :
> [snip]

It certainly doesn't sound like a particularly good idea to me. This
would add great complexity to the kernel while having very few
users. Perhaps there's something I haven't considered but I can't think
of any good applications for this sort of functionality. Do you have
something in particular in mind?

It seems like what you want here is simple virtualization. Have you
considered KVM? The closest thing to your request currently upstream is
containers, although I'm unsure of whether a container can be created
with an independent clock. Might be something to look into.

Cheers,

- Ben
--
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/