Bug 78275

Summary: [patch] Keyword size needs to be changed to length in vinum(8) manpage.
Product: Documentation Reporter: Loren M. Lang <lorenl>
Component: Books & ArticlesAssignee: freebsd-doc (Nobody) <doc>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Latest   
Hardware: Any   
OS: Any   
Attachments:
Description Flags
vinum.patch none

Description Loren M. Lang 2005-03-02 06:10:19 UTC 
      Several places in the examples used in the vinum(8) man page, the keyword size is used on the subdisk lines when it should be length.

Fix: 

Change size to length on lines like
sd name vinum0.p0.s0 drive vinumdrive0 size 0
sd name vinum0.p0.s1 drive vinumdrive1 size 0
sd name vinum0.p0.s3 drive vinumdrive3 size 0
..
Should read:
sd name vinum0.p0.s0 drive vinumdrive0 length 0
..
How-To-Repeat:       Follow one of the examples under SIMPLIFIED CONFIGURATION and see vinum create complain when it tries to read it.
Comment 1 Loren M. Lang 2005-06-07 13:47:40 UTC 
Here is a patch to fix it.

-- 
I sense much NT in you.
NT leads to Bluescreen.
Bluescreen leads to downtime.
Downtime leads to suffering.
NT is the path to the darkside.
Powerful Unix is.

Public Key: ftp://ftp.tallye.com/pub/lorenl_pubkey.asc
Fingerprint: CEE1 AAE2 F66C 59B5 34CA  C415 6D35 E847 0118 A3D2
Comment 2 Remko Lodder freebsd_committer freebsd_triage 2005-12-25 10:00:00 UTC 
State Changed
From-To: open->closed

Actually the printed output is correct.  When looking 
into the commands.c file (used for vinum) you will 
see a lot of lines with: 

commands.c:         printf("    sd name %s.p0.s%d drive %s size %lldbn", 

those statements, which tells me the output should be correct. 
On the other hand, the length statements are used to configure 
vinum from a file. 

I do not believe we should correct this, but thanks 
for taking the time to investigate/patch and report!