Anton Zaytsev
writes:
> Ok, I've decided to just leave it as is. It's production systems, service
> restarts are not so often.
> So only solution for this issue now is to use host system just as host.
>
> Tim,
> Migration to Debian will be not so simple.
> Yes, I think it's needed to send bug rep
Zitat von Kir Kolyshkin :
On 11/10/2011 03:28 AM, JR Richardson wrote:
This was great feedback gentleman. I really appreciate your time. I think
I'm leaning toward using the RH kernel on Debian, checking out proxmox now.
You can use latest RHEL6-based kernel builds on your Debian or
Ubuntu m
I've submited the bug to RHEL.
https://bugzilla.redhat.com/show_bug.cgi?id=753834
Yes for now it's only to limit services on the host.
On Mon, Nov 14, 2011 at 11:57 AM, Aleksandar Ivanisevic <
aleksan...@ivanisevic.de> wrote:
> Anton Zaytsev
> writes:
>
> > Ok, I've decided to just leave it as
On 14/11/11 16:46, Anton Zaytsev wrote:
> I've submited the bug to RHEL.
> https://bugzilla.redhat.com/show_bug.cgi?id=753834
>
> Yes for now it's only to limit services on the host.
>
To get this bug taken more seriously, I would be more concrete.
e.g. give the name of an init script which f
Hi,
> Hm,
>
> in contrast to the standard Debian Kernel the OpenVZ kernel looks like missing
> the gdth driver for the older ICP Vortex RAID Controller?
> When trying to steps above all i get is a system which cannot access its boot
> device any more :-( Any reason why gdth is exluded in your ker
You may wonna take a look at this:
http://qubes-os.org/Architecture.html
On Nov 10, 2011, at 12:36 PM, Kir Kolyshkin wrote:
On 11/10/2011 01:29 PM, Stoyan Stoyanov wrote:
If thats right you just need to isolate the application process/
processes ? So may be the best way is just chroot it in the
