| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <AANLkTin=BMcfmm_0p=OVwN6FYUfp6nUuT85uKZnqHGE8@mail.gmail.com> Date: Sat, 27 Nov 2010 16:27:36 -0300 From: Elias Gabriel Amaral da Silva <tolkiendili@...il.com> To: Ben Gamari <bgamari@...il.com> Cc: jason.vas.dias@...il.com, linux-kernel@...r.kernel.org Subject: Re: per-chroot clock module ? 2010/11/27 Ben Gamari <bgamari@...il.com>: > On Sat, 27 Nov 2010 18:21:34 +0000, Jason Vas Dias <jason.vas.dias@...il.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. KVM needs hardware support (but chroot runs wherever Linux runs) -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists