before refactoring reference links

This commit is contained in:
brent s. 2016-12-26 10:04:41 -05:00
parent 856bea09a2
commit 0af57624fb
5 changed files with 6 additions and 5 deletions

View File

@ -7,6 +7,7 @@ v1.0, 2016-12
:sectlinks: :sectlinks:
:toc: preamble :toc: preamble
:toc2: left :toc2: left
:idprefix:
:sectnums: :sectnums:
:toclevels: 2 :toclevels: 2
// So there's currently a "bug" in that the TOC will display with continued numbering across parts. // So there's currently a "bug" in that the TOC will display with continued numbering across parts.

View File

@ -1,5 +1,5 @@
== Bug Reports/Feature Requests == Bug Reports/Feature Requests
NOTE: It is possible to submit a bug or feature request without registering in my bugtracker. One of my pet peeves is needing to create an account/register on a bugtracker simply to report a bug! The following links only require an email address to file a bug (which is necessary in case I need any further clarification from you or to keep you updated on the stats of the bug/feature request -- so please be sure to use a valid email address). NOTE: It is possible to submit a bug or feature request without registering in my bugtracker. One of my pet peeves is needing to create an account/register on a bugtracker simply to report a bug! The following links only require an email address to file a bug (which is necessary in case I need any further clarification from you or to keep you updated on the status of the bug/feature request -- so please be sure to use a valid email address).


=== Bugs === Bugs
If you encounter any bugs in *BDisk*, you can file a bug report https://bugs.square-r00t.net/index.php?do=newtask&project=2&task_type=1[here^]. If you encounter any bugs in *BDisk*, you can file a bug report https://bugs.square-r00t.net/index.php?do=newtask&project=2&task_type=1[here^].

View File

@ -2,7 +2,7 @@
NOTE: If you're specifying passwords, be sure to use a https://www.schneier.com/blog/archives/2014/03/choosing_secure_1.html[strong password^]! NOTE: If you're specifying passwords, be sure to use a https://www.schneier.com/blog/archives/2014/03/choosing_secure_1.html[strong password^]!


=== `build.ini` Password Value Examples === `build.ini` Password Value Examples
Passwords work a little interestingly in BDisk. These aspects all apply to both <<__code_root_password_code,the root password>> and <<__code_passwowrd_code,the user password>> (if you enable a regular user). Passwords work a little interestingly in BDisk. These aspects all apply to both <<__code_root_password_code,the root password>> and <<__code_password_code,the user password>> (if you enable a regular user).


CAUTION: DO *NOT* USE A PLAINTEXT PASSWORD IN THE `build.ini`! This is _by design_; plaintext passwords are much more insecure. If you use a plaintext password, it *will not work*. CAUTION: DO *NOT* USE A PLAINTEXT PASSWORD IN THE `build.ini`! This is _by design_; plaintext passwords are much more insecure. If you use a plaintext password, it *will not work*.



View File

@ -60,7 +60,7 @@ Assuming you saved BDisk Mini to your Desktop, you can do:


sudo dd if=~/Desktop/bdisk-mini.iso of=/dev/disk42 sudo dd if=~/Desktop/bdisk-mini.iso of=/dev/disk42


NOTE: the above command may prompt you for a password. This is the same password you use to log into your Mac (and unlock the screensaver, etc.). No characters will show up when you type (for security reasons, in case someone is behind you watching your screen) so it may take you a couple tries. NOTE: The above command may prompt you for a password. This is the same password you use to log into your Mac (and unlock the screensaver, etc.). No characters will show up when you type (for security reasons, in case someone is behind you watching your screen) so it may take you a couple tries.


This will run for a couple seconds. When it finishes, you should see something similar to (but not necessarily the same numbers as) this: This will run for a couple seconds. When it finishes, you should see something similar to (but not necessarily the same numbers as) this:


@ -113,7 +113,7 @@ Next, simply dd over the ISO file.


sudo dd if=~/Desktop/bdisk-mini.iso of=/dev/sdz sudo dd if=~/Desktop/bdisk-mini.iso of=/dev/sdz


NOTE: the above command may prompt you for a password. This is the same password you use to log in (and unlock the screensaver, etc.). No characters will show up when you type (for security reasons, in case someone is behind you watching your screen) so it may take you a couple tries. NOTE: The above command may prompt you for a password. This is the same password you use to log in (and unlock the screensaver, etc.). No characters will show up when you type (for security reasons, in case someone is behind you watching your screen) so it may take you a couple tries.


This will run for a couple seconds. When it finishes, you should see something similar to (but not necessarily the same numbers as) this: This will run for a couple seconds. When it finishes, you should see something similar to (but not necessarily the same numbers as) this:



View File

@ -196,7 +196,7 @@ What is the path to the tarball directory on the <<__code_mirror_code,`mirror`>>
. No whitespace . No whitespace


==== `mirrorfile` ==== `mirrorfile`
What is the filename for the tarball found in the path specified in <<__code_mirrorpath_code,`mirrorpath`>>? If left blank, we will use the sha1 <<__code_mirrorchksum_code,checksum>> file to try to guess the most recent file. What is the filename for the tarball found in the path specified in <<__code_mirrorpath_code,`mirrorpath`>> ? If left blank, we will use the sha1 <<__code_mirrorchksum_code,checksum>> file to try to guess the most recent file.


==== `mirrorchksum` ==== `mirrorchksum`
The path to a sha1 checksum file of the bootstrap tarball. The path to a sha1 checksum file of the bootstrap tarball.