confusing statement regarding newfs(8) on vinum(4) volumes. Fix: Patch attached with submission follows:
> confusing statement regarding newfs(8) on vinum(4) volumes. > > > diff -r -u handbook.orig/vinum-object-naming.html > handbook/vinum-object-naming.html > --- handbook.orig/vinum-object-naming.html 2008-03-22 05:43:54.000000000 > +0100 > +++ handbook/vinum-object-naming.html 2008-03-24 16:27:00.000000000 +0100 > @@ -157,15 +157,6 @@ > Vinum volume might be called <tt > class="FILENAME">/dev/gvinum/concat</tt>, a name which > has no relationship with a partition name.</p> > > -<p>Normally, <a > href="http://www.FreeBSD.org/cgi/man.cgi?query=newfs&sektion=8"><span > -class="CITEREFENTRY"><span > class="REFENTRYTITLE">newfs</span>(8)</span></a> interprets > -the name of the disk and complains if it cannot understand it. For > example:</p> > - > -<pre class="SCREEN"> > -<samp class="PROMPT">#</samp> <kbd class="USERINPUT">newfs > /dev/gvinum/concat</kbd> > -newfs: /dev/gvinum/concat: can't figure out file system partition > -</pre> > - > <p>In order to create a file system on this volume, use <a > href="http://www.FreeBSD.org/cgi/man.cgi?query=newfs&sektion=8"><span > class="CITEREFENTRY"><span > class="REFENTRYTITLE">newfs</span>(8)</span></a>:</p> > I dont see the confusing part actually; I think this tells what we should know in case we encounter such a thing right I dont see any reference to vinum(4) or anything... Can you explain this a bit more? I think the change like this isn't needed. Thanks, remko -- /"\ Best regards, | remko@FreeBSD.org \ / Remko Lodder | remko@EFnet X http://www.evilcoder.org/ | / \ ASCII Ribbon Campaign | Against HTML Mail and News
Well, now the minor update is not that minor. Find attached a patch file. This patch -> deprecates: handbook/vinum-object-naming.html handbook/vinum-access-bottlenecks.html handbook/vinum/vinum-concat.png handbook/vinum/vinum-raid10-vol.png handbook/vinum/vinum-simple-vol.png handbook/vinum/vinum-striped.png handbook/vinum/vinum-mirrored-vol.png handbook/vinum/vinum-raid5-org.png handbook/vinum/vinum-striped-vol.png creates: handbook/vinum-disk-performance-issues.html handbook.new/vinum/vinum-concat.png handbook.new/vinum/vinum-raid01.png handbook.new/vinum/vinum-raid10.png handbook.new/vinum/vinum-simple.png handbook.new/vinum/vinum-raid0.png handbook.new/vinum/vinum-raid1.png handbook.new/vinum/vinum-raid5.png updates: all remaining handbook/vinum-*.html handbook/raid.html handbook/virtualization.html. I think I cannot attach the new PNG files here. Please, advise how to submit them. . ____________________________________________________________________________________ You rock. That's why Blockbuster's offering you one month of Blockbuster Total Access, No Cost. http://tc.deals.yahoo.com/tc/blockbuster/text5.com
the new PNG files are here: http://del.ufrj.br/~federico.besnard/test/vinum_png.tgz Fico. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Hi, You've submitted a rather large patch here; however, there is no explanation why you feel we should deprecate most of the chapter. Is there something seriously wrong with it? Also, the patch is not in SGML format and will not apply to the handbook like this; could you submit a new patch against the chapter.sgml file? You may find more information here: http://www.freebsd.org/docproj/ Thanks, -- Tom Rhodes
State Changed From-To: open->feedback Switch to feedback as requested in my follow up. Thanks!
Hi Tom, Greg Lehey work writing VINUM is outstanding. However, the manual does not match the quality of the source code. Some highlights: 1) The definition of RAID-10 given in 21.6.4 is wrong. It actually describes RAID-01. I added RAID-10, for the sake of completeness. http://en.wikipedia.org/wiki/Nested_RAID_levels 2) VINUM was originally written for Release 4.x, the manual needed updates to accommodate most recent Releases and GEOM framework. Same stands for man pages. This patch separates clearly 4.x from > 5.x. Also, all misleading embedded-guidances have been treated. 3) This patch improves the whole section text and figures. 4) Examples have been also improved. Configuration files and <gvinum list> output are shown. I will appreciate any feedback if there is a committer, familiar with VINUM, available for reading (and compare to the actual version) the proposed update (shown in this link for the sake of simplicity and for few fellows who requested it): http://www.del.ufrj.br/~federico.besnard/FreeBSD/apocrypha/handbook/vinum-vinum.html I will work on the SGML version only if this patch makes sense to someone with power for committing the patch. I have seen recent developers' activity on the GEOM side, it might be the case of not having a need for VINUM any longer. So this work on the handbook is not only low priority but useless. I am not sure, I am not writing code for GEOM nor tracking all activity there. Please advise.
The vinum chapter was removed some time ago. No need to keep this PR open any longer.