deejoe
/
bugs
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

I misunderstood the instructions

This commit is contained in:
Joe 2018-01-18 08:54:39 -05:00
parent a45ea4c08d
commit d46edcaadf
1 changed files with 14 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

26
linode-custom-install.md
View File

@ -1,21 +1,23 @@
OK, backing out of earlier suggestion, which was based on a misunderstanding
of the document in question.
In
At this point, I think I'll suggest changing the language so that the two
profiles do not have the same names as the two disk images.
https://linode.com/docs/tools-reference/custom-kernels-distros/install-a-custom-distribution-on-a-linode/#download-and-install-image
**Installation** profile, but **installer** image.
a miracle is assumed to occur between step 2 and step 3.
**Production** profile, but **target** image.
That is to say, the installation image is downloaded to the disk image
associated with the Installer profile in step 2, but in step 3 the disk
image associated with the Boot profile is assumed to be available to the
Installer on reboot of the Installer.
So, in Rescue Mode, one writes, eg, a GNU/Linux distribution's
download ISO file to the **installer** disk image.
Instructions should be added, possibly including screenshots, showing how
the target disk image from the Boot profile becomes associated with the
Installer profile before one reboots into the Installer.
When booted into the **Installation** profile, one boots from the
**installer** image, but writes to the **target** image.
Whether one has to change any associations between disk image files and
profiles after the Installation is not clear to this writer.
In the **Production** profile, one boots from the **target** image, and the
**installer** image is dormant.
The process optionally can stop here, or continue into the improvements
suggested by the rest of the document.