CVS log for src/usr.sbin/quot/quot.c

Up to [cvs.NetBSD.org] / src / usr.sbin / quot

Request diff between arbitrary revisions

Keyword substitution: kv
Default branch: MAIN

Restore backward compatibility of UFS2 with previous NetBSD releases by
disabling support in UFS2 for extended attributes (including ACLs).
Add a new variant of UFS2 called "UFS2ea" that does support extended attributes.
Add new	fsck_ffs operations "-c	ea" and	"-c no-ea" to convert file systems
from UFS2 to UFS2ea and	vice-versa (both of which delete all existing extended
attributes in the process).

Pull up following revision(s) (requested by martin in ticket #1210):
	sys/ufs/ffs/ffs_vfsops.c: revision 1.340
	usr.sbin/quot/quot.c: revision 1.34
	sbin/fsdb/fsdb.c: revision 1.49
From Michael Plass:
The superblock field that distinguishes between 4.2BSD and 4.4BSD
inodes is really only relevant on a UFS1 file system. Make sure that
it is a UFS1 fs before using fs_old_inodefmt.
Note that the NetBSD newfs and mkfs utilities initialize fs_old_inodefmt
even for UFS2, so problems were apparent only on file systems created
by other operating systems, for example, FreeBSD.

Pull up following revision(s) (requested by martin in ticket #1210):
	sys/ufs/ffs/ffs_vfsops.c: revision 1.340
	usr.sbin/quot/quot.c: revision 1.34
	sbin/fsdb/fsdb.c: revision 1.49
From Michael Plass:
The superblock field that distinguishes between 4.2BSD and 4.4BSD
inodes is really only relevant on a UFS1 file system. Make sure that
it is a UFS1 fs before using fs_old_inodefmt.
Note that the NetBSD newfs and mkfs utilities initialize fs_old_inodefmt
even for UFS2, so problems were apparent only on file systems created
by other operating systems, for example, FreeBSD.

Pull up following revision(s) (requested by martin in ticket #1395):
	sys/ufs/ffs/ffs_vfsops.c: revision 1.340
	usr.sbin/quot/quot.c: revision 1.34
	sbin/fsdb/fsdb.c: revision 1.49
From Michael Plass:
The superblock field that distinguishes between 4.2BSD and 4.4BSD
inodes is really only relevant on a UFS1 file system. Make sure that
it is a UFS1 fs before using fs_old_inodefmt.
Note that the NetBSD newfs and mkfs utilities initialize fs_old_inodefmt
even for UFS2, so problems were apparent only on file systems created
by other operating systems, for example, FreeBSD.

Pull up following revision(s) (requested by martin in ticket #1395):
	sys/ufs/ffs/ffs_vfsops.c: revision 1.340
	usr.sbin/quot/quot.c: revision 1.34
	sbin/fsdb/fsdb.c: revision 1.49
From Michael Plass:
The superblock field that distinguishes between 4.2BSD and 4.4BSD
inodes is really only relevant on a UFS1 file system. Make sure that
it is a UFS1 fs before using fs_old_inodefmt.
Note that the NetBSD newfs and mkfs utilities initialize fs_old_inodefmt
even for UFS2, so problems were apparent only on file systems created
by other operating systems, for example, FreeBSD.

Pull up following revision(s) (requested by martin in ticket #1395):
	sys/ufs/ffs/ffs_vfsops.c: revision 1.340
	usr.sbin/quot/quot.c: revision 1.34
	sbin/fsdb/fsdb.c: revision 1.49
From Michael Plass:
The superblock field that distinguishes between 4.2BSD and 4.4BSD
inodes is really only relevant on a UFS1 file system. Make sure that
it is a UFS1 fs before using fs_old_inodefmt.
Note that the NetBSD newfs and mkfs utilities initialize fs_old_inodefmt
even for UFS2, so problems were apparent only on file systems created
by other operating systems, for example, FreeBSD.

Sync with HEAD

From Michael Plass:

The superblock field that distinguishes between 4.2BSD and 4.4BSD
inodes is really only relevant on a UFS1 file system. Make sure that
it is a UFS1 fs before using fs_old_inodefmt.

Note that the NetBSD newfs and mkfs utilities initialize fs_old_inodefmt
even for UFS2, so problems were apparent only on file systems created
by other operating systems, for example, FreeBSD.

Rebase to HEAD as of a few days ago.

sync with head.

for a reference, the tree before this commit was tagged
as yamt-pagecache-tag8.

this commit was splitted into small chunks to avoid
a limitation of cvs.  ("Protocol error: too many arguments")

fix unused variable warnings.

Stick ffs_, ext2_, chfs_, filecore_, cd9660_, or mfs_ in front of
the following symbols so as to disambiguate fully. (Christos already
did the lfs ones.)

   lblkno
   lblktosize
   lfragtosize
   numfrags
   blkroundup
   fragroundup

resync from head

Rename ambiguous macros:
   MAXDIRSIZE -> UFS_MAXDIRSIZE or LFS_MAXDIRSIZE
   NINDIR -> FFS_NINDIR, EXT2_NINDIR, LFS_NINDIR, or MFS_NINDIR
   INOPB -> FFS_INOPB, LFS_INOPB
   INOPF -> FFS_INOPF, LFS_INOPF
   blksize -> ffs_blksize, ext2_blksize, or lfs_blksize
   sblksize -> ffs_blksize

These are not the only ambiguously defined filesystem macros, of
course, there's a pile more. I may not have found all the ambiguous
definitions of blksize(), too, as there are a lot of other things
called 'blksize' in the system.

resync with head

sync with head

Stuff UFS_ in front of a few of ufs's symbols to reduce namespace
pollution. Specifically:
   ROOTINO -> UFS_ROOTINO
   WINO -> UFS_WINO
   NXADDR -> UFS_NXADDR
   NDADDR -> UFS_NDADDR
   NIADDR -> UFS_NIADDR
   MAXSYMLINKLEN -> UFS_MAXSYMLINKLEN
   MAXSYMLINKLEN_UFS[12] -> UFS[12]_MAXSYMLINKLEN (for consistency)

Sort out ext2fs's misuse of NDADDR and NIADDR; fortunately, these have
the same values in ext2fs and ffs.

No functional change intended.

KNF

Sync with HEAD.

Third (and last) commit. See http://mail-index.netbsd.org/source-changes/2009/05/13/msg221222.html

Fix -Wcast-qual issue

Eliminate MFSNAMELEN

fix compilatio problems on LP64

64 bit inode changes

Replace the statfs() family of system calls with statvfs().
Retain binary compatibility.

ffsv2 might not have FS_FLAGS_UPDATED set

When searching for the superblock, don't pick an ffsv1 superblock from the
location where we expect to find an ffsv2 superblock.
It could be the first alternate for a ffsv1 filesystem with 64k blocks.
Fixes part of PR kern/24809

Remove unused max macro. From Jeff Ito in PR 23995.

Homogenize usage messages: make the 'usage' word all lowercase, as this seems
to be the most common practice in our tree.

Pass a NULL to getbsize() for any arguments that aren't needed, and
remove the otherwise unused variables.

Add support for UFS2. UFS2 is an enhanced FFS, adding support for
64 bit block pointers, extended attribute storage, and a few
other things.

This commit does not yet include the code to manipulate the extended
storage (for e.g. ACLs), this will be done later.

Originally written by Kirk McKusick and Network Associates Laboratories for
FreeBSD.

remove #include <ufs/ufs/quota.h> where it was just to appease
<ufs/ufs/inode.h>, since the latter now includes the former.  leave the former
in source that obviously uses specific bits of it (for completeness.)

Pull up to last week's -current.

pull up revs 1.15-1.16 from trunk (requested by mycroft):
  Fix integer overflows with file systems >=2GB.

Adjust this to work on the Alpha.

Make this work on file systems larger than 2GB.

Merge with Lite2 + local changes

Pull rev 1.13 up from trunk (mrg)

use warn not warnx to find out why the open failed (as old quot did).

deprecate register, use err/warn instead of perror, memmove instead of bcopy

WARNSify

Format police.

pulled up from version 1.9 by request of ws

Fix PR 2462
While I am here do some reformatting, remove hardwired DEV_BSIZE values,
add old fs compatibility (stolen from libsa), and change to new RCSids.

pull in <unistd.h> to make lseek() work ...

merge in changes from 1.1 release branch

complete ufs -> ffs change (From John Kohl; PR #1403)

fix a macro's usage

update for new fs includes

need <sys/time.h>

fs type names

general: cleanup.  fix RCS Id's.  ("$Id $" doesn't work.)
Makefile: no special bingrp.
quot.8: bugs section is empty; comment it out.
quot.c: add static RCS Id, KNF-ify, break long lines.

First version of a quot utility

Initial revision