From owner-freebsd-current Fri Mar 24 03:08:39 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id DAA02426 for current-outgoing; Fri, 24 Mar 1995 03:08:39 -0800 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id DAA02369; Fri, 24 Mar 1995 03:08:25 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id VAA14559; Fri, 24 Mar 1995 21:04:40 +1000 Date: Fri, 24 Mar 1995 21:04:40 +1000 From: Bruce Evans Message-Id: <199503241104.VAA14559@godzilla.zeta.org.au> To: bde@zeta.org.au, jkh@freefall.cdrom.com Subject: Re: /etc/rc ordering hosed Cc: current@FreeBSD.org Sender: current-owner@FreeBSD.org Precedence: bulk >> netstart now starts a lot of network applications. This fails if /usr >> is mounted over nfs (unless the mount is moved into netstart, which >Ah feh. I've never mounted my /usr over NFS (I like that cached locally >everywhere :-) and thus didn't notice this problem creep in. >> syslogd is now started much too late. >Where would you suggest we start it? A bit later than where it got moved to :-). syslogd is in /usr/sbin, so it fails if /usr is mounted over nfs :-]. >I'm not at all adverse to suggestions here, folks, this IS a group >project and if you don't like something I'm doing or have a better >suggestion then please, SPEAK UP! Start only network interfaces in /etc/netstart. Then optionally mount things over nfs. Then start syslogd. Then run rc.maint. Then start network applications in /etc/rc.net[app?]start. This is almost the old order. Bruce