Re: [MirageOS-devel] MacOS X vmnet support

[Anil Madhavapeddy <anil@xxxxxxxxxx>]

On 2 Dec 2014, at 12:53, Daniel BÃnzli <daniel.buenzli@xxxxxxxxxxxx> wrote:
> 
> Le lundi, 1 dÃcembre 2014 Ã 22:06, Anil Madhavapeddy a Ãcrit :
>> I could use a sanity test from someone else running Yosemite first before I 
>> release this. If you are on an older MacOS X, then you will need to pass 
>> `--no-macosx` to the Mirage CLI to not use the new packages and use the old 
>> tuntap module.
> 
> Wouldn't be âno-vmnet or âno-macosx-vmnet or âuse-tuntap (I usually prefer 
> positive flags) more accurate ? Passing âno-macosx on macosx feels a little 
> bit absurd.  

Well, it's overriding the actual platform flag (which could involve things 
beyond Vmnet in the future, such as a fancy console or binary sandboxing).  We 
have:

: --unix
: --xen
: --no-macosx

The other alternative is to get rid of the whole flagset and replace it with 
'--platform=[unix|xen|macosx] instead, leaving --xen and --unix as 
compatibility shims.

-anil




_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@xxxxxxxxxxxxxxxxxxxx
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel