Summary: | portmap not automatically installed | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Peter Bienstman (RETIRED) <pbienst> |
Component: | [OLD] Unspecified | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | ||
Priority: | High | ||
Version: | 2006.1 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Peter Bienstman (RETIRED)
![]() "it complained" - exactly what complained? A service that was shutting down (unable to stop portmap). I think NFS, but I'm not exactly sure, as once I emerged portmap, the message obviously disappeared. this is on purpose ... the netmount script is written generically so that it works with all network based filesystems and if it detects nfs, it'll require portmap we cant force portmap in RDEPEND as not everyone wants it So why does the netmount script require portmap if it detects NFS, if you say portmap is not needed for NFS? i never said that OK, so the conclusion is that if you want NFS, you should be manually emerging portmap, as the only way portage could know you are using NFS is by looking e.g. at fstab or the kernel config? Perhaps the netmount script could print out a warning saying that portmap should be installed, rather than saying portmap could not be stopped? correct, that is the only way portage could know ... and it gets even more complicated as you can use NFS mounts perfectly fine without portmap if you specify enough options while mounting (i do this on all my machines so i dont need portmap) the warning comes from the baselayout init system, not from the netmount script; but that is because the netmount script adds 'portmap' to depend ... nothing to be done i think and netmount has some more tweaks wrt nfs/portmap |