Re: [Xen-devel] sHype changeset causes error in domU creation

[aq <aquynh@xxxxxxxxx>]

On 6/24/05, Reiner Sailer <sailer@xxxxxxxxxx> wrote:
> Keir Fraser <Keir.Fraser@xxxxxxxxxxxx> wrote on 06/23/2005 05:48:12 AM:
> 
> >
> > On 23 Jun 2005, at 04:01, Stefan Berger wrote:
> >
> > > This is a problem that comes with an FC 4 install and the newer python
> > > that comes along with it.
> > > Below a patch that solves the problem. ( default=~0 would also work )
> > >
> > > Signed-off-by: Stefan Berger <stefanb@xxxxxxxxxx>
> >
> > Steve applied this patch, but I'd strongly argue for 0 as the default
> > ssid value. I don't know if this this is a hard change to make?
> 
> Hi Keir, we already started to change the default ssid (to 0). The change
> is not much work but will need testing. We will have a patch in a few
> days.
> 
> > As an aside, I also don't like the name of the policy hypercall and
> > policy control tools. Can we call them 'acm_policy' or
> > 'security_policy' or something like that? Calling them 'policy' with no
> > further qualification is too vague.
> 
> This is a good suggestion as well. We are going to make the name change
> to security_policy. acm_policy is a bit too restrictive since the security
> architecture will generally involve more than just the current access
> control
> module.

BTW, how about changing the name of "policy_tool" (in tool/policy/)? i
guess it has the same problem, doesnt it?

regards,
aq

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel