Groups > linux.debian.user > #219328

Re: Unable to use Buster as an nfs client

From	Mark Raynsford <list+org.debian@io7m.com>
Newsgroups	linux.debian.user
Subject	Re: Unable to use Buster as an nfs client
Date	2020-02-22 16:40 +0100
Message-ID	<zCF2O-2jP-7@gated-at.bofh.it> (permalink)
References	<zCCHD-12K-1@gated-at.bofh.it> <zCE6K-1KR-15@gated-at.bofh.it> <zCEgp-1Ol-3@gated-at.bofh.it> <zCET7-2gG-1@gated-at.bofh.it>
Organization	io7m.com

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

On 2020-02-22T10:27:41 -0500
rhkramer@gmail.com wrote:

> On Saturday, February 22, 2020 09:42:32 AM Mark Raynsford wrote:
> > It's a new VM, but this actually _was_ the problem, amusingly. I had
> > the following in the bhyve device.map:  
> 
> I sometimes get too curious, but is bhyve a typo, or something real?  (I tried 
> locate on my system, didn't find anything.)

It's a BSD hypervisor:

  https://bhyve.org/

The host machine is a rather large thing running FreeBSD, with a mix of
Debian, OpenBSD, and FreeBSD guests.

-- 
Mark Raynsford | http://www.io7m.com

Thread

Unable to use Buster as an nfs client Mark Raynsford <list+org.debian@io7m.com> - 2020-02-22 14:10 +0100
  Re: Unable to use Buster as an nfs client Reco <recoverym4n@enotuniq.net> - 2020-02-22 14:50 +0100
    Re: Unable to use Buster as an nfs client Mark Raynsford <list+org.debian@io7m.com> - 2020-02-22 15:10 +0100
      Re: Unable to use Buster as an nfs client Reco <recoverym4n@enotuniq.net> - 2020-02-22 15:40 +0100
        Re: Unable to use Buster as an nfs client Mark Raynsford <list+org.debian@io7m.com> - 2020-02-22 15:50 +0100
          Re: Unable to use Buster as an nfs client rhkramer@gmail.com - 2020-02-22 16:30 +0100
            Re: Unable to use Buster as an nfs client Mark Raynsford <list+org.debian@io7m.com> - 2020-02-22 16:40 +0100
            Re: Unable to use Buster as an nfs client Greg Wooledge <wooledg@eeg.ccf.org> - 2020-02-24 15:40 +0100

csiph-web