summaryrefslogtreecommitdiffstats
path: root/sbin/fsck/fsutil.c
Commit message (Collapse)AuthorAgeFilesLines
* sbin/fsck: s/perror/perr/ to avoid shadowinguqs2012-10-211-16/+17
| | | | | | | | | - rename some other vars too - merge NetBSD license changes Obtained from: NetBSD PR: bin/139802 Reviewed by: ed
* Remove advertising clause from University of California Regent's license,markm2004-04-091-4/+0
| | | | | | per letter dated July 22, 1999. Approved by: core, imp
* Garbage-collected hotroot, rawname() and unrawname() again. Thesebde2003-12-271-38/+0
| | | | | | became garbage when block devices were axed and were removed a few months later, but they came back (with hotroot renamed to hot + hotroot()) when the NetBSD fsck was mismerged.
* fsck_msdosfs/main.c:bde2003-12-271-12/+0
| | | | | | | | | | | | - Don't use errexit() to (mis)implement usage(). Using errexit() just gave the bogus exit code 8. - Fixed 3 other style bugs in usage(). fsck/fsutil.[ch]: - Garbage-collected errexit(). It is essentially just one of NetBSD's fsck_ext2fs error printing functions, but we don't have fsck_ext2fs and the function is unsuitable for use there too (since pfatal() is also used and it printf to a different stream).
* Replace __progname with the functionally identical but moremarkm2002-03-241-14/+11
| | | | acceptable (documented) getprogname(3).
* o __P removedimp2002-03-201-138/+14
| | | | | | | o ansi function prototypes o unifdef -D__STDC__ o __dead2 on usage prototype o remove now-bogus main prototype
* Silence non-constant format string warnings by marking functionskris2001-08-191-1/+1
| | | | | | | as __printflike()/__printf0like(), adding const, or adding missing "%s" format strings, as appropriate. MFC after: 2 weeks
* Add support for running foreground (-F) and background (-B) checks.mckusick2001-04-251-1/+44
| | | | | | | | | | | | | | | | | | | | | | | | | | Traditionally, fsck is invoked before the filesystems are mounted and all checks are done to completion at that time. If background checking is available, fsck is invoked twice. It is first invoked at the traditional time, before the filesystems are mounted, with the -F flag to do checking on all the filesystems that cannot do background checking. It is then invoked a second time, after the system has completed going multiuser, with the -B flag to do checking on all the filesystems that can do background checking. Unlike the foreground checking, the background checking is started asynchonously so that other system activity can proceed even on the filesystems that are being checked. At the moment, only the fast filesystem supports background checking. To be able to do background checking, a filesystem must have been running with soft updates, not have been marked as needing a foreground check, and be mounted and writable when the background check is to be done (i.e., not listed as `noauto' in /etc/fstab). These changes are the final piece needed to support background filesystem checking. They will not have any effect until you update your /etc/rc to invoke fsck in its new mode of operation. I am still playing around with exactly what those changes should be and should be committing them later this week.
* Reviewed by: rwatson, bpadrian2000-10-091-0/+363
Approved by: rwatson Obtained from: NetBSD source tree Second part of the fsck wrappers commit. This commit enables the new fsck code (removing the fsck/* code and replacing it with the netbsd fsck wrapper code), and enabling some FFS-based utilities to compile. Details: * quotacheck, fsdb required modification to use the fsck_ffs/ code rather than fsck/ . This might change later since quotacheck requires preen.c which should exist in fsck/ rather than fsck_ffs/ * src/Makefile has fsck_ffs added to it so it it built as part of the tree now * share/doc/smm/03.fsck/ uses the SMM.doc/ stuff from fsck_ffs, not fsck. I've tested this, and it shouldn't require any changes on your machine. The fsck wrapper reads /etc/fsck and is command-line-compatible enough to not require rc changes (well, most changes unless you want to do anything nifty by specifying the fs types explicityly, read the man page if you want further details on what it can do.) This now allows us to support multiple filesystem types during bootup.
OpenPOWER on IntegriCloud