On Mon, Jan 18, 2016 at 12:52:31AM +0700, Robert Elz wrote:
> [...]
> That's because you're still running the 7.0 release vnconfig (because
> that is what is still on the netbsd-7 branch). That's simply broken, and
> it is not surprising that you are seeing problems with vnconfig -l.
>
> Note that all of this occurred because NetBSD 7 got a broken hack to
> vnconfig to work around the change to being a cloning (which ignored
> backwards compat) rather than fixing it in a rational way, which has
> now been done ... just not yet(fully) pulled up to -7 and -7-0
I totally dissagree that the code in head is a "rational way".
It removes usefull functionality. You can always immagine setups where this
would have given wrong informations, but there are common uses for it.
If you have a setup where is gives incomplete informations just don't use it
but there's no reason to remove something that works fine for out of the box
setup.
>
> And this (irrelevant side issue) still doesn't explain what is happening
> with the xen startup, which doesn't use vn{d}config -l You wouldn't
> even be thinking about it if you had not noticed (largely because of
> the mismatch of vnconfig & kernel) the change while looking for whatever
> the real issue is here. You also didn't object when the original
> problem, and this solution, were being discussed early last November.
I didn't notice that it would remove free devices from vnconfig -l
output at this time, or I would have complained.
--
Manuel Bouyer <bou...@antioche.eu.org>
NetBSD: 26 ans d'experience feront toujours la difference
--
