Jason W
Group: Members
Posts: 260
Joined: Nov. 2006 |
 |
Posted: Feb. 17 2008,02:34 |
 |
chaostic,
Thank you for your feedback. This extension uses the /etc/init.d/nfs-kernel-server script already present in base DSL, and that script is a little different from the one in Debian Woody. But it does the same thing. Here is the issue. /etc/init.d/portmap of course starts portmap. /etc/init.d/nfs-common starts rpc.statd and (if needed) rpc.lockd but not portmap, though it needs portmap running to work. /etc/init.d/nfs-kernel-server starts rpc.nfsd and rcp.mountd as well as issuing /sbin/exportfs, but it does not start portmap, rpc.statd, or rpc.lockd. On standard Debian, apt-getting nfs-kernel-server has nfs-common as a dependency, which has portmap as a dependency. And if installed, all three get started at boot in Debian without the need to start them manually. But not with a DSL live cd, since DSL lets you decide which services to start. To use nfs-common in DSL, I have to start portmap first if I have rebooted in live mode.
(Actually, I have not been able to get nfs-common to work by itself from the DSL menu since it does not start portmap, but please correct me if I am missing something there.)
I am looking at the nfs-kernel-server script from Woody as well as DSL and they do not start the portmap or nfs-common (rpc.statd rpc.lockd) related services. Debian apparently uses startup scripts to start them. But in DSL they must be started manually on a live cd instance. I am also looking at the nfs script of another distro and it does start portmap and the other nfs scripts. I guess I could have created a wrapper, but I figured since manual configuration is required to use nfs anyway, starting services is small issue.
|
.
DSL Market ,
Great VPS hosting provided by Tektonic
