From owner-freebsd-questions Thu Feb 1 19:53:44 2001 Delivered-To: freebsd-questions@freebsd.org Received: from nameserver.austclear.com.au (nameserver.austclear.com.au [192.83.119.132]) by hub.freebsd.org (Postfix) with ESMTP id 403E137B503 for ; Thu, 1 Feb 2001 19:53:24 -0800 (PST) Received: from tungsten.austclear.com.au (tungsten.austclear.com.au [192.168.70.1]) by nameserver.austclear.com.au (8.9.3/8.9.3) with ESMTP id OAA04526; Fri, 2 Feb 2001 14:53:23 +1100 (EST) Received: from tungsten (tungsten [192.168.70.1]) by tungsten.austclear.com.au (8.9.3/8.9.3) with ESMTP id OAA10465; Fri, 2 Feb 2001 14:53:22 +1100 (EST) Message-Id: <200102020353.OAA10465@tungsten.austclear.com.au> X-Mailer: exmh version 2.1.1 10/15/1999 To: Greg Lehey Cc: freebsd-questions@FreeBSD.ORG Subject: Re: installing onto vinum In-Reply-To: Your message of "Fri, 02 Feb 2001 12:58:11 +1030." <20010202125811.G82163@wantadilla.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 02 Feb 2001 14:53:22 +1100 From: Tony Landells Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I can't reproduce this. It should start an editor for you. Can you > show me the vinum_history output? Well, given that without mounting /var I have no vinum_history... I've done it again (rebooted to single user, started /bin/sh, invoked "vinum", and typed "create") and this time it's: # vinum vinum -> create Can't open (null): no such file or directory viunum -> quit Note that there is no editor session, so it doesn't really put much in vinum_history anyway. After I mounted /var and did the same thing, I got: # vinum vinum -> create /usr/bin/vi: not found Can't edit config: status 32512 vinum -> quit and vinum_history had: 2 Feb 2001 14:28:54.299319 *** vinum started *** 2 Feb 2001 14:28:56.178572 create 2 Feb 2001 14:29:09.308706 quit and /var/log/messages was empty (probably because it's single user mode and syslog isn't running...). > It would almost be worthwhile writing a script to turn disklabel > output into a Vinum config file. Now there's an idea... > > This is the stuff I was telling you about where I kept getting: > > vinum -> create > > 1: drive d1 device /dev/ad2s1d > > ** 1: Invalid argument > > Hmm. Interesting. Again, the /var/log/messages and vinum_history > contents might give a clue. Again, /var/log/messages doesn't have anything. Vinum_history has 2 Feb 2001 14:36:40.563941 *** vinum started *** 2 Feb 2001 14:36:46.293202 create drive d1 device /dev/ad2s1d 2 Feb 2001 14:36:57.939402 *** Created devices *** 2 Feb 2001 14:37:06.273407 quit It works if I use "create -f". Cheers, Tony -- Tony Landells Senior Network Engineer Ph: +61 3 9677 9319 Australian Clearing Services Pty Ltd Fax: +61 3 9677 9355 Level 4, Rialto North Tower 525 Collins Street Melbourne VIC 3000 Australia To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message