From owner-freebsd-questions@FreeBSD.ORG Wed Apr 13 18:23:36 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 911AD16A4CE for ; Wed, 13 Apr 2005 18:23:36 +0000 (GMT) Received: from april.chuckr.org (april.chuckr.org [66.92.151.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4E48A43D39 for ; Wed, 13 Apr 2005 18:23:36 +0000 (GMT) (envelope-from chuckr@chuckr.org) Received: from [66.92.151.195] (july.chuckr.org [66.92.151.195]) by april.chuckr.org (Postfix) with ESMTP id 7A50611F46 for ; Wed, 13 Apr 2005 14:16:52 -0400 (EDT) Message-ID: <425D6395.4050504@chuckr.org> Date: Wed, 13 Apr 2005 18:23:17 +0000 From: Chuck Robey User-Agent: Mozilla Thunderbird 1.0 (X11/20050316) X-Accept-Language: en-us, en MIME-Version: 1.0 To: questions@freebsd.org References: <425C317E.6040807@chuckr.org> <444qea4ybi.fsf@be-well.ilk.org> In-Reply-To: <444qea4ybi.fsf@be-well.ilk.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: vinum setup X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Apr 2005 18:23:36 -0000 Lowell Gilbert wrote: > Chuck Robey writes: > > >>Sorry, I'm having a miserable time trying to get vinum working on my >>amd64 system. Vinum tells me that it can't load the kernel ("vinum: >>Kernel module not available: No such file or directory"). Gvinum >>simply refuses to take any commands at all. I tried looking at >>/boot/kernel, naturally didn't find any such module, so I wanted to >>see about building one, but I can't get "device vinum" to pass >>config's purview. >> >>Does vinum work on amd64's? > > > Shouldn't that be gvinum? when I wrote that, I didn't understand the difference between vinum and gvinum. I do now, but I tell you, gvinum sure as heck needs documentation. Fixing the resetconfig command would be a really good thing, too.