| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
file in the NFS file system when the underlying device is not a
network device. A Sparc64 specific hack for this exact problem was
already present (nfs.c:1.9, tftp.c:1.10), but the problem is not
specific to Sparc64. The hack has been promoted to a non-i386 test
because on non-i386 architectures it's either impossible to have
non-network devices coexist in the same loader with the NFS FS, or
network and non-network device coexist and NFS filesystems can only
be used on top of network devices. I believe i386 pxeboot is where
this does not hold.
The root cause of this problem is in open.c where each file system
is tried until no more file systems exist or a file system returns
success. There's no notion of a list of valid file systems given
the underlying device and the non-existence of a file can cause
the invalid combination to be tried.
|
|
|
|
| |
to pick up, ala pxe.
|
|
|
|
| |
devices as though they were backed by network devices.
|
| |
|
| |
|
|
|
|
| |
NFS filehandle for the root mount.
|
| |
|
|
|
|
|
| |
node is statically allocated and is not guarded, so free will panic
in nfs_close.
|
|
|
|
| |
functionality for some of the filesystesms.
|
|
|
|
|
|
| |
them.
Submitted by: write-protected text segment in BTX
|
|
modules).
Obtained from: NetBSD, with some architectural changes and many additions.
|