Yea! That's one boot problem out of 5 completely solved! I ran dpkg --status nfs-common as suggested and found the name of the package, which was nfs-common, amazingly enough. I started dselect and went right to the select screen where I located the nfs-common package and marked it for purge. This led me to a dependancy resolution screen where I also marked the nfs-server to be purged. I accepted these changes and let dselect remove the packages, which it did without error or complaint. Finally, I rebooted and everything works as it did before, except for the lack of the rpc.statd error messages.
Thanks to Jeremy Gaddis, I feel like there might be hope to resolve the other boot problems on my new linux installations. - g -----Original Message----- From: Jeremy Gaddis [mailto:[EMAIL PROTECTED] Sent: Saturday, July 14, 2001 4:36 PM To: [EMAIL PROTECTED] Cc: Debian-User (E-mail) Subject: Re: NFS related error; do I need NFS? On Sat, 14 Jul 2001, Gladimir wrote: > 1) Do I need NFS on this linux machine? The general rule is if (a) you don't know what a service is, or (b) you don't know if you need it, you probably don't. If you did need it, you'd know. Disable rpc.statd, rpc.nfsd, portmap(per), and any other RPC-related daemons that might be running. Running unneeded rpc.* services has caused more than one machine to get compromised. > 2a) If so, how do I make this error go away? Uninstall the package that provides rpc.statd. > 2b) If not, what is the process for removing the nfs-common scripts from the > system initialization? Remove the packages that provide rpc.statd, rpc.mountd, portmap, and the other RPC services that are installed. I don't recall the package names right off-hand, but it's nothing that `dpkg --status filename` won't tell you. HTH. j. -- Jeremy L. Gaddis <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
