From 272a7ecfbddcadcd6f9c4ac98786c7c010b38585 Mon Sep 17 00:00:00 2001 From: Sascha Wildner Date: Sat, 10 Mar 2018 09:16:00 +0100 Subject: [PATCH] lsvfs.1: Explain why lsvfs(1) shows 2 references to UFS on encrypted root. While here, fix two cases where a new sentence didn't start on a new line. Idea-by: Aaron LI --- usr.bin/lsvfs/lsvfs.1 | 22 ++++++++++++++++++---- 1 file changed, 18 insertions(+), 4 deletions(-) diff --git a/usr.bin/lsvfs/lsvfs.1 b/usr.bin/lsvfs/lsvfs.1 index 84b1cbbf96..e660409624 100644 --- a/usr.bin/lsvfs/lsvfs.1 +++ b/usr.bin/lsvfs/lsvfs.1 @@ -1,9 +1,8 @@ .\" $FreeBSD: src/usr.bin/lsvfs/lsvfs.1,v 1.7.2.3 2003/02/24 22:37:42 trhodes Exp $ -.\" $DragonFly: src/usr.bin/lsvfs/lsvfs.1,v 1.2 2003/06/17 04:29:28 dillon Exp $ .\" Garrett A. Wollman, September 1994 .\" This file is in the public domain. .\" -.Dd March 16, 1995 +.Dd March 10, 2018 .Dt LSVFS 1 .Os .Sh NAME @@ -16,11 +15,13 @@ The .Nm command lists information about the currently loaded virtual file system -modules. When +modules. +When .Ar vfsname arguments are given, .Nm -lists information about the specified VFS modules. Otherwise, +lists information about the specified VFS modules. +Otherwise, .Nm lists all currently loaded modules. The information is as follows: @@ -49,3 +50,16 @@ A .Nm command appeared in .Fx 2.0 . +.Sh BUGS +In +.Dx Ap s +encrypted root setup, +.Nm +will show at least 2 references to +.Dq ufs +even though just +.Pa /boot +seems to be mounted. +The second reference is the initial root from the +.Pa /boot/kernel/initrd.img.gz +image. -- 2.11.4.GIT