Text 5501, 68 rader
Skriven 2006-03-13 17:24:00 av Paul Rogers (1:105/360.0)
     Kommentar till en text av Maurice Kinal
Ärende: Anybody using famd & 2.6
================================
 PR> Not that WE need to, but KDE/Gnome is keeping track of things
 PR> in various configuration & cache files.
 MK> Ah!  That isn't an issue here.

After my first experiment building LFS-4.1 by hand, step by
step, I used KDE to cut and paste from the book into scripts.
That eliminated most of the typos.  It took weeks the first
time, but just days with the scripts.  That gave me a cleaner
installation--"this is what I should have done in the first
place."

 MK> Probably the idea that any daemon under it's configuration could be
 MK> set to only listen on specific interfaces where security isn't as

OK, strictly speaking, but inetd uses tcpwrappers and it can
allow or deny based on IP addresses, not just interfaces, e.g.
eth0.  And anybody connected to the big, wide world needs a
ipchains/iptables firewall which can do both, and protocols &
ports too.  What can xinetd do that inetd/tcpwrappers/iptables
doesn't?

 MK> to the main server here through a direct connection to my
 MK> workstation via a specific ethernet chip.  Thus I can have

The MAC address.

 MK> Me too.  I still like 486's and find them extremely usable
 MK> for most of my needs.

I'm a bit more ambitious than THAT.  But I'm working with
Pentium-I's.

 PR> which get the job done but are still efficient.  I'll need a
 PR> good reason to switch to xinetd.
 MK> Yep.  That is a good plan.  It depends on your situation

I give up.  I can't make it work, and can't get advice from
anyone.  The only thing inetd was starting currently is famd.
So I had the overhead of inetd always, famd sometimes, but it
was easy to add more services.  But famd does work, so I'm
starting it in an init/rc script.  I'll just hope the kernel
pages it all out most of the time.

 MK> and if you are the only one who has access then jumping

I'd never make that presumption.  I have firewalls on all my
"pod" workstations, and a separate firewall on the ppp box.
You'd be surprized how often my internal firewall trips-up a
webpage trying to "phone home" on another port.  But the main
idea is to get in the way of any malware that does sneak
through, and to protect the LAN from a "run away".

 MK> through whatever hoops for something that isn't useful
 MK> isn't the best way to learn what you really want on that
 MK> system.

You never know.  I've never found a situation where the less I
knew, the better.

Paul Rogers, paulgrogers@yahoo.com                       -o)
http://www.angelfire.com/or/paulrogers                   /\\
Rogers' Second Law: Everything you do communicates.     _\_V

... NOBODY expects the Spanish Inquisition!
___ MultiMail/MS-DOS v0.35

---
 * Origin: The Bare Bones BBS (1:105/360)