consider a out-of-range partition letter at the end of the special
device node to be a fatal error; just return NULL and let the caller
fall back to FFS.
This fixes the "mount -u /kern/rootdev /" done by the script installer.
XXX this is still gross, and breaks things like
"mount /my/strange/dev/path/b /mnt". Perhaps it should stat the node
and use the minor number as an index instead?
- don't warn. It's just too verbose when we know there is
no disklabel and want to use the default filesystem type.
- close the file descriptor so that further mount success.
mount_mfs(8); the mount_*(8) are hardlinked to mount (appropriate mount routine
is called depending on program name) - this saves approx. 1.7MB of /sbin
space
mount.c: make all local symbols static
for the disklabel if the given device fails with EBUSY. Also make disklabel
errors non fatal (just fall back to ffs as per pre-autofilesystem behaviour)
Based on further discussion with Launey Thomas <ljt@alum.mit.edu>
statfs() or getmountinfo() did not tell about the freshly mounted
ramdisk.
XXX Imo, "mount_mfs" should not return before the mount is done.
This is the only place where this can be done cleanly. But this would
require a substancial restructuring of "newfs". For now, wait in "mount"
until the filesystem appears.
"verbose" mode after printing the exec args.
This invalidates most of my comment in the previous commit. (Not all,
there are still bogosities with mount_mfs.)
check all mounts (getmntinfo), not only the top one (statfs).
Otherwise we might miss lower level mounts on the same mountpoint.
XXX "mount" behaves differently with the "verbose" flag (-v) in some
cases, probably due to asynchronous calls to fs dependant mount programs.
that require all of /sbin/mount_* and /sbin/umount to be modified:
* incorporate vfslist.c, adding checkvfsname() and makevfslist()
* getmntopts() now takes 4 args (adding int *altflagp)
types. when using mount(8) with '-a', do _NOT_ remount file systems
that have been mounted once already. (This cannot be 100% precisely
determined (thanks to mfs, union fs, and similar file systems which
don't use a 'real' mounted-from node), and changed options cannot be updated
with mount -a. however, options wouldn't be updated with the old mount -a
anyway, and this solves several annoyances.
