This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | Next revision Both sides next revision | ||
|
openos [2016/06/20 06:07] payonel |
openos [2016/06/20 07:11] payonel [Install Tool] |
||
|---|---|---|---|
| Line 56: | Line 56: | ||
| ------------ | ------------ | ||
| - | A various places in the documentation we refer to running a command in shell called `install`. This is referring to a versatile tool that comes as part of the OpenOS software package and installation. | + | In various places in the documentation we refer to running a command in shell called `install`. This is referring to a versatile tool that comes as part of the OpenOS software package and installation. |
| + | |||
| + | To understand more about command line options for `install`, it is recommended to read its man pages by running `man install`, or by reading the man page online [[https://raw.githubusercontent.com/MightyPirates/OpenComputers/master-MC1.7.10/src/main/resources/assets/opencomputers/loot/openos/usr/man/install|here]]. | ||
| + | |||
| + | `install` takes the following actions | ||
| + | |||
| + | - Step One: Scan for Software to Install | ||
| + | |||
| + | First it scans for candidate source filesystems. These are filesystems, such as [[:item:loot disks|loot disks]], that can be used as a software package for installation. If more than one candidate source filesystem is found, it prompts the user, asking | ||
| + | |||
| + | `What do you want to install?` | ||
| + | |||
| + | Followed by a list of disks it found that can be installed. | ||
| + | |||
| + | - Step Two: Scan for Hard Drives | ||
| + | |||
| + | The next step is a scan for candidate target filesystems. These are filesystems, such as hard drives, that can be the target of an install. In the example of installing OpenOS from a loot disk to the hard drive, the hard drive is the target filesystem. Like candidate sources, if `install` finds multiple candidate targets, it asks the user to select one: | ||
| + | |||
| + | `Where do you want to install to?` | ||
| + | |||
| + | Followed by a list of disks it found that can be installed **to**. | ||
| + | |||
| + | - Step Three: Installation | ||
| + | |||
| + | Before continuing with the install, the user is asked for confirmation to install | ||
| + | |||
| + | `Install OpenOS to /mnt/e03/? [Y/n]` | ||
| + | |||
| + | Confirming this step will copy the files from the (e.g.) loot disk to the target filesystem. Software installs may have an optional `.prop` file which can tell `install` whether or not to set the default filesystem the computer should boot to, what label if any to set, and whether the system should reboot when installation is complete. | ||
| + | There is also the option for software disks to provide a fully custom install experience by creating an `.install` file at the root of the disk's filesystem. After confirming the source and target, `install` will invoke `.install` if it exists in the source filesystem. | ||
| + | |||
| + | - Optional Arguments | ||
| + | |||
| + | It is recommend to review the `install` man page for greater details and a full list of supported arguments. But I considered it interesting to mention here that the label of the loot disk can be used as a command line argument for install -- which will refine the candidate search to disks matching that label. | ||
| + | |||
| + | `install openos` | ||
| + | |||
| + | Note that the argument is case insensitive. In a scenario where there would have been multiple software disks available to install, specifying the label in this manner could allow `install` to reduce the candidate selection without prompting the user. | ||
| + | |||
| Command Line Interface | Command Line Interface | ||