wrote:
Il 12/04/2015 23:11, Kelly Miller ha scritto:
I just tried to mount my home folders using NFS as I usually do, but no
matter what I get the error mount.nfs: requested NFS version or transport
protocol is not supported. Did something change in the Alpha of Fedora 22
to suddenly break
No, it isn't.
On Tue, Apr 14, 2015 at 5:22 AM, Benjamin Coddington bcodd...@redhat.com
wrote:
On Mon, 13 Apr 2015, Kelly Miller wrote:
I managed to figure it out. nfs-lock doesn't seem to be starting through
systemd, and I'm not sure why. I can start it using start manually, but
when I
I managed to figure it out. nfs-lock doesn't seem to be starting through
systemd, and I'm not sure why. I can start it using start manually, but
when I try to enable it to start on system load, it claims No file or
directory.
On Mon, Apr 13, 2015 at 6:15 PM, Kelly Miller lightsolphoe
III ti...@math.uh.edu
wrote:
KM == Kelly Miller lightsolphoe...@gmail.com writes:
KM I just tried to mount my home folders using NFS as I usually do, but
KM no matter what I get the error mount.nfs: requested NFS version or
KM transport protocol is not supported. Did something change
I just tried to mount my home folders using NFS as I usually do, but no
matter what I get the error mount.nfs: requested NFS version or transport
protocol is not supported. Did something change in the Alpha of Fedora 22
to suddenly break NFS mounting? I've tried a bunch of mount options, but
I have to admit, I love the claim that systemd is anti-Unix. Isn't the
fact that systemd makes use of systems that exist already, like DBus and
udev, following the Unix philosophy of letting programs worry about their
own problem space? The fact is, any system that is required to do system
