<p dir="ltr"><br>
On Dec 27, 2013 5:49 PM, "bruce" <<a href="mailto:badouglas@gmail.com">badouglas@gmail.com</a>> wrote:<br>
><br>
> Pete.<br>
><br>
> The 1st OS will be the os that gets run, it's the "master".. However<br>
> if I detect that it's hacked, I want to be able to reinstall the OS.<br>
><br>
> Noramlly, you'd do that with a cd, and do it manually, but if you<br>
> don't have access to the box, then what?<br>
><br>
> My approach is to have a 2nd minimal system/OS that has the only<br>
> function to invoke a complete/fresh netinstall to restore/refresh the<br>
> OS on the 1st system.<br>
></p>
<p dir="ltr">Yes, but how do you plan to actually do it? Do you intend to write your own installation program from scratch? What makes a minimal installation capable of performing a net install?</p>
<p dir="ltr">> This allows the 1st OS/system to be completely restored, wiping out<br>
> any remnants of the hacked process.<br>
><br>
> At the same time, the master/2nd OS will periodically update/restore<br>
> the minimal/1st OS by the 2nd OS/system. This process allows the<br>
> system to be able to be refreshed as required, with a clean OS..<br>
><br>
> If you have a better approach, I'm open for discussion.<br>
></p>
<p dir="ltr">I do, but you don't seem interested. If you want to perform an installation, boot the installer. If you want to install using an alternative boot option instead of with removable media, do a medialess installation. There are instructions and examples in the installation guide. </p>
<p dir="ltr">--Pete<br>
</p>