Re: Unable to use Buster as an nfs client

2020-02-24 Thread Greg Wooledge
On Sat, Feb 22, 2020 at 10:27:41AM -0500, rhkra...@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

Re: Unable to use Buster as an nfs client

2020-02-22 Thread Mark Raynsford
On 2020-02-22T10:27:41 -0500 rhkra...@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

Re: Unable to use Buster as an nfs client

2020-02-22 Thread rhkramer
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

Re: Unable to use Buster as an nfs client

2020-02-22 Thread Mark Raynsford
I've discovered what the problem was... On 2020-02-22T17:39:05 +0300 Reco wrote: > > A leftover from an old installation maybe? It's a new VM, but this actually _was_ the problem, amusingly. I had the following in the bhyve device.map: (hd0) /dev/zvol/storage/vm/peppermint/disk1 (cd0) /storage/

Re: Unable to use Buster as an nfs client

2020-02-22 Thread Reco
On Sat, Feb 22, 2020 at 02:03:55PM +, Mark Raynsford wrote: > On 2020-02-22T16:44:18 +0300 > Reco wrote: > > > > And yet it is a case of running a wrong kernel. > > You see, buster's kernel currently has version 4.19.0-8, but yours > > (4.9.0-9) looks like an outdated stretch one. > > And you

Re: Unable to use Buster as an nfs client

2020-02-22 Thread Mark Raynsford
On 2020-02-22T16:44:18 +0300 Reco wrote: > > And yet it is a case of running a wrong kernel. > You see, buster's kernel currently has version 4.19.0-8, but yours > (4.9.0-9) looks like an outdated stretch one. > And you do have a kernel 4.9, but you don't have the modules for it. > You do have a k

Re: Unable to use Buster as an nfs client

2020-02-22 Thread Reco
Hi. On Sat, Feb 22, 2020 at 12:53:38PM +, Mark Raynsford wrote: > I've rebooted the VM several times, so it's definitely not a case of > running the wrong kernel. > > # uname -a > Linux bloodorange.int.arc7.info 4.9.0-9-amd64 And yet it is a case of running a wrong kernel. You see, b

Unable to use Buster as an nfs client

2020-02-22 Thread Mark Raynsford
Hello! I have a fresh install of Buster installed in a VM. I have the following in /etc/apt/sources.list: deb http://ftp.uk.debian.org/debian/ buster main deb http://ftp.uk.debian.org/debian/ buster-updates main deb http://security.debian.org/debian-security buster/updates main deb-src http://ftp