alan@lxorguk.ukuu.org.uk said:
> > 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
Yeah - I know. We've been here before. It was a proof-of-concept hack - I
wasn't interested in the details; just wanted to know if people approved of
the callback idea at all - and I know better than to expect people to
respond unless they're actually shown code, so I threw together a patch:
http://kernelnotes.org/lnxlists/linux-kernel/lk_9909_01/msg00362.html
In spite of the fact that I said...
> This is work in progress, but I'm posting it for comments before I go and
> round up the loose ends.
... I received no comments, but it got merged into the next knfsd release
as-is. There followed a flurry of patches to address some of the corner
cases which I hadn't even attempted to handle correctly, but never to
switch it to use a netlink socket.
I haven't yet been able to make the time to fix it properly, and to add
automatic expiry of the kernel's mount entries as I'd like, because I've
been busy with what my employer (at least until Friday) considers to be
'real work'.
Perhaps my new employer will ask me to spend a few days on it. We'll see.
-- dwmw2- 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:26 EST