Mattia Dongili wrote:
> how do you deal with
>
> [global]
> umlargs=init=/bin/sh mem=256M bla=b
> mem=128M
Uups, didn't think about this.
How does uml handle ... mem=128M mem=256M ... ?
Looks like the last one wins ...
> We could just ship a rootstrap.conf with some clear comment on possible
> issues deriving by too low mem values, but still I'd go with umlargs
This should be enough.
> BTW: I'd also say we have one more bug because the --umlargs command line
> option and umlargs= confg option are not exclusive, I'll modify them to
> have a well defined precedence not allowing to overlap.
IMO, the following precedence should be used:
--umlargs (highest precedence, allow even
rootstrap --umlargs "eth0=shoot,me,in,the,foot ubd1=/dev/null")
mem=... (if we had one; same precedence as e.g. networking options
generated from [networking])
umlargs=... (lowest precedence, may not override e.g. network settings
that are configured separately, may be overridden by command line)
Andreas
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
