It saves time to write a Frequently Given Answer just once, and then just post a reference to it every time that a relevant question is asked, rather than soak up large amounts of bandwidth posting the same answer longhand time and again.
The common practice is to refer questioners directly to one or more specific answers, which will themsleves cross-reference the other answers that they relate to, if any. But there are people out there who are terminally inquisitive. To satisfy them, here is a list of all of the FGAs that you can find here, broken down by category.
Feel free to refer people to any of these answers yourself if you need to.
Sometimes, it's time to invoke Dukhat.
How to wrap commands in scripts in order to add default options and arguments to them.
How to perform common tasks using JP Software's command interpreters.
A description of the PC/AT boot process.
A description of the boot process of DOS-Windows.
A description of the boot process of Windows NT version 6.
A description of the boot process on EFI systems.
A description of the boot process on ARC systems.
A description of the shutdown process of Windows NT version 6.
The gen on emergency and rescue mode bootstrap.
Disc and volume size limits, with a focus on OS/2.
An explanation of fix terminology.
The gen on the CSRSS backspace bug in Windows NT 4/2000/XP.
The gen on the operating system nut metaphor.
How to deal with OS/2 applications that do not understand timezones.
The various daemons on the Hurd and what services they provide.
What Unicode CJKV character set rationalization is, and isn't.
Because of a defect in the C Standard void main() is illegal in C++ but legal in C.
Because of a defect in the C++ Standard it's not actually legal to use reinterpret_cast<> with pointers to
void in C++.
The thread safety problems of function scope static variables in many C++ implementations.
The gen on Metaware High C/C++'s iterator-driven
How one goes about capturing console I/O in Win32, at long last.
On Windows, do not put your DLLs in the System32 directory.
The gen on the UNIX Client-Server Program Interface.
The gen on the C and C++ language bindings to the DOS API.
How one goes about redirecting standard I/O from within a program.
In the C and C++ languages, variables cannot be used as functions.
Predefined macros in the C and C++ languages …
The gen on Tesco.NET.
Do not obscure your DNS data when asking for help. It's pointless and silly.
Avoid RFC 2317's classless "in-addr.arpa." delegation. Modern well designed DNS server softwares simply don't need it.
How one goes about updating a resolving proxy DNS server's list of root content DNS servers.
Remember to populate your "internal" DNS database with data after setting up "split horizon" DNS service.
A similar "Big Picture" for the ISC's BIND.
ISC's BIND understands bailiwick. It doesn't make full use of it, however.
nslookup is a seriously flawed tool. Don't use it.
The anti-UBM measures for SMTP-based Internet mail are fundamentally flawed. Use IM2000 Internet mail.
Do not send Microsoft Word documents to me. I cannot read them and I will simply delete your mail unread.
Use appropriate body part formats in your mail and news messages.
Add the Followup-To: header to your message if you think that replies should go to another newsgroup.
Read the References: header to find out what message is being replied to.
Always read the back messages when joining a new discussion forum.
legacy is not a pejorative. Do not use it as such.
The gen on Newtonmas.
Robert Pepper's Five Stages of Cerocers, preserved for posterity.
Robert Pepper's Advice for Ceroc novices, preserved for posterity.
My dance calendars.
The gen on Hush! here comes the Dream man..
© Copyright 2001–2004,2007,2010
Jonathan de Boyne Pollard.
"Moral" rights asserted.
Permission is hereby granted to copy and to distribute this web page in its original, unmodified form as long as its last modification datestamp is preserved.