|
|
|
In this document are used a number of conventions to make it clear to readers what are commands, what are files, where the commands are ran and so on. When following the conventions below, readers show be able to better understand and follow the examples.
|
|
|
|
Commands, commands outputs, file contents, file names and paths in general are configured to use a mono font with size 9 to differentiate them from the rest of the text.
|
|
|
|
|
|
|
|
[remoteos][command] – commands under this section must be ran in the remote boot server, in this document, also called, “remoteos”.
|
|
|
|
|
|
|
|
[chroot][command] – commands under this section must be ran in the chroot environment, therefore, chroot command must be ran before the commands under this section be executed, as shown:
|
|
|
|
|
|
|
|
[remoteos][command]
|
|
|
|
root@debian:~# chroot /opt/ltsp/i386
|
|
|
|
|
|
|
|
[command output] – lines under this sections are the output of the command right above it.
|
|
|
|
|
|
|
|
[whole][file content][file name] – file contents when show in its integrity will be displayed under this section.
|
|
|
|
|
|
|
|
[partial][file content][file name] – file content under this section are only a part of the file and therefore it doesn’t represent the file as a whole. Readers should pay attention to it to not to break the services configuration. Usually content under it, starts, end and might have in between the lines the “...” mark, without the double quotes. That mark represent contents that aren’t visible.
|
|
|
|
|
|
|
|
To edit files sometimes I use vi and other times I use nano, as more convenient, you can use any text editor of your choice. |
|
|
|
\ No newline at end of file |
