Subject: Re: Can't open /dev/vinum/control: Device not configured
To: Thor Lancelot Simon <>
From: Greg 'groggy' Lehey <>
List: current-users
Date: 11/14/2003 21:02:57
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wednesday, 12 November 2003 at 18:32:09 -0500, Thor Lancelot Simon wrote:
> On Thu, Nov 13, 2003 at 09:21:53AM +1030, Greg 'groggy' Lehey wrote:
>> On Wednesday, 12 November 2003 at 22:54:29 +0100, wrote:
>>>> On Wednesday, 12 November 2003 at  5:56:34 +0100, wrote:
>>>>> # ls -l /dev/vinum/
>>>>> total 14
>>>>> crw-------  1 root  wheel  108, 262142 Nov 12 05:30 control
>>>> Hmm.  This looks like a victim of the change of major device number.
>>>> Vinum now has major number 162.  Try rm -rf /dev/vinum and see if it
>>>> works like that.
>>> Ok, I figure these numbers are defined somewhere else than /sys/dev/vin=
um or
>>> /sys/sbin/vinum and my kernel being out of sync to the userland is an i=
>>> here.
>> Yes, that's the problem.  You'll need to rebuild vinum(8).
> Why does the vinum executable have special knowledge of the device *numbe=
> for Vinum, rather than using filesystem naming?=20

How else can it create devices dynamically?  I mentioned this in a
separate thread.  Wasn't I clear?

> That seems like a severe bug.


See complete headers for address and phone numbers.

Content-Type: application/pgp-signature
Content-Disposition: inline

Version: GnuPG v1.2.0 (FreeBSD)