A/UX® Programmer's Reference Sections

zb(4) bzb(4)
3
tion of autorecovery. The swap file system is an example
of a critical file system, and therefore, all swap file system
Block Zero Blocks should have this field sel
If this bit is on, no attempt will be made to create or use a bad
block file for bad block handling.
bzb rsrvd
This field contains bits reserved for later use.
bzb filler
This field is reserved for later use.
bzb tmade
This field contains a time-stamp which indicates when the file
system located on the corresponding partition was created.
This field's value is the standard NUX time-stamp value (as
returned from time(2». The value of this field can be set
and retrieved through calls to ioctl(2). See gd(7) for more
details.
bzb tmount
This field indicates the date the last mount(3) (or equivalent
routine) call was made on the file system located on the
corresponding partition. In some cases, such as on a root file
system during startup, this field should be set to the
mount(3) equivalent date. This field is not updated if a file
system is mounted read-only. The value of this field can be
set and retrieved through calls to ioctl(2). See gd(7) for
more details.
bzb tumount
This field indicates the date the last umount(3) (or
equivalent routine) call was made on the file system located
on the corresponding partition. In some cases, such as root
file system during shutdown, this field should be set to the
umount(3) equivalent date. This field is not updated if an
file system was mounted read-only. The value of this field
can be set and retrieved through calls to ioctl(2). See
gd(7) for more details.
bzb abm
This field is the alternate block map structure for the associated
partition. See altblk(4) for more details about this
structure. The value of this field can be retrieved through
calls to ioctl(2). See gd(7) for more details.
February, 1990
Revision C