r00t2/bdisk
1
0
Fork 0
Code Issues Pull Requests Projects Releases Activity

more documentation...

Browse Source
This commit is contained in:
brent s.
2016-12-27 15:25:56 -05:00
parent 2094cf4f1f
commit d0d8105db3
14 changed files with 184 additions and 45 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/manual/HEAD.adoc
View File

@@ -21,7 +21,7 @@ See CREDITS in the project source for a list of thanks.
[preface]
= Preface
=== About the Author
I (Brent Saner) am a GNU/Linux Systems/Network Administrator/Engineer- I wear a lot of hats. I have a lot of side projects to keep me busy when I’m not working at _${dayjob}_, mostly to assist in other side projects and become more efficient and proficient at those tasks. “Shaving the yak,” footnote:[See http://catb.org/jargon/html/Y/yak-shaving.html] indeed.
I am a GNU/Linux Systems/Network Administrator/Engineer- I wear a lot of hats. I have a lot of side projects to keep me busy when I’m not working at _${dayjob}_, mostly to assist in other side projects and become more efficient and proficient at those tasks. “Shaving the yak,” footnote:[See http://catb.org/jargon/html/Y/yak-shaving.html] indeed.
A lot of research went into how low-level boot operations take place when writing BDisk, both in BIOS and UEFI footnote:[*Unified Extensible Firmware Interface.* UEFI is not BIOS, and BIOS is not UEFI.] (and corresponding concepts such as Secureboot, etc.) which is no easy task to understand and very commonly misunderstood. (For instance, a common misconception is that UEFI necessarily implies Secureboot. This is quite far from the truth and UEFI by itself is quite a useful replacement for BIOS). I invite you to do research into the specifications yourself; it's rather fascinating.