Hi,
Has anyone here sucessfully used a Netapp fileserver as the NFS root
filesystem for FreeBSD clients?
My FreeBSD client basically mounts the Netapp, boots the kernel, but
fails early in /etc/rc because /dev/mem, /dev/kmem, /dev/null (and
friends) are unavailable.
NOTE that this all works
* Brian Dean [EMAIL PROTECTED] [010116 10:17] wrote:
Hi,
Has anyone here sucessfully used a Netapp fileserver as the NFS root
filesystem for FreeBSD clients?
My FreeBSD client basically mounts the Netapp, boots the kernel, but
fails early in /etc/rc because /dev/mem, /dev/kmem, /dev/null
# ls -l /dev/null
crw-rw-rw- 1 root wheel0, 0x00080002 Jan 16 11:35 /dev/null
# ls -l /dev/mem
crw-r- 1 root kmem0, 0x0008 Jan 15 13:28 /dev/mem
# df -k .
mass:~ls -l /dev/null
crw-rw-rw- 1 root wheel2, 2 Jan 16 12:20 /dev/null
mass:~ls -l /dev/mem
crw-r- 1
On Tue, Jan 16, 2001 at 12:27:31PM -0800, Mike Smith wrote:
What did you use to actually create your exported /dev on the NetApp in
the first place? Encoding of device major/minor numbers is funky with
NFS, and FreeBSD only does NFSv2 for the root filesystem by default
(which makes
However, this was done with an NFS V3 mount and as you observed,
FreeBSD uses NFSv2 for the root. After repeating this same same
procedure using an NVSv2 mount to the Netapp, the major/minor numbers
look a whole lot better and it now works just fine.
It's odd, though, that the NFSv2 and
5 matches
Mail list logo
