Mirror of git://git.busybox.net/busybox with our patches on top
Source
static struct fs_info *create_fs_device(const char *device, const char *mntpnt,
/* vi: set sw=4 ts=4: */
/*
* fsck --- A generic, parallelizing front-end for the fsck program.
* It will automatically try to run fsck programs in parallel if the
* devices are on separate spindles. It is based on the same ideas as
* the generic front end for fsck by David Engel and Fred van Kempen,
* but it has been completely rewritten from scratch to support
* parallel execution.
*
* Written by Theodore Ts'o, <tytso@mit.edu>
*
* Miquel van Smoorenburg (miquels@drinkel.ow.org) 20-Oct-1994:
* o Changed -t fstype to behave like with mount when -A (all file
* systems) or -M (like mount) is specified.
* o fsck looks if it can find the fsck.type program to decide
* if it should ignore the fs type. This way more fsck programs
* can be added without changing this front-end.
* o -R flag skip root file system.
*
* Copyright (C) 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2000,
* 2001, 2002, 2003, 2004, 2005 by Theodore Ts'o.
*
* %Begin-Header%
* This file may be redistributed under the terms of the GNU Public
* License.
* %End-Header%
*/
/* All filesystem specific hooks have been removed.
* If filesystem cannot be determined, we will execute
* "fsck.auto". Currently this also happens if you specify
* UUID=xxx or LABEL=xxx as an object to check.
* Detection code for that is also probably has to be in fsck.auto.
*
* In other words, this is _really_ is just a driver program which
* spawns actual fsck.something for each filesystem to check.
* It doesn't guess filesystem types from on-disk format.
*/
/* "progress indicator" code is somewhat buggy and ext[23] specific.
* We should be filesystem agnostic. IOW: there should be a well-defined
* API for fsck.something, NOT ad-hoc hacks in generic fsck. */
/* Aborted with a signal or ^C */
/*
* Internal structure for mount table entries.
*/
struct fs_info {
struct fs_info *next;
char *device;
char *mountpt;
char *type;