But while you're at it,  migrate to md(4) instead of vn(4), it does
vn(4) will be deprecated RSN.  mdconfig(8) configures the md(4) devices

Poul-Henning


In message <[EMAIL PROTECTED]>, Thierry Herbelot writes:
>thanks a lot : that was it !
>
>Peter Jeremy wrote:
>> 
>> On 2001-Jan-21 10:15:22 +0100, Thierry Herbelot <[EMAIL PROTECTED]> wrote:
>> >I've got a recent current (cvsuped and rebuilt yesterday) on a laptop
>> >and I can't use the vn(4) pseudo-driver : I've compiled it in the kernel
>> >and I've also tried to kldload vn.ko, but I get consistently "vn0c :
>> >device not configured" when I try to use it to mount a locally stored
>> >iso image.
>> 
>> Change "vn0c" to "vn0".  I believe this is the result of PHK's change
>> in mid-December which added cloning to vn.
>> 
>> Peter
>
>-- 
>Thierry Herbelot
>
>
>To Unsubscribe: send mail to [EMAIL PROTECTED]
>with "unsubscribe freebsd-current" in the body of the message
>

--
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED]         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to