Date: Mon, 8 Nov 2004 21:55:51 +1100 (EST) From: Andy Farkas <andy@bradfieldprichard.com.au> To: =?iso-8859-1?q?Dag-Erling_Sm=F8rgrav?= <des@des.no> Cc: freebsd-current@freebsd.org Subject: Re: gvinum remains broken in 5.3-RELEASE? Message-ID: <20041108215243.O59160@bpgate.speednet.com.au> In-Reply-To: <xzphdo0ybwr.fsf@dwp.des.no> References: <20041107003413.GQ24507@wantadilla.lemis.com> <200411071124.35056.msch@snafu.de><xzphdo0ybwr.fsf@dwp.des.no>
next in thread | previous in thread | raw e-mail | index | archive | help
This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --0-808265141-1099911351=:59160 Content-Type: TEXT/PLAIN; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE On Mon, 8 Nov 2004, [iso-8859-1] Dag-Erling Sm=F8rgrav wrote: > Andy Farkas <andy@bradfieldprichard.com.au> writes: >> # gvinum load >> unknown command 'load' > > vinum(8) has no 'load' command, so why do you expect gvinum(8) to have > one? Because manually typing 'gtripe load' after 'boot -s' is the only way=20 I can start my workstation. >> # gvinum unload >> unknown command 'unload' > > vinum(8) has no 'unload' command, so why do you expect gvinum(8) to > have one? Because its the opposite of 'gstripe load'. - andyf --0-808265141-1099911351=:59160--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041108215243.O59160>