Kostik wrote:
> On Sun, Oct 26, 2014 at 06:42:29PM -0400, Rick Macklem wrote:
> > Worked fine for me. Do you mind if I commit this or would you
> > rather
> > do it.
>
> I committed the change as r273727.
>
> One issue with the commit is the specified MFC. The change will
> compile
> on stable/10
On Sun, Oct 26, 2014 at 06:42:29PM -0400, Rick Macklem wrote:
> Worked fine for me. Do you mind if I commit this or would you rather
> do it.
I committed the change as r273727.
One issue with the commit is the specified MFC. The change will compile
on stable/10, but as far as I remember the state
Kostik wrote:
> On Sun, Oct 26, 2014 at 08:14:05AM -0400, Rick Macklem wrote:
> > Beeblebrox wrote:
> > > Sorry guys, we have a considerable time-zone difference.
> > >
> > > >> It appears that the sysctl must be set before mountd, nfsd are
> > > >> started to take effect. (Or they must be restart
Beeblebrox wrote:
Dan:
>> to get pxeboot to do v3, add to /boot/loader.conf
>> boot-nfsroot-options="nfsv3"
>Thanks. I'm using grub for the bootloader and menu, and comparable entry
>should be:
>set kfreebsd.boot.nfsroot.options=3D"nfsv3"
>It does not work however. mount_root hangs for a while the
Beeblebrox wrote:
> Dan:
> >> to get pxeboot to do v3, add to /boot/loader.conf
> >> boot-nfsroot-options=“nfsv3”
> Thanks. I'm using grub for the bootloader and menu, and comparable
> entry should be:
> set kfreebsd.boot.nfsroot.options="nfsv3"
> It does not work however. mount_root hangs for a wh
Dan:
>> to get pxeboot to do v3, add to /boot/loader.conf
>> boot-nfsroot-options=“nfsv3”
Thanks. I'm using grub for the bootloader and menu, and comparable entry should
be:
set kfreebsd.boot.nfsroot.options="nfsv3"
It does not work however. mount_root hangs for a while then reverts to V2. I've
a
On Sun, Oct 26, 2014 at 08:14:05AM -0400, Rick Macklem wrote:
> Beeblebrox wrote:
> > Sorry guys, we have a considerable time-zone difference.
> >
> > >> It appears that the sysctl must be set before mountd, nfsd are
> > >> started to take effect. (Or they must be restarted after it is
> > >> set.
Beeblebrox wrote:
> Sorry guys, we have a considerable time-zone difference.
>
> >> It appears that the sysctl must be set before mountd, nfsd are
> >> started to take effect. (Or they must be restarted after it is
> >> set.)
> I had apparently re-started nfsd but not mountd. This time
> re-starti
Beeblebrox wrote:
> Sorry guys, we have a considerable time-zone difference.
>
> >> It appears that the sysctl must be set before mountd, nfsd are
> >> started to take effect. (Or they must be restarted after it is
> >> set.)
> I had apparently re-started nfsd but not mountd. This time
> re-starti
> On Oct 26, 2014, at 10:48 AM, Beeblebrox wrote:
>
> Sorry guys, we have a considerable time-zone difference.
>
>>> It appears that the sysctl must be set before mountd, nfsd are
>>> started to take effect. (Or they must be restarted after it is set.)
> I had apparently re-started nfsd but not
Sorry guys, we have a considerable time-zone difference.
>> It appears that the sysctl must be set before mountd, nfsd are
>> started to take effect. (Or they must be restarted after it is set.)
I had apparently re-started nfsd but not mountd. This time re-starting both and
launching the PXE clie
Russell L. Carter wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
>
> On 10/25/14 09:58, Beeblebrox wrote:
> > Hi Russ,
> >
> >>> PXE client's /etc/fstab is: 92.168.2.1:/data/amd64 / nfs
> >>> ro 0 0 192.168.2.1:/usr/local /usr/local nfs ro 0
> >>
> >> Possibly
Russell L. Carter wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
>
> On 10/25/14 09:58, Beeblebrox wrote:
> > Hi Russ,
> >
> >>> PXE client's /etc/fstab is: 92.168.2.1:/data/amd64 / nfs
> >>> ro 0 0 192.168.2.1:/usr/local /usr/local nfs ro 0
> >>
> >> Possibly
Russell L. Carter wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
>
> On 10/25/14 03:07, Beeblebrox wrote:
> > * I can't get the NFS server to run V4 only. I have: sysctl
> > vfs.nfsd.server_min_nfsvers=4
> >
>
> [...]
>
> > PXE client's /etc/fstab is: 92.168.2.1:/data/amd64 /
Beeblebrox wrote:
> * I can't get the NFS server to run V4 only. I have:
> sysctl vfs.nfsd.server_min_nfsvers=4
>
Hmm. With this set the NFS server shouldn't accept V2, 3
RPCs. The mount will work, since that is done by the Mount
protocol (mountd), but the client should be saying "server
not respo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/25/14 09:58, Beeblebrox wrote:
> Hi Russ,
>
>>> PXE client's /etc/fstab is: 92.168.2.1:/data/amd64 / nfs
>>> ro 0 0 192.168.2.1:/usr/local /usr/local nfs ro 0
>>
>> Possibly need to arrange for mount_nfs to see -o nfsv4 (I
Hi Russ,
> > PXE client's /etc/fstab is: 92.168.2.1:/data/amd64 / nfs
> > ro 0 0 192.168.2.1:/usr/local /usr/local nfs ro 0
>
> Possibly need to arrange for mount_nfs to see -o nfsv4
> (I use mount_nfs -o nfsv4,minorversion=1)
Yeah, that would work very likely and thanks.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/25/14 03:07, Beeblebrox wrote:
> * I can't get the NFS server to run V4 only. I have: sysctl
> vfs.nfsd.server_min_nfsvers=4
>
[...]
> PXE client's /etc/fstab is: 92.168.2.1:/data/amd64 / nfs
> ro 0 0 192.168.2.1:/usr/local
18 matches
Mail list logo
