[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 14 Dec 2009 17:04:47 +0700
From: Ihsan Sabri <ishobr@...il.com>
To: owl-users@...ts.openwall.com
Subject: Re: Network unreachable from inside Owl CT
On Sun, Dec 13, 2009 at 8:24 PM, Solar Designer <solar@...nwall.com> wrote:
> Oh, you could also rename Owl-current-20091129-x86_64.tar.gz to
> owl.tar.gz (or create a link of that name and use it to refer to the
> template), but that's arguably more confusing.
>
You and GalaxyMaster are right. Renaming
Owl-current-20091129-x86_64.tar.gz to owl-current-20091129-x86_64.tar.gz and
use owl-current-20091129-x86_64 as ostemplate works great. No more
workaround nedeed.
P.S. Perhaps the next step for you is to replace the host system with Owl.
> You should be able to continue running both Owl and non-Owl containers.
>
I have been waiting for 3 years until Owl support Virtualization. I switched
to Centos 3 years ago. I think, time to switch back to Owl agaian :)
Ihsan
Content of type "text/html" skipped
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
