On Sat, 9 Apr 2011, Bill Thoen wrote:
> /etc/hosts:
> # Do not remove the following line, or various programs
> # that require network functionality will fail.
> 127.0.0.1 localhost.localdomain localhost
> ::1 localhost.localdomain6 localhost6
Bill,
Professional SysAdmins will correct me if I'm wrong, but /etc/hosts,
/etc/hosts.allow, /etc/hosts.deny, /etc/hosts.equiv, and /etc/host.conf
identify the hosts on your local nectwork so they can directly communicate
with one another. In /etc/host.conf here I have:
[root@salmo ~]# less /etc/host.conf
order hosts, bind
multi on
So the system looks in the hosts file first.
Read the wikipedia page on /etc/hosts:
<http://en.wikipedia.org/wiki/Hosts_%28file%29>
> In hosts? I thought that stuff would be in /etc/syhsconfig/network or
> somewhere down that networking directory tree in razamatz.cf or
> ishkabibble.conf.
Again, in Slackware (with more BSD than SysV in some aspects compared with
the Red Hats and relatives), /etc/rc.d/rc.inet1.conf holds port information;
e.g.,
# Config information for eth0:
IPADDR[0]="192.168.55.1"
NETMASK[0]="255.255.255.0"
USE_DHCP[0]=""
DHCP_HOSTNAME[0]=""
> (Sorry, but was this stuff hard to learn when you were first going at it?
Actually, no. But, I spent a year reading about linux before installing
RH-4.0 and booting into it the first time. I also bought, read, and used a
ton of books. I've six of thse that I was going to give to Goodwill since I
no longer need/use them, but I'll send them to you via media mail:
- Linux in a Nutshell by Jessica Perry Hekman.
- Linux System Administration, A Users Guide by Marcel Gagne'.
- Linux Cookbok, by my friend Carla Schroder.
= Running Linux, 2nd Ed, by Matt Welsh and Lar Kaufman.
- Building Secure Servers With Linux, by Michael D. Bauer.
= Multitool Linux, by Michael Schwarz et al.
You can re-imburse me the postgage cost. They may be old but they have the
basic information that will increase your understanding and comfort.
> I think it's especially hard for the knowlessman because it's in
> networking where several major software packages come together, and half
> the time when I try to debug these sorts of things I don't even know what
> I'm looking for, let alone know in what package the problem origiinates.
That's true. However, once you understand the overall structure it all
becomes clearer and makes sense. The key aspect of linux (and the other
unices) comes down to what I was told many years ago: linux tools are
single-purpose and easy to understand, but there are thousands of such
tools.
> I don't really want edit sendmail.cf, ...
Despite your need, like the needs of most of us, to do too many things at
the same time, seriously consider replacing sendmail with postfix. (There
are other replacements but I've been happily running postfix here since I
brought our mail sever inside more than a dozen years ago.) Much easier to
understand, maintain, and configure.
Rich
_______________________________________________
PLUG mailing list
[email protected]
http://lists.pdxlinux.org/mailman/listinfo/plug
