Date: Tue, 25 Jun 2013 11:47:53 -0600 (MDT) From: Warren Block <wblock@wonkity.com> To: Frank Leonhardt <frank2@fjl.co.uk> Cc: freebsd-doc@freebsd.org Subject: Re: Handbook obsolescence scan: "The vinum Volume Manager" Message-ID: <alpine.BSF.2.00.1306251143080.65313@wonkity.com> In-Reply-To: <51C9CD3B.4090001@fjl.co.uk> References: <alpine.BSF.2.00.1306250933560.64224@wonkity.com> <51C9CD3B.4090001@fjl.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 25 Jun 2013, Frank Leonhardt wrote: > On 25/06/2013 16:43, Warren Block wrote: >> Next on the list of potentially outdated things in the Handbook: "The vinum >> Volume Manager", a whole chapter on vinum. Actually, it is really now about >> gvinum. >> >> Are there any situations where new users should be advised to use gvinum >> rather than ZFS or gconcat/gstripe/gmirror? >> >> What reasons are there for this chapter to remain in the Handbook given the >> newer, simpler alternatives? >> >> If the information should remain, why should it be separate from the GEOM >> chapter? > > I remember reading this and the gmirror stuff at the same time and wondering > what it was all about. Whilst I'm generally not in favour of chucking stuff > out of a manual if it exists on the ground, at the very least this could do > with a sanity warning. At the time I had no way of knowing whether one method > or the other was deprecated. I suppose I made a lucky guess. That is exactly the problem with old information. gvinum still works, but there is little reason to recommend it over the newer solutions. Rather than just removing this chapter, it could be converted to a separate article, along with an added introduction about when it was removed from the Handbook and why.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1306251143080.65313>