Document the diskid automatic label class.
While there, also document the glabel "native" labels and explain why there are additional nodes created for nested GEOM classes. Reminded by: jmg
This commit is contained in:
parent
4c524a4287
commit
e74d21571f
Notes:
svn2git
2020-12-20 02:59:44 +00:00
svn path=/head/; revision=266972
@ -130,8 +130,26 @@ GPT UUIDs (directory
|
|||||||
.Pa /dev/gptid/ ) .
|
.Pa /dev/gptid/ ) .
|
||||||
.El
|
.El
|
||||||
.Pp
|
.Pp
|
||||||
Generic labels are created in the directory
|
Generic disk ID strings are exported as labels in the format
|
||||||
.Pa /dev/label/ .
|
.Pa /dev/diskid/GEOM_CLASS-ident
|
||||||
|
e.g.
|
||||||
|
.Pa /dev/diskid/DISK-6QG3Z026 .
|
||||||
|
.Pp
|
||||||
|
Generic labels created and managed solely by
|
||||||
|
.Xr glabel 8
|
||||||
|
are created in the
|
||||||
|
.Pa /dev/label/
|
||||||
|
directory.
|
||||||
|
.Pp
|
||||||
|
Note that for all label types, nested GEOM classes will cause additional
|
||||||
|
device nodes to be created, with context-specific data appended to their
|
||||||
|
names. E.g. for every node like
|
||||||
|
.Pa /dev/label/bigdisk
|
||||||
|
there will be additional entries for any partitions which the device
|
||||||
|
contains, like
|
||||||
|
.Pa /dev/label/bigdiskp1
|
||||||
|
and
|
||||||
|
.Pa /dev/label/bigdiskp1a .
|
||||||
.Pp
|
.Pp
|
||||||
The first argument to
|
The first argument to
|
||||||
.Nm
|
.Nm
|
||||||
|
Loading…
Reference in New Issue
Block a user