On Mon, Apr 11, 2016 at 01:04:14PM +0200, Markus Armbruster wrote: > My best guess > is you're referring to the part where I challenge mapping > /unsupported/root/FOO to FOO. I find that baroque. I can accept > baroque when I see a reason. That's why I asked for it. "I got ACKs > for it" is not a particular satisfying reason, but I figure you got > another one. Do tell :)
The issue I am trying to address is that users can put stuff outside "opt/" without realizing they are violating any rules. I do not think printing a warning is sufficient for this: it is masked by tools too often. Thus, anything outside "opt/" must be forbidden and cause a failure. Gerd and others asked for a way to bypass this "for development" which presumably means they way a quick way to develop guest code interacting with QEMU without changing qemu proper, with the intent to merge support into QEMU a bit later. We could add a special flag for this instead but the mapping is a couple of lines of code, so seems easier, the point is to have "unsupported" there. -- MST
