From owner-freebsd-bugs Tue Mar 28 22:27:16 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id WAA06941 for bugs-outgoing; Tue, 28 Mar 1995 22:27:16 -0800 Received: from precipice.shockwave.com (precipice.shockwave.com [171.69.108.33]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id WAA06915; Tue, 28 Mar 1995 22:27:12 -0800 Received: from localhost (localhost [127.0.0.1]) by precipice.shockwave.com (8.6.11/8.6.9) with SMTP id WAA00864; Tue, 28 Mar 1995 22:26:34 -0800 Message-Id: <199503290626.WAA00864@precipice.shockwave.com> To: jkh@FreeBSD.org cc: freebsd-bugs@FreeBSD.org Subject: misc/276: rc.maint vs syslogd Date: Tue, 28 Mar 1995 22:26:34 -0800 From: Paul Traina Sender: bugs-owner@FreeBSD.org Precedence: bulk I'm a little confused on how this all got messed up. Here's what I think should be done to get us back behaving in classic fashion: (a) /etc/netstart just starts things needed to start networking (i.e. it -just- does the interface configurations, no NFS, no xntpd, no sendmail, no inetd) (b) start up the networking daemons necessary for mounting remote disks (portmapper, nfsiod, do the mount) (c) start up the time tracking stuff (ntpdate/xntpd/timed/adjtime) (d) invoke syslogd right after the directory clearing stuff in /etc/rc.maint (except it's back in rc...see below) (e) lose /etc/rc.maint ... I don't see what advantage we gained by splitting this stuff out in the first place... put that stuff back in to /etc/rc so we have more flexibility with placement... (f) start up the other daemons that we need and inetd If you don't hate this, I'll actually go to the trouble of generating the new /etc files and test them out. I would -like- to make it so that FreeBSD really can boot properly with a remote /usr or boot diskless. It's really bad that we've lost this ability.