q2K BHP
Black History Portal
THE BHP WIRE —
HIDDEN TRUTHS
What's New!
THE JOURNEY THROUGH TIME

Explore Black History

Explore the people, places, events, achievements, struggles and stories that shaped our journey.

✊🏾

Civil Rights

Movements, leaders, victories and the continuing fight for equality.

⚙️

Black Inventors

Innovation, patents, science, technology and world-changing contributions.

🏆

Sports

Pioneers, champions, Negro Leagues, records, activism and excellence.

♟️

People

Meet the people whose lives, choices and achievements shaped the journey.

📍

Places

Black towns, communities, institutions and places where history happened.

📜

Events

Moments that changed communities, movements, institutions and the nation.

Enter a person, place, event, or topic.
MY'STORY

The MOVE Fire

This is a personal recollection on the Move fire on May 13, 1985 Philadelphia police fired thousands of rounds at the MOVE house, city officials approved dropping an explosive device on the roof, the resulting fire was allowed to burn, 11 people—including five children—died, and 61 homes were destroyed. Philadelphia City Council later called it a “brutal attack carried out by the City of Philadelphia on its own citizens” and acknowledged that no individual faced criminal consequences for the bombing. One timeline correction worth preserving for the BHP record: the major previous MOVE-police confrontation was August 8, 1978, about seven years before the bombing, not a year or two earlier. Officer James Ramp was killed, other police and firefighters were wounded, nine MOVE members were later convicted, and television cameras recorded police beating Delbert Africa during his arrest. The 1985 MOVE Commission later specifically criticized city planners for failing to adequately use lessons from that 1978 confrontation. And that actually strengthens the point you’re making: 1985 did not happen without precedent or institutional memory. There had already been a deadly confrontation with MOVE, years of conflict, negotiations and police involvement before Osage Avenue.

MORE →
BLACK FACTS
The Truths They Never Taught You...

Katherine Johnson — Mathematics to the Moon

Katherine Johnson’s mathematical calculations helped guide some of America’s most important early space missions while she confronted the racial and gender barriers faced by Black women in twentieth-century America.

MORE →
BHP gathered finds from its connected research sources. Showing the 4 strongest Black History matches.
← BACK TO RESULTS
Wikipedia

Transaction-Safe FAT File System

Transaction-Safe FAT File System (TFAT) and Transaction-Safe Extended FAT File System (TexFAT) refer to two file systems used in Microsoft products to provide transaction-safety for data stored on a disk. The goal is to reduce the risk of data loss in cases of power loss or unexpected removal of the drive. The latter problem has become more common with the spread of USB drives.

TFAT

[edit]

The Transaction-Safe FAT File System (TFAT) of the TFAT12, TFAT16 and TFAT32 file systems is a driver layer modification to the original FAT file systems FAT12, FAT16 and FAT32 maintaining two copies (FAT 0 and FAT 1) of the file allocation table instead of two identical ones. While performing a drive operation, changes would be made to FAT 1. When the operation is complete, the FAT 1 table would be copied to FAT 0, updating the stable view of the file system.[1]

TexFAT

[edit]

The Transaction-Safe Extended FAT File System (TexFAT), TexFAT provides similar functionality to TFAT using the exFAT file system as the base file system instead of FAT. Introduced with Windows Embedded CE 6.0, it is sometimes referred to as TFAT as well, which can lead to confusion with the original TFAT described above.[2]

The use of exFAT as the underlying file system allows for larger files and larger partitions. TexFAT requires a hardware-specific driver designed for the type of media on which the TexFAT volume resides.[2] TexFAT is not supported by desktop/server versions of Windows.

Limitations

[edit]

Due to the lack of support in desktop operating systems, neither TFAT nor TexFAT are recommended for removable media. While the desktop OS could still read the drive, it could not use the transaction-safe features, so unexpected removal or a power outage could lead to data loss. In addition, directories created under the desktop OS may not be transaction-safe even if the drive is later attached to a TFAT/TexFAT aware operating system.[1]

See also

[edit]

References

[edit]
  1. ^ a b "TFAT Overview". microsoft.com. Microsoft Developer Network. November 17, 2015. Retrieved December 5, 2019.
  2. ^ a b "Transaction-Safe Extended FAT File System". microsoft.com. Microsoft Developer Network. March 18, 2010. Retrieved December 5, 2019.

Further reading

[edit]
  • Munegowda, Keshava; Raju, G.T.; Raju, Veera Manikandan; Manjunath, T.N. (December 2014). Design Methodologies of Transaction-Safe Cluster Allocations in TFAT File System for Embedded Storage Devices. 2014 International Conference on Information Technology. IEEE. doi:10.1109/ICIT.2014.22.
  • Munegowda, Keshava; Raju, G.T.; Raju, Veera Manikandan; Manjunath, T.N. (December 11, 2014). Characterization of Transaction-Safe Cluster Allocation Strategies of TexFAT File System for Embedded Storage Devices. Computational Intelligence in Data Mining. doi:10.1007/978-81-322-2205-7_47.

Source: Wikipedia. Article content is retrieved live through the MediaWiki API.

No preview image
Wikipedia

Transaction-Safe FAT File System

Transaction-Safe FAT File System (TFAT) and Transaction-Safe Extended FAT File System (TexFAT) refer to two file systems used in Microsoft products to provide transaction-safety for data stored on a disk. The goal is to reduce the risk of data loss in cases of power loss or unexpected removal of the drive. The latter problem has become more common with the spread of USB drives.

MORE →
No preview image
Wikipedia

NetWare File System

In computing, the NetWare File System (NWFS) was a file system based on a heavily optimized, journal-based FAT file system. It was used in the Novell NetWare network operating system. It was the only file system for all volumes in NetWare versions 2.x, 3.x and 4.x, and the default and only file system for the SYS: volume continuing through version 5.x. Novell developed two varieties of NWFS: 16-bit NWFS 286, used in NetWare 2.x 32-bit NWFS 386, used in NetWare 3.x through NetWare 6.x. In NetWare 5 and above, Novell Storage Services (NSS, released in 1998), superseded the NWFS format. The NWFS on-disk format was never publicly released by Novell, but it was released by former Novell engineers as an open source project on Windows, Linux, and DOS in 2000. The project contains a complete rewrite of the NetWare File System, publishes all of the file system internals, and is hosted on GitHub and GitLab. The published specifications for 32-bit NWFS are: Maximum file size: 4 GB Maximum volume size: 1 TB Maximum files per volume: 2 million when using a single name space. Maximum files per server: 16 million Maximum directory entries: 16 million Maximum volumes per server: 64 Maximum volumes per partition: 8 Maximum open files per server: 100,000 Maximum directory tree depth: 100 levels Characters used: ASCII double-byte Maximum extended attributes: 512 Maximum data streams: 10 Support for different name spaces: Microsoft Windows Long names (a.k.a. OS/2 namespace), Unix, Apple Macintosh Support for restoring deleted files (salvage) Support for journaling (Novell Transaction Tracking System a.k.a. TTS) Support for block suballocation, starting in NetWare 4.x For larger files, the file system utilized a performance feature named Turbo FAT. Transparent file compression was also supported, although this had a significant impact on the performance of file serving. Every name space requires its own separate directory entry for each file. While the maximum number of directory entries is 16,000,000, two resident name spaces would reduce the usable maximum number of directory entries to 8,000,000, and three to 5,333,333. 16-bit NWFS could handle volumes of up to 256 MB. However, its only name-space support was a dedicated API to handle Macintosh clients. The Netware File System supported native RAID 0 and RAID 1 capabilities long before RAID systems came into use on personal computers. Disk mirroring and duplexing were basic features of the file system, and NWFS also supported multi-segmented volumes, and round-robin reads, much like RAID 0 and RAID 1 does today.

MORE →
No preview image
Wikipedia

File Allocation Table

File Allocation Table (FAT) is a file system developed for personal computers and was the default file system for the DOS and Windows 9x operating systems. Originally developed in 1977 for use on floppy disks, it was adapted for use on hard disks and other devices. The increase in disk drive capacity over time drove modifications to the design that resulted in new versions: FAT12, FAT16, FAT32, and exFAT. FAT was replaced with NTFS as the default file system on Microsoft operating systems starting with Windows XP. Nevertheless, FAT continues to be commonly used on relatively small capacity solid-state storage technologies such as USB flash drives, SD cards, MultiMediaCards (MMC) and eMMC because of its compatibility across operating systems and embedded systems, and ease of implementation.

MORE →
No preview image
Wikipedia

Fat binary

A fat binary (or multiarchitecture binary) is a computer executable program or library which has been expanded (or "fattened") with code native to multiple instruction sets which can consequently be run on multiple processor types. This results in a file larger than a normal one-architecture binary file, thus the name. The usual method of implementation is to include a version of the machine code for each instruction set, preceded by a single entry point with code compatible with all operating systems, which executes a jump to the appropriate section. Alternative implementations store different executables in different forks, each with its own entry point that is directly used by the operating system. The use of fat binaries is not common in operating system software, except on NeXTSTEP and NeXTSTEP-derived Apple operating systems such as macOS and iOS (see below); there are several alternatives to solve the same problem, such as the use of an installer program to choose an architecture-specific binary at install time (such as with Android multiple APKs), selecting an architecture-specific binary at runtime (such as with Plan 9's union directories and GNUstep's fat bundles), distributing software in source code form and compiling it in-place, or the use of a virtual machine (such as with Java) and just-in-time compilation.

MORE →
TOPIC OF THE DAY

Greenwood / Black Wall Street

Before the 1921 destruction of Tulsa’s Greenwood District, Black residents had created a remarkable center of business and community life. The district included stores, professional offices, entertainment venues and homes owned by Black citizens. Understanding Greenwood means learning what was built—not only what was burned.

MORE →
TRIVIA QUESTION OF THE DAY

Who became the first Black woman to travel into space?

Mae Jemison, aboard Space Shuttle Endeavour in 1992.