From 852ad1b3553fd307fda4563acb512a5074cfa41c Mon Sep 17 00:00:00 2001 From: Glen Barber Date: Sun, 24 Jul 2011 21:27:50 +0000 Subject: [PATCH] The vn(4) device has been replaced with the md(4) device. Update the Release Engineering article accordingly. Submitted by: eadler (via email) Approved by: jkois (mentor) --- en_US.ISO8859-1/articles/releng/article.sgml | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/en_US.ISO8859-1/articles/releng/article.sgml b/en_US.ISO8859-1/articles/releng/article.sgml index 5fa66a3b26..a0fb85a69d 100644 --- a/en_US.ISO8859-1/articles/releng/article.sgml +++ b/en_US.ISO8859-1/articles/releng/article.sgml @@ -560,11 +560,9 @@ applicable. fast machine and access to a source repository. (That should be everyone, since we offer anonymous CVS! See The Handbook for details.) The only special requirement is - that the &man.vn.4; device must be available. (On -CURRENT, this - device has been replaced by the new &man.md.4; - memory disk driver.) If the + that the &man.md.4; device must be available. If the device is not loaded into your kernel, then the kernel module - should be automatically loaded when &man.vnconfig.8; is executed + should be automatically loaded when &man.mdconfig.8; is executed during the boot media creation phase. All of the tools necessary to build a release are available from the CVS repository in src/release. These tools aim to provide a