Messages in this thread | | | Date | Thu, 21 Mar 1996 12:01:59 -0600 | From | "Andrew C. Esh" <> | Subject | Re: inetd Messages |
| |
Alex Krimkevich wrote: > > Andrew C. Esh writes: > > > > The three answers to this message I saw were not as helpful as I think they > > could have been. I'd rather teach you to fish, than throw you some fluff > > answer, like "Delete some lines out of your inetd.conf". > > I figure, I'll stick with your "fishing" format for now. > Fishing tip #1: When you assume such a patronizing tone, make sure you > know what you are talking about.
But I do. I use Samba.
> > In particular, the "nmbd" is a netbios nameserver. It's part of a package > > called "Samba", > > > > If you hadn't intended to run the samba package, then follow the advice of > > the others who posted answers: Remove all references to /usr/sbin/nmbd from > > your /etc/inetd.conf file. > > Fishing tip #2: Don't you think that if the person is going to run > Samba, he / she would know what nmbd is?
No. The install script puts it there automatically. The mystery to me is how this person's /etc/inetd.conf got updated. I assumed that some distributions are starting to include SMB support by default. This person's situation could have been the result of unsuccessfully trying to install Samba, or some other SMB support. Rather than simply tell them to take it back out (and have them come back and complain that their SMB stuff has stopped working), I assumed that they wanted SMB to be fixed. I tried to help them go forward, not back.
> And if he / she is not > going to, than all your teachings about nmbd and Samba are just a > waste of bandwidth?
I didn't realize there was a bandwidth problem, here. Maybe the solution is to increase the bandwidth, not to decrease the communication.
> For your information, neither /usr/sbin/nmbd nor > its man page get installed unless one chooses them for the installation.
No, mine got installed automatically with the rest of Samba. The only part I had to do by hand is the inetd.conf editing, and I had to check /etc/services. If this person's system di not have either one of those files, then I suppose we should have pointed them toward understanding /etc/inetd.conf, klogd, syslogd, and the logfiles in /var/adm. Then they could decide whether to complete the SMB installation, or remove the partial one. That's specifically why I explained what Samba is: So they can decide if they want it.
> I did not have either of them on my hard drive yet, the error message > quoted in the original post did show up in the syslog. I understand, > it is not very logical, you did not know about those things and got > confused.
I was not confused. I only lacked the information which you are now halfway telling me. What distribution or package is it that adds nmbd to /etc/inetd.conf without also adding /usr/sbin/nmbd? That's what we need to know. That's what appears causing the specific problem.
> But, now, that you know how irrational things can be, you > will think twice before concluding that someone's question is idiotic > and the person did not make his / hers own effort or did not have > enough knowledge to type "man nmbd", won't you?
No, I won't. I assume when someone asks a question, that they want to know enough to solve the problem they are having. I did not assume the person's question was idiotic, simply that they were not aware of what nmbd, SMB, or Samba was. If this person has read the manpage, and tried to execute nmbd, then they would have solved the problem for themselves, which is the goal of "learning to fish".
I suppose I am at fault for the "fluff answer" comment. What I should have tried to convey is that we should try to fully answer the question the first time, rather than have the person come back time and time again because their information inventory hasn't reached critical mass yet. I try to point people toward methods, and sources of information. That way they solve their problems for themselves, and they post fewer questions. That saves bandwidth.
> > Last fishing tip: Install an IRC client, and attach to EFNet. Join the #linux > > channel, and ask questions there. There is a lot of help available there, but one > > caveat: They expect you to have read everything before asking questions. > > > Last fishing tip: One does not improve his own image by showing a > disrespect to those who may not know as much.
Et Tu, Brute.
-- Andrew C. Esh mailto:andrew_esh@cnt.com Computer Network Technology andrewes@mtn.org (finger for PGP key) 6500 Wedgwood Road 612.550.8000 (main) Maple Grove MN 55311 612.550.8229 (direct) http://www.cnt.com - CNT Inc. Home Page http://www.mtn.org/~andrewes - ACE Home Page
| |