summaryrefslogtreecommitdiffstats
path: root/sbin/fsirand
Commit message (Collapse)AuthorAgeFilesLines
* fsirand(8): make WARNS=3 cleanuqs2010-05-142-18/+23
| | | | | | | | | | | | | | | | | | | | | | | | | | | - Drop bogus quad_t cast for di_gen, it is a 32bit type - Print di_gen with leading zeros, to get consistent output Before this change, amd64 would print: ino 18 gen 616ca2bd ino 19 gen ffffffff95c2a3ff ino 20 gen 25c3a3d5 ino 21 gen 8dc1472 ino 22 gen 3797056b ino 23 gen 1d47853a ino 24 gen ffffffff82d26995 After the change ino 18 gen 616ca2bd ino 19 gen 95c2a3ff ino 20 gen 25c3a3d5 ino 21 gen 08dc1472 ino 22 gen 3797056b ino 23 gen 1d47853a ino 24 gen 82d26995 PR: bin/139994 (sort of) Reviewed by: mckusick
* mdoc: move CAVEATS, BUGS and SECURITY CONSIDERATIONS sections to theuqs2010-05-131-6/+6
| | | | | | | | | | | bottom of the manpages and order them consistently. GNU groff doesn't care about the ordering, and doesn't even mention CAVEATS and SECURITY CONSIDERATIONS as common sections and where to put them. Found by: mdocml lint run Reviewed by: ru
* Avoid casts as lvalues.kan2004-07-281-2/+3
|
* Mechanically kill hard sentence breaks.ru2004-07-021-1/+2
|
* style.Makefile(5):johan2004-02-231-1/+1
| | | | Use WARNS?= instead of WARNS=.
* Create a new 32-bit fs_flags word in the superblock. Add code to movemckusick2002-11-271-2/+1
| | | | | | | | | | | | | | | | | the old 8-bit fs_old_flags to the new location the first time that the filesystem is mounted by a new kernel. One of the unused flags in fs_old_flags is used to indicate that the flags have been moved. Leave the fs_old_flags word intact so that it will work properly if used on an old kernel. Change the fs_sblockloc superblock location field to be in units of bytes instead of in units of filesystem fragments. The old units did not work properly when the fragment size exceeeded the superblock size (8192). Update old fs_sblockloc values at the same time that the flags are moved. Suggested by: BOUWSMA Barry <freebsd-misuser@netscum.dyndns.dk> Sponsored by: DARPA & NAI Labs.
* s/filesystem/file system/g as discussed on -developerstrhodes2002-08-212-12/+12
|
* mdoc(7) police: Removed redundant .Ns calls.ru2002-08-131-1/+1
|
* The .Nm utilitycharnier2002-07-061-6/+8
|
* This commit adds basic support for the UFS2 filesystem. The UFS2mckusick2002-06-211-47/+70
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | filesystem expands the inode to 256 bytes to make space for 64-bit block pointers. It also adds a file-creation time field, an ability to use jumbo blocks per inode to allow extent like pointer density, and space for extended attributes (up to twice the filesystem block size worth of attributes, e.g., on a 16K filesystem, there is space for 32K of attributes). UFS2 fully supports and runs existing UFS1 filesystems. New filesystems built using newfs can be built in either UFS1 or UFS2 format using the -O option. In this commit UFS1 is the default format, so if you want to build UFS2 format filesystems, you must specify -O 2. This default will be changed to UFS2 when UFS2 proves itself to be stable. In this commit the boot code for reading UFS2 filesystems is not compiled (see /sys/boot/common/ufsread.c) as there is insufficient space in the boot block. Once the size of the boot block is increased, this code can be defined. Things to note: the definition of SBSIZE has changed to SBLOCKSIZE. The header file <ufs/ufs/dinode.h> must be included before <ufs/ffs/fs.h> so as to get the definitions of ufs2_daddr_t and ufs_lbn_t. Still TODO: Verify that the first level bootstraps work for all the architectures. Convert the utility ffsinfo to understand UFS2 and test growfs. Add support for the extended attribute storage. Update soft updates to ensure integrity of extended attribute storage. Switch the current extended attribute interfaces to use the extended attribute storage. Add the extent like functionality (framework is there, but is currently never used). Sponsored by: DARPA & NAI Labs. Reviewed by: Poul-Henning Kamp <phk@freebsd.org>
* o __P removal.imp2002-03-211-8/+5
| | | | | | o ansi function definitions. o main prototype removal o unifdef __STDC__
* Default to WARNS=2.obrien2001-12-041-0/+1
| | | | | | Binary builds that cannot handle this must explicitly set WARNS=0. Reviewed by: mike
* - Backout botched attempt to introduce MANSECT feature.ru2001-03-261-0/+1
| | | | - MAN[1-9] -> MAN.
* Set the default manual section for sbin/ to 8.ru2001-03-201-1/+1
|
* Prepare for mdoc(7)NG.ru2000-12-181-0/+1
|
* mdoc(7) police: use the new features of the Nm macro.ru2000-11-201-1/+1
|
* Avoid use of direct troff requests in mdoc(7) manual pages.ru2000-11-101-1/+2
|
* Remove unused include.asmodai2000-05-011-1/+0
|
* Fix various man pages to stop abusing the .Bx macro to generatempp2000-01-231-1/+1
| | | | | the strings "FreeBSD" and "NetBSD". Use the .Fx or .Nx macro instead.
* $Id$ -> $FreeBSD$peter1999-08-282-2/+2
|
* Do not dot terminate SEE ALSO list. Add rcsid, remove unused #includes. Err(3)charnier1998-06-302-40/+38
| | | | messages should start with a lowercase letter.
* .Sh AUTHOR -> .Sh AUTHORS. Use .An/.Aq.charnier1998-03-191-6/+4
|
* Typo fix.max1997-06-161-2/+2
| | | | | PR: 3868 Submitted by: Kazuo Horikawa <k-horik@yk.rim.or.jp>
* Remove srandomdev fallbackache1997-06-141-2/+1
|
* Add Id. Staticize usage function. Typo in usage string.charnier1997-06-112-3/+4
|
* Update HISTORY to reflect that this will first appear in 2.2.5.mpp1997-03-271-1/+1
|
* Typo fix (now how did that one get by me :-).mpp1997-03-271-1/+1
| | | | Submitted by: Philippe Charnier
* Get rid of __progname. I thought I already did that...guido1997-03-261-4/+2
|
* Typo police. Also update HISTORY to reflect when this first appearedmpp1997-03-241-3/+6
| | | | in FreeBSD.
* Include missing <time.h>ache1997-03-241-0/+4
| | | | | Add missing RNG initialization Use srandomdev() for RNG initialization
* Changed MAN to MAN8 so that this builds.bde1997-03-241-1/+1
|
* Add generation number randomization. Newly created filesystems wil nowguido1997-03-233-0/+409
automatically have random generation numbers. The kenel way of handling those also changed. Further it is advised to run fsirand on all your nfs exported filesystems. the code is mostly copied from OpenBSD, with the randomization chanegd to use /dev/urandom Reviewed by: Garrett Obtained from: OpenBSD
OpenPOWER on IntegriCloud