(again, i'm actually testing this on SLES 11 but i'm guessing the packaging is identical to that of opensuse 11.) currently reading a courseware manual for SLES 11 and, in the chapter on NFS, a table states that NFSv4 server *requires* the name mapping daemon /usr/sbin/rpc.idmapd. fair enough, i guess, except that that daemon is part of the *nfs-client* package. a closer look shows that that dependency is satisfied by simply including nfs-client as a dependency of nfs-kernel-server. that strikes me as an odd packaging -- it suggests you can't install those two NFS packages independently (server will always drag in client). and if /usr/sbin/rpc.idmapd is truly required by the server component, why not just move it to that package? another scheme i've seen is, of course, the "nfs-common" approach, required by either package. picky, yes, but it just seems non-intuitive by stating that a particular file is *required* by a package, only to satisfy that requirement by placing that file in a *different* package, then requiring that entire other package (even if the packages are as closely related as NFS client and NFS server). or am i misreading something? rday -- ======================================================================== Robert P. J. Day Waterloo, Ontario, CANADA Linux Consulting, Training and Annoying Kernel Pedantry. Web page: http://crashcourse.ca Twitter: http://twitter.com/rpjday ======================================================================== -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org