From: garrett@garnet.berkeley.edu (Garrett D'Amore) Subject: /etc/inet vs. /etc Date: 12 Apr 1993 06:13:01 GMT
Okay, I know this has gone round & round a few times, but here's the scoop.
I've upgraded my libraries, and everything works, as long as I have files
in BOTH /etc and /etc/inet. I'd like to move *EVERYTHING* into /etc and
do away with the inet subdir altogether, but if I try that (by just renaming
the subdir) all networking functions (like ping) cease!
Question: is this /etc/inet dependency built into inetd? Other executables
as well? (FTP, fingerd, telnetd???) (I'm using SLS stuff...)
If this is the case, it may well be worth the time & effort to systematically
go through each package and recompile with the dependencies in /etc instead.
If anyone else has already done this, please let me know. Otherwise I'll
do it myself and u/l a "complete" networking package to tsx-11 and sunsite.
Personally, I like the move into a more standard directory structure. It
means us newbies can just look at our neighbors config files and modify them,
even tho' they're not running Linux! (Ahhh... portability...) :-)
Thanks!
====================================================================
Garrett D'Amore | garrett@haas.berkeley.edu
Software Co-Ordinator | 68 Barrows Hall, UC Berkeley
Haas Computing Services | Ph: 510-643-5923 Fax: 642-4769
====================================================================