260 lines
10 KiB
HTML
260 lines
10 KiB
HTML
<!--startcut ======================================================= -->
|
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
|
<html>
|
|
<head>
|
|
<META NAME="generator" CONTENT="lgazmail v1.1H.i">
|
|
<TITLE>The Answer Guy 37: setting up an ISP to serve email</TITLE>
|
|
</HEAD><BODY BGCOLOR="#FFFFFF" TEXT="#000000"
|
|
LINK="#3366FF" VLINK="#A000A0">
|
|
<!-- ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: -->
|
|
<H4>"The Linux Gazette...<I>making Linux just a little more fun!</I>"</H4>
|
|
<P> <hr> <P>
|
|
<!-- ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: -->
|
|
<center>
|
|
<H1><A NAME="answer">
|
|
<img src="../../gx/dennis/qbubble.gif" alt="(?)"
|
|
border="0" align="middle">
|
|
<font color="#B03060">The Answer Guy</font>
|
|
<img src="../../gx/dennis/bbubble.gif" alt="(!)"
|
|
border="0" align="middle">
|
|
</A></H1>
|
|
<BR>
|
|
<H4>By James T. Dennis,
|
|
<a href="mailto:linux-questions-only@ssc.com">linux-questions-only@ssc.com</a><BR>
|
|
Starshine Technical Services,
|
|
<A HREF="http://www.starshine.org/">http://www.starshine.org/</A>
|
|
</H4>
|
|
</center>
|
|
|
|
<p><hr><p>
|
|
<!-- endcut ======================================================= -->
|
|
<!-- begin 5 -->
|
|
<H3 align="left"><img src="../../gx/dennis/qbubble.gif"
|
|
height="50" width="60" alt="(?) " border="0"
|
|
>setting up an ISP to serve email</H3>
|
|
|
|
|
|
<p><strong>From chris smith on Wed, 30 Dec 1998
|
|
</strong></p>
|
|
<P><STRONG>
|
|
Jim:
|
|
Thanks for your response
|
|
</STRONG></P>
|
|
<P><STRONG>
|
|
in checking out my system with the command ps
|
|
I find that there is no pop deamon running so I guess i will have to
|
|
find that.
|
|
</STRONG></P>
|
|
<BLOCKQUOTE><IMG SRC="../../gx/dennis/bbub.gif" ALT="(!)"
|
|
HEIGHT="28" WIDTH="50" BORDER="0"
|
|
>
|
|
in.popd (and most other POP daemons such as qpopper)
|
|
wouldn't show up during 'ps' unless someone was accessing
|
|
the service concurrently to your running the 'ps' command.
|
|
</BLOCKQUOTE>
|
|
<BLOCKQUOTE>
|
|
The whole point of '<tt>inetd</tt>' is that it monitors all of
|
|
the TCP/UDP ports (on all of your interfaces) and
|
|
dynamically launches the services daemons (<tt>in.popd</tt>,
|
|
<tt>in.ftpd</tt>, <tt>in.telnetd</tt>, etc) <EM>on demand</EM>.
|
|
</BLOCKQUOTE>
|
|
<BLOCKQUOTE>
|
|
So, check your <TT>/etc/inetd.conf</TT> --- and make sure that
|
|
inetd is running. Then try to run a POP client.
|
|
</BLOCKQUOTE>
|
|
<BLOCKQUOTE>
|
|
Another trick is to use telnet to connect to the POP-3
|
|
port (110). You can then issue USER and PASS commands
|
|
-- followed by a QUIT command. If those work then
|
|
your POP daemon is responding.
|
|
</BLOCKQUOTE>
|
|
<BLOCKQUOTE>
|
|
As with most Unix TCP services, the control messages
|
|
in the protocol are implemented as a set of short
|
|
commands and standardized responses. This is the way that
|
|
SMTP, FTP, POP, IMAP and several others work. (There are
|
|
also services that use binary and null terminated strings
|
|
for their protocol elements --- those generally can't be
|
|
"spoofed" or "debugged" using just plain old 'telnet').
|
|
</BLOCKQUOTE>
|
|
<P><STRONG><IMG SRC="../../gx/dennis/qbub.gif" ALT="(?)"
|
|
HEIGHT="28" WIDTH="50" BORDER="0"
|
|
>
|
|
as for my comments about the dos\windows directory structures, let me
|
|
clarify in dos\ windows when you go to a a folder for say Netscape,
|
|
you will find all of the files(for the most part) to run that program
|
|
under that folder and in directories directly under that folder (
|
|
excepting perhaps some common system .dll and autoexec.bat config.sys,
|
|
and 3 or 4 other common system files,ignoring the system registry fro a
|
|
while) It seems to me that the programs under linux are scattered all
|
|
over the place. I understand that mostly all of the files are text
|
|
based (makes sense to me for set up reasons), but why are they
|
|
everywhere, and no one has been able to tell me just what the major
|
|
directories mean (or represent) just why is stuff where it is?
|
|
</STRONG></P>
|
|
<BLOCKQUOTE><IMG SRC="../../gx/dennis/bbub.gif" ALT="(!)"
|
|
HEIGHT="28" WIDTH="50" BORDER="0"
|
|
>
|
|
First of all, "folders" are a completely different
|
|
abstraction than "directories." Folders don't exist in
|
|
MS-DOS. They are a Windows thing. (Terminology borrowed
|
|
from the MacOS paradigm).
|
|
</BLOCKQUOTE>
|
|
<BLOCKQUOTE>
|
|
I think that you belief that Linux and Unix files are
|
|
"scattered all over the place" (a complaint you've repeated
|
|
twice now) is largely a matter of your perception. As you
|
|
say, some DLL's, fonts, and other elements of Windows
|
|
programs are put outside of the folders and directories that
|
|
are associated with them.
|
|
</BLOCKQUOTE>
|
|
<BLOCKQUOTE>
|
|
In any event, Unix (and Linux) provide "mechanisms" --- they
|
|
don't set "policy." So each programmer is free to use
|
|
whatever conventions best suit their needs. Most Unix/Linux
|
|
programmers follow a fairly complex set of conventions ---
|
|
which have evolved over the course of about 30 years.
|
|
</BLOCKQUOTE>
|
|
<BLOCKQUOTE>
|
|
That's ten times longer than Windows '95 has been around,
|
|
and twice as long as MS-DOS.
|
|
</BLOCKQUOTE>
|
|
<BLOCKQUOTE>
|
|
As for what the different directories "mean" --- read the
|
|
FHS (filesystem hiearchy standard) which is part of the
|
|
Linux Documentation Project.
|
|
</BLOCKQUOTE>
|
|
<BLOCKQUOTE>
|
|
It sounds like you spending more time fighting the
|
|
conventions than understanding or accepting them. Some
|
|
of them are a bit silly (/etc for configuration files, why
|
|
isn't it <TT>/conf?)</TT> and some of the file names are historical
|
|
(which is why we store user account names, shells, home
|
|
directories, and other info in the <TT>/etc/passwd</TT> file ---
|
|
and we store password hashes in the <TT>/etc/shadow</TT> file).
|
|
</BLOCKQUOTE>
|
|
<BLOCKQUOTE>
|
|
<TT>/usr</TT> is the home of "user space" programs and resources,
|
|
while <TT>/var</TT> is the tree for <TT>/usr</TT> type files that are expected
|
|
to differ between systems (things that used to be in <TT>/usr</TT>
|
|
until people started trying to share <TT>/usr</TT> over NFS). <TT>/home</TT>
|
|
is common on Linux and less common on other Unix platforms
|
|
--- most of which use a set of fileystems like <TT>/u1</TT>, <TT>/u2</TT>,
|
|
etc. <TT>/proc</TT> is a "virtual" filesystem --- a representation
|
|
of the kernel's process status as a tree of nodes. This
|
|
allows programs and shell scripts to access process status
|
|
and other kernel data without requiring special interfaces
|
|
into the kernel. The <TT>/dev</TT> directory is for "device nodes"
|
|
(filenames through which programs can access and control
|
|
devices).
|
|
</BLOCKQUOTE>
|
|
<BLOCKQUOTE>
|
|
It would take a rather lengthy book to go over all of these
|
|
conventions. You could read "Linux Installation and Getting
|
|
Started" for some of this. Most of it is more of an "oral"
|
|
tradition (carried mostly by netnews, over mailing lists,
|
|
in user group meetings and at technical conferences like
|
|
USENIX, SANS, and the IETF workshops.
|
|
</BLOCKQUOTE>
|
|
<P><STRONG><IMG SRC="../../gx/dennis/qbub.gif" ALT="(?)"
|
|
HEIGHT="28" WIDTH="50" BORDER="0"
|
|
>
|
|
there must be a philosophy behind this system I don't understand yet
|
|
can you shed a little light on this??
|
|
</STRONG></P>
|
|
<BLOCKQUOTE><IMG SRC="../../gx/dennis/bbub.gif" ALT="(!)"
|
|
HEIGHT="28" WIDTH="50" BORDER="0"
|
|
>
|
|
Read Peter Salus' "A Quarter Century of Unix" if you want to
|
|
understand the background of Unix (and thereby the heritage
|
|
of Linux). There is also another book whose title escapes
|
|
me --- but it's something like: "the philosophy of Unix"
|
|
--- which is more for programmers.
|
|
</BLOCKQUOTE>
|
|
<P><STRONG><IMG SRC="../../gx/dennis/qbub.gif" ALT="(?)"
|
|
HEIGHT="28" WIDTH="50" BORDER="0"
|
|
>
|
|
thanks
|
|
chris
|
|
</STRONG></P>
|
|
<!-- sig -->
|
|
|
|
<!-- end 5 -->
|
|
<!--startcut ======================================================= -->
|
|
<P> <hr> <P>
|
|
<H5 align="center"><a href="http://www.linuxgazette.com/copying.html"
|
|
>Copyright ©</a> 1999, James T. Dennis
|
|
<BR>Published in <I>The Linux Gazette</I> Issue 37 February 1999</H5>
|
|
<P> <hr> <P>
|
|
<!-- ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: -->
|
|
<P align="center">
|
|
<table width="98%"><tr valign="center" align="center">
|
|
<td rowspan="3" colspan="4"><A HREF="../lg_answer37.html"><IMG
|
|
SRC="../../gx/dennis/answernew.gif"
|
|
ALT="[ Answer Guy Index ]"></A></td>
|
|
<TD width="8%"><A HREF="./1.html">1</A></TD>
|
|
<TD width="8%"><A HREF="./2.html">2</A></TD>
|
|
<TD width="8%"><A HREF="./3.html">3</A></TD>
|
|
<TD width="8%"><A HREF="./4.html">4</A></TD>
|
|
<TD width="8%"><A HREF="./5.html">5</A></TD>
|
|
<TD width="8%"><A HREF="./6.html">6</A></TD>
|
|
<TD width="8%"><A HREF="./7.html">7</A></TD>
|
|
<TD width="8%"><A HREF="./8.html">8</A></TD>
|
|
<TD width="8%"><A HREF="./9.html">9</A></TD>
|
|
<TD width="8%"><A HREF="./10.html">10</A></TD>
|
|
|
|
</tr><tr valign="center" align="center">
|
|
<TD><A HREF="./11.html">11</A></TD>
|
|
<TD><A HREF="./12.html">12</A></TD>
|
|
<TD><A HREF="./14.html">14</A></TD>
|
|
<TD><A HREF="./15.html">15</A></TD>
|
|
<TD><A HREF="./16.html">16</A></TD>
|
|
<TD><A HREF="./17.html">17</A></TD>
|
|
<TD><A HREF="./18.html">18</A></TD>
|
|
<TD><A HREF="./19.html">19</A></TD>
|
|
<TD><A HREF="./21.html">21</A></TD>
|
|
<TD><A HREF="./22.html">22</A></TD>
|
|
|
|
</tr><tr valign="center" align="center">
|
|
<TD><A HREF="./23.html">23</A></TD>
|
|
<TD><A HREF="./28.html">28</A></TD>
|
|
<TD><A HREF="./29.html">29</A></TD>
|
|
<TD><A HREF="./30.html">30</A></TD>
|
|
<TD><A HREF="./31.html">31</A></TD>
|
|
<TD><A HREF="./32.html">32</A></TD>
|
|
<TD><A HREF="./33.html">33</A></TD>
|
|
<TD><A HREF="./34.html">34</A></TD>
|
|
<TD><A HREF="./37.html">37</A></TD>
|
|
<TD><A HREF="./38.html">38</A></TD>
|
|
|
|
</tr><tr valign="center" align="center">
|
|
<TD><A HREF="./39.html">39</A></TD>
|
|
<TD><A HREF="./41.html">41</A></TD>
|
|
<TD><A HREF="./42.html">42</A></TD>
|
|
<TD><A HREF="./43.html">43</A></TD>
|
|
<TD><A HREF="./44.html">44</A></TD>
|
|
<TD><A HREF="./45.html">45</A></TD>
|
|
<TD><A HREF="./46.html">46</A></TD>
|
|
<TD><A HREF="./47.html">47</A></TD>
|
|
<TD><A HREF="./48.html">48</A></TD>
|
|
<TD><A HREF="./49.html">49</A></TD>
|
|
|
|
</tr></table>
|
|
</P>
|
|
<P> <hr> <P>
|
|
<!-- ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: -->
|
|
<P> <hr> <P>
|
|
<!-- begin lgnav ::::::::::::::::::::::::::::::::::::::::::::::::::: -->
|
|
<A HREF="../index.html"
|
|
><IMG SRC="../../gx/indexnew.gif" ALT="[ Table Of Contents ]"></A>
|
|
<A HREF="../../index.html"
|
|
><IMG SRC="../../gx/homenew.gif" ALT="[ Front Page ]"></A>
|
|
<A HREF="../lg_bytes37.html"
|
|
><IMG SRC="../../gx/back2.gif" ALT="[ Previous Section ]"></A>
|
|
<A HREF="../york.html"
|
|
><IMG SRC="../../gx/fwd.gif" ALT="[ Next Section ]"></A>
|
|
<!-- end lgnav ::::::::::::::::::::::::::::::::::::::::::::::::::::: -->
|
|
<!-- ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: -->
|
|
</BODY></HTML>
|
|
<!--endcut ========================================================= -->
|