[#fany]: f*

Many abbreviations that start with f may have the f mean “file”. Examples (sorted from more common abbreviations to less common) may include: fstream, fspec, fsys.

[#flpydskd]: floppy disk drive (“FDD”)

A drive that can read a “floppy disk”. Some ancient disks were larger (e.g., an 8 inch disk), although more common disk sizes included 5.25 inch disks that stored 360K, 720K, or 1.2MB, or 3.5 inch disks that stored 720K or 1.44MB. At leat, those were the most well-known capacities, although there were others (the 3.5 inch disks actually stored 2.0MB, but then lost some amounts due to formatting), and the amount of 1.44MB was even a technically inaccurate measurement, as was the size of 3.5 inches. Those disks could actually hold more data, swuch as 32MB, when used with the right equipment. This is discussed further by the section on floppy disks. There were larger formats (a 4.0 disk that was referred to as 2.88MB when formatted, and floptical formats).

Back during the days when floppy drives were used most widely, the abbreviation was commonly used as an alternative to HDD (hard disk drive), or ODD (optical disc drive). As floppy disk usage became less common, the phrases of ODD and SDD became used more frequently than FDD.

[#fspecabb]: filespec

The term “filespec” is a rather common abbreviation for file specification.

[#filespec]: filespec (“file specification”)

A filespec refers to a precise filename, or the name of a directory (a.k.a. folder), or any more generalized specification that involves using wildcards.

The phrase “file specification” is rather commonly abbreviated to filespec, which is semi-pronouncable. Another abbreviation which may be found (typically typed out, not verbally stated) is fspec.

[#filesys]: filesystem

The term “filesystem” is sometimes written out as one word, and sometimes as multiple words (“file system”).

An entirely valid use of the term is to refer to a method that is used to keep track of files and similar “objects” on the filesystem (such as directories, and perhaps pointers to devices, and maybe a volume label). The term is often also used to describe a volume.

See the section about filesystems, and similar terms such as volume, partition (specifically a “disk partition”), and “slice”.

[#fire]: fire
  • Literally: a process where matter is getting burned. A saying goes as follows: “Where there's smoke, there's fire!” (Perhaps some more related information is at disaster recovery.)
  • Literally: terminating employment.
  • Figuratively: any problem which, like an actual fire, is likely to keep growing until efforts are made to stop it. The problem itself may get bigger, and the problem may cause stress in other areas (such as creating new, usually related, fires). This is a general business term, not specific to IT, but a term that many people don't understand. (They may understand that the term refers to “problems”, not understanding the reference to problems that grow.) Members of management will often have the task of “putting out fires”.
[#fork]:
  • A software project which was created as an alternative option of another software project. The newer software product is often created by different people than those who have worked on the original software product. Famous examples include OpenBSD and FreeBSD which split off of NetBSD.
  • A data stream in a file which is not the only data stream in the file. With NTFS, all forks except for the first are generally called an “alternate data stream”.
  • A spork with longer seperations between the teeth.
[#format]: format
noun: format
A method of how data is routinely laid out. There are file formats that define what patterns exist in certain types of files, as well as filesystem types which could be considered to be the format adhered to when working with a volume.
verb: format
Formatting is an action that can be applied to a data storage device. Formatting creates a volume, which is a section of disk that is laid out according to a specific set of guidelines/rules. This set of rules may itself be called a “format”, although
[#fspecabr]: fspec

Like filespec, this may just be an abbreviation for file specification.

[#fsys]: fsys

Presumably an abbreviation for filesystem

[#fun]: FUN

What is fun? That depends on who you ask.

The bullet point and subsequent section about “FUN” from OpenBSD Journal (Undeadly.org) article by jcr (“J.C. Roberts”) about preparing portable systems (part 1) (which, naturally, is the predecessor to subsequent part(s)) provides an interesting definition: dealing with non-working hardware. To quote the exact text:

“If I got a new system and all the hardware "Just Works" with OpenBSD, where's the fun in that? Many people enjoy the challenge of getting stuff working in OpenBSD, but of course, you might have a different definition of "fun" and that's your loss. ;)”

(The efforts of this developer, and similar people, end up turning non-working types of hardware into types of hardware that work well, both for those developers and for other people too. Their fondness for such challenges reap rewards for more people than just themselves.)