> Op 6 nov. 2013 om 05:23 heeft Scott McEachern <[email protected]> het > volgende geschreven: > >> On 11/05/13 23:02, Philip Guenther wrote: >>> On Tue, Nov 5, 2013 at 7:33 PM, Scott McEachern <[email protected]> wrote: >>>> On 11/05/13 22:29, Ted Unangst wrote: >>>>> On Tue, Nov 05, 2013 at 22:18, Scott McEachern wrote: >>>>> Anyone else running into this when running "make release" with -current? >>>>> vnconfig -v -c vnd0 /var/tmp/image.11200 >>>>> vnconfig: VNDIOCSET: Device busy >>>> Are you already using vnd0? >>> No, not intentionally at least. >> So you've used "vnconfig -l" to see what it's currently bound to and... > > # vnconfig -l > vnd0: covering /var/tmp/image.28401 on sd0e, inode 12 > vnd1: not in use > vnd2: not in use > vnd3: not in use > > I'm not sure if that's from something earlier in the build process, or > possibly from a failed build the other night. > > Either way, I'm going to just nuke it all, install from scratch, and see how > that goes. I'll bet it will work just fine..
Unconfig and restart should do it. -Otto > > -- > Scott McEachern > > https://www.blackstaff.ca > > "Beware the Four Horsemen of the Information Apocalypse: terrorists, drug > dealers, kidnappers, and child pornographers. Seems like you can scare any > public into allowing the government to do anything with those four." -- > Bruce Schneier
