Enable WARNS=4 by default except for:
dump dump_lfs fsck_ffs fsck_lfs fsdb mount_smbfs
newfs_ext2fs newfs_lfs resize_lfs setkey

branches: 1.4.4;
Refactor mount utilities to provide a mount_fs_parseargs() routine.
Use this routine both in mount_fs and rump_fs to provide equivalent
command line parameters and therefore usage interchangeability.
While doing this, combine some common mountgoop to mountprog.h

Install mount argument structure header just like every other file system.

branches: 1.2.4; 1.2.8;
- Use fattr.c functions instead of home brewed ones.
- Use new dehumanize number.

branches: 1.1.10; 1.1.12;
Initial addition of tmpfs, an efficient memory file-system. This project
was developed as part of Google's Summer of Code 2005 program. This
change adds the kernel code, the mount_tmpfs utility, a regression test
suite and does all other related changes to integrate these.

The file-system is still *experimental*. Therefore, it is disabled by
default in all kernels. However, as typically done, a commented-out
entry is added in them to ease its setup.

Note that I haven't commited the required mountd(8) changes to be able
to export tmpfs file-systems because NFS support is still very unstable
and because, before enabling it, I'd like to do some other changes.

OK'ed by my project mentor, William Studenmund (wrstuden@).

s/similarily/similarly/

Remove reference to (no longer) fixed 4 mbyte kernel memory being reserved,
it is now dynamic.

branches: 1.17.2;
Bump date for previous.

Provide variants of the -s option to allow limiting the tmpfs dynamically
at mount time to 1/Nth or to N percent of the available ram.

Improvements from jmc@openbsd.

branches: 1.14.20; 1.14.26;
Convert TNF licenses to new 2 clause variant

branches: 1.13.4; 1.13.6;
The first non-optional parameter is ignored by this program.

ok'ed by jmmv@.

branches: 1.12.4; 1.12.6;
s/tons/lots/, per simonb@'s suggestion. This looks more formal.

Nicer macro usage.

Note that meta data is stored in non-pageable memory and the problems this
may carry. Suggested by Greg Troxel in private mail.

tmpfs is not considered experimental any more. OK'ed by core@.

Point to the share/examples/fstab/fstab.ramdisk file for some more information.

Add an EXAMPLES section. Requested by martti@ to clarify the purpose of
the field before the mount point.

Kill reference to tmpfs(9). Noticed by "pancake".

Ignore case of trailing unit specifiers in size measures to remove confusion.

Inherit owner, group and mode of the mount directory so that mounting a
tmpfs over, e.g., /tmp, is trivial.

Kill the tmpfs(9) manual page; it was just documenting internal details of
tmpfs' "API" and was already rotting.

Instead, merge all the relevant comments into the code. This includes
acknowledgements to Google's Summer of Code 2005 program (they were in the
AUTHORS section of tmpfs(9) before), so all the files need to be changed
to include this sentence alongside the title. (Note that this was not a
requirement of the program.)

wiz@ remembers that the preferred way to spell file-system in NetBSD is
file system.

Initial addition of tmpfs, an efficient memory file-system. This project
was developed as part of Google's Summer of Code 2005 program. This
change adds the kernel code, the mount_tmpfs utility, a regression test
suite and does all other related changes to integrate these.

The file-system is still *experimental*. Therefore, it is disabled by
default in all kernels. However, as typically done, a commented-out
entry is added in them to ease its setup.

Note that I haven't commited the required mountd(8) changes to be able
to export tmpfs file-systems because NFS support is still very unstable
and because, before enabling it, I'd like to do some other changes.

OK'ed by my project mentor, William Studenmund (wrstuden@).

Add MOPT_{REL,NO}ATIME as supported by the underlying filesystems.

allow update

branches: 1.27.2;
Fix err/errx confusion, pointed out by rmind.

Provide variants of the -s option to allow limiting the tmpfs dynamically
at mount time to 1/Nth or to N percent of the available ram.

Sync with man page. From jmc@openbsd.

branches: 1.24.18; 1.24.24;
Refactor mount utilities to provide a mount_fs_parseargs() routine.
Use this routine both in mount_fs and rump_fs to provide equivalent
command line parameters and therefore usage interchangeability.
While doing this, combine some common mountgoop to mountprog.h

Install mount argument structure header just like every other file system.

branches: 1.22.2;
Remove clause 3 and 4 from TNF licenses

branches: 1.21.4; 1.21.6;
Print the second parameter in the error messages, since the first is
ignored anyway.

ok'ed by jmmv@.

NB: I didn't add a regression test for this because of lack of knowledge,
as the existing tests don't seem to follow the regress/README file.

convert __attribute__s to applicable cdefs.h macros

- Use fattr.c functions instead of home brewed ones.
- Use new dehumanize number.

branches: 1.18.4; 1.18.6;
Print MNT_GETARGS results in one line to make them display
properly with mount -vvvvvvvvvv

Make all mount(2) return value error checks against -1. Some file
systems just checked != 0, breaking MNT_GETARGS. Others worked with < 0,
but make them check against -1 too for consistency. And sprinkle some
stylish line wrapping where appropriate.

Add additional 'sizeof args' parameter to mount(2).

use MOPT_NULL

remove __POOL_EXPOSE.

There is no need to check for the resulting value of a strto*l call after
ERANGE has been raised. Just remove the extra checks, which were incorrect
anyway in almost all calls because they did not match their corresponding
strto*l function.

This caused mount_tmpfs to not catch some error cases in, e.g., i386, as
strtoll was returning LLONG_MAX instead of LONG_MAX, which are different
in this platform (but not on 64-bit ones).

Problem found by martin@; thanks!

Always check the results of getmntopts() and free them.

define __POOL_EXPOSE.

Do not use stdbool.h; it breaks the build on ports using gcc 2.x (such as
vax). Ew. Pointed out by he@.

Handle overflow errors in dehumanize_number. Noticed by chs@.

Implement the getargs option. I knew the code in the kernel had to be of
some use...

Fix some type mismatch issues (gid_t and uid_t are unsigned); pointed out
by chs@.

Change two variables from size_t to long as they are used with long
values (strtol). Silences a warning from lint.

Ignore case of trailing unit specifiers in size measures to remove confusion.

Inherit owner, group and mode of the mount directory so that mounting a
tmpfs over, e.g., /tmp, is trivial.

Kill the tmpfs(9) manual page; it was just documenting internal details of
tmpfs' "API" and was already rotting.

Instead, merge all the relevant comments into the code. This includes
acknowledgements to Google's Summer of Code 2005 program (they were in the
AUTHORS section of tmpfs(9) before), so all the files need to be changed
to include this sentence alongside the title. (Note that this was not a
requirement of the program.)

Apply the NFS exports list rototill patch:

- Remove all NFS related stuff from file system specific code.
- Drop the vfs_checkexp hook and generalize it in the new nfs_check_export
function, thus removing redundancy from all file systems.
- Move all NFS export-related stuff from kern/vfs_subr.c to the new
file sys/nfs/nfs_export.c. The former was becoming large and its code
is always compiled, regardless of the build options. Using the latter,
the code is only compiled in when NFSSERVER is enabled. While doing this,
also make some functions in nfs_subs.c conditional to NFSSERVER.
- Add a new command in nfssvc(2), called NFSSVC_SETEXPORTSLIST, that takes a
path and a set of export entries. At the moment it can only clear the
exports list or append entries, one by one, but it is done in a way that
allows setting the whole set of entries atomically in the future (see the
comment in mountd_set_exports_list or in doc/TODO).
- Change mountd(8) to use the nfssvc(2) system call instead of mount(2) so
that it becomes file system agnostic. In fact, all this whole thing was
done to remove a 'XXX' block from this utility!
- Change the mount*, newfs and fsck* userland utilities to not deal with NFS
exports initialization; done internally by the kernel when initializing
the NFS support for each file system.
- Implement an interface for VFS (called VFS hooks) so that several kernel
subsystems can run arbitrary code upon receipt of specific VFS events.
At the moment, this only provides support for unmount and is used to
destroy NFS exports lists from the file systems being unmounted, though it
has room for extension.

Thanks go to yamt@, chs@, thorpej@, wrstuden@ and others for their comments
and advice in the development of this patch.

Initial addition of tmpfs, an efficient memory file-system. This project
was developed as part of Google's Summer of Code 2005 program. This
change adds the kernel code, the mount_tmpfs utility, a regression test
suite and does all other related changes to integrate these.

The file-system is still *experimental*. Therefore, it is disabled by
default in all kernels. However, as typically done, a commented-out
entry is added in them to ease its setup.

Note that I haven't commited the required mountd(8) changes to be able
to export tmpfs file-systems because NFS support is still very unstable
and because, before enabling it, I'd like to do some other changes.

OK'ed by my project mentor, William Studenmund (wrstuden@).

branches: 1.1.2; 1.1.4;
Refactor mount utilities to provide a mount_fs_parseargs() routine.
Use this routine both in mount_fs and rump_fs to provide equivalent
command line parameters and therefore usage interchangeability.
While doing this, combine some common mountgoop to mountprog.h