> From: Alan Cox <alan@lxorguk.ukuu.org.uk>
> Date: Sun, 28 May 2000 10:51:31 +0100 (BST)
> Subject: Re: Linux 2.2.16pre5 - NFS?!
>
> > > They have nothing to do with NFS. So its even stranger
> >
> > Newer knfsd uses the netlink device (not the socket :-()_to ask mountd again
> > after reboots for new requests.
>
> The netlink device is obsolete. Thats silly to say the least
>
> > Normally that should be only supported by the knfsd patches various
> > distributions ship though. But maybe the newer user land knfsd breaks
> > without netlink ?
>
> The more I hear the more it sounds that way
Here's what I found in /etc/messages - maybe someone's interested:
------------- 8< ----------------
Apr 7 20:31:11 fuckup automount[159]: starting automounter version 3.1.3,
path
= /misc, maptype = file, mapname = /etc/auto.misc
Apr 7 20:31:11 fuckup automount[159]: Map argc = 1
Apr 7 20:31:11 fuckup automount[159]: Map argv[0] = /etc/auto.misc
Apr 7 20:31:11 fuckup automount[159]: using kernel protocol version 3
Apr 7 20:31:12 fuckup modprobe: modprobe: Can't locate module
char-major-36
Apr 7 20:31:12 fuckup mountd[171]: Failed to open /dev/nfsd_netlink: No
such de
vice!
------------- 8< ----------------
and... conf.modules for char-major 36:
alias char-major-36 netlink_dev
Anyway, I don't understand why mountd needs netlink_dev :-(
I'd be happy to provide you with more information if needed.
Daniel
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed May 31 2000 - 21:00:19 EST