[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] Re: multiple disk images, how to?


  • To: Charles Duffy <cduffy@xxxxxxxxxxx>
  • From: Molle Bestefich <molle.bestefich@xxxxxxxxx>
  • Date: Tue, 17 Jan 2006 17:51:14 +0100
  • Cc: xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Tue, 17 Jan 2006 16:58:52 +0000
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=XTjEuLXA8iPcgxYWUqSf3VxgTbiaf9bZzoMDdBEmbpcjyCL/e0JMJ47lRipHsuyuaojYQMOKw2553hRwYYsgC98TRm7bmlgePxk1Zczc/jbvd2L16Tp8SMSRgDvK1XfB/u0KKsNETQuzL2EDlRI88VfbyTapAx0VAheptGCXwMA=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Charles Duffy wrote:
> Think of it as if you were sourcing a file to get your config settings
> in bash. Someone could have logic like this:
>
> if [ -n "$foo" ] ; then
>     DISK="/dev/foo/bar${foo}"
> else
>     DISK="/dev/foo/baz"
> fi

Even if that's desirable for <insert insane scenario here>...

> ...and that would be valid, so you wouldn't want to call the config file
> invalid if it had more than one line matching ^[[:space:]]*DISK=

...you would want at least be able to throw a warning when it happens,
since regular users probably expect standard config-file semantics
from a config file, not Python semantics.

Another approach would be to note in each configuration file that it's
Python syntax.

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.