On Sun, 31 Oct 2010, Tim Dunphy wrote:
On Sat, Oct 30, 2010 at 8:10 PM, Warren Block <wbl...@wonkity.com> wrote:
On Sat, 30 Oct 2010, Tim Dunphy wrote:
I am having some trouble adding entries to /etc/fstab.. what happens
to work under CentOS does not under FreeBSD!! no surprise there, I
suppose.. heh
I have nfs_client_enable="YES" in my /etc/rc.conf
Yet if I add even one line such as
nas2.summitnhome.com:/mnt/home /home nfs rw 0 0
the system refuses to boot normally and I have to add the path to
/bin//sh manually each time
Add the "late" option ('man mount | less +3/late') to the rw option in that
line:
nas2.summitnhome.com:/mnt/home /home nfs rw,late 0 0
why on Earth can I not add entries to fstab as I do to CentOS??
Beyond knowing that they're different, dunno. Maybe the async DHCP in
FreeBSD is different.
thanks!! Yeah I tried adding the late option, but that didn't change
anything. But then I thought that perhaps DNS was not loaded by the
time the fstab is parsed making any DNS style mounts render the
machine unbootable in normal mode.
So I tried referring to the mount by the IP address rather than the
DNS name, and that fixed it.. I suppose I could setup the order in
which the services load in /etc/rc.d/ by pre-pending each one with
numbers (i.e. 00netif 01named 02syslogd...etc etc).
Changing that order is not easy, there are internal dependencies.
Forcing the startup to wait for DHCP in /etc/rc.conf may be enough:
ifconfig_re0="SYNCDHCP"
re0 used for example, change to whatever interface you have.
_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
