| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
| |
superblock.
Submitted by: kkenn
Can't use it verbatim, at least I hate to, as the ", skipped" bit doesn't
make much sense in a library, to me.
|
|
|
|
| |
along with the errno, if one is set.
|
|
|
|
| |
Reminded by: Rachel Hestilow <hestilow@ximian.com>
|
|
|
|
|
|
|
| |
(unless someone tries to use libufs support functions without using
_fillout or _ctor to construct a uufsd.)
Obtained from: jmallett_libufs Perforce branch.
|
|
|
|
| |
inodes in our inoblock (disk->d_ino{min,max}) appropriately.
|
|
|
|
| |
Reviewed by: jmallett
|
|
|
|
| |
turn on tracing.
|
|
|
|
|
|
| |
does not know what sort of UFS filesystem this is.
Add some DEBUG(NULL)'s to function entry points.
|
|
the build. It is here to compartmentalise functionality currently duplicated
in many notable programs in the base system. It currently handles block
reads and writes, as well as reading and writing of the filesystem superblock,
and the reading/lookup of inode data. It supports both UFS and UFS2. I
will be maintaining it, and porting programs to use it, however for now, it
is simply being built as part of world.
|