Netstd reorganization
Can someone point me to some documentation or clue me into the netstd reorganization? I understand that netstd was broken down into individual components, but I sort of miss the old way, simply because I never learned all of what was in netstd. When netstd asked if I wanted to disable the r services, I just said yes. Now I'm not sure of what services I actually *need* and which ones I don't and I'd like to close down as many ports as possible. Any advice on that score? TIA. Regards, . Randy -- If the current stylistic distinctions between open-source and commercial software persist, an open-software revolution could lead to yet another divide between haves and have-nots: those with the skills and connections to make use of free software, and those who must pay high prices for increasingly dated commercial offerings. -- Scientific American
Re: Netstd reorganization
On Sun, Dec 05, 1999 at 02:31:04PM +, Randy Edwards wrote: Can someone point me to some documentation or clue me into the netstd reorganization? I understand that netstd was broken down into individual components, but I sort of miss the old way, simply because I never learned all of what was in netstd. Whatever the netstd package now depends on is what used to be in netstd. When netstd asked if I wanted to disable the r services, I just said yes. Now I'm not sure of what services I actually *need* and which ones I don't and I'd like to close down as many ports as possible. Any advice on that score? TIA. The ones you need are the ones you use. The rest can probably be gotten rid of. Since you don't use the r services, you can get rid of any package netstd depends on that begins with the letter r, with the possible exception of routed (which is not an r service). Beyond that, determine what you don't use and remove it. lsof with the -i option can tell you which ports are open, and by which processes. Note that ports open from inetd are configured in /etc/inetd.conf, and you should remove the offending lines from that file (and the program responsible for those lines). -- finger for GPG public key. 29 Nov 1999 - new email address added to gpg key pgpv40nXZDkER.pgp Description: PGP signature
Re: Netstd reorganization
On Sun, Dec 05, 1999 at 11:53:45AM -0800, George Bonser wrote: On Sun, 5 Dec 1999, Brad wrote: Whatever the netstd package now depends on is what used to be in netstd. But the dependancies need to change. I want rwho on one system but I do NOT want rwhod on it. I want rsh but I do NOT want rshd. Separating the clients from the daemons would be a good idea ... netstd-client and netstd-server would be better. It appears you can easily install rsh-client without rsh-server. As for rwho without rwhod, rwho depends on rwhod. If rwho doesn't actually need rwhod, file a bug report on rwho. You don't actually need netstd installed at all (any packages that depend on it and not whichever components are needed are broken and should be fixed soon). The ones you need are the ones you use. The rest can probably be gotten rid of. Since you don't use the r services, you can get rid of any package netstd depends on that begins with the letter r, with the possible exception of routed (which is not an r service). Beyond that, determine what you don't use and remove it. It should check to see if you have ssh installed and ask if you want to use ssh for those services. Which It? BTW, when installing ssh (from potato at least) it detects if you have rsh-server | non-ssl telnetd installed and advises you that they are insecure. -- finger for GPG public key. 29 Nov 1999 - new email address added to gpg key pgpp3EGiSfX7R.pgp Description: PGP signature
Re: Netstd reorganization
George Bonser writes: But the dependancies need to change. I want rwho on one system but I do NOT want rwhod on it. I want rsh but I do NOT want rshd. Separating the clients from the daemons would be a good idea ... netstd-client and netstd-server would be better. All those services used to be in netstd. The decision was made to get rid of it and break them out into seperate packages. That's fine for new installs, but what about upgrades? If netstd just vanished the stuff that was in it would never get upgraded, since those new packages containing stuff broken out from netstd were never installed. The solution is a dummy netstd package. It contains nothing and nothing depends on it, but it depends on the packages containing stuff that used to be in it. The result is that when you upgrade you get the new empty netstd and it pulls in the new packages that contain stuff it used to contain. Once you have upgraded netstd you can remove it. The description says: Legacy package that you should remove. This package exists only to provide smooth upgrades. Please remove it. -- John Hasler [EMAIL PROTECTED] Dancing Horse Hill Elmwood, Wisconsin
