Can't save Vinum config: No such file or directory

Hi,

after I reverted the syscons change I could build a working kernel, but
something has changed in vinum, so that the volumes are not created in
/dev/vinum anymore.

I get this:

[stijn_at_pcwin002] <~> sudo vinum start
vinum: loaded
vinum: reading configuration from /dev/ad4s1e
vinum: updating configuration from /dev/ad6s1e
Can't save Vinum config: No such file or directory

but unfortunately I can't figure out where it is trying to save.

[stijn_at_pcwin002] <~> ls -ld /dev /dev/vinum /dev/vinum/*
dr-xr-xr-x  5 root  wheel       512 Feb 13 13:47 /dev
dr-xr-xr-x  2 root  wheel       512 Feb 13 13:55 /dev/vinum
crw-------  1 root  wheel   91, 0x3fff00fe Feb 13 13:46 /dev/vinum/control
crw-------  1 root  wheel   91, 0x3fff00ff Feb 13 13:46 /dev/vinum/controld

[stijn_at_pcwin002] <~> ls -ld /dev/ad4* /dev/ad6*
crw-r-----  1 root  operator    4,  22 Feb 13 13:46 /dev/ad4
crw-r-----  1 root  operator    4,  26 Feb 13 13:46 /dev/ad4s1
crw-r-----  1 root  operator    4,  28 Feb 13 13:46 /dev/ad4s1c
crw-r-----  1 root  operator    4,  29 Feb 13 13:46 /dev/ad4s1e
crw-r-----  1 root  operator    4,  23 Feb 13 13:46 /dev/ad6
crw-r-----  1 root  operator    4,  27 Feb 13 13:46 /dev/ad6s1
crw-r-----  1 root  operator    4,  30 Feb 13 13:46 /dev/ad6s1c
crw-r-----  1 root  operator    4,  31 Feb 13 13:46 /dev/ad6s1e

Does anyone have any clue?

--Stijn

-- 
The problem is that there are several people in design positions now who
couldn't design the Next Big Thing(TM) unless it involved them taking a
photocopier and someone else's design of The Next Big Thing(TM).
		-- 'Alkaiser' in a post on Slashdot on game originality