Date: Tue, 28 Mar 1995 22:26:34 -0800 From: Paul Traina <pst@shockwave.com> To: jkh@FreeBSD.org Cc: freebsd-bugs@FreeBSD.org Subject: misc/276: rc.maint vs syslogd Message-ID: <199503290626.WAA00864@precipice.shockwave.com>
next in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199503290626.WAA00864>