Yes,

        I was missing the 'source' line in my rc.firewall file.
But that doesn't change the fact that I have no mouse support,
named doesn't come up.  No default route... -Nothing- specified in the
/etc/rc.conf file occurs at boot.
        I just ran mergemaster -s that didn't change things either.

        I appreciate the suggestions, but it is a pretty fundamental
problem.  I can start most things easily by hand, but it is annoying to
do.

-------------------------------------------------------------------------
Marius M. Rex
"Well," Brahma said, "even after ten thousand explanations, a fool is
no wiser, but an intelligent man requires only two thousand five
hundred."
                -- The Mahabharata

On Thu, 5 Oct 2000, Noor Dawod wrote:

> Hi Marius,
> 
> I once had a similar problem. The solution was that one of the many
> /etc/rc.* (a hunch: check /etc/rc.firewall) is not properly reading
> /etc/defaults/rc.donf correctly, and this is causing mis-understanding
> in your box.
> 
> The /etc/rc.firewall should have at the begining of it the following
> lines:
> 
> if [ -r /etc/defaults/rc.conf ]; then
>         . /etc/defaults/rc.conf
>         source_rc_confs
> elif [ -r /etc/rc.conf ]; then
>         . /etc/rc.conf
> fi
> 
> Make sure this is inserted correctly.
> 
> Noor
> 
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Marius M. Rex
> Sent: Thursday, October 05, 2000 4:19 PM
> To: [EMAIL PROTECTED]
> Subject: FreeBSD ignoring /etc/rc.conf
> 
> 
> Hi,
> 
> I am using:
> 
> $ uname -a
> FreeBSD utterlux.communityconnect.com 4.1-STABLE FreeBSD 4.1-STABLE
> #0: Wed Oct  4 10:39:24 EDT 2000
> [EMAIL PROTECTED]:/usr/obj/usr/src/sys/UTTERLUX  i386
> 
> 
> Though I cvsup'ed a while back, I just got to 'make installworld'
> yesterday. (work has been busy)  Anyway, I rebooted this morning and
> found
> that it is basically ignoring my /etc/rc.conf file.  It ignores the
> firewall type I setup, my default route, the fact that I have a
> mouse. etc.  (It does this consistantly on each reboot)
> 
> This same thing happened to me before the last time I cvsup'ed to
> 4.x-stable.  I thought it was just that I did something wrong.  So I was
> expecting doing it again, now that I have updated a number of
> other machines sucessfully, that it would work again.
> 
> 'make buildworld' 'make installworld' and mergemaster (Done completely
> by
> hand) went through without a hitch.  I don't quite understand what is
> wrong.  But it will do this to me every time I reboot.  (Which,
> admittedly, is infrequently.)
> 
> Anyone else had this problem?  I havn't sen it mentioned on the list.
> 
> Here is my /etc/rc.conf file if it matters:
> -----------------------------------------------------------------------
> # This file now contains just the overrides from /etc/defaults/rc.conf
> # please make all changes to this file.
> 
> # -- sysinstall generated deltas -- #
> linux_enable="YES"
> moused_enable="YES"
> # -- marius additions -- #
> firewall_enable="YES"
> firewall_type="CLIENT"
> tcp_drop_synfin="YES"
> tcp_restrict_rst="YES"
> sendmail_enable="NO"
> named_enable="YES"
> 
> # -- sysinstall generated deltas -- #
> lpd_enable="YES"
> ipv6_enable="NO"
> usbd_enable="YES"
> sshd_enable="YES"
> ifconfig_fxp0="inet 216.89.86.152  netmask 255.255.255.0"
> defaultrouter="216.89.86.128"
> hostname="utterlux.communityconnect.com"
> check_quotas="NO"
> ntpdate_flags="bitsy.mit.edu"
> ntpdate_enable="YES"
> moused_enable="YES"
> ------------------------------------------------------------------
> 
> ------------------------------------------------------------------------
> -
> Marius M. Rex
> "Well," Brahma said, "even after ten thousand explanations, a fool is
> no wiser, but an intelligent man requires only two thousand five
> hundred."
>                 -- The Mahabharata
> 
> 
> 
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-stable" in the body of the message
> 
> 



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message

Reply via email to