Date: Tue, 21 Jul 1998 20:45:41 +0100 From: Brian Somers <brian@Awfulhak.org> To: "Jordan K. Hubbard" <jkh@time.cdrom.com> Cc: Alfred Perlstein <bright@hotjobs.com>, Joel Ray Holveck <joelh@gnu.org>, freebsd-current@FreeBSD.ORG Subject: Re: vn subsystem Message-ID: <199807211945.UAA19823@awfulhak.org> In-Reply-To: Your message of "Mon, 20 Jul 1998 20:33:39 PDT." <27156.900992019@time.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > hrm, not really there was some traffic on the lists a few weeks/months
> > back about it being broken, but that's all i know.
>
> Erm, wonderful. Can we have some commentary from someone who's
> actually proven this either way now? Like I said, my own usage of the
> vn driver has not shown any such instability. If someone who's
> _actually used it_ can now comment on its instability, we'll get a lot
> further.
I have several iso images on disk and a script that vnconfig's the
files then mount -t cd9660's them. The results are then seen as
shares via samba to windows clients (albeit read-only).
This (and ``make release'') has caused me no problems - in -current &
-stable.
> - Jordan
--
Brian <brian@Awfulhak.org>, <brian@FreeBSD.org>, <brian@OpenBSD.org>
<http://www.Awfulhak.org>;
Don't _EVER_ lose your sense of humour....
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199807211945.UAA19823>